Understand the change behind the game
You do not need to read every file to make a good decision. Start with the behavior you care about, the change your agent made, and the result you can play.
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.
Use Code as a map
Open Code to inspect the project’s source. Ask your agent which files own the behavior you want to change. Content stores creative choices; source defines how the game behaves; assets give it visual and audio material.
For a lantern, find the input that requests lighting, the state that records it, and the feedback that tells the player it worked. Changing only the displayed counter will not repair the underlying interaction.
Tie an edit to a playable question
Ask for the changed files and the intended effect. A focused stopping adjustment should have a clear explanation. An unexpected artwork replacement or layout rewrite deserves a closer look.
Build the current source, then try the affected sequence. A completed build does not establish that the lantern can be reached or that the new timing feels right. Keep the last useful observations with the version that produced them.
See the operations your agent can use
Tools shows the selected game service’s actual operation catalog, input contracts, and returned results. It is useful for understanding what your agent can inspect or change. You do not need to run technical operations to use the game’s ordinary Editor controls.
When an operation fails, retain the error and reread the relevant content before another edit. A useful repair responds to the reported boundary or defect rather than assuming an earlier request succeeded.
Keep the Editor Handbook nearby as you work. Pick one change, test it, and keep what helps.