Creator & Publishing

The DAI 3.0 Creator Layout

The Creator stays intentionally practical while exposing the new game-maker controls where they matter.

Guided Editor + Universal Files

Use the first-class editor when it understands a system. Use Universal Files when it does not. Universal Files can create or import JSON, mcfunction, text, binary and arbitrary nested pack paths, so the Creator can build normal Minecraft data alongside DAI-specific data.

Visual DAI editor
     +
Universal JSON / text / binary files
     +
Imported passthrough files
     ↓
One normal datapack/resource-pack ZIP

Advanced Templates

The Universal Files view can seed common DAI definitions: experience, worldgen, attribute, animation, processing recipe, reaction event, screen profile, function and arbitrary JSON. Templates are starting points, not a closed schema.

Import Without Losing Work

Managed definitions are converted back into visual editor state. Files the Creator does not own remain preserved. Those preserved files are also visible in the Universal Files view, where text/JSON can be edited and binary files can be renamed, replaced or removed.

Complete Experience Starter

The Experiences view now includes a Complete Experience Starter. It creates a paired experience/worldgen profile and pre-fills the experience-owned UI convention (<namespace>:open, <namespace>:close, and main_frame) so creators can start from a complete-game layout instead of assembling lifecycle fields one at a time.

Main vs Addon Role

New datapacks can explicitly declare their role in pack.mcmeta. The Creator can write this metadata for you.

{
  "pack": { ... },
  "dai": { "role": "addon" }
}

Choose Auto / Legacy Detection when editing an older project that should keep its undeclared behavior. DAI infers legacy packs with dai_experiences or dai_title_screens as main; other DAI packs are addons.

Distribution View

The Creator's Distribution view explains the DAI 3.0 install model without changing the exported ZIP: datapacks go to DAI's global /datapacks library, resource packs go to /resourcepacks, and official combo metadata belongs in the website registry only after public download files exist.

Model Converter

The Creator now links to a client-side model conversion tool for Minecraft model JSON, Blockbench / GeckoLib geometry, existing DAI bone/cube JSON, and Wavefront OBJ. The converter auto-detects supported JSON structures, preserves rig hierarchy where available, previews geometry as a wireframe, and exports normalized dai:model/1.0 JSON.

Open Model Converter →

Validation Philosophy

Validation catches what the browser can know: paths, duplicate IDs, JSON syntax, local references, known action/condition requirements and selected schema constraints. It does not replace testing in Minecraft. Unknown imported DAI fields and arbitrary Minecraft files remain exportable so the Creator never destroys forward-compatible data.

Search Before You Build

The DAI 3.0 Creator adds a searchable Action & Condition Library inside the Creator. Use it to look up IDs, categories, parameters, provider inputs and descriptions before wiring an objective. This is especially useful for the large condition catalog and keeps discovery separate from editing.

DAI 3.0 Resource Companion Metadata

When the project is a resource pack, Pack Setup exposes DAI Companion Auto-Enable and Stable Companion ID. The Creator writes those values to the top-level dai object in pack.mcmeta while preserving unrelated imported metadata.

"dai": {
  "auto_enable": true,
  "companion_id": "tamacrafti"
}

Use the same stable companion ID across releases even when the downloadable ZIP filename changes.

DAI 3.0 Creator Additions

The Creator now exposes the current experience branding object as open JSON, native item Data Components in content definitions, native biome/dimension-type/timeline definitions and the dai_registry / dai_data escape hatches. The Runtime editor deliberately preserves unknown fields instead of narrowing new Mojang schemas.

3.0 Pack Identity, Versions & Mod Distribution

The Creator's Pack Setup screen can now author a stable datapack ID and version directly into pack.mcmeta. Keep the ID fixed across releases and advance the version normally.

{
  "pack": { ... },
  "dai": {
    "role": "addon",
    "pack_id": "my_addon",
    "version": "1.2.0"
  }
}

This metadata lets DAI 3.0 replace an outdated save-local copy with the current copy from the global datapack library even when the ZIP filename changes.

Use a Public Pack as a Creator Base

The Creator toolbar can now clone a public pack into the normal import pipeline. Official entries come from /dai/api/packs.json; any public direct ZIP URL can also be used when its host permits browser CORS.

Use Public Pack as Base
        ↓
Official registry component / direct ZIP URL
        ↓
Normal ZIP importer
        ↓
Managed definitions become visual editors
Unknown files remain Universal Files
        ↓
Optional DAI_CREATOR_BASE_SOURCE.txt provenance note

Public-base tutorial →