DAI 3.0 · STEP-BY-STEP

Currencies, Shops, Dialogues, Quests & Factions

Create social/progression systems that share stable IDs and server-owned state.

Build from scratchTest in MinecraftMultiplayer-safe by designDAI 3.0

What you are building

Primary path: dai_currencies / dai_shops / dai_dialogues / dai_quests / dai_factions
Create social/progression systems that share stable IDs and server-owned state.

Step-by-step

  1. Define factions firstNPC/enemy/shop/quest ownership becomes easier when relationships are explicit.
  2. Define currencyChoose storage and earning/spending rules.
  3. Create one shop transactionValidate price, inventory space and authority before changing either side.
  4. Create one dialogueTie choices to readable world/quest state.
  5. Create one questUse explicit stages and completion criteria; do not infer everything from dialogue text.
  6. 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.