DAI 2.2 Changelog

Native Content Exposure

DAI 2.2 significantly expands the native datapack API, allowing Experiences and addons to define much more of their gameplay directly through JSON instead of relying on vanilla carriers, command workarounds, or hardcoded Java behavior.

Native Blocks

Expanded registry-backed custom block support with configurable:

• Hardness
• Explosion resistance
• Luminance
• Sound type
• Map color
• Friction
• Movement speed factor
• Jump factor
• Correct-tool requirements
• Occlusion
• Replaceability
• Random ticking
• Lava ignition
• Emissive rendering
• Piston reaction
• Block states
• Collision shapes
• Outline shapes
• Climbability
• Redstone state/output
• Scheduled ticks

Added block lifecycle events including:

• Place
• Break
• Use
• Attack
• Step
• Entity inside
• Neighbor changed
• Random tick
• Scheduled tick
• Redstone/state changes

This allows datapacks to create native illuminated blocks, boost surfaces, hazards, interactive panels, custom doors, traversal blocks, and other gameplay-focused materials.

Native Items

Expanded custom item lifecycle support.

Items can now respond to:

• Use
• Use on block
• Use on entity
• Use start
• Use tick
• Use release
• Attack entity
• Inventory tick
• Equip
• Unequip
• Drop
• Pickup

The existing Mojang data-component bridge remains available for defining native item components.

Changes to native item components can now participate in DAI registry preflight detection.

Native Entities

Expanded native DAI entity gameplay and lifecycle support.

New runtime event support includes:

• Spawn
• Tick
• Hurt
• Damage dealt
• Attack
• Interact
• Death
• Kill
• Jump
• Fall
• Target acquired
• Target lost
• Mount
• Dismount
• Passenger changes

Entity gameplay definitions can now actively use faction metadata and dispatch their configured gameplay events.

Added expanded rider/passenger positioning support for custom mounts and vehicles.

Native Projectiles

DAI projectiles now have an actual runtime physics layer.

Existing projectile fields such as:

• projectile_speed
• gravity

are now actively consumed by the runtime.

Additional projectile behavior includes:

• Drag
• Lifetime
• Damage
• Knockback
• Collision radius
• Piercing
• Ricochets
• Homing
• Return-to-owner behavior
• Entity impact events
• Block impact events
• Expiration events
• Tick events

This allows datapacks to create substantially more complete custom projectile systems without command-driven projectile simulations.

Vehicle Runtime

Expanded dai_vehicles from basic summon/ride behavior into a configurable vehicle-control system.

Added client-to-server vehicle input support for:

• Forward
• Backward
• Strafing
• Jump
• Sneak
• Sprint / boost
• Player look direction

Vehicle movement can now define:

• Acceleration
• Maximum speed
• Reverse speed
• Braking
• Drag
• Steering rate
• Jump behavior
• Boost behavior

This gives custom DAI entities a proper foundation for bikes, mounts, cars, flying craft, and other controllable vehicles.

Portals

Expanded DAI portal support.

Entity-hosted portals can now affect:

• Players
• Entities
• Mobs
• Items
• Projectiles
• Vehicles
• All supported entity types

Added standalone DAI portal volumes so portals no longer need to be hosted by a living entity.

Portal definitions can provide custom destination and traversal behavior while retaining compatibility with existing player-only portals.

Native Particles

Added registry-backed native DAI particle support.

Custom particle definitions can now control:

• Registry ID
• Texture
• Lifetime
• Gravity
• Friction / drag
• Scale
• Tint
• Alpha
• Collision
• Full-bright rendering

Generated particle descriptions and client providers are created automatically for registered DAI particles.

Native Effects

Registry-backed dai_effects can now create actual Minecraft effect registry entries.

Native effects can define:

• Effect category
• Effect color
• Tick behavior
• DAI lifecycle events

Existing virtual DAI effect behavior remains supported for packs that do not require native registration.

Native Potions

Registry-backed dai_potions can now compose registered effects into actual Minecraft Potion registry entries.

This allows custom DAI effects to participate in Minecraft's native potion systems.

Fluids

Expanded DAI fluid runtime behavior.

Custom fluid definitions can now influence entities through:

• Drag / viscosity
• Buoyancy
• Gravity behavior
• Damage
• Extinguishing
• Enter events
• Tick events
• Exit events

Existing block/carrier-based fluid behavior remains supported for compatibility.

Interactives

Expanded dai_interactives into runtime interaction volumes.

Interactive areas can now respond to:

• Enter
• Exit
• Tick
• Use
• Attack

This provides a cleaner system for terminals, consoles, holograms, capture points, invisible triggers, and other world interactions.

Audio & Music

Expanded sound targeting and playback control.

Sound definitions now support improved:

• Audience targeting
• Positional targeting
• Minimum volume behavior

Music/runtime audio gained additional support for:

• Looping
• Priority
• Track transitions
• Server-owned playback control

Custom sound assets remain resource-pack driven through Minecraft's normal sound system.

Registry & Reload Improvements

Expanded DAI's native registry system to recognize:

• Item
• Block
• Entity
• Effect
• Potion
• Particle

Updated:

• Early registry scanning
• Registry cache
• Static-definition comparison
• Registry preflight
• Tombstone handling
• Restart detection

Registry-static changes now correctly request a restart instead of attempting unsafe hot reloads.

Fixed registry preflight handling for the newly supported Effect, Potion, and Particle registry types.

Codec Improvements

Refactored several large codecs that exceeded Mojang DataFixerUpper's RecordCodecBuilder.group() field limit.

Updated codecs include:

• DAI_BlockSettings
• DAI_ContentDefinition
• DAI_ParticleSettings
• DAI_EntitySettings

The external JSON format remains unchanged.

Compatibility

• Existing DAI 2.1 datapacks remain supported.
• New configuration fields are optional unless explicitly used.
• Existing player-only portals preserve their previous behavior.
• Existing virtual content systems remain available alongside the new native implementations.
• Existing Mojang component definitions remain supported.
• Existing "native_components" definitions remain compatible.
• "components" is now also understood by the normal DAI content codec and registry preflight system.

Creator & Documentation

Updated the DAI Creator and documentation for DAI 2.2.

Creator additions include:

• Native Block templates
• Projectile templates
• Particle templates
• Native Effect templates
• Vehicle runtime templates
• Standalone Portal templates
• Interactive volume templates
• Fluid runtime templates
• Effect, Potion, and Particle registry targets

Added Use Public Pack as Base support.

Creators can now import:

• Official public DAI datapacks
• Official public DAI resource packs
• Public direct-download datapack ZIPs
• Public direct-download resource-pack ZIPs

Imported packs are processed through the normal Creator importer while preserving unsupported or unknown files.

New and expanded tutorials cover:

• Native blocks
• Entity lifecycle
• Riding and vehicles
• Projectile physics
• Standalone portals
• Particles
• Effects
• Fluids
• Public-pack-based project creation

DAI 2.2 focuses on moving custom Experiences away from vanilla-carrier workarounds and toward fully data-driven native Minecraft content and runtime behavior.