
Feed The Beast has been synonymous with modded Minecraft for over a decade, and with the release of FTB StoneBlock 4 for Minecraft 1.21.1 on NeoForge, they've delivered one of the most technically ambitious underground survival experiences ever created. Forget the sky. Forget sunlight. In StoneBlock 4, the entire world is solid stone, and you must dig, automate, and engineer your way through handcrafted vaults powered by the mysterious "World Engine."
If you're researching how to host FTB StoneBlock 4, you've likely already discovered that this is not a casual modpack. It has strict technical requirements, including a configuration detail that trips up the majority of first-time administrators. In this guide, we'll cover everything you need to know to get StoneBlock 4 running flawlessly.
The Critical Setting Most Admins Miss
Let's address the single most common issue first, because it saves you hours of frustration:
FTB StoneBlock 4 absolutely requires
enable-command-block=truein yourserver.propertiesfile.
The pack's progression system, vault triggers, and World Engine mechanics rely on command blocks embedded within the handcrafted structures. If command blocks are disabled (which is the default setting in vanilla Minecraft), entire progression paths will silently break. Quests won't trigger. Vaults won't open. And the console won't throw an obvious error-the pack simply won't function correctly.
After your first server boot, immediately stop the server and verify:
# server.properties - CRITICAL for StoneBlock 4
enable-command-block=true
This single line is the difference between a functional server and hours of bewildered debugging.
Server Requirements
FTB officially recommends a minimum of 8GB of RAM for StoneBlock 4. Based on real-world testing, here is a more nuanced breakdown:
| Player Count | RAM | CPU | Storage | Notes |
|---|---|---|---|---|
| 1-4 players | 8GB | 3.5GHz+ | 40GB NVMe | FTB minimum recommendation |
| 5-10 players | 8-10GB | 4.0GHz+ | 60GB NVMe | Comfortable for vault exploration |
| 11-20 players | 10-14GB | 4.2GHz+ | 80GB NVMe | Heavy automation + vaults |
| 20+ players | 14-18GB | 4.5GHz+ | 100GB+ NVMe | Dedicated infrastructure recommended |
Why Underground Packs Are Deceptively Heavy
You might assume that a pack set entirely underground-with no sky rendering, no weather, and no biome diversity-would be lighter on resources than an overworld pack. This is a common misconception.
StoneBlock 4's underground world is dense with:
- Handcrafted Vault Structures: These are large, complex structures loaded with spawners, loot tables, and command block logic. When a player enters a vault, the server must simultaneously process entity spawns, loot generation, and command execution.
- The World Engine: The pack's central mechanic involves a progression system that dynamically modifies the world. This adds persistent server-side calculations that run continuously in the background.
- Automation Density: Because players cannot simply spread out across a vast overworld, all bases tend to be concentrated in a relatively small area. This means the server must process an extremely dense concentration of tile entities (machines, pipes, cables) within a compact chunk radius.
Step-by-Step Server Setup
1. Obtain the Server Pack
FTB distributes its packs through the official FTB App and CurseForge. Download the StoneBlock 4 server files:
mkdir stoneblock4 && cd stoneblock4
# Extract the downloaded server pack
unzip FTB-StoneBlock-4-Server-[VERSION].zip
2. Install Java 21
StoneBlock 4 runs on NeoForge for 1.21.1, which mandates Java 21:
sudo apt install openjdk-21-jdk -y
java -version
3. Configure Startup Flags
Create a start.sh with Generational ZGC tuning:
#!/bin/bash
java -Xms8G -Xmx8G -XX:+UseZGC -XX:+ZGenerational -XX:+AlwaysPreTouch \
-XX:+DisableExplicitGC -XX:+PerfDisableSharedMem \
-jar forge-[VERSION]-shim.jar nogui
chmod +x start.sh
4. First Boot and Configuration
echo "eula=true" > eula.txt
./start.sh
Wait for the initial world generation to complete (this may take 5-10 minutes). Then stop the server and configure server.properties:
# CRITICAL - StoneBlock 4 will not function without this
enable-command-block=true
# Performance tuning for underground packs
view-distance=8
simulation-distance=6
network-compression-threshold=256
Restart the server. StoneBlock 4 is now fully operational.
5. Verify Command Blocks
After joining the server, test that the World Engine and vault mechanics are working. If quests appear but don't trigger rewards, or if vault doors don't respond, double-check that enable-command-block=true is set and the server was fully restarted after the change.
The Infrastructure Behind the Underground
StoneBlock 4's concentrated base density creates a unique hosting challenge. Unlike sprawling overworld packs where players spread across thousands of blocks, StoneBlock players build within a tight radius. This means the server must process an enormous number of tile entities and command block executions within a very small number of chunks.
This concentrated load punishes weak CPUs and slow storage drives mercilessly. When a group of players simultaneously triggers a vault event while their factories are running at full capacity, only a high-frequency processor can keep the TPS stable.
Space-Node's VPS plans, powered by AMD Ryzen processors with NVMe storage, are specifically designed to handle this concentrated processing demand. Our 8GB+ plans provide the exact hardware profile that FTB officially recommends, ensuring that the World Engine runs smoothly and every vault opens exactly when it should.
