This is a suggested development exercise, not a pretested MCP adaptation. The exact engine, project ref, and MCP must be checked together.
1. Open a small, complete game
Choose Dodge the Creeps. Record its repository ref and matching Godot version. Run it without AI first: move, avoid enemies, lose, and restart. Save a version-control checkpoint.
2. Connect one MCP
Follow the installation guide for the server compatible with your engine. Read the scene tree and confirm the project path. If your MCP requires an engine upgrade, adapt a copy and verify the original gameplay again before adding a feature.
3. Give the assistant a bounded task
A session-best score display is a small example of a script-and-UI change. Ask the assistant to inspect the existing implementation first so it does not duplicate an already implemented feature.
Work on a copy of Dodge the Creeps. First inspect the project and identify how score and the HUD work. If a high-score display already exists, explain and verify it instead of duplicating it. Otherwise propose the smallest change to show the best score during this session. Preserve the existing restart behavior. Make one change at a time, show the file diff, and check normal play, game over, and restart. Tell me what you actually tested and what I should check manually.Use normal file editing for straightforward script changes. Use MCP where scene state, editor actions, or runtime feedback help.
4. Check the script and the scene
- Review which files changed and whether the new label is connected to the intended script.
- Parse or run the script using the selected tool’s supported workflow.
- Save and reopen the scene. Check node paths, resource references, and signal connections.
- Keep existing movement and enemy behavior intact.
5. Verify observable behavior
| Action | Expected result |
|---|---|
| Start a run | The score and best-score label are readable. |
| Beat the previous score | The displayed session best updates correctly. |
| Lose and restart | The run score resets; the session best remains. |
| Restart the whole application | Behavior matches the explicitly chosen session-only scope. |
If the server supports runtime input or screenshots, use them to help check these cases. Also inspect the screen and controls yourself. Errors or unexpected changes should be fixed before expanding the feature.
6. Save the result and choose the next improvement
Commit a working checkpoint with the version, prompt, and checks you performed. Possible next steps include persistent high scores, a pause menu, or a new enemy pattern. Take one at a time and repeat the same verification loop.
Choose your starting project