See Saved Changes in Unreal
Update an open View while Play is running and understand when setup must repeat.
- Connect Studio to your Unreal project and open a View in Play.
- Edit the View, one of its components, or its CSS.
- Save.
- Wait for Studio to finish rebuilding and sending the update.
The footer's status dot and Compiler daemon label change while your save is rebuilt and sent to the connected Editor. A green dot with ready means the previous update finished; watch this instead of guessing whether the save has reached Unreal yet.
Ordinary UI source edits do not require restarting Play. The previous working UI remains visible during the update. Check the status to distinguish a saved file from a package that has also reached Unreal.
If an update fails
Open Problems, click the reported location, correct it, and save again. A failed update keeps the previous working package active. Version or data-definition errors also need to be corrected before the new package can load.
When game data definitions change
Saving Store fields or actions rebuilds the package and can reload complete Views. Compatible game values are preserved. Studio manages definition versions when you save a changed definition.
In the current runtime, changing the loaded definitions clears Blueprint Store and action subscriptions. Restart Play after those changes to repeat your BeginPlay setup. Subscribe from the package-opening node's Completed output, as shown in the action tutorial.
This restart is for changed Store/action definitions, not ordinary visual saves.