Runtime Dispatch 3.3 & Registry Scope
DAI 3.3 expands direct JSON dispatch for UI, input and persistent data while keeping client/server and native-entity behavior scopes explicit.
3.3 runtime catalog
The normal DAI action registry in the 3.3 source used for this site sync contains 259 registered action IDs. The web Creator catalog now mirrors that registry instead of the older subset.
New client-facing dispatch
New authoritative persistent-data dispatch
3.3 adds item Data Component set/remove/copy plus JSON block-entity typed state and inventory slot mutation. Existing server-owned function, command, block, item, projectile, particle, effect and potion paths remain available.
Condition scope
The general action/condition registry remains separate from native entity behavior vocabulary. 3.3 adds raw-key, mouse/UI, item-component and block-entity providers to the general condition registry.
Atomic interaction rule
When input spends ammo/currency/resources, prefer one server-owned function/action that rechecks cost and performs mutation + result together. Avoid multi-action chains that can remain queued after the originating input.