Keep your creative choices and a way back
An experiment is easier to try when you know what was saved and how to go back. Your creative choices should be part of the project, not only part of a conversation.
In this guide
Practical guidance for creating, playing, and shaping games with the agent-native Dashpop Game Engine. Each game has its own creative controls, artwork, and source.
Know which change you are talking about
A control value, a source change, and a running game are related, but they are not the same thing. Read the result of a save or build rather than assuming the screen already shows every new edit.
Published controls bind to actual content. Accepted edits save the chosen values, and ordinary undo can restore a preceding accepted edit. Source rebuilds have a separate lifecycle; do not assume control undo reverses every possible source change.
Use undo to explore a decision
Try a shorter delay or a different atmosphere. Play the result. If the previous choice worked better, undo the accepted control edit and check the game again.
Tell your agent which choices to preserve during the next revision. Saved content gives that request a concrete starting point. A change that needs broader source work should still have a clearly stated boundary and a playable check.
Keep the project’s real source and content
Code, Assets, and the Editor show the source, artwork, and creative choices that make up your game. Keep those parts together when you make a copy or hand the project to another person.
Connect your preferred agent through MCP to work on that same project. A new agent can inspect the game and its saved choices before making a change, so you can continue with the decisions you have already made.
Before a handoff, record the source version, saved content, required assets, and the run you observed. A project copy is useful when the next person can understand what it contains and how it was tested.
Keep the Editor Handbook nearby as you work. Pick one change, test it, and keep what helps.