FAQ

Why Does Nothing Change in Game After Installing the Mod?

The mod only provides the framework, generic items, slots, HUD and commands; it contains no realm values, abilities or recipes. You need a datapack or content pack (including content written with KubeJS) before real gameplay appears. Start with the Datapack overview and look up an individual registry in JSON Data Formats.

What Dependencies Are Required?

Jupiter and ApricityUI are required dependencies, and every other required dependency is bundled inside the mod. KubeJS is only needed if you want to register content from scripts. JEI and Jade are optional compatibility mods, and the game works fine without them. See Installation for the exact versions.

How Do I Switch a Piece of Content Off Temporarily?

Write a NeoForge resource condition into the definition file itself; an entry whose condition does not hold does not enter the registry, so nothing reads it and it never shows up in command completion either:

{
  "neoforge:conditions": [
    { "type": "neoforge:never" }
  ]
}

WARNING

An entry whose condition does not hold is the same as a definition that was never written, and a holder reference pointing at it fails to decode along with it. There is no middle state where the definition stays around, stops taking part in gameplay and can still be referenced by others.

Why Does /reload Not Apply My Edit?

MiXianTu's registries are native Minecraft data pack registries, and Minecraft reads them while the world loads. /reload only refreshes recipes, loot tables, advancements, functions and the KubeJS server scripts, so it never re-reads a MiXianTu registry.

To apply an edit, load the world again: in single player, leave to the title screen and open the world again; on a server, restart it. A file that cannot be decoded prevents the world from loading until it is fixed, because the registries keep no previous snapshot. See Loading, Syncing and Debugging.

Why Does a Formula Fail Only in My Development Environment?

A formula problem that the codec can already see while the data pack is parsed — a malformed expression, a bad params entry, an empty weighted list — is a decode error. The loader collects every failing entry and reports them together, and the load fails with its usual aggregated error, so you see all broken formulas at once rather than only the first one. That part behaves the same in development and in production.

Problems that only show up when a formula is evaluated — a name no variable provides, a name the current context cannot supply such as realm_rank in an ability formula, a variable that produces NaN or a variable that throws — are reported at runtime instead, because nothing can know them earlier. To keep the log clean, production silences them, while a development environment logs the whole error, including the exception and its stack trace, and keeps evaluating with 0. See Formula Variables.

Can I Make My Own Content Pack and Distribute It?

You can build content packs on this framework, and distributing them is not restricted in any way.

License

The mod's code and assets are All Rights Reserved, and commercial distribution (such as a paid server) requires extra permission — see LICENSE for details.

Where Can I Edit Datapacks Without Writing JSON by Hand?

The Datapack Visual Editor edits this mod's datapacks in the browser as a form, with field descriptions and registry completion.

Or hand these docs to an AI and use them as a skill.

Where Can I Ask Questions?

Join our Discord to discuss.