Astra + Godot: a first playable workflow

Start with a project that opens

Create or open a Godot project and run it before introducing AI changes. Record the engine version. If the starting project already fails, fix that first so you can tell what the next change did.

Godot’s official first 2D game guide is a useful foundation for understanding scenes and scripts. You do not need to memorize the engine, but knowing where your player and main scene live makes feedback much easier.

Give the assistant the scene, not just a script

A script can depend on node paths, signals, resources, and input actions outside the file. Include the relevant scene tree and connections. A missing child node is not a problem another movement formula will solve.

Ask the assistant to inspect existing conventions before making changes. If your project already has a restart function, extend that path instead of adding a second reset system beside it.

A brief to make your own

This Godot [version] project has the following scene tree and scripts: [context]. Add a collectible that opens the gate after all three are collected. Reuse the existing restart flow. Explain changed files and check collection, early gate entry, completion, and two restarts. Report any check you cannot run.

Play the whole loop

A model saying the feature is complete is a useful handoff message. The running project tells you whether it is true. Keep the test route short enough that you will actually repeat it.

1. Start from the main scene rather than a convenient isolated scene.
2. Visit the gate before collecting everything.
3. Collect items in a different order on a second run.
4. Fail halfway through and restart.
5. Finish, restart, and confirm all objects and counters return.

Describe the thing the player feels

For movement, describe the input and result: “releasing the key still carries me over the ledge.” For a scene, describe the view: “the foreground hides the next platform.” For a rule, describe the state: “the gate opens after two lights.”

These reports help separate a code defect from a design choice. You might want momentum. You probably do not want a counter that lies.

Export while the game is still small

Read the export requirements for your target. A browser build has its own constraints, and a successful desktop run does not establish that it works on a phone browser. Test the controls and restart behavior there too.

This is an independent engine workflow. For Dashpop’s current creation experience, use the agent-native Dashpop Game Engine: describe a game, play the result, and work with its own creative controls and source.

Sources & further reading

References for the tools and facts discussed here. Follow the documentation for the versions you use.

• Godot: your first 2D game
• Godot: exporting for the web
• OpenAI: GPT-6 Astra model documentation