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 a new SkyFactory 4 world, use the legacy Minecraft 1.12.2/Forge stack with 64-bit Java 8, set level-type=topography and generator-settings={"Topography-Preset":"Sky Factory 4"} before the first launch, and keep max-tick-time=60000 enabled. Start with about 4 GB of Java heap for a small group, then adjust from actual tick time, CPU load, and heap usage. These world-generation values do not convert an existing normal world; you must create a new save or restore a backup.
Use this baseline server.properties configuration
Stop the server before editing server.properties. For a fresh SkyFactory 4 save, make these entries exactly as shown:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| # | 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 |
| Property | Value | Purpose |
|---|---|---|
level-type |
topography |
Loads the Topography world generator used by the pack. |
generator-settings |
{"Topography-Preset":"Sky Factory 4"} |
Selects the Sky Factory 4 preset rather than a standard terrain preset. |
max-tick-time |
60000 |
Keeps the normal server watchdog protection enabled. The value is in milliseconds. |
Do not add Markdown formatting, smart quotes, or extra spaces inside the JSON value. The complete relevant block is:
level-type=topography
generator-settings={"Topography-Preset":"Sky Factory 4"}
max-tick-time=60000
These are the important SkyFactory-specific settings. Other entries in the file control general Minecraft behavior, but changing them without a measured reason can make troubleshooting harder. Preserve the rest of the file unless you have a separate requirement and know which component owns that setting.
#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).
Install the correct legacy server stack first
SkyFactory 4 targets Minecraft 1.12.2 and its Forge-based mod ecosystem. It is not interchangeable with instructions for current Minecraft releases, which commonly assume Java 17 or Java 21. For this pack, Java 8 is the conservative compatibility baseline documented by setup guidance and issue reports.
Use a 64-bit Java 8 runtime
- Install a 64-bit Java 8 runtime on the host.
- From the same account that launches the server, run
java -versionand confirm that it reports Java 8 rather than a newer major version. - If several Java installations exist, use the full path to the Java 8 executable in your startup script so a system update cannot silently switch runtimes.
- Keep the client and server on the same SkyFactory 4 build. A client joining with a different pack version can fail even when the server itself is healthy.
Java flags copied from a newer Minecraft guide are not automatically suitable here. One official issue discussion records Aikar-style flags in a particular Java 8 environment, but that report is evidence for that environment, not a universal SkyFactory 4 command line. Add advanced garbage-collection or memory flags only after confirming they support your Java 8 build and deployment.
Run the complete modded server package
Use the SkyFactory 4 server files, Forge launcher, mods, configuration files, and scripts supplied for the pack. A vanilla server JAR does not contain the mod classes, recipes, advancements, or Topography generator. The official issue discussion notes that a correctly configured modded server can expose the pack’s available world types through server.properties; a vanilla server cannot load those mod-provided features.
Before inviting players, start the server once, accept the EULA if required by your installation, stop it cleanly, and then edit the generated properties file. This confirms that you are changing the file read by the actual launch script rather than an unused copy in another directory.
Create the SkyFactory world with the preset enabled
World-generation properties are read when a save is created. Follow this sequence whenever you are starting from a new installation or intentionally replacing a normal world.
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).
- Stop the server completely. Wait for the console to report that saving has finished. Do not edit a live properties file while the process is writing the world.
- Back up the server directory. At minimum, copy the existing world directory,
server.properties, theconfigandscriptsdirectories, and the installed mods. Store the copy outside the live server directory. - Edit the active properties file. Set
level-type=topographyandgenerator-settings={"Topography-Preset":"Sky Factory 4"}. Leavemax-tick-time=60000in place. - Choose the save action. If no world has been generated yet, continue to launch. If a normal world already exists, rename it or move it out of the server directory so Minecraft cannot reuse it. Keep the backup until the new save has been verified.
- Start the Forge server. Watch the console for world-generation errors. The first launch can take longer while terrain and mod data are initialized.
- Verify in-game. Join with a client running the identical SkyFactory 4 build and confirm that the expected SkyFactory starting environment appears, rather than ordinary Overworld terrain.
Changing the two generator properties after a world already exists does not regenerate that save. Minecraft keeps using the generator data associated with the existing world. To correct a normal-world mistake, stop the server, preserve the save as a backup, and generate a fresh world or restore a known-good SkyFactory backup.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Why a server sometimes creates a normal world
The world was generated before the properties were changed
This is the most common explanation. The server reads the generator pair during world creation, not every time a player joins. Editing the file later leaves the old save unchanged. Rename or remove only the live copy after making a verified backup, then start the server again.
The wrong properties file was edited
Control panels and startup scripts can use a different working directory from the one you opened in a file manager. Stop the server, identify the directory containing the active world and Forge files, and edit the server.properties in that directory. Restart and inspect the file after launch to ensure the values remain present.
The server is vanilla or incomplete
A vanilla JAR cannot interpret the Topography preset or provide SkyFactory advancements. Confirm that the launch command starts Forge and that the pack’s mods, configs, and scripts are installed together. Missing files can produce a normal-looking server even when the text in server.properties appears correct.
The value was typed incorrectly
Use the exact lowercase generator type and the exact JSON key and preset name. Common mistakes include changing topography to a newer-version world type, replacing straight quotation marks with typographic quotes, adding a second equals sign, or inserting comments on the same line. Remove the malformed line and re-enter it exactly from the baseline block.
Windows 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 reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchRank #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.
Java heap and hardware: choose a starting point, not a promise
No official DarkPacks source establishes a universal RAM number for SkyFactory 4. A practical starting point for a small group is 4 GB of heap, then adjustment based on measurements. It is not a guarantee for a particular player count, factory, or host.
| Situation | How to use the guidance | What to monitor |
|---|---|---|
| Small, lightly automated world | Begin around 4 GB of Java heap and test normal play. | Used heap, garbage-collection pauses, CPU utilization, and server tick time. |
| Large automation, many loaded chunks, entities, dimensions, or concurrent players | Increase only when measurements show heap pressure and the host has spare RAM. | Whether lag follows heap exhaustion, CPU saturation, a particular chunk, or entity growth. |
| Container deployment example | One documented Docker setup uses a 2048 MB limit; treat it as a deployment example, not a recommended universal allocation. | Container memory limit, Java process usage, restart events, and garbage-collection behavior. |
Leave headroom for the operating system, Forge, file caching, and monitoring tools. Never assign all physical RAM to Java. If the host has 8 GB total, allocating 8 GB to the server leaves no room for the operating system and can cause swapping or an outright out-of-memory failure.
RAM cannot fix every kind of lag
SkyFactory factories can create a pathological single chunk: thousands of dropped items, a machine loop, excessive entities, or a chunk loader that keeps a large automation network active. More heap may delay a crash but will not make that tick complete quickly. CPU capacity, entity counts, loaded chunks, storage speed, and network latency all matter.
Increase memory in measured increments rather than jumping to a fixed 8 GB or 12 GB target. Record the same conditions after each change: number of players, loaded dimensions, active automation, heap usage, and average tick behavior. This separates a genuine memory shortage from a CPU-bound or content-specific problem.
Keep the watchdog enabled during normal service
max-tick-time=60000 is the normal safety setting in the documented recovery discussion. It lets the server stop protecting itself when a tick remains stuck for too long, which is preferable to allowing an unresponsive process to consume resources indefinitely.
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
Do not set max-tick-time=-1 as a permanent performance tweak. Disabling the watchdog can keep a broken machine loop or overloaded chunk alive while the rest of the server becomes unusable. Use it only as a short, supervised recovery measure when the server cannot stay up long enough to clean the cause.
Emergency recovery for an overloaded chunk
The following procedure is for a server that repeatedly times out because one area contains an extreme number of dropped items or another known entity overload. Make a backup before attempting cleanup.
Recommended Free Tools
- Stop the server and copy the world. Keep the untouched copy in case the cleanup damages the save.
- Change the watchdog temporarily. Set
max-tick-time=-1inserver.properties. This removes the timeout protection only for the recovery session. - Start the server and connect quickly. Use an operator account and move to the affected area if the server remains responsive long enough.
- Remove the dropped items. The documented example uses
/kill @e[type=item]. That selector targets item entities; review the command and your permissions before running it, because it removes all matching dropped items in the command’s effective scope. - Stop the server after cleanup. Do not leave the process running indefinitely with the watchdog disabled.
- Restore protection. Return
max-tick-time=60000, restart, and test the area. - Fix the source. Disable or redesign the farm, machine, transport line, chunk loader, or storage setup that created the spill. Otherwise the same overload will return.
If the server cannot remain online even with the temporary setting, restore the backup and investigate offline. A world-editor operation or targeted region repair may be safer than repeated live starts, but the correct method depends on the failure and the tools available on your host.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.A practical lag-diagnosis workflow
1. Identify whether the problem is global or local
- If every player experiences delayed block updates, inspect CPU saturation, Java pauses, disk activity, and network latency.
- If only one base or dimension is affected, suspect a machine network, entity pile, chunk loader, or farm in that area.
- If lag begins after a build is activated, disable that build before adding RAM.
2. Watch tick time and CPU, not just the heap bar
Heap usage shows whether Java is under memory pressure; it does not show that one expensive tile entity is monopolizing a tick. Compare heap trends with CPU usage and the server’s tick-time readout. A nearly full heap with long garbage-collection pauses calls for a memory review. A single saturated CPU core with moderate heap usage points toward workload or mod behavior instead.
3. Reduce loaded work
Temporarily disable chunk loaders, pause large farms, remove unnecessary entities, and limit the number of simultaneously active dimensions. Make one change at a time and record whether tick time improves. This creates a reversible path instead of destroying a working build blindly.
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
4. Check the host and network
For self-hosting, verify that the public port is forwarded to the correct machine and that the firewall permits it. For a remote host, check CPU contention, storage health, memory limits, and the server location relative to players. Network latency can feel like server lag even when tick time is normal.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →5. Profile before changing safety limits
Use the server console and available profiling tools to find the expensive dimension, chunk, entity type, or tile entity. Changing max-tick-time hides the symptom; profiling and removing the workload addresses it.
Settings that should change together with an upgrade
SkyFactory 4 updates can alter how saves behave. The DarkPacks 4.2.4 changelog warns that tomb behavior changed and instructs administrators to open old graves before updating and to use backups. Treat that as a migration requirement, not an optional housekeeping step.
- Stop the server cleanly.
- Copy the world,
server.properties, configs, scripts, and mods to a separate backup location. - Start the old version and open any existing graves identified by the release guidance.
- Shut down again and install the target SkyFactory build exactly on the server and clients.
- Start the updated server and test spawn, inventories, dimensions, automation, and recovery commands before inviting everyone back.
- Keep the pre-upgrade backup until the world has survived normal play.
Do not assume that a successful launch proves an upgrade is safe. A save can load while a specific grave, machine chain, or dimension still needs validation.
Self-hosting or managed SkyFactory 4 server hosting?
Self-hosting gives you direct control over Java 8, Forge, pack files, backups, and emergency cleanup, but you must maintain every part of the legacy stack. Managed hosting reduces installation and networking work, yet you still need to verify that the provider supports this old combination rather than only current Minecraft versions.
| Decision factor | Self-hosted server | Managed service |
|---|---|---|
| Compatibility control | You pin Java 8, Forge, the exact SkyFactory build, configs, and scripts. | Ask whether Java 8 and Minecraft 1.12.2/Forge are available and whether you can select the exact pack build. |
| Operational burden | You handle installation, updates, port forwarding, monitoring, backups, and recovery. | The provider may supply a panel and networking, but confirm what updates and backups actually include. |
| Resources | You choose the machine and retain all available CPU and RAM, subject to your hardware and connection. | Check guaranteed CPU, RAM, storage, oversubscription policy, and upgrade limits rather than relying on a plan label. |
| Recovery access | You can access the console, files, world backups, and the affected chunk directly. | Verify that the panel offers console access, file management, downloadable backups, and a way to run cleanup commands. |
| Network reachability | You arrange a public address, firewall rules, port forwarding, and DDoS protection. | Ask about location, latency, public connectivity, and network mitigation. |
For a managed option, confirm current 1.12.2 support, Java packaging, exact Forge compatibility, backup retention, and restoration procedure before paying. Availability and pricing change, so a provider’s present product page is the authority for its current offer.
Backup checklist for a reliable server
- Copy the complete world directory before changing generator settings or pack versions.
- Save
server.properties, the Forge launch files,config,scripts, and the mods directory together so a restore uses matching versions. - Keep at least one backup away from the live machine or container.
- Label backups with the SkyFactory build, Java version, and date.
- Test restoring a copy, not the production save, so you know the backup is usable before an emergency.
- Make an additional backup immediately before the 4.2.4 migration procedure and retain it until graves, dimensions, and automation have been checked.
Final pre-launch checklist
- Java reports a 64-bit Java 8 runtime.
- The launch command starts Forge and the complete SkyFactory 4 server package, not vanilla Minecraft.
- Clients and server use the same SkyFactory build.
level-type=topographyis present.generator-settings={"Topography-Preset":"Sky Factory 4"}is present before the world is created.- The old normal-world directory has been backed up and moved aside if a replacement save is required.
max-tick-time=60000is restored after any emergency cleanup.- Heap allocation leaves RAM for the operating system and is being evaluated with CPU, tick-time, and garbage-collection data.
- Backups include the world and the configuration, scripts, and mods that define it.
What “best settings” means for SkyFactory 4
The best configuration is a correct, reproducible baseline rather than a list of extreme values: the legacy Java 8/Forge stack, the exact Topography preset before world creation, a measured memory allocation, and an enabled watchdog. When performance degrades, identify the workload first. Temporarily disabling the watchdog can rescue a save from an item spill, but restoring 60000 and correcting the farm or machine is what makes the server dependable.
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.

