How to Fix a ModernCraft (Distant Horizons) Server That Keeps Crashing
ModernCraft (Distant Horizons) is a Fabric pack for Minecraft 1.21.1 built around Distant Horizons and Iris Shaders, with a deliberately minimal mod list beyond that visual layer so the extended render distance and lighting stay the focus. That thin mod list is actually good news for crash-hunting: most server crashes on this pack trace back to environment issues — the wrong Java version, a client-only mod in the wrong folder, or RAM sizing — rather than a tangle of mod interactions.
See the ModernCraft (Distant Horizons) pack page for the full RAM and setup breakdown before you chase anything else.
1. Check your Java version first
Fabric on Minecraft 1.21.x requires Java 21. If your server fails to launch at all, or dies within the first few seconds with no meaningful world activity, this is the first thing to rule out — not a mod conflict. Running an older Java runtime (left over from a previous pack or a default host image) is one of the most-reported causes of an immediate boot failure on 1.21.1 packs.
- Confirm the server is launching with Java 21, not an inherited Java 17 or 8 runtime
- A clean boot failure with no world-generation activity in the log points here before anywhere else
2. A client-only visual mod ending up in the server's mods folder
Distant Horizons' LOD rendering and the Iris shader integration are primarily client-side visual features. The server-side half is intentionally light. If you or a player dropped a client-only jar (a shader pack companion, a visual tweak mod) into the server's mods folder instead of the client's, that's a common way to get a server-side crash that looks like it's coming from the rendering stack — the same pattern you see with shader-adjacent mods on other packs when they're miscategorized as server mods.
3. Rule out mod interactions before assuming there are any
Because ModernCraft (Distant Horizons) keeps its mod list deliberately minimal outside the Distant Horizons/Iris visual layer, classic mod-vs-mod crash chains are less likely here than on a heavy tech or kitchen-sink pack. If you've confirmed Java 21 and checked for stray client-only jars, the next most productive step is usually environment — RAM and disk — rather than digging through mod compatibility threads.
4. Corrupted LOD/chunk data after an abrupt shutdown
Distant Horizons maintains its own LOD data alongside the normal world save. A hard crash, a forced stop, or running out of disk space mid-write can leave that LOD data or a region file in a partially-written state, which can then throw errors on the next boot as the server tries to read it back. If crashes started right after an unclean shutdown rather than out of nowhere, this is worth checking before assuming a fresh mod issue.
5. RAM under the pack's realistic floor
8 GB is the real floor for a ModernCraft (Distant Horizons) server. Going below that doesn't usually produce a clean, instant crash — it shows up first as rising lag and longer garbage-collection pauses as LOD and chunk data churn under memory pressure, and only escalates into an actual crash once the server hits a tick timeout. If your crashes correlate with more players exploring further out (and therefore more LOD chunks being generated and held in memory), undersized RAM is the first thing to check, ahead of any mod or config theory.
FAQ
Why does my ModernCraft (Distant Horizons) server fail to boot right after an update?+
The most common cause is a Java version mismatch. Fabric on Minecraft 1.21.1 requires Java 21 — if your server is still running Java 17 or earlier from an older pack, the server will fail at startup or crash almost immediately. Check your runtime's Java version first before looking at mods or configs.
Does Distant Horizons itself run on the server, or is it a client-side mod?+
Distant Horizons' LOD (level-of-detail) rendering and Iris shader support are primarily client-side visual features. The server-side component is lightweight by design, so if you're seeing a server crash tied to rendering or shader behavior, the usual culprit is a client-only jar that accidentally ended up in the server's mods folder rather than Distant Horizons itself misbehaving server-side.
How much RAM does a ModernCraft (Distant Horizons) server actually need?+
8 GB is the real floor for this pack. Because the mod list is deliberately minimal beyond the visual layer, the RAM pressure here comes mostly from world generation and chunk/LOD data turnover rather than a large mod stack — but going below 8 GB still produces the same symptoms as any under-provisioned server: rising GC pauses, lag, and eventually a tick timeout.
Host ModernCraft (Distant Horizons) on hardware sized for its real floor
This pack's real floor is 8 GB RAM, and running a backup before any shader, mod, or config change keeps a bad update from turning into a lost world.
View Minecraft Hosting →