D.A.I. — Decisions and Impulses

Development Ended

D.A.I. Engine is no longer being developed or released.

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

It became a JSON-driven game framework built inside Minecraft — a system for creating automation, interactive systems, custom interfaces, gameplay mechanics, worlds, and complete experiences through data.

It grew from an experiment into an ecosystem.

Unfortunately, this is where that development ends.

I have decided to discontinue D.A.I. Engine rather than continue developing a framework whose primary distribution through CurseForge has become increasingly unreliable, restrictive, and difficult to maintain.

This decision was not made because development stopped, because there were no more ideas, or because D.A.I. had reached the end of what it could become.

It was made after a documented series of events involving D.A.I. and CurseForge.

Why Development Ended

The following events are documented through CurseForge / Overwolf support tickets, project moderation records, and CurseForge's own project pages.

Supported Data Pack Loader Review

D.A.I. implements automatic datapack loading functionality.

CurseForge already recognizes supported datapack loaders and its own application directs users toward compatible loader mods when datapack support is required.

I contacted CurseForge Support to determine the correct process for having D.A.I. considered as a supported datapack loader.

In ticket #389488, CurseForge Support initially directed me to contact a specific individual through the CurseForge Authors Discord.

After explaining that I had been permanently banned from that Discord and therefore could not use the process CurseForge had provided, Support escalated the request internally.

CurseForge later confirmed in writing:

"You did follow the correct steps in requesting consideration for your project to be added as a supported data pack loader on the platform."

CurseForge also confirmed:

"There is currently no formal, publicly available process for this - these are handled as special cases on a discretionary basis…"

Most importantly, CurseForge stated:

"your prior warnings and ban were taken into account during this review"

and declined to continue with the supported-loader review.

No technical incompatibility with D.A.I.'s loader implementation was identified to me as the reason for ending the review.

The decision was instead explicitly connected to my prior Discord moderation history.

Discord Moderation and Review

During Minecraft ModJam 2026, I was permanently banned from the CurseForge Authors Discord.

Because this occurred while D.A.I. was participating in an active CurseForge competition, I immediately opened ticket #389835 requesting written confirmation that the Discord dispute would not affect:

• D.A.I.'s ModJam participation
• Project moderation
• Judging
• Rewards
• Visibility
• Eligibility
• Other treatment of D.A.I. on CurseForge

CurseForge responded:

"This Discord action does not affect your ModJam participation."

and:

"It also has no bearing on CurseForge project moderation"

However, Support later confirmed that the same Discord warnings and ban were considered when deciding not to continue D.A.I.'s supported-loader review.

When I asked for an independent review of the Discord moderation history in ticket #391097, particularly because that history was now affecting decisions outside Discord, CurseForge responded that the decisions were final.

CurseForge ultimately stated:

"We will no longer answer any related tickets."

I specifically requested escalation to a supervisor or another person who had not participated in the original decisions.

No independent review was provided to me.

Undefined Project Moderation Requirements

Several D.A.I.-related projects later received the moderation instruction:

"Please merge your uploads into a single project, or space them out."

Because these were separate projects with different gameplay, files, assets, descriptions, and releases, I asked CurseForge in ticket #391488 to define the rule being applied.

I specifically asked:

1. How much time must separate submissions?
2. Whether there was a maximum number of projects or files per day or week.
3. What published policy established the requirement.
4. What criteria determine when separate projects must be merged.
5. Whether the requirement applied generally or specifically to my submissions.

CurseForge later noted that the projects had eventually been approved.

The requested spacing interval, upload limit, merger criteria, and published policy were not provided.

D.A.I. Engine Release Moderation

Over time, D.A.I. Engine updates began spending increasingly long periods under manual review.

Earlier D.A.I. releases commonly completed review within hours.

Later releases began remaining under review for approximately a day, then multiple days.

Eventually, consecutive D.A.I. Engine releases were simultaneously held under manual review for several days.

I opened ticket #394186 requesting a formal review of this pattern.

I asked CurseForge to clarify:

• Why D.A.I. updates were repeatedly entering extended manual review
• Whether anything about my account or projects had changed
• Whether additional moderation flags or restrictions existed
• Whether D.A.I. was subject to additional review requirements
• Whether those requirements were being applied consistently
• What review timeframe I should expect
• How the delays would affect participation in ModJam 2026

While that ticket remained unresolved, D.A.I. Engine 3.9 and 4.0 were rejected and removed with the explanation:

"Editing server files(JSON) is not allowed."

I immediately requested the exact file, path, code behavior, or functionality responsible for the rejection.

I also asked CurseForge to identify the published policy establishing the restriction.

The relevant D.A.I. writes I identified were to D.A.I.-owned data such as:

• world/data/dai_state.json
• world/dai/creator/export/data/.../*.json

I specifically asked whether the restriction prohibited:

• All mod-owned JSON persistence

or only:

• Modification of Minecraft / server administrative JSON files

I also asked where the rule was published and when it took effect.

A substantive technical answer identifying the offending D.A.I. code or file was not provided to me.

D.A.I. Engine 4.1 and 4.2

After D.A.I. Engine 3.9 and 4.0 were rejected, replacement versions were prepared.

D.A.I. Engine 4.1 and 4.2 subsequently remained simultaneously under manual review.

At that point, D.A.I. Engine 3.8, approved on September 9, remained the newest version I had successfully been able to publish through CurseForge.

For approximately ten days, newer D.A.I. development could not reach CurseForge users through a successful Engine release.

During that period I repeatedly asked:

• What exact behavior needed to be changed?
• Were 4.1 and 4.2 being reviewed for the same reason?
• Was D.A.I. subject to an additional moderation flag or restriction?
• What published policy was being applied?
• What was required to produce a compliant build?

Those questions remained unresolved while development continued moving forward.

Minecraft ModJam 2026

These events also occurred while D.A.I. was participating in Minecraft ModJam 2026.

That mattered because ModJam was a time-limited competition.

CurseForge moderation controlled when project updates became publicly available, while project availability and downloads could affect participation and competitive conditions.

I raised this concern with CurseForge while the competition was still active.

Ticket #389835 was created on August 18 under the subject:

URGENT – ModJam 2026 Participant Access / Eligibility Following CurseForge Discord Ban

I specifically requested confirmation that the Discord dispute would not:

• Disqualify D.A.I.
• Flag or deprioritize D.A.I.
• Reduce its visibility
• Affect moderation
• Affect judging
• Affect rewards
• Affect Community Favorites
• Affect other treatment of the project

The concern was therefore documented during the competition itself, not created after its conclusion.

D.A.I. Was Still Growing

D.A.I. was not discontinued because interest disappeared.

CurseForge's own statistics showed D.A.I. accelerating rapidly during this period.

The ecosystem grew from only a small number of early downloads into hundreds and then more than a thousand downloads across D.A.I.-related projects within a relatively short period.

D.A.I. Engine itself remained one of the strongest individual projects in that ecosystem.

Development also continued expanding into:

• Complete gameplay experiences
• Custom interfaces
• Datapack and resource-pack systems
• Creator tools
• JSON-driven actions
• Conditions
• Automation
• Recognition systems
• Custom screens
• Experience management
• Animation support
• Server-authoritative gameplay
• Persistent state
• World initialization
• Content distribution
• Modular D.A.I. addons

The project was still moving forward.

The distribution process was not.

What D.A.I. Became

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

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

That experiment grew into something much larger.

D.A.I. became a framework where creators could build:

• 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
• Server-authoritative gameplay
• Persistent game state
• Complete playable experiences

A menu button could run an action.

An action could evaluate conditions.

A condition could depend on what the player recognized.

A reaction could interrupt normal behavior.

An experience could control its own world, interface, progression, datapack, resource pack, and presentation.

JSON stopped being merely configuration.

JSON became gameplay.

D.A.I. was becoming a way to build games using Minecraft as the engine.

Why I Am Stopping Here

I am willing to fix bugs.

I am willing to rewrite systems.

I am willing to redesign APIs.

I am willing to spend ridiculous amounts of time debugging Minecraft.

What I am not willing to do is continue building releases when I cannot reliably determine:

• When they will become available
• Why they are being held
• What unpublished requirement I am expected to satisfy
• Whether a rejection concerns actual technical behavior
• Whether prior disciplinary history is influencing discretionary decisions
• Whether an appeal or independent review is available
• Whether a completed fix will simply enter another extended manual review

D.A.I. was built to remove unnecessary barriers between an idea and a playable experience.

Continuing to develop it under these conditions would mean accepting exactly the kind of barrier the project was designed to eliminate.

So I won't.

End of Development

D.A.I. Engine development ends here.

Not because the framework ran out of potential.

Not because development became technically impossible.

Not because players stopped downloading it.

I am ending it because continuing to build an actively developed framework around a distribution process I no longer consider dependable would be worse than ending the project cleanly.

Rather than leave D.A.I. permanently trapped between development and moderation:

I've decided to give it some mercy and put it out of its misery.

The existing CurseForge project, releases, screenshots, changelogs, and history remain as a record of what D.A.I. became during its development.

Thank you to everyone who:

• Downloaded D.A.I.
• Tested it
• Broke it
• Reported bugs
• Created something with it
• Built experiences around it
• Followed its development
• Watched the ecosystem grow
• Or simply wondered what the hell I was building

It was an experiment.

Then it became an engine.

Then it became an ecosystem.

And for a while, it showed just how far Minecraft could be pushed when JSON stopped being treated like configuration and started being treated like a programming layer for entire experiences.

That was D.A.I.

Decisions and Impulses.

Development Status: Discontinued.