Factorio 2.1: Update a Space Age Server Without Losing Your Factory

What 2.1 changes for a Space Age server

The 2.1 release focuses on usability and balance, without adding a new planet. Space platforms gain features including platform-to-platform transfers and mixed-cargo rockets. Circuit networks change too, with separate input and output behavior. The developer warns that some 2.0 factory designs may behave differently after migration.

Space Age, Quality, Elevated Rails and Recycler are official content packaged as built-in mods. In 2.1, Quality is optional when playing Space Age. Do not disable a component on an existing world without checking its dependencies and data; first reproduce the live mod list on a copy of the save.

Before moving a server from 2.0 to 2.1

1. Announce downtime and stop the server. Wait for the exit save to finish. Headless servers also autosave, but an autosave is not an independent archive.
2. Download an off-server copy of the world .zip, important blueprints, the mod directory and server settings. Keep that 2.0 copy untouched during testing: a 2.1 save cannot be rolled back.
3. Check third-party mods. The Factorio team says most popular mods were updated during the experimental period, but not necessarily every mod you use. Verify compatibility for essential mods and keep the same mod set and game version on clients and server.
4. Install the stable 2.1 server version. On a hosted plan, select the stable 2.1 branch in the control panel if offered; confirm the host's process first. On a self-hosted Linux server, download the official headless package for your machine's architecture and keep saves and settings separate from the old executable.
5. Open and test a copy of the world. Check loading, mods, circuits, space platforms and logs. Ask a few players with matching versions to join. After these checks, schedule migration of the main world.

For a headless server, start a save with --start-server path/to/world.zip and load settings with --server-settings. The official command reference also documents --sync-mods; automatic mod downloads on a headless server require configured service credentials. Never publish those credentials in a guide, repository or support post.

If players cannot join or the factory slows down

First compare the exact game version and mod set on client and server: Factorio requires them to match. Then inspect logs to separate world loading, mod and network errors. The default game port is UDP 34197. On a home server, check the firewall and port forwarding only after confirming that the server starts.

Do not buy more RAM based on a slowdown alone. Measure usage and examine save size, mods and simulation behavior. If you want to move the factory, see the Factorio hosting comparison. Before ordering, confirm save export, 2.1 version selection and mod handling with the provider.

A headless server remains reachable when nobody is online, but simulation pauses by default while it is empty. The no-auto-pause setting can change that if your group wants production to continue without connected players.

Frequently asked questions

Can I go back to Factorio 2.0 after migrating? Not with a save or blueprint already written in 2.1. Keep a separate 2.0 copy before upgrading.

Does 2.1 add a new Space Age planet? No. The developer describes changes to logistics, circuits, balance and general usability.

Does the factory run when nobody is connected? Not by default on a headless server: the world pauses when empty. Check no-auto-pause if you want continuous simulation.