Factorio Base vs Space Age Server: Choose Before Creating the World

Factorio's official headless package can host both a Base game world and a Space Age world. The meaningful choice happens before map creation, when the server reads mods/mod-list.json. Treat it as a world-creation decision, not a checkbox to flip later.

Choose a managed Base or Space Age Factorio world

One package, two world configurations

Factorio's stable Linux headless download includes the relevant data. Base game creation keeps elevated-rails, quality and space-age disabled. A Space Age world enables them before --create. This aligns the server's prototype data with the world it writes.

{"mods":[
  {"name":"base","enabled":true},
  {"name":"elevated-rails","enabled":true},
  {"name":"quality","enabled":true},
  {"name":"space-age","enabled":true}
]}

The multiplayer reference documents save creation and loading. The key operational rule is simple: write the list first, create the first save once, then use --start-server-load-latest so existing saves always win.

Clients need the appropriate ownership and matching state

Players joining a Space Age server need the compatible game and DLC entitlement. Every player also needs the same Factorio version and enabled mod list. Base worlds avoid the DLC data, but ordinary mod parity still applies. If a connection fails, check this before assuming an internet problem.

Why toggling an existing world is unsafe

A live save can contain entities, technology and progression that rely on the currently enabled prototypes. Turning DLC data on or off after it exists can make the save inconsistent or leave players with a mismatched set of content. It is not equivalent to changing a password, player limit or autosave interval.

Use a migration copy, not the production save

1. Stop the server cleanly and copy the complete saves directory.
2. Make a separate test server or directory.
3. Change the mod list only in the test copy, then load it with the target client version.
4. Check logs, join with representative clients and validate progression before scheduling any production change.

Keep the original backup until the group has played successfully on the new configuration. For the rest of the operational setup, including paths, services and updates, see the dedicated-server guide. For UDP and mismatch troubleshooting, see the connection checklist.