Add long-term family NPC intelligence roadmap
This commit is contained in:
@@ -594,9 +594,36 @@ Future persistence design should address:
|
||||
- tile package changes;
|
||||
- player-owned structures;
|
||||
- family/generation data;
|
||||
- family and community NPC memory, relationships, teaching history, emotional
|
||||
state, task state, and offline stewardship logs;
|
||||
- economy and transaction records;
|
||||
- settlement governance records.
|
||||
|
||||
## Family, Community NPC, And Offline Stewardship Intelligence
|
||||
|
||||
Long-term NPC and family behavior should be built as inspectable simulation
|
||||
systems before relying on any generative AI layer.
|
||||
|
||||
Core rules:
|
||||
|
||||
- The server remains authoritative for NPC choices, movement, resource use,
|
||||
combat, teaching, learning, economy effects, and offline character outcomes.
|
||||
- Nearby characters can run fuller behavior/state-tree logic, while distant
|
||||
settlement members use cheaper task simulation and ledger updates.
|
||||
- Family and community characters need persistent needs, relationships,
|
||||
memories, skills, roles, emotional state, task state, and contribution logs.
|
||||
- Logged-off player characters may contribute locally from their last valid
|
||||
home, claim, or assigned post, but should not explore, learn new skills,
|
||||
complete major projects, accept strategic risk, or gain hidden progression.
|
||||
- Core behavior must remain deterministic, debuggable, and functional without
|
||||
model inference.
|
||||
- Any AI model layer should be proprietary-first: local or self-hosted where
|
||||
practical, privacy-safe, replaceable, and limited to optional dialogue
|
||||
variation, event summarization, teaching flavor, memory compression, and
|
||||
settlement reports unless explicitly promoted after review.
|
||||
- External AI services must not receive private player history, unreleased world
|
||||
state, economy data, or proprietary design context for core gameplay.
|
||||
|
||||
## Multiplayer Strategy
|
||||
|
||||
The MVP should prove at least two players on the same server.
|
||||
|
||||
Reference in New Issue
Block a user