Factorio 2.1 Is Stable and the Last Major Update: What Long-Term Support Means for Server Owners

The timeline from experimental to stable

• May 29, 2026, Friday Facts #440: Wube lays out the plan for 2.1, scoped as quality of life, small features, polish and modding improvements, and calls it the last major update.
• June 26, 2026: 2.1 opens as an experimental release and stays there through the summer so mod authors can update.
• September 18, 2026, Friday Facts #446: native ARM64 Linux builds, headless server included.
• October 20, 2026: 2.1.23 released.
• October 23, 2026, Friday Facts #449: 2.1 is marked stable with 2.1.23, and Steam's default branch moves to it.
• October 27, 2026: 2.1.24 released on experimental.
• October 29, 2026: Steam's default branch moves to 2.1.24 at 11:29 UTC; Steam relabels the 2.1.23 branch "Outdated Stable".

On November 7 factorio.com's release API listed 2.1.24 for both stable and experimental, game, expansion and headless alike. Six days from stable to the next stable point release is fast, and it is a reminder that "stable" in Factorio means a build Wube recommends, not a build that stops changing.

What "the last major update" means

Wube's own framing is that 2.1 is the last major Factorio update: no new planets, no new enemies, no new research trees, followed by long-term support. Wube's scope list for 2.1 was quality of life, small features, polish and modding improvements, with space logistics as the substantial area and balance tuning still going on during experimental, such as the 2.1.21 change that made space platform drag depend on platform mass rather than width.

For a server owner that framing is good news with a footnote. Good news, because a long-term support game is a stable target: fewer protocol breaks, fewer moments when every mod on your list breaks at once, and saves that keep working for years. The footnote is that "no new major update" is not "no new versions". Point releases like 2.1.24 keep arriving, every one of them still requires server and players to run the same version, and a server that sits on an old point release will turn away players whose game updated.

What 2.1 adds, through a server owner's eyes

Friday Facts #449 gave players still on 2.0 a tour of what waits in 2.1. Read with a multiplayer server in mind, these are the parts that change how a shared factory plays:

• Space logistics: mixed rockets that carry several item types in one launch, an "Import from" slot that can be left blank to pull from all locations, platform-to-platform transfers in orbit, hub requests set by the circuit network, and a radar "Universe" mode that passes circuit signals between planets and platforms.
• Platform balance: asteroid damage now depends on the asteroid's remaining health instead of its speed, the hub has more health and resistances, and drag depends on mass, so the narrow "pencil ship" is no longer the only fast design.
• Landing pad unloading bay: a cargo bay that inserters can unload straight into trains, chests or belts.
• Circuit network: the input and output split that sends reads and writes to different wire colours, replacing the old self-subtraction trick. This is the change Wube warns can break existing designs.
• Quality becomes optional: Space Age can now be played without Quality, the Recycler is split into its own mod, and Quality is a recommended dependency enabled by default. That changes what a fresh save's mod list looks like, which matters when you copy a mod list between servers.
• Enemy expansions scale with evolution instead of spawning many tiny nests, and exploring early no longer reduces expansions near your base, which PvE servers with long-running worlds will feel.
• Fluids: mixing prevention is back, so pipelines with different fluids no longer merge, and fluid flow scales properly at high throughput.

Moving a server from 2.0 to 2.1

Wube's notes for the move are short and worth taking literally:

• 2.0 saves load in 2.1, but changes such as the circuit input and output split can break factory designs.
• The move is one way. Saves and blueprints updated to 2.1 cannot be taken back to 2.0. Keep a copy of the 2.0 save before the first 2.1 start.
• Mods are the hard part. Most popular mods were updated during experimental, some were not. A 2.1 server refuses to start with any mod whose info.json still declares factorio_version 2.0, so a mod list that worked yesterday can stop the server today until each mod is updated or removed.

For a dedicated server the safe order is the boring one: back up the save, update the mods on a test copy first, start 2.1 on that copy and only then move the live server and tell players to update.

The Steam branches that matter now

Steam's branch list for Factorio (app 427520) on November 7 shows how Wube handles the transition:

Two branches deserve attention. The 2.0.77 branch is the escape hatch for groups whose mods are not ready: pin both clients and server to 2.0.77, and move later. The console branch says something about the console editions: their latest release matches 2.0.77, so a PC player or server that wants to meet console players has to be on that version, not on 2.1.

Headless builds, ARM64 and the 2.1.24 fixes

The headless server remains a free download from factorio.com, and since Friday Facts #446 Factorio runs natively on ARM64 Linux, headless included. Wube's own list of where that helps is refreshingly concrete: Raspberry Pi headless servers, Asahi Linux on Apple Silicon MacBooks, and "the free VPS you claimed from Oracle that one time". That widens the hardware a small server can run on, although Factorio's simulation still rewards fast single-thread performance more than core count, and a big late-game factory will find the limits of a small board quickly.

The 2.1.24 changelog, dated October 27, is mostly bug fixes, and several of them are server-relevant: a crash when request-to-save-and-quit is used in headless mode, a performance regression in fluid flow on certain saves, and the joining and catching-up screen not sizing correctly when mods were involved and several players joined at once. It also adds --test-save, --test-scenario, --test-ticks and --test-arg command line options, plus matching scripting hooks, which matter to mod authors testing against a server rather than to most operators.

Running a server in the long-term support era

If 2.1 really is the last major update, the job of running a Factorio server changes shape. Less of it is reacting to big releases and more of it is routine:

• Follow point releases, not just headlines. Version match is absolute in Factorio, so each stable point release is a server update day.
• Curate the mod list for longevity. In a long-term support game the mods that keep getting maintained are worth more than the ones that were exciting in a single season.
• Keep save backups across versions. One-way upgrades are fine as long as the copy from before exists.
• Decide early about the 2.0 holdouts. If part of your group lives on 2.0.77 or the console branch, the server has to choose a side; there is no mixing.

Wube's announcement of the stable release is Friday Facts #449.