Opengame

Open Game gives coding agents a structured path from your original idea to editable engine files, playable builds, and the next iteration.

Install the CLI from GitHub, check your local tools, and open the Blueprint Studio. The MCP server connects the same project tools to your coding agent.

Git · Node.js 20 or newer · a coding agent. Game engines are optional until you build a project that needs one.

npm install --global git+https://github.com/Radiiduration/OPEN-GAME.git#master open-game doctor open-game studio

✓Studio opens at http://127.0.0.1:4173

This installs Open Game directly from GitHub. A versioned npm registry package has not been published yet; tagged GitHub releases are listed on the Releases page.

Open Game is the toolbelt and production guide. Your connected coding LLM does the game-specific design and implementation.

Describe the game, original characters, world, target platform, and multiplayer needs.

Export a blueprint or build brief. The Open Game Creator skill gives your agent a full implementation contract.

The LLM edits real project files using the shared core, CLI, and MCP operations.

Inspect the engine, build, run, fix observed issues, record evidence, and package supported outputs.

Capture a game vision and export a structured blueprint or agent-ready brief.

Guide an agent through the real project, connected systems, implementation, build, play, and continuation record.

Inspect tools, create project handoffs, plan systems, track obligations, run supported engine operations, and package exports.

Use available project integrations for engine builds and scenarios. Check requirements and limits before selecting a target.

Run the local MCP server over stdio and add it to the MCP configuration supported by your agent. Set a workspace folder where projects may be created, then restart the agent.

{ "mcpServers": { "open-game": { "command": "open-game", "args": ["mcp"], "env": { "OPEN_GAME_WORKSPACE": "/absolute/path/to/game-projects" } } } }

Use an absolute path for your own workspace. The server creates projects only inside that configured folder.

Follow releases, inspect the source, report problems, and help shape the tools. Open Game is an independent community project.

The first tagged Open Game package is ready to download. It bundles the Studio, Creator skill, CLI, MCP tools, initial engine adapters, docs, and a bounded browser racing example.

Start with the docs, check the limits, and use the tools that fit your environment.

No. A creator's brief starts an end-to-end coding-agent task. The connected LLM implements the game, and scope, quality, assets, and builds depend on that agent and its environment.

No. Open Game supplies the agent workflow and project tools. Use your own coding agent and configure its model/provider separately.

The project schema is engine-neutral and current adapters include initial Godot, Unity, and Unreal operations. Build support is partial and depends on the engine, export tools, presets, and project configuration.

No. The toolkit can represent multiplayer requirements and includes a bounded example server. It does not provision production matchmaking, identity, cloud saves, or hosting.

Open Game supports original projects inspired by broad genres. No scan or workflow can promise legal safety; use original or properly licensed material.

Read the contribution notes in the repository README, open an issue, and include your environment and exact command output where relevant.