How to Fix an FTB StoneBlock 2 Server That Keeps Crashing
FTB StoneBlock 2 drops the whole world underground on Forge 1.12.2 — no open sky, just a stone block to tunnel out from and build in. That design is part of what makes it fun, but it also means base-building and machine tick load end up packed into a much smaller chunk radius than a normal survival world, which is the root of most of the crashes and freezes reported on this pack.
See the FTB StoneBlock 2 pack page for the full RAM and setup breakdown before you chase anything else.
1. Wrong Java version for Forge 1.12.2
StoneBlock 2 runs on Forge for Minecraft 1.12.2, and 1.12.2-era Forge requires Java 8 — newer Java runtimes are a well-known source of startup crashes and odd class-loading errors on packs this old. If your server fails to boot at all, or dies within the first few seconds with no clear in-game cause, check the Java version the server process is actually using before looking anywhere else.
- Confirm the launch script or panel is pointed at a Java 8 JRE, not a newer default
- A clean boot that immediately exits is more often a Java mismatch than a mod conflict
2. Underground base concentrates tick load into a small area
Because StoneBlock 2 has no open world above the starting block, every player's base, farms, and machines end up stacked into a much tighter chunk footprint than a typical surface pack. Vanilla Minecraft's tick cost scales with how much is happening per chunk, so a StoneBlock base with the same number of machines as a spread-out base on another modpack will generally cost more server tick time per tick.
This usually shows up as the server getting progressively laggier as the group expands their underground build, rather than as a sudden one-time crash.
3. Tech mod power or auto-crafting networks growing unchecked
Tech mod integration is a core part of the StoneBlock 2 experience, and in 1.12-era packs like this one, large power networks and auto-crafting setups are a classic source of rising tick cost over time. A network that was small and cheap to process at the start of the world can become expensive to tick once it's expanded — without any config changing, just scale.
4. Config corruption or a conflicting mod edit after a manual change
If crashes started right after someone edited a mod's config file, added or removed a mod, or applied a tweak from a guide meant for a different pack version, that's the first thing to revert and retest. 1.12.2 Forge configs can fail silently or produce confusing downstream errors when a value is out of the range a mod expects, so a clean revert-and-reboot test is more reliable than trying to read the crash log for the real cause.
5. RAM under the pack's realistic floor
8 GB is the real floor for FTB StoneBlock 2, based on how the pack actually behaves once a base is established — not a generic Forge-pack estimate. Under-provisioning rarely produces an instant, clean crash. More often it looks like cascading lag and longer garbage-collection pauses as the underground base and tech networks grow, until the server finally hits a tick timeout and drops. If crashes correlate with how built-out the world has become rather than any specific action, RAM headroom is the first thing to check.
FAQ
Why does my StoneBlock 2 server lag more than a normal survival server with the same player count?+
Because the entire world is underground, all building and machine activity ends up concentrated inside a small chunk radius instead of spread across a normal-sized map. More tile entities, hoppers, pipes, and power network blocks packed into fewer chunks means a higher tick cost per chunk than you'd see on a surface-based pack with the same mod list.
The server was fine for weeks and now it's crashing or freezing — what changed?+
The most common cause in 1.12-era StoneBlock-style packs is that a tech mod's power or auto-crafting network grew past what it was when the world started. As players expand machine networks and automation, the per-tick cost of processing that network rises gradually, so the server can run fine for a while and then start hitting tick timeouts once a base crosses a certain size — without any single config change causing it.
Does StoneBlock 2 actually need 8 GB of RAM, or is that overkill for a small group?+
8 GB is the real floor we've seen hold up for StoneBlock 2, not a generic Forge-pack guess. Running it lower may boot fine and seem okay for a short test, but as players dig out more of the underground base and tech networks grow, memory pressure rises and you'll start seeing GC pauses before an eventual crash.
Host FTB StoneBlock 2 on hardware sized for its real floor
FTB StoneBlock 2 needs a genuine 8 GB floor to handle its chunk-concentrated tick load, and taking a backup before any risky config or mod change is the cheapest insurance against losing an underground base to a bad edit.
View Minecraft Hosting →