feat: share village needs with helpers
This commit is contained in:
@@ -99,6 +99,14 @@ opening; invalidation emits no event and stores the close tick and stable
|
||||
reason. Resolution or invalidation returns the trigger to normal bounded
|
||||
retention.
|
||||
|
||||
When a performer or direct witness meets another villager at an eligible shared
|
||||
activity, the active opportunity's trigger is attempted before normal
|
||||
lasting/recent communication ranking. `EventKnowledgeSystem` still requires
|
||||
performed/witnessed source provenance and records only the existing event ID,
|
||||
speaker ID, source method, listener, and acquisition tick. A newer unrelated
|
||||
fact cannot displace the active report, while communicated listeners still
|
||||
cannot relay it onward.
|
||||
|
||||
For an open need, the same system can derive one capable helper without
|
||||
assigning work. A candidate must know the exact trigger and have a familiar
|
||||
directed relationship with at least 0.6 trust toward the interested villager.
|
||||
@@ -148,6 +156,10 @@ world cue remains specific to the pantry shortage rather than representing a
|
||||
wood need as hunger. The active summary additionally names the currently
|
||||
derived helper, supply action, trust fact, and inventory or finite-source route,
|
||||
or states that no informed trusted villager is currently able to supply it.
|
||||
One separate cardless player HUD gives transient warm-amber feedback for the
|
||||
authoritative need opening, exact named report, newly informed helper decision,
|
||||
and real resolution. It stays available when development overlays are hidden,
|
||||
but clears on restore and never becomes objective or save state.
|
||||
|
||||
## Deliberate limits
|
||||
|
||||
|
||||
Reference in New Issue
Block a user