ship-godot-game

Ship a Godot game

Treat shipping as an evidence gate. Preserve the project and release artifacts; never turn an unavailable platform, signing identity, export template, SDK, toolchain, or target device into a passing claim. Support begins at Godot 4.7.

Control contract

• Validate projectPath, artifact destinations, and local sources against the effective MCP roots and allowed directories before access or mutation.

• Record whether release verification is watched or unattended. For watched work, call editor_session with ensure and launch enabled; stop if a usable editor cannot be established rather than silently continuing detached. For unattended release work, do not launch an editor; use direct and hidden inspection/runtime tools so readiness checks do not alter project metadata.

• Keep inspection read-only until the user authorizes a repair, export, signing, addon/import change, or other release mutation. Distinguish persistent project changes, runtime-ephemeral playtest state, process lifecycle, and deliverables.

• Use canonical core tools directly (compact is only the compatibility alias). Resolve hidden analyze_project_integrity, verify_export_readiness, manage_import_pipeline, verify_dotnet_project, and manage_addon through godot_catalog detail, then invoke them with godot_call; never call a hidden tool directly.

• The wrapper field is exactly toolName, not name or tool. Use godot_catalog like this:

  { "action": "describe", "toolName": "verify_export_readiness", "detail": "full" }
  

  Then dispatch through godot_call like this:

  { "toolName": "verify_export_readiness", "arguments": { "projectPath": "...", "action": "inspect", "presetName": "Local Eval" } }
  

• Respect Pause Agent without retry or bypass. While paused, retain inspection, input release, stop, and cleanup; report any blocked effective mutation.

• Use privileged reflection or evaluation only when already enabled and necessary for a release criterion. Never enable it to manufacture missing evidence.