DAI 3.0 · STEP-BY-STEP
Experiences, Worldgen & Title/Loading Presentation
Create a MAIN experience that owns its save bootstrap, world construction, resume path and presentation.
What you are building
Primary path:
Create a MAIN experience that owns its save bootstrap, world construction, resume path and presentation.
dai_experiences + dai_worldgen + dai_title_screensCreate a MAIN experience that owns its save bootstrap, world construction, resume path and presentation.
Step-by-step
- Define the experience identityStable MAIN pack ID/version and experience JSON.
- Define worldgen/bootstrapCreate the world preset/profile and a safe spawn/bootstrap location.
- Build the minimum playable roomDo not generate the whole game before the player can stand somewhere safely.
- Add first-join vs resumeFresh setup and returning-player recovery are separate paths.
- Stage constructionBuild expensive regions in bounded batches and only preload what the next scene requires.
- Add title/loading brandingPresentation is allowed to be rich because gameplay already works.
- Add an explicit end-to-end loopSpawn → objective → challenge → reward → return/progression.
- Test mature-world joinsA new player on an old server must receive the correct personal intro without rewinding shared state.
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.