Games & SimulationsDone with Cursor
Playtest a Godot 4 game with a Cursor agent
A Cursor plugin and subagent lets an agent capture screenshots and click through UI flows of a Godot 4 game like a player.
- What They Did
- You install a Godot plugin, skills, a command and a subagent. The caller gives the studio-playtester subagent a slice with criteria, a scene and an action. The agent inspects the scene's unique node names and InputMap, writes a JSON flow under res://agent/, and runs it through the plugin's CLI. Button presses go in as mapped input actions, and screenshots land in out/.
- How It Went
- Each run ends in AGENT_OK or AGENT_FAIL, and the agent reports PASS/FAIL. A script error or unmapped input counts as a failure. The source gives no measured results beyond a boot-to-race demo.
- Worth Knowing
- Capture and flow runs need a real game window. If the debug scene is missing, the agent returns NEED_SETUP and stops, and it won't build one.
Try it yourself with Cursor
Set up an agent that can launch my Godot 4 game, take screenshots, and click through the main UI flows like a player would. Have it report any broken buttons, dead ends, or visual glitches it finds.