Configuration

Configuration

Applies to the 26.2 modules. On 26.1.2 a single utility_core covers all of it.

Two ways to configure

Either works, and they stay in sync:

• the in-game config menu, or
• config/utility_core-common.toml on disk.

Most options are booleans that switch one fix on or off, and all default to on for the safety features. There is nothing you need to change.

Per-module configs

The four modules each own their own config class:

Module	Config class
utility_core_admin	AdminConfig
utility_core_fixes	FixesConfig
utility_core_qol	BridgingConfig
utility_core_hud	HudConfig

Installed together they share config/utility_core-common.toml; each remains independently configurable.

Fixes — the crash guards

FixesConfig is the one worth reading, because every option is a guard you can turn off:

Option	Default	What it prevents
enableNegativeDamageFix	on	Negative damage from mod interactions — the Apothic Attributes + Tombstone server crash
enableOutpostZeroDamageCap	on	Infection damage killing you before the death event fires
enableTombstoneGuiScaleFix	on	Tombstone GUI rendering at the wrong scale
enableTombstoneItemInitFix	on	Tombstone items getting their NBT initialised wrongly
enableTombstoneErrorHandler	on	The mixin errors the Tombstone combination produces
enableBlockentityMismatchFix	on	Block entity mismatch errors from inconsistent mod data
enableCuriosLootPredicateFix	on	Loot that should drop not dropping, via the Curios predicate path
enableVehicleAntiCheatWhitelist	on	Anti-cheat moved too quickly spam for vehicles
enableNetherReturnPortalFix	on	Return portals routing you to the wrong paired portal

The vehicle whitelist deserves a note. Vanilla's moved too quickly check misfires on vehicles that are supposed to move fast — the documented case being an Evilcraft broom — and spams the log. The whitelist takes namespace:path entries and defaults to ["evilcraft:broom"].

Turning off enableNegativeDamageFix on a public server is how you get a crash. Nothing else in this list has that consequence.

Admin

Option	Default	What it does
enableSpawnSchematic	off	Enables pasting your .schem at world creation.

The schematic itself is not bundled. Even enabled, nothing happens until you place a file at:

<game-directory>/utility_core/spawn_schem/schematic_spawn.schem

There is no startup warning about a missing file. If the spawn schematic does not appear, check the path before checking anything else.

The chunk generator and the server rules manager are managed separately — the rules manager reads its list from a JSON file rather than from a config toggle.

QoL

Bridging — BridgingConfig covers adjacency rules, the key mappings and the crosshair behaviour.

Recipe selector — the maximum number of shown recipes is configurable, so a pack with many conflicting recipes for the same ingredients cannot bury you in selector buttons. Lower it if the selector becomes unwieldy.

Titles — the biome/dimension title behaviour.

HUD

HudConfig covers the overlay. Position is set by dragging in the position editor screen rather than by editing a coordinate, so there is no position option in the config to look for.

The 1.x config

On 26.1.2 the single mod uses config/utility_core-common.toml with one combined set of options — the same filename the 26.2 line uses, which is worth knowing if you move between them.

Because the split redistributed features across four modules, an old 1.x config does not map one-to-one onto the 26.2 modules. Expect to set the module configs rather than migrating the file.