feat: surface player routes for village needs
This commit is contained in:
@@ -746,13 +746,17 @@ Completed:
|
||||
informed trusted helper to respond autonomously. One cardless warm-amber HUD
|
||||
ribbon gently rises, pulses, and fades through need, named report, response,
|
||||
and resolution beats while remaining separate from development overlays.
|
||||
31. Player response whisper: when no capable helper exists, the same ribbon now
|
||||
derives one concise ordinary harvest route from current player-usable finite
|
||||
resources and the real pantry or woodpile. It clears when help emerges or
|
||||
the need closes, and adds no quest, waypoint, tracker, or saved UI state.
|
||||
|
||||
Next:
|
||||
|
||||
1. When no capable helper exists, show one contextual player response hint
|
||||
derived from a current player-usable finite source and the real storage
|
||||
target. Clear it as soon as help emerges or the need closes; do not add quest
|
||||
acceptance, waypoint state, or a generic tracker, as sequenced in
|
||||
1. Begin Milestone 8 with a deterministic headless scaling baseline over
|
||||
increasing NPC and event counts. Measure current tick throughput,
|
||||
serialized-state growth, and retained history before choosing a target
|
||||
population or adding spatial partitions and simulation LOD, as sequenced in
|
||||
`LEARNING_ROADMAP.md`.
|
||||
|
||||
Do not start with GIS data, a full city, a large asset pack, or more NPC
|
||||
|
||||
Reference in New Issue
Block a user