-
Notifications
You must be signed in to change notification settings - Fork 0
Wire movement narration through the pipeline #515
Copy link
Copy link
Open
Labels
engineCore game engine workCore game engine workllmLLM narration integrationLLM narration integrationnarrativesquad:drizztAssigned to Drizzt (Engine Dev)Assigned to Drizzt (Engine Dev)wiringConnecting existing code into runtime pathsConnecting existing code into runtime paths
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
engineCore game engine workCore game engine workllmLLM narration integrationLLM narration integrationnarrativesquad:drizztAssigned to Drizzt (Engine Dev)Assigned to Drizzt (Engine Dev)wiringConnecting existing code into runtime pathsConnecting existing code into runtime paths
Summary
The
movementnarration type is defined and template-backed but never reachesNarrationServiceat runtime. Route room-entry/exit narration on player movement throughgenerateNarration('movement', …).Scope / Tasks
ZoneRoom/movement command.generateNarration('movement', playerId, destinationRoomId, fallbackText)on successful move, non-blocking.recent_eventscontext (e.g. direction moved) to pass; coordinate with Populate real narration context (fill ZoneRoom TODOs) #513 context fields.movementreachesnarrate().Acceptance Criteria
movementnarration through the pipeline with template fallback.narrate().Dependencies
#513; Milestone A for live output.
Size
S
Derived from the LLM narration gap analysis (Volo) and decomposition (Elminster).