DAI 3.0 · STEP-BY-STEP
Currencies, Shops, Dialogues, Quests & Factions
Create social/progression systems that share stable IDs and server-owned state.
What you are building
Primary path:
Create social/progression systems that share stable IDs and server-owned state.
dai_currencies / dai_shops / dai_dialogues / dai_quests / dai_factionsCreate social/progression systems that share stable IDs and server-owned state.
Step-by-step
- Define factions firstNPC/enemy/shop/quest ownership becomes easier when relationships are explicit.
- Define currencyChoose storage and earning/spending rules.
- Create one shop transactionValidate price, inventory space and authority before changing either side.
- Create one dialogueTie choices to readable world/quest state.
- Create one questUse explicit stages and completion criteria; do not infer everything from dialogue text.
- Test cross-system failureKill NPCs, leave/rejoin, abandon objectives and try purchases at insufficient funds.
Definition of done
- The feature still works after save/reload.
- Server state is authoritative; presentation mirrors it.
- Invalid input cannot duplicate rewards or bypass costs.
- Two players can use the system without sharing unintended temporary state.
- Any optional resource pack can be disabled without breaking datapack logic.
Next integration
Once this feature works alone, connect it to a complete loop instead of adding more isolated content. Use the complete-game tracks to see where it belongs in ACMS, Space Between Blocks, MineTrigger or Hollow Spiral.