How to Fix a Medieval Horizons Server That Keeps Crashing
Medieval Horizons is a medieval Vanilla+ pack built on Fabric for Minecraft 1.21.1, designed around Distant Horizons' massive-render-distance LOD terrain, paired with performance mods, shaders, and medieval aesthetic additions. Its crash patterns are different from a heavy Forge kitchen-sink pack — Fabric modlists are generally lighter and less conflict-prone, so most server crashes here trace back to the Java version, a stray client-only mod, or RAM rather than mod-on-mod conflicts.
See the Medieval Horizons pack page for the full RAM and setup breakdown before you chase anything else.
1. Check the Java version before anything else
Fabric on Minecraft 1.21.1 requires Java 21. If the server process is still launching under an older Java runtime — a leftover 8, 11, or 17 install from a previous pack — it will typically fail to boot entirely, or throw class-loading errors almost immediately. This is the first thing to verify on any fresh install or any crash that happens within seconds of starting the server.
- Confirm the startup script or panel is pointing at a Java 21 binary
- A clean, immediate crash on boot (not mid-session) is the classic symptom of a Java mismatch
2. A client-only Distant Horizons or shader mod in the server mods folder
Distant Horizons' LOD rendering and the pack's shader support are primarily client-side visual features. If one of these ends up copied into the server's mods folder — which can happen during a manual pack setup or an incomplete server-pack export — it can cause the server to crash in the same way shader mods do on other modpacks: the mod expects a rendering context that doesn't exist server-side.
If your server mods folder was assembled by hand rather than from an official server-pack export, this is worth checking directly against the pack's documented server-side mod list.
3. Gradual lag before the crash, not an instant one
Because this is a lighter Fabric pack rather than a Forge kitchen-sink, a crash that follows a period of normal play is less likely to be a sudden mod conflict and more likely to be resource pressure building up — more terrain loaded, more entities tracked, memory slowly filling. If you notice rising lag or delayed world updates in the minutes before a crash, treat it as a RAM or garbage-collection symptom rather than a mod bug.
4. Config corruption after a bad shutdown
A server that was force-stopped or crashed mid-save can leave a mod's config or world data in a partially-written state, which then causes the next boot to fail or crash shortly after startup. If a crash started happening only after a previous hard stop or power interruption, restoring from a known-good backup is usually faster and safer than trying to hand-edit the corrupted file.
5. RAM under the pack's realistic floor
The real floor for Medieval Horizons is 6 GB. Under-provisioning rarely produces a clean, instant crash — what actually happens is cascading lag and longer garbage-collection pauses as the server struggles to keep up with Distant Horizons' LOD terrain and world state, which eventually trips a tick timeout and takes the server down. If your crashes correlate with more players online or more terrain explored rather than a specific action, check your allocated RAM against the 6 GB floor before anything else.
FAQ
My Medieval Horizons server won't boot at all — where do I start?+
Check the Java version first. Medieval Horizons runs on Fabric for Minecraft 1.21.1, which requires Java 21. If the server is still pointed at an older Java runtime (8, 11, or 17), it will fail to launch or crash immediately on startup. This is the single most common cause of a boot failure on this pack.
The server crashes but it worked fine for a few minutes first — is that still a Java issue?+
Usually not. A crash that happens after the server has been running for a while — especially during exploration or when more terrain loads — points toward RAM pressure rather than a Java mismatch. Watch for the server slowing down (growing lag, delayed chunk loads) in the minutes before the crash, which is the signature of memory exhaustion rather than a clean startup error.
Could a client-only mod be causing server crashes on this pack?+
Yes, and it's worth checking. Distant Horizons' LOD rendering and the pack's shader support are primarily client-side visual features. If a client-only visual mod from the pack ends up sitting in the server's mods folder (rather than being correctly excluded as client-side), it can throw the server into a crash loop the same way shader mods do on other modpacks. Compare your server's mods folder against the pack's official server-side mod list if you're unsure.
How much RAM does Medieval Horizons actually need?+
The real floor is 6 GB. Fabric modlists tend to be lighter than Forge kitchen-sink packs, but Distant Horizons' LOD terrain generation and rendering support still add meaningful memory overhead on top of the base world. Going below 6 GB tends to produce slow degradation rather than a crash on launch.
Host Medieval Horizons on hardware sized for its real floor
Medieval Horizons needs a real 6 GB RAM floor to handle Distant Horizons' terrain load without cascading lag, so provision for that from day one and take a backup before any mod or config change in case you need to roll back.
View Minecraft Hosting →