Third-Party Development Tool
DAI Datapack Creator
Create a new DAI datapack or import an existing one, edit objectives, styled menus, JSON title screens, registry-backed custom content, reactions, recognition and presentation actions visually, validate references and runtime constraints, then export a normal datapack ZIP.
Pack SetupIdentity and Minecraft datapack metadata
Lowercase letters, numbers, _, -, and .
Written as pack.pack_format in pack.mcmeta.
ObjectivesNamed behavior made from ordered DAI actions
Presentation actions: overlay_sprite and overlay_sprite_sheet are edited
as normal actions. Their texture IDs resolve through Minecraft's enabled resource packs,
for example
my_pack:gui/combat/pow →
assets/my_pack/textures/gui/combat/pow.png.
Title ScreensJSON-driven replacement main menus with Minecraft item icons and hover animation
Exports to
data/<namespace>/dai_title_screens/*.json. Highest enabled priority wins. Buttons can render real Minecraft item models and animate them with spin, bob, pulse, orbit, or none.DAI ContentDatapack-defined items, blocks, weapons, armor, effects, potions, projectiles, particles, and enchantment identities
Registry-backed ITEM/BLOCK definitions can receive real Minecraft IDs. Existing-on-disk definitions are discovered by DAI's early registry scanner before RegisterEvent; vanilla carrier/model IDs can be reused without custom art.
Reactions
JSON event hooks with default, override, or cancel behavior
Reaction conditions are evaluated synchronously at the selected event phase.
Their sequence is queued into DAI's normal action runtime.
Recognition GroupsReusable block ID registries
Recognition DefinitionsStructural perception and semantic results
Resource FilesTextures and other files stored inside the resource pack ZIP
New files default to
assets/<namespace>/textures/.... Edit the ZIP path on any file to create models, fonts, sounds, atlases, or nested texture folders. Binary files such as PNGs are preserved exactly when imported and re-exported.No pack.png selected.
ValidationCheck the current pack before export
Validation errors no longer hard-block ZIP export. If hard errors are present, the creator will warn you and require confirmation before exporting a potentially broken pack.
ExportCompile a standard Minecraft datapack ZIP after validation
The exported ZIP is the editable project. Re-import it later to continue working; no separate creator-project file is required.