Skip to content

v0.9.1 β€” Unity MCP documentation updates

Choose a tag to compare

@striderZA striderZA released this 15 Jun 19:24

v0.9.1 β€” Unity MCP documentation updates

Small follow-up to v0.9.0. Adds unity-mcp coverage to user-facing docs that PR #63 didn't touch.

What's in this release

Three follow-up commits, all doc-only (no code changes):

  • docs: add unity-mcp sections to setup-requirements and quick-start (9ffbdb8)
    • .opencode/docs/setup-requirements.md β€” new ### Unity-MCP section parallel to the existing ### Godot-MCP section (prerequisites, install via Unity Package Manager, manual opencode.json config fallback, Editor-running warning, tool list)
    • .opencode/docs/quick-start.md β€” new step 4b "Enhance with unity-mcp (Unity only)" parallel to the existing godot-mcp step
  • docs(readme): mention unity-mcp in engine-unity module row (88a4719)
    • README.md β€” adds + unity-mcp to the engine-unity row in the Modular Framework table, matching the existing aseprite MCP mention in the art row
  • feat: integrate unity-mcp (CoplayDev) into OCGS framework (1f1f018, from #63) β€” included for context as the underlying change

Notes

  • The framework/docs/superpowers/specs/ and .../plans/ files from the planning phase were intentionally NOT included in any release (treated as local-only working artifacts)
  • Pre-existing badge/count inconsistencies in README (76 skills vs actual 77, 183 tests vs actual 182) are unrelated to this release and not addressed here
  • No new validation suite changes; all checks continue to pass (182/182 framework validation, 129/129 plugin scenarios)

For users

No action required. The unity-mcp integration is unchanged from v0.9.0; this release just makes it more discoverable in the docs.


Full diff vs v0.9.0: v0.9.0...v0.9.1