DAI ENGINE 4.2 ECOSYSTEM

Official Packs

DAI Engine 4.2 separates complete Experience Packs from stackable Addons. The registry below is the Engine 4.2 source of truth. The legacy DAI 3.x registry remains available for backwards compatibility, and the 4.0 registry endpoint remains available as a compatibility alias for older 4.x clients.

DAI Engine 4.2: packs are now classified by runtime role: Experience Packs provide the primary experience, while Addons are reusable stackable systems. Existing namespaces and IDs remain stable where possible.

Core Engine

DAI Engine 4.2 Pack Registry

The 4.1 schema-4 registry introduced separate Experience Pack and stackable Addon entries. DAI 4.2 keeps that public network and makes it the current registry.

EXPERIENCE PACKSComplete playable projects intended to provide the main rules, progression, world or gameplay experience. Normally one Experience Pack acts as the primary experience.
ADDONSReusable systems that can be layered onto an Experience Pack or used independently when supported: HUDs, effects, combat systems, automation, time systems and similar features.
DAI 4.2 registry: /dai/api/packs-4.2.json. This is the canonical public network registry consumed by DAI Engine 4.2, the web Packs page, and Creator fallbacks. /dai/api/packs.json remains legacy DAI 3.x compatibility only.

Experience Packs

Primary playable experiences registered for DAI Engine 4.2.

00

LOADING EXPERIENCE PACKS…

Addons

Stackable reusable systems registered for DAI Engine 4.2.

00

LOADING ADDONS…

Resource Packs

Dedicated visual companions for DAI experiences and presentation systems.

Ready-to-Play Modpacks

Preassembled distributions for players who want a complete profile instead of installing the engine, datapack and companion resources separately.

DAI Engine 4.2 Pack Registry

This JSON is the canonical DAI Engine 4.2 public network. The schema-4 registry separates sections.experience_packs[] and sections.addons[] while keeping stable pack IDs and direct component download URLs.

Backwards compatibility: DAI 4.2, the Packs page and Creator now share /dai/api/packs-4.2.json. DAI 3.x can continue using the legacy /dai/api/packs.json endpoint; older Engine 4.x builds can continue using /dai/api/packs-4.1.json (DAI 4.1) or /dai/api/packs-4.0.json (DAI 4.0).
Loading /api/packs-4.2.json…

Installation Behavior

Open DAI 4.2 Packs
    ↓
Choose EXPERIENCE PACKS or ADDONS
    ↓
Experience Pack → primary gameplay/runtime content
Addon → stackable reusable feature/system
    ↓
Install / Update / Uninstall owned components
    ↓
DAI changes only files it owns
Normal companion ZIPs can auto-enable through matching namespaces or explicit dai.auto_enable / dai.companion_id metadata. Stable IDs allow renamed/versioned updates without disturbing unrelated resource packs.

Learn From a Public Pack

The DAI Creator can use public packs as editable starting bases. Creator now reads the same canonical /dai/api/packs-4.2.json network used by DAI Engine first, with /dai/api/public-bases.json retained as a compatible fallback/source index; direct public ZIP URLs still work too.

Derivative-work reminder: importing a public ZIP is a technical convenience, not a license grant. Keep source attribution and follow the pack's license before publishing modified code/assets.

Open Creator Public-base tutorial