feat: share village needs with helpers
This commit is contained in:
@@ -741,13 +741,18 @@ Completed:
|
||||
and sleep/meal precedence. Existing target resolution chooses and reserves
|
||||
the finite source, while no quest acceptance, reward, or helper assignment
|
||||
is introduced.
|
||||
30. Village whisper: direct witnesses/performers now report the active need's
|
||||
exact trigger before unrelated facts at shared work, allowing a newly
|
||||
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.
|
||||
|
||||
Next:
|
||||
|
||||
1. Prove one direct information-to-help chain: transfer the exact open-need
|
||||
trigger at an existing shared activity, then let the newly informed trusted
|
||||
villager be re-derived and respond through the same autonomous selector.
|
||||
Keep generic dialogue and multi-hop rumours out of scope, as sequenced in
|
||||
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
|
||||
`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