How to Update a Nomifactory Server | Safer 2026 Guide
Nomifactory's own update history includes major GTCEu version transitions that came with a full server wipe, not an in-place update — knowing which kind of update you're facing matters more here than on almost any other pack.
Already crash-looping? See the Nomifactory crash-fix guide, or the Nomifactory CEu pack page.
1. Check whether this is a minor update or a major GTCEu jump
Read the changelog closely. A minor version within the same GTCEu generation is a routine, backup-and-go update. A major GTCEu version transition has, in this pack's own history, required a full world wipe with updated Sponge Forge API and configs — treat that as a new world, not an update path.
2. Back up before any update, regardless of size
Nomifactory's production chains represent weeks of real time investment. Take a full backup before touching the pack files even for what looks like a minor patch.
3. Install the matching server pack
- Download the server pack for your exact target version — not the client pack.
- Shut the server down with the stop command first.
- Install into a clean folder rather than layering the new version over the old one.
4. Re-check server.properties after updating
Confirm max-tick-time=-1 is still set. It's a standing requirement for this pack's processing load, not a one-off fix tied to a specific version — an update that resets server.properties defaults can silently remove it.
FAQ
Has a Nomifactory update ever required a full world wipe?+
Yes — major GTCEu version transitions in the pack's own history have come with a full server wipe and updated configs, not an in-place update. Check the specific changelog for your target version before assuming a routine update applies.
Will updating lose weeks of GregTech automation progress?+
Not for a minor version within the same GTCEu generation, as long as you back up first. For a major GTCEu jump, treat it as the pack's own history suggests: a new world, not a migration.
What should I set in server.properties after updating?+
max-tick-time=-1 is a known, accepted setting for this pack specifically — GregTech's processing chains can legitimately exceed the default tick watchdog, and that isn't unique to the version you're updating to.
Update Nomifactory without losing weeks of GregTech progress
CoalHost keeps automatic backups ahead of every update and the right tick-watchdog settings for Nomifactory's processing load in place by default.
View Minecraft Hosting →