Saving and Publishing

Editing changes nothing permanent until you save. This chapter explains what saving does and how your edits reach the live game.

What Save & Rebuild does

When you save, the editor takes all your changes — object positions, level structure, physics, assets, settings — and writes them back into the game, regenerating the playable version. The "rebuild" part means the actual game that players load is reconstructed to include your edits. Until you save, your changes exist only in the editor session.

This is comparable to building or cooking a project in an engine: you work on the project, then produce the final runnable version. In TupicGame this happens in one step when you save.

Making sure changes take effect

A few practical points:

• Save after meaningful changes, especially structural ones like adding or removing levels, so the game reflects the new state.
• After editing or regenerating assets, save and then reload the game to confirm the new versions appear, since saving is what locks in asset references.
• Use the Test tab and a quick Play after saving to verify everything works as expected.

From saved to published

Saving updates the game itself. Publishing — making the game live and available to play and share — is handled in the main TupicGame flow rather than the editor. The editor's job is to get the game exactly right; publishing then puts that finished game in front of players.

A safety habit

Because every save is recorded in the Versions tab, saving also creates restore points. Saving at good milestones gives you both an up-to-date game and a history you can roll back to — so save often, and save deliberately at points you'd want to return to.