iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
For an RLCraft 2.9 dedicated server, start with the compatibility settings below, then tune distance values against your machine’s tick time and memory use. The important baseline is not a single “low-lag” preset: command blocks, flight permission, watchdog behavior and Hard difficulty affect whether RLCraft works correctly, while view distance, simulation distance, RAM and pregeneration determine how much work the server must do.
enable-command-block=true
allow-flight=true
max-tick-time=-1
difficulty=3
view-distance=6Use 4 GB as the installation guide’s starting RAM allocation, leave headroom for the operating system, and increase resource limits only after monitoring demonstrates a need. Keep normal survival-generation properties enabled unless your server has a deliberate policy that requires something else.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minute| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Minecraft | Java & Bedrock Deluxe Collection | Windows Digital Code | $39.99 | Buy on Amazon |
| 2 |
|
Minecraft | Java & Bedrock Ultimate Collection | Windows Digital Code | $49.99 | Buy on Amazon |
| 3 |
|
Minecraft | Standard Edition | XBOX Digital Code | $19.99 | Buy on Amazon |
| 4 |
|
Minecraft | $6.99 | Buy on Amazon |
| 5 |
|
Minecraft - Bedrock Edition PS4 | $42.98 | Buy on Amazon |
Recommended RLCraft 2.9 baseline
Stop the server before editing server.properties, make a backup of the file, and use this as the first configuration for a new or existing RLCraft 2.9 world:
enable-command-block=true
allow-flight=true
max-tick-time=-1
difficulty=3
view-distance=6These values address RLCraft-specific compatibility first and performance second. A distance of 6 is deliberately conservative for a modded server. Once the world is stable, raise it in small steps only when CPU, memory and tick behavior remain acceptable.
#1 Best Overall
- DELUXE COLLECTION — Includes Minecraft: Java & Bedrock Edition, three Bedrock add-ons, three exclusive Character Creator items, and 700 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
| Property | Starting value | What it controls | Why RLCraft servers use it |
|---|---|---|---|
enable-command-block |
true |
Whether command blocks execute | The RLCraft 2.9 wiki says this must be enabled for structures to generate correctly and for villager spawns to be present. |
allow-flight |
true |
Whether the server’s movement checks permit flight | Flying mounts and fairy-ring mechanics can otherwise trigger false flight kicks. |
max-tick-time |
-1 |
Watchdog timeout for a server tick | Long structure-generation operations and terrain pregeneration are less likely to be terminated by the watchdog. |
difficulty |
3 |
World difficulty, where 3 is Hard | RLCraft is balanced around Hard difficulty. |
view-distance |
6 |
World data sent to each client | It limits network and chunk work while providing a practical starting point for a heavily modded server. |
Do not treat max-tick-time=-1 as a performance boost. It disables the watchdog’s automatic termination of an overlong tick, so a stalled process can remain stalled instead of being restarted. Use it because RLCraft’s generation tasks can legitimately run long, and supervise the server during generation and maintenance.
RAM and Java startup settings
The RLCraft installation guide recommends allocating 4 GB of RAM. That is a starting allocation, not a promise that every player count or modpack workload will fit comfortably. More memory is not automatically better: the guide warns that allocating more can introduce Java memory-leak problems.
Free tools Windows power users keep installed
One-click scans. No signup required.
Set a realistic heap
Configure the Forge server wrapper or launch script with Java -Xms and -Xmx values that fit the host. Keep those values consistent with the machine’s available memory. Editing server.properties cannot repair an undersized JVM, and raising the heap cannot compensate for a weak single-thread CPU or excessive chunk distance.
- Begin near the documented 4 GB allocation.
- Reserve memory for the operating system, Java overhead, backups, monitoring and any other services on the host.
- Do not assign all physical RAM to Java; doing so can cause swapping or leave no room for the operating system.
- Change the allocation only after observing heap usage, garbage-collection pauses, crashes or sustained memory pressure.
- If a wrapper exposes separate initial and maximum heap values, set them deliberately rather than allowing unrelated defaults to oversubscribe the machine.
What RAM does and does not fix
Additional heap can provide room for loaded chunks and mod data, but it does not make each server tick execute faster. RLCraft’s terrain generation, entity processing and block-entity work can be limited by one busy CPU thread even when free memory is abundant. Conversely, reducing distance settings may resolve lag without changing the heap at all. Diagnose the limiting resource before changing Java arguments.
Rank #2
- ULTIMATE COLLECTION — Includes Minecraft: Java & Bedrock Edition, five Bedrock add-ons, five exclusive Character Creator items, and 1000 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
View distance and simulation distance
view-distance determines how much world data the server sends to each client. A higher value can make more terrain visible but increases chunk loading, generation, memory use and network traffic. A lower value reduces work but can make the visible world feel smaller.
simulation-distance, when the server version exposes it, controls how far active ticking occurs. Mobs, redstone, crops and block entities outside that radius may not update in the same way they do near a player. It is therefore a different control from view distance: one mainly affects what clients receive, while the other affects how much of the world remains active.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallA safe tuning sequence
- Start with
view-distance=6and the server version’s available simulation-distance setting. - Join with the largest expected number of concurrent players, travel through unexplored terrain and perform normal RLCraft activities.
- Watch tick time, CPU utilization, heap use, garbage-collection pauses and the server log while players explore.
- If ticks remain stable and the host has spare capacity, raise view distance by a small increment, restart if the server requires it, and repeat the same workload.
- If mobs or block entities create lag, lower simulation distance before sacrificing visible terrain; if exploration causes spikes, lower view distance or pregenerate the area.
- Keep the lowest values that preserve the experience your group actually expects. There is no universal optimum for every host, player count or world.
Choosing a view-distance target
| Scenario | Practical starting choice | When to test a higher value |
|---|---|---|
| Small private server or uncertain hardware | 6 |
Only after exploration and normal combat remain tick-stable. |
| Powerful host with few players | 6, then test 8 |
Increase to 8 when CPU, memory and network headroom remain available. |
| High-visibility preference on a proven host | Test 8, then 10 |
Use 10 only if the actual workload remains stable; community notes that use 8–10 are workload-dependent, not guarantees. |
Community configurations commonly choose 6 for performance, while other RLCraft notes use 8–10 for visibility or compatibility. Those figures describe different workloads. Player count, unexplored terrain, pregeneration status, CPU single-thread performance and simulation settings matter more than the number by itself.
Properties to keep enabled for normal survival
After applying the RLCraft-specific baseline, review the other entries in the file. The following choices match a conventional authenticated RLCraft survival server:
Rank #3
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that is unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world full of surprises.
- SURVIVAL ADVENTURES — Face mysterious foes, travel across varied landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play solo or join friends in local split-screen and cross-platform play across console, mobile, and PC. Online multiplayer supports up to 8 players.
- COMMUNITY PLAY — Connect with players on community servers, or subscribe to Realms Plus (sold separately) to play with up to 10 friends on a private server.
| Property | Normal survival choice | Reason and qualification |
|---|---|---|
online-mode |
true |
Use authenticated accounts on public or private servers unless you operate a specific, controlled offline-mode architecture. |
generate-structures |
true |
Allows the world’s structures to generate; disabling it changes the intended survival world. |
spawn-monsters |
true |
Preserves hostile-mob gameplay and RLCraft’s expected progression. |
spawn-animals |
true |
Preserves passive animal spawns. |
spawn-npcs |
true |
Preserves villager and other non-player-character spawning. |
max-players |
Set to the actual group size | Avoid an unnecessarily high advertised cap that encourages a workload the machine cannot sustain. |
These are policy and gameplay settings as much as performance settings. For example, lowering the player cap can protect a small machine, but disabling structures or mobs to hide a capacity problem changes the modpack rather than tuning it.
How to apply the settings safely
- Shut down the Forge server cleanly and wait until the process exits. Do not edit the file while the server is writing it.
- Copy
server.propertiesto a dated backup location. Keep the world backup separate as well. - Open the file as plain text. Change only the keys you intend to change; retain one
key=valuepair per line. - Insert or replace the five baseline entries and review the survival entries in the tables above.
- Save the file as plain text without adding quotation marks, spaces around the equals sign or a second extension such as
.txt. - Start the server with the same Forge wrapper and Java heap allocation you normally use.
- Read the startup log for malformed-property errors, missing mods, watchdog messages or world-generation exceptions before allowing players to connect.
- Test with one operator account, then with the expected player count. Check a structure, a villager area, a flying mount and unexplored terrain before declaring the configuration stable.
Pregenerating terrain
Pregeneration moves some chunk-generation cost out of live exploration. That can reduce the sudden lag a player experiences when entering unexplored terrain, but it is CPU- and memory-intensive and can consume substantial storage and time.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →RLCraft guidance recommends max-tick-time=-1 for pregeneration so long generation tasks are not terminated by the watchdog. Run the operation during a maintenance window, keep players out of the world, and monitor CPU, memory, disk activity and the server log. A watchdog disabled during an unattended job can leave a process hung, so have a way to stop and restart it if progress ceases.
Operational checklist
- Back up the world before generating a large area.
- Choose a radius that matches where players will actually travel; generating an enormous unused region wastes resources.
- Schedule the job when player demand is low.
- Watch free disk space as generated region files accumulate.
- After completion, restore normal player access and test exploration outside the generated boundary.
- Continue periodic server restarts as recommended by the RLCraft documentation. No universal restart interval is published, so choose one from observed uptime, memory behavior and your maintenance window.
Troubleshooting common RLCraft server problems
Structures do not generate or villagers are missing
Check enable-command-block=true first, then confirm that generate-structures=true and spawn-npcs=true were not disabled. Test in newly generated chunks; changing a property cannot retroactively add a structure to terrain that was already created. If the problem continues, inspect the Forge and RLCraft logs for generation errors rather than repeatedly changing distance values.
Rank #4
- Skins! We have biome settlers, city folk, town folk, and more!
- The Nether and all its inhabitants. Fight Ghasts and make friends with Pigmen
- Cross platform play for up to five players between Pocket Edition and Windows 10
- Revamped touch controls, controller support, and a controller mapping screen
- Enhanced Weather effects! Accumulating snow and more
Players are kicked when using a flying mount
Verify allow-flight=true. RLCraft’s flying mounts and fairy-ring mechanics can look like unauthorized flight to the server’s movement checks when this property is false. Reconnect after restarting the server and test the same mount in a safe area.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →The server freezes during exploration or pregeneration
Long generation work can exceed the watchdog timeout. RLCraft’s baseline uses max-tick-time=-1 to prevent termination, but that setting does not reduce the work. Check whether the process is still consuming CPU and writing progress. If it is stalled, stop it safely, restore a backup if the world was damaged, and reduce the generation scope or distance workload before trying again.
Players see terrain slowly or experience chunk stalls
Lower view-distance to 6 if it has been raised, reduce simulation distance when available, and test again while exploring new chunks. If the machine is swapping, reduce the Java heap only with care and leave more memory for the operating system; if the heap is genuinely exhausted, increase it only within the host’s limits. Do not judge the fix from an already loaded area alone, because live generation is usually the heavier test.
Mobs, crops or machines update too far away or too slowly
Review simulation-distance separately from view distance. A lower simulation radius can reduce active ticking but also means distant farms, mobs and block entities will not behave as if a player were nearby. Raise it gradually only when the resulting tick workload is acceptable.
Best Value
- Play and share with friends on console, mobile and Windows 10
- discover community creations in the new in-game store
- access new mini games and game modes through servers
Memory usage grows over time
Record heap use and restart behavior rather than immediately assigning more RAM. The RLCraft installation guidance specifically warns that larger allocations can cause Java memory-leak issues. Periodic restarts are recommended, but the interval should be based on your observed memory pattern and the amount of disruption your players can tolerate.
Compare configurations by workload, not RAM alone
When deciding whether a host or configuration is adequate, compare the factors that shape actual tick work:
- Expected simultaneous player count and whether players spread out into different regions.
- Single-thread CPU performance, not just the advertised core count.
- Java heap allocation and the memory reserved for the operating system.
- View distance and simulation distance.
- How much terrain is pregenerated versus generated while players explore.
- Required uptime, restart windows and backup time.
- Whether the server runs on a local machine or a managed service with its own resource limits.
Two servers with the same nominal RAM can perform very differently if one is generating many new chunks at view distance 10 while the other has a small, pregenerated world at distance 6. Measure the workload your players create before changing a setting based on a generic recommendation.
A repeatable tuning workflow
- Apply the compatibility baseline and normal survival properties.
- Start near the 4 GB RAM recommendation and reserve host memory outside the Java heap.
- Use view distance 6 and the available simulation-distance default.
- Establish a baseline with one player, then repeat with the largest realistic concurrent group.
- Test the expensive cases: unexplored terrain, structures, combat, farms, machines and flying travel.
- Change one variable at a time. A distance increase and a heap change made together obscure which change helped or hurt.
- Keep a short record of tick behavior, memory use, player count and the setting tested.
- Stop increasing values when tick stability, latency or memory behavior worsens. A lower setting that stays stable is better than a higher setting that produces intermittent freezes.
This process produces a configuration tailored to your world instead of assuming that a value copied from another server will behave the same way.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
