D.A.I. — Decisions and Impulses

A JSON-driven game framework built inside Minecraft.

D.A.I. began as an experiment in separating thought from action.

Instead of directly controlling a Minecraft character, you could make decisions and allow the character to interpret and perform them.

That experiment grew.

Today, D.A.I. is a framework for building automation, interactive systems, custom interfaces, game mechanics, worlds, and complete playable experiences through data.

Using datapacks, resource packs, JSON definitions, functions, and D.A.I.'s client/server runtime, creators can transform Minecraft into experiences that barely need to resemble ordinary Minecraft at all.

D.A.I. is no longer just another way to play Minecraft.

It is a way to build games with Minecraft as the engine.

Minecraft as a Game Engine

Traditional datapacks are incredibly powerful, but they operate within limits.

D.A.I. adds another execution layer around them.

Creators can define systems such as:

• Actions and sequences
• Objectives and automation
• Conditions and branching logic
• Recognition and perception
• Context-sensitive menus
• Interactive overlays
• Reactions and event responses
• Animations
• Custom content
• Experience-specific interfaces
• World initialization and worldgen
• Server-authoritative gameplay
• Persistent game state

All of these systems can work together.

A menu button can run an action.

An action can check conditions.

A condition can depend on what the player recognizes.

A reaction can interrupt or replace normal behavior.

An experience can own its world, interface, datapack, progression, and presentation.

The result is a framework where JSON isn't merely configuration.

JSON becomes gameplay.

Build Complete Experiences

D.A.I. experiences can behave more like standalone games than traditional Minecraft datapacks.

An experience can define:

• Its own title-screen entry
• Its own Minecraft save
• Automatic world creation
• First-join behavior
• Resume behavior
• Custom world setup
• Experience-specific menus
• Interactive overlays
• Custom controls
• Persistent progression
• Server-side gameplay functions
• Automatic datapack installation
• Companion resource packs

While an experience is active, it can even replace D.A.I.'s normal interface with its own game UI.

This allows creators to build experiences with their own identity instead of forcing every project to look and feel like a Minecraft mod menu.

Client Presentation + Server Authority

D.A.I. 1.8 introduced a dedicated client/server architecture.

The physical client handles systems such as:

• Menus
• Input
• Automation
• Recognition
• Overlays
• Animation
• Custom title screens
• Presentation
• Interaction

The logical server handles authoritative gameplay such as:

• Datapack functions
• World mutation
• Inventory mutation
• Experience state
• World initialization
• Server-side game logic

This means D.A.I. experiences can combine rich client-side presentation with gameplay that actually belongs to the server.

For example:

```text Player presses a custom UI button ↓ D.A.I. client action ↓ Server-authoritative request ↓ Datapack function executes ↓ World changes ↓ Client presentation updates