Skip to content

Wire movement narration through the pipeline #515

Description

@dkirby-ms

Summary

The movement narration type is defined and template-backed but never reaches NarrationService at runtime. Route room-entry/exit narration on player movement through generateNarration('movement', …).

Scope / Tasks

  • Locate the movement/room-transition handler in ZoneRoom/movement command.
  • Call generateNarration('movement', playerId, destinationRoomId, fallbackText) on successful move, non-blocking.
  • Decide what recent_events context (e.g. direction moved) to pass; coordinate with Populate real narration context (fill ZoneRoom TODOs) #513 context fields.
  • Add a wiring test asserting movement reaches narrate().

Acceptance Criteria

  • Moving between rooms emits movement narration through the pipeline with template fallback.
  • Test confirms the type is passed to narrate().

Dependencies

#513; Milestone A for live output.

Size

S

Derived from the LLM narration gap analysis (Volo) and decomposition (Elminster).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    engineCore game engine workllmLLM narration integrationnarrativesquad:drizztAssigned to Drizzt (Engine Dev)wiringConnecting existing code into runtime paths

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions