Copyright © 2026 Unity Technologies
Thank you for reporting a bug to Unity. The source prefab doesn't contain the field at all — it was added to the script after the prefab was authored, so nothing was ever serialized for it. Both views therefore fall back to the C# initializer, just at different times: Isolation mode reads the source prefab and runs the current initializer, while the Project view shows the imported artifact, which captured the initializer values at import time. Changing only the default values doesn't change the script's serialized layout, so the prefab isn't reimported and the artifact keeps the older values. Workaround: save the prefab once after adding the field, so real values land in the file. From then on the file wins and initializer changes are ignored.
How to reproduce:
Actual result: The Inspector displays the old, “Min” and “Max” values when selecting the Prefab in the Project window, but displays the newly updated values when opening the Prefab in Isolation mode
Expected result: The Inspector values should remain consistent and match whether the Prefab is selected in the Project window or opened in Isolation mode
Reproducible with: 6000.0.0f1, 6000.0.83f1, 6000.3.23f1, 6000.6.0f1, 6000.7.0a6
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Note:
When testing across different Unity versions, you usually do not need to repeat all the steps. You can simply upgrade the existing project and start directly from Step 8
Issues you vote on will appear here