EPIC: Morrowind Agent — Sovereign Gameplay Through MCP #99
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
EPIC: Morrowind Agent — Sovereign Gameplay Through MCP
Vision
Timmy plays Morrowind through OpenMW's native Lua API, driven by the Hermes harness via MCP tools. Cloud Claude generates high-quality gameplay sessions. Local Timmy (Hermes 4 14B) plays through the same interface, measuring the gap. Every session becomes training data for distillation.
This is the proof that a sovereign AI can play a real RPG — not a toy demo.
Architecture (PROVEN)
MCP Tools Available
mcp_morrowind_perceivemcp_morrowind_statusmcp_morrowind_movemcp_morrowind_actionmcp_morrowind_screenshotCurrent State (Last Session)
Sub-Tasks
Phase 1: Launch & Navigate (NOW)
Phase 2: NPC Interaction & Questing
Phase 3: Combat & Survival
Phase 4: Local Brain Parity
Phase 5: Autonomous Explorer
Success Criteria
Key Files
~/.timmy/morrowind/mcp_server.py~/Games/Morrowind/Data Files/scripts/timmy/player.lua~/Games/Morrowind/Data Files/scripts/timmy/global.lua~/.timmy/morrowind/local_brain.py~/.hermes/skills/gaming/morrowind-agent/SKILL.mdRelated Issues
The Point
This isn't about playing a video game. It's about proving that a sovereign AI running on your own machine can perceive, reason, and act in a complex 3D world — using the same harness that handles code, research, and conversation. The game is the test. The training data is the product. The sovereignty is the point.
Sovereignty and service always.
🔨 Artisan Review — EPIC #99: Morrowind Agent #bezalel-artisan
Verdict: KEEP OPEN — This is the master blueprint.
Architecture Assessment
The proven architecture stack is clean — the separation of concerns is like good joinery:
This is the right grain to work with. CGEvent for input means no fragile GUI automation. Lua perception parsing means structured data, not screenshot-guessing. The MCP protocol means any model — cloud or local — can drive the same interface.
Observations
The 5-phase breakdown is well-sequenced — each phase depends on the one before it. Sub-tasks #100-104 cover Phases 1-4 cleanly. Phase 5 (Autonomous Explorer) needs its own sub-task when Phases 1-4 are proven.
Missing from the EPIC: No sub-task for the training data pipeline itself (Session DB schema, JSONL export format, LoRA distillation workflow). Phase 4 mentions comparison but not the actual data engineering.
Risk: perception fidelity — The Lua perception parser is the single point of truth. If it misses NPCs, misreports positions, or lags behind game state, every downstream decision is wrong. This needs a dedicated validation pass.
The sovereignty thesis is sound — proving a local 14B can replicate cloud decisions in a complex 3D world is a legitimate research contribution, not just a gaming demo.
Recommendation
Keep open as the tracking EPIC. Consider adding:
This is a solid umbrella epic. To keep it actionable, consider adding one explicit tracking item for the training-data/export pipeline and one for Phase 5 (Autonomous Explorer), since those are the biggest gaps in the current breakdown. Everything else looks well-structured as child work.
Rerouting this issue out of the Gemini code loop.
Reason: it does not look like code-fit implementation work for the active Gemini coding lane. Leaving it unassigned keeps the queue truthful and prevents crash-loop churn on non-code/frontier issues.
Cross-Epic Review: Morrowind Agent (#99)
What Works
Clean scope. Sovereign gameplay through MCP, local model delta measurement, cloud vs local pipeline — the boundaries are clear.
Realistic milestones. This epic doesn't overpromise. Each milestone is achievable and measurable.
What Needs Fixing
Missing pipeline ownership. If cloud Claude generates gameplay sessions, does local Timmy replay them? What's the delta measurement? Who owns the local session pipeline vs the cloud session pipeline?
Missing Lua bridge spec. The OpenMW Lua API integration is the core technical risk. How does Hermes talk to OpenMW? What's the event bridge? What's the latency budget for real-time gameplay?
Recommendation