Skip to content

GodotMaker Wiki

GodotMaker turns a game idea into a playable Godot 4 prototype. The normal path is godotmaker-cli: it helps shape the idea into a GDD, then drives the same /gm-* role commands through planning, implementation, tests, gameplay runs, screenshots, evaluation, and fixes until the current design scope is complete.

New here? Start with these three pages

  1. Installation - required tools, optional API keys, and environment checks.
  2. Your first game - the CLI-driven idea-to-prototype workflow.
  3. How it works - the roles, quality gates, and fix loops behind the CLI.

Wiki sections

Section When to read it
Getting Started First time setting up GodotMaker, or making a fresh project
Concepts You want to understand the CLI workflow, 9 role commands, ECS, and design choices
Skills What the role / supporting / reviewer skills are and which one does what
Troubleshooting A run stopped, was blocked, or behaved oddly - find a fix here
Tools Reference for publish.py, check_env.py, check_project.py, asset helpers
Configuration Per-project preferences, provider setup, host paths, addon version pinning
Contributing You want to add a skill, hook, or tool, or cut a release
Reference Glossary, FAQ, and pointer to the changelog

What you can do with GodotMaker

Capability What it means for you
Bring an idea, not a finished spec Describe the game in natural language; GodotMaker helps turn it into a GDD and planning docs
Let the workflow keep moving A small prototype can take 5-8 hours of agent runtime, but you do not manually drive every role command
Keep the local Godot project The generated code, scenes, assets, tests, screenshots, and reports live in your project folder
Get tested code by default Unit tests and end-to-end gameplay tests are written alongside game code
Use visual QA as feedback Automated screenshots and visual assessment turn UI and scene issues into fix tasks
Stay on a real engine The result lands in Godot, so you can keep debugging, extending, exporting, and shipping

Current boundaries

  • GodotMaker currently targets 2D Godot games. 3D game generation is not supported.
  • The art pipeline is still alpha and may need follow-up repair for atlas regions, animation setup, or asset binding.
  • Pixel art and TileMap support are planned but not currently supported.
  • Level layout, puzzle content, and numeric balance still need human judgment and manual refinement.
  • Audio generation is not supported yet.
  • Very long automated runs are cost-sensitive, and rare projects may fail to converge after repeated build/fix/evaluate loops.

Manual /gm-* role commands still exist for advanced users, debugging, and framework development. They are not the recommended first-run path. The normal CLI path supports Claude Code, Codex, and OpenCode runners; see Installation for runner-specific setup notes.

Project status