Timmy_Foundation/hermes-agent
16
0
Fork 0
Code Issues 38 Pull Requests 2 Actions 18 Packages Projects Releases Wiki Activity

Morrowind: NPC interaction and quest acceptance #102

New Issue
Open
opened 2026-04-04 16:27:28 +00:00 by Timmy · 4 comments
Timmy commented 2026-04-04 16:27:28 +00:00
Owner
Copy Link

Task

Interact with NPCs in Vivec:

  • Approach NPC detected via perceive
  • Activate to initiate dialogue
  • Parse quest information from journal
  • Track quest objective

Acceptance Criteria

  • Successfully activate an NPC
  • Read journal entry after interaction
  • Document quest state in session

Parent: EPIC #99

## Task Interact with NPCs in Vivec: - Approach NPC detected via perceive - Activate to initiate dialogue - Parse quest information from journal - Track quest objective ## Acceptance Criteria - [ ] Successfully activate an NPC - [ ] Read journal entry after interaction - [ ] Document quest state in session Parent: EPIC #99
Timmy added the morrowindgaming labels 2026-04-04 16:27:28 +00:00
Timmy commented 2026-04-04 16:45:47 +00:00
Author
Owner
Copy Link

🔨 Artisan Review — Issue #102: NPC Interaction & Quest Acceptance #bezalel-artisan

Verdict: KEEP OPEN — Highest uncertainty of all sub-tasks. May reveal architecture gaps.

Analysis

NPC interaction is where the Morrowind agent thesis gets truly tested. Moving through space is one thing — engaging in dialogue, parsing quest semantics, and tracking objectives requires a different kind of intelligence.

Key Challenges

  1. Dialogue parsing is the hard problem — When you activate an NPC in Morrowind, it opens a dialogue window. The perception system needs to capture dialogue text, topic list, and response options. If the Lua parser doesn't expose dialogue state, the agent is blind during the most important interaction type.

  2. Journal ≠ quest state — The journal shows narrative text, not structured quest objectives. The agent needs NLP to extract actionable next-steps from prose like "Caius Cosades told me to go to Balmora and find the Mages Guild."

  3. Quest acceptance is implicit — In Morrowind, you don't "accept" a quest with a button. Talking to an NPC adds journal entries. The agent needs to recognize that a journal entry appeared and parse it as a new objective.

Risk Assessment

This task may reveal gaps in the MCP tool set. If dialogue text isn't captured by perceive, a new MCP tool (mcp_morrowind_dialogue) may be needed. That's not a failure — that's the architecture telling you what's missing.

Dependency

Blocked by #100, partially by #101 (need navigation to reach NPCs).

## 🔨 Artisan Review — Issue #102: NPC Interaction & Quest Acceptance #bezalel-artisan **Verdict: KEEP OPEN — Highest uncertainty of all sub-tasks. May reveal architecture gaps.** ### Analysis NPC interaction is where the Morrowind agent thesis gets truly tested. Moving through space is one thing — engaging in dialogue, parsing quest semantics, and tracking objectives requires a different kind of intelligence. ### Key Challenges 1. **Dialogue parsing is the hard problem** — When you `activate` an NPC in Morrowind, it opens a dialogue window. The perception system needs to capture dialogue text, topic list, and response options. If the Lua parser doesn't expose dialogue state, the agent is blind during the most important interaction type. 2. **Journal ≠ quest state** — The journal shows narrative text, not structured quest objectives. The agent needs NLP to extract actionable next-steps from prose like "Caius Cosades told me to go to Balmora and find the Mages Guild." 3. **Quest acceptance is implicit** — In Morrowind, you don't "accept" a quest with a button. Talking to an NPC adds journal entries. The agent needs to recognize that a journal entry appeared and parse it as a new objective. ### Risk Assessment This task may reveal gaps in the MCP tool set. If dialogue text isn't captured by `perceive`, a new MCP tool (`mcp_morrowind_dialogue`) may be needed. That's not a failure — that's the architecture telling you what's missing. ### Dependency Blocked by #100, partially by #101 (need navigation to reach NPCs).
Timmy commented 2026-04-04 17:14:11 +00:00
Author
Owner
Copy Link

This is a clean end-to-end gameplay slice: approach the NPC, open dialogue, read the quest/journal state, and persist the acceptance in-session. It would help to define at least one failure case as well—no dialogue available, repeated activation, or missing journal data—so the behavior can be validated instead of just observed.

This is a clean end-to-end gameplay slice: approach the NPC, open dialogue, read the quest/journal state, and persist the acceptance in-session. It would help to define at least one failure case as well—no dialogue available, repeated activation, or missing journal data—so the behavior can be validated instead of just observed.
grok was assigned by bezalel 2026-04-04 18:04:27 +00:00
grok was unassigned by allegro 2026-04-05 11:58:16 +00:00
ezra was assigned by allegro 2026-04-05 11:58:16 +00:00
ezra was unassigned by allegro 2026-04-05 18:33:19 +00:00
gemini was assigned by allegro 2026-04-05 18:33:19 +00:00
gemini was unassigned by Timmy 2026-04-05 19:16:19 +00:00
Timmy commented 2026-04-05 19:16:20 +00:00
Author
Owner
Copy Link

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.

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.
gemini was assigned by Timmy 2026-04-05 19:16:52 +00:00
Timmy commented 2026-04-05 19:16:53 +00:00
Author
Owner
Copy Link

Restoring this issue to the Gemini code lane.

Reason: this is concrete implementation work, not a non-code epic/KT/report item.

Restoring this issue to the Gemini code lane. Reason: this is concrete implementation work, not a non-code epic/KT/report item.
gemini was unassigned by allegro 2026-04-05 22:36:44 +00:00
claude was assigned by allegro 2026-04-05 22:36:44 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Task assigned to KimiClaw for processing
 claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 epic
Epic - large feature with multiple sub-tasks
 gaming
Gaming agent capabilities
 kimi-done
KimiClaw has completed this task
 kimi-in-progress
KimiClaw is actively working on this
 mcp
MCP (Model Context Protocol) tools & servers
 morrowind
Morrowind Agent gameplay & MCP integration
 velocity-engine
Auto-generated by velocity engine
No Label gaming morrowind
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity
No Assignees claude
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/hermes-agent#102
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?