Skip to content

The Four Modules

LlaGuiTo edited this page Oct 5, 2026 · 1 revision

The Four Modules

Applies to the 26.2 line. On 26.1.2 all of this is one mod called utility_core.

Why the split

Until 2.0.0-beta.1 Utility Core was a single mod with everything in it. It was split into independent mods so you can install only the parts you actually want — most servers want the crash guards and none of the client conveniences.

The split is also where the licence changed from All Rights Reserved to MIT.

The four

Module Mod id Classes What it is
Admin utility_core_admin 21 Server administration.
Fixes utility_core_fixes 16 Crash guards and compatibility patches.
QoL utility_core_qol 52 Client and gameplay quality of life.
HUD utility_core_hud 7 A configurable overlay.

They share a repository and a build, but not a dependency: install any combination, including one module alone. The 96 classes across the four are what replaced the 31-class monolith.

Admin — utility_core_admin

Server administration. Installs server-side only.

  • Automatic Chunk Pregeneration (ChunkGen) — pre-generates chunks in a spiral pattern while the server is empty, so the first players in do not generate terrain in front of everyone else.
  • Spawn Zone Protection — the spawn schematic area becomes unbreakable, unplaceable, explosion-proof and free of natural mob spawns. Useful when the schematic has no lighting of its own.
  • Server Rules Manager — enforces a curated list of game rules from a JSON file, applying only the ones that differ from the server's current value.
  • Spawn Schematic (opt-in) — pastes a WorldEdit/FAWE .schem at world creation centred on (0,0), protects the area permanently, and sets world spawn inside the structure.
  • Data Pack Folder (opt-in) — loads every datapack in <game-directory>/datapacks into every world automatically, on dedicated servers and single-player alike.

Fixes — utility_core_fixes

The crash guards. Server-side, and the one module most servers want.

  • Negative Damage Safety — negative damage from mod interactions, such as Apothic Attributes combined with Tombstone, is clamped to 0. Without this it crashes the server.
  • Corail Tombstone Compatibility — GUI scale fix, item NBT initialisation fix, and mixin error suppression.
  • OutpostZero Damage Cap — limits infection damage so it cannot kill you outright before the death event has had a chance to fire. Without the cap the death never registers.
  • Return portal data handling.

QoL — utility_core_qol

The largest module by class count, and the one that mostly runs client-side.

  • Recipe Conflict Resolution — when several crafting recipes match the same ingredients, a selector appears in the crafting table. Click an alternative to get the result you wanted. Without it the game silently picks one and you get the wrong item with no explanation.
  • Biome/Dimension Titles — a title on screen when you enter a new biome or dimension. Ported from Traveler's Titles by YUNGNICKYOUNG.
  • Bridging — a bridging assistance feature with configurable adjacency, its own key mappings, and crosshair tweaks.

HUD — utility_core_hud

A configurable overlay — the smallest module, and entirely client-side.

  • HudOverlay / HudRenderer — the overlay itself.
  • HudMenuScreen and HudPositionEditorScreen — a menu and a drag-to-position editor, so you can place it wherever you want rather than accepting a fixed spot.

Which combination

If you are… Take
Running a public server Fixes — the crash guards are the point.
Playing on a server QoL — the recipe selector and the titles.
Preparing a world Admin — chunk pregeneration and spawn protection.
Wanting an overlay HUD, on its own, if that is all you need.

All four together is a valid install. Most people do not want all four.

The root project is not a mod

The repository root builds the four modules and holds shared resources only — the icon, the en_us lang file, utility_core.mixins.json and the access transformer. Its gradle.properties carries mod_id = utility_core_fixes and mod_name = Utility Core Fixes, which is a leftover from before the split and does not mean the root produces a fifth JAR. Look at settings.gradle for the real module list.

Clone this wiki locally