How to Fix a Kingdoms and Colonies Rebirth Server That Keeps Crashing
Kingdoms and Colonies Rebirth is a Forge 1.20.1 pack built around MineColonies settlement growth and diplomacy with procedurally-generated rival kingdoms — which means its crash profile looks less like a single bad mod and more like gradually rising tick cost as your world matures. Most reported crashes trace back to one of a small set of causes: a Java version mismatch at boot, colonist count outgrowing the server's tick budget, or kingdom AI load climbing as more rivals become active. This guide walks through each in order, then covers the RAM floor you actually need to stay ahead of it.
See the Kingdoms and Colonies Rebirth pack page for the full RAM and setup breakdown before you chase anything else.
1. Confirm the Java version before touching anything else
Forge 1.20.1 requires Java 17. If the server was set up manually, migrated from an older pack, or is running through a launcher profile that defaulted to an older JVM, this is the first thing to rule out — and it's the single fastest check on the list. A Java mismatch on Forge 1.20.1 tends to produce startup failures or crashes that look mod-related at a glance but are actually the JVM rejecting bytecode it can't run.
- Check the JVM version your server launcher is actually invoking, not just what's installed system-wide
- If you recently changed hosting providers or launch scripts, re-verify the Java path explicitly
2. MineColonies colonist count driving up tick cost
Once Java is confirmed correct, the next most common source of trouble is colony size. MineColonies pathfinding, building AI, and work-order processing scale with colonist count the same way they do on any other colony-building pack — a settlement with a handful of colonists ticks cheaply, but a settlement that's grown for weeks with multiple built-out colonies carries meaningfully more per-tick overhead.
If crashes or severe lag line up with colony growth rather than any specific action, this is the likely driver. Reducing concurrent active colonies, capping colonist count, or spacing settlements further apart can buy real headroom.
3. Rival-kingdom AI load as more kingdoms become active
The pack's procedurally-generated rival kingdoms simulate diplomacy and military conflict in the background, and that simulation adds ongoing tick cost that grows as more kingdoms become active — the same growth pattern seen on other kingdom-conquest packs. A server that was smooth early on can start showing lag spikes or crashes later simply because more kingdoms have spun up and are now actively simulating against each other, independent of anything the players are doing.
4. Mod conflicts and config corruption on a long-running world
If Java and tick-load causes are both ruled out, check for a corrupted config or a conflict introduced by a client-side change that doesn't match the server's mod list — this is a common long-tail cause on large Forge 1.20.1 packs generally. Compare the server's config folder against a known-good backup from before the problem started, and confirm every player is running the exact same modpack version rather than a locally modified copy.
5. RAM under the pack's realistic floor
The real floor for Kingdoms and Colonies Rebirth is 7 GB. Under-provisioning rarely shows up as an instant, clean crash — what you'll actually see is cascading lag as colonist count and active-kingdom count rise, longer and longer GC pauses as the heap gets squeezed, and eventually a tick timeout that takes the server down. If your crashes correlate with colony or kingdom growth rather than a specific action, check your allocated RAM against the 7 GB floor before assuming it's a mod bug.
FAQ
Why does my Kingdoms and Colonies Rebirth server crash only after a few weeks of play, not at launch?+
This is the most common pattern on colony-building packs. A fresh world has light tick load — a few colonists, one or two kingdoms. As your MineColonies settlement grows and more rival kingdoms activate their diplomacy and military AI, per-tick cost rises steadily. The crash usually isn't a sudden bug, it's the server slowly running out of tick budget until a watchdog or GC pause tips it over. If your server was fine for the first week and now lags or crashes under load, check colonist count and active kingdom count before anything else.
The server fails to even boot — what should I check first?+
Forge 1.20.1 requires Java 17 specifically. If your host or launcher is still pointed at an older Java runtime (common after a manual setup or an old launcher profile), the server will fail at startup with Forge-related errors that look unrelated to Java at first glance. Confirm the JVM version being used to launch the server before digging into mod-specific causes.
How much RAM does Kingdoms and Colonies Rebirth actually need?+
The real floor for stable play is 7 GB. That's higher than what you'd guess from the base modlist alone, because MineColonies pathfinding and the procedurally-generated rival-kingdom simulation both add ongoing memory and tick pressure as the world ages — a number sized for day-one play will eventually fall short once colonies and kingdoms scale up.
Host Kingdoms and Colonies Rebirth on hardware sized for its real floor
Run Kingdoms and Colonies Rebirth on a plan built around its real 7 GB floor, and take a backup before any risky change — like a colonist cap or a config rollback — so a bad fix never costs you the world.
View Minecraft Hosting →