Compatibility

Compatibility

Applies to Utility Core across both lines.

Loaders

Loader	Supported
NeoForge	Yes
Fabric	No
Forge	No

Java 25.

Dependencies

None. Nothing is required to install any module.

Side

Almost everything is server-side:

Module	Server	Client
utility_core_admin	yes	no
utility_core_fixes	yes	no
utility_core_qol	partly	yes
utility_core_hud	no	yes

utility_core_fixes does nothing useful on a client — the crash guards protect the server. Installing it client-side is harmless but pointless.

Mods it patches or interacts with

Referenced in the fix names and code, and required by nothing:

• Apothic Attributes and Tombstone — the negative damage combination that crashes the server.
• OutpostZero — infection damage that could kill before the death event fires.
• Curios / Regalia Slots API — the loot predicate fix.
• Evilcraft — the broom vehicle in the anti-cheat whitelist.
• Traveler's Titles by YUNGNICKYOUNG — the title logic is ported from it, LGPL-3.0.

None of these is a dependency. Every patch is inert when its target is absent.

WorldEdit / FAWE

The Spawn Schematic feature pastes a .schem file. It does not require WorldEdit or FAWE at runtime — it reads the file format directly — but it expects a schematic produced by one of them.

Content added

None. No items, no blocks, no recipes, no world generation. There is nothing to clean up on uninstall and saves are untouched.

Version support

Minecraft	Line	Shape
26.1.2	1.x	one mod, utility_core
26.2	2.x	four modules

There is no 1.x build for 26.2, and no 2.x build for 26.1.2. The split happened on the 26.2 line; 26.1.2 stayed on the monolith. If you need the single-mod experience on 26.2, it does not exist — use the modules. See The Four Modules.

The licence differs between lines

Line	Licence
1.x (26.1.2 and older)	All Rights Reserved
2.x (26.2 modules)	MIT

The change came with the split, in commit fb540de — "v2.0.0-beta.1: Split monolithic Utility Core into 3 independent mods". Both branches now ship a LICENSE file matching their declared mod_license, which they did not before.

If you are vendoring or redistributing, check which line you are dealing with: the terms are genuinely different.

Known gaps

• The root project's gradle.properties is misleading. It says mod_id = utility_core_fixes and mod_name = Utility Core Fixes, but the root only holds shared resources — it does not build a fifth JAR. settings.gradle is the authoritative module list.
• No per-module README. Each of the four modules is undocumented in the repository; the documentation for all of them is in the root README.md.
• The root README.md describes the pre-split mod. Its feature list covers all four modules and is still titled "Utility Core", so it overstates what any single module does.