feat: surface player routes for village needs

This commit is contained in:
Rijad Zuzo
2026-07-16 12:36:50 +02:00
parent d6e6a63048
commit 4f88d15e12
15 changed files with 417 additions and 47 deletions
+9 -6
View File
@@ -196,10 +196,13 @@ lasting during deterministic memory maintenance. Resolution or invalidation
releases that fact back to the normal bounded-retention rules; neither deletes
objective event or opportunity history.
`OpportunityHelperResult` is deliberately absent from this schema. It is
re-derived from the open opportunity plus current NPC knowledge, directed
relationship, inventory, action-definition, storage-capacity, and finite-
resource records. Save/restore regressions require the same helper/action/route
`OpportunityHelperResult` and `OpportunityPlayerResponseResult` are deliberately
absent from this schema. The helper result is re-derived from the open
opportunity plus current NPC knowledge, directed relationship, inventory,
action-definition, storage-capacity, and finite-resource records. The player
result additionally requires no capable helper and derives its ordinary gather
action, real destination, and source count from current enabled player-usable
finite resources. Save/restore regressions require the same applicable route
result and an unchanged checksum before and after querying.
When an idle derived helper chooses the reported supply action, only the
@@ -209,8 +212,8 @@ and independently re-derives current capability from restored facts.
Active-need communication adds no schema fields. It persists through the
existing `KnownEventStateRecord` event, listener, source NPC, direct source
method, and acquisition-tick fields. Communication/HUD animations are transient
and are cleared rather than replayed after restore.
method, and acquisition-tick fields. Communication and player-response HUD
animations are transient and are cleared rather than replayed after restore.
## Resource authority