Following prefab variants

Version 1.0.0

Trace a leaf property through a variant chain to find the nearest level that defines or overrides it. Inspect the source before changing values in Unity's Inspector.

Choose Tools > Saphing Studio > Prefab Provenance > Create Example Prefabs. The command creates a new folder under Assets/SaphingProvenanceExamples. Repeating it creates a separate folder and preserves existing assets. Your open scene is not changed.

1. Select BossInteractable.prefab in the generated folder.

2. Choose BoxCollider and inspect m_Size.x.

3. Read 3 in BossInteractable, 2 in WideInteractable and 1 in Interactable.

4. Select the WideInteractable row and inspect its source details.

5. Choose Open source if you want to inspect or edit that variant with Unity's native tools.

If the built-in Physics module is absent, the example uses Transform Scale X instead. Prefab Provenance itself does not require the Physics module.

Drag BossInteractable into a scene. Its Size X initially inherits from the prefab. In Unity's Inspector, change Size X to 7. The scene instance becomes the value source. Unity's Undo restores the edit and inheritance state.

These edits are made by Unity's Inspector, not by the Prefab Provenance window. Save or discard the test scene using Unity's normal workflow.

Edit a base when the change belongs to all objects that inherit that field. Edit a variant when it belongs to that variation. An existing override at a later level can stop inheritance of the changed value.

The displayed scope is descriptive. The tool does not scan the project to count every affected instance.

Scene overrides explains instance-specific changes. Nested prefabs covers ownership by a containing prefab.