Understanding nested prefabs

Version 1.0.0

A nested prefab occurrence can have an override owned by the prefab that contains it. That ownership is different from a change to the nested prefab asset itself.

Generate the examples using Tools > Saphing Studio > Prefab Provenance > Create Example Prefabs.

1. Open HardEncounter.prefab.

2. Select the second WideInteractable child, positioned at X = 2.

3. Choose BoxCollider and inspect m_Size.x.

4. Follow 6, 4, 2, 1 through HardEncounter, Encounter, WideInteractable and Interactable.

5. Compare the first child. It keeps 2, despite sharing the same name as the second occurrence.

The tool resolves prefab identity rather than assuming identically named objects are the same occurrence.

Select the inheritance row that owns the override. Source details identifies the context and editing scope. Open source opens the corresponding prefab and selects the object when its exact identity can be resolved.

An override in the containing prefab belongs to that nested occurrence. Editing the original nested asset has a different scope. Read the selected row before switching to the Inspector.

In the included Examples/LightingProvenance.unity scene, inspect DockingStation/AlertLamp and m_Intensity. The containing DockingStation prefab owns an override of 3, above the AlertLamp, WarmLamp and BaseLamp chain.

The warehouse environment shown on the product page illustrates the same workflow. Those marketing assets are separate from the included native examples.

See reading results for the state glossary and troubleshooting if a source is missing or unavailable.