m_Modification in Prefabs: First signs of Nested / Inherited Prefabs? Or a bug?

Unity Engine
1

Hi,

I just updated to 5.1.1p3 (from 5.0.1f1) and changed a prefab in one of our projects. Then I saved and wanted to commit the change.

I found, that there where two differences to the original in the corresponding prefab yaml: Once the change in the property. But also a change in the “m_Modifications” - section, just as you are used to when changing scene prefabs.

Now that concerns me a bit. Either we see here the first sign of an attempt to have inherited prefabs, so that the prefab is tracking its list modifications along with the actual data. OR, its a bug. What is concerning are the implications to mergability of Prefabs. I expect that with 5.1.1p3 onwards, we will get a LOT more merge conflicts in these m_Modification parts. :frowning:

Anyone knows whats that supposed to be and whether its a bug worth reporting?

2

Any dev? Anyone?

3

I’ve been wondering this too, but have not been able to get a dev to respond. It currently seems like a bug, because it’s unnecessarily duplicating data in the root prefab.

4

Issue number is 711720, bug is still open with no response from anyone.

Said that, I think, I saw a tweet or blog somewhere from someone sometimes ago talking about this and that it will be fixed someday. Maybe.

5

Bump! This is causing dependency issues!