Satisfactory Version History: 1.0, 1.1 and 1.2 Compared

Satisfactory spent years in Early Access, so a large amount of the advice you will find online was written for a version that no longer behaves the way it describes. Knowing which release introduced what makes old guides usable rather than misleading.

The three releases that matter

1.0 — 10 September 2024. The game left Early Access after more than five years, having entered Early Access in March 2019. This release added the ending, finished progression through the final phase, moved and removed some resource nodes, and rebalanced recipes to reduce late-tier dependence on Computers and Heavy Modular Frames. Anything written before this is describing a meaningfully different game — including its map.

1.1 — June 2025, PC. A mid-size update on PC. Worth separating from the console launch, because the two are routinely confused.

Console launch — 4 November 2025, on PS5 and Xbox Series X|S, shipping on 1.1.1.0. The console port was built by Coffee Stain in cooperation with FishLabs. Its fixes and controller work were folded back into the PC version in 1.2.

1.2 — June 2026. Weather, Game Modes with cost multipliers and world randomization, Creative Mode, Fluid Trucks, buildable vehicle paths, and an upgrade to Unreal Engine 5.6.1. Released on PC and both consoles the same day, and it is the release that brought the console improvements back to PC.

Current stable is 1.2.3.1.

Changes that invalidate older advice

These are the ones where following an old guide will actively mislead you.

Overclock power exponent. Changed from 1.6 to 1.321929 back in patch 0.7.0.0. Guides and third-party calculators written before that overstate what overclocking costs — and some still-active calculators have never updated it.

Generators scale linearly. Also 0.7.0.0. Any advice treating generator overclocking as expensive is out of date.

Hard drives give two options, not three, and each can be rerolled once for free. This changed in 1.0, along with the introduction of the Hard Drive Library. Older guides describe three options and no reroll.

Advanced Game Settings is now called Creative Mode. Renamed in 1.2. Same feature, and guides using either name are talking about the same thing.

Vehicle paths are placeable. Before 1.2 you recorded a route by driving it. Guides explaining how to drive a good recording lap are describing a workflow you no longer need.

How to tell which version a guide was written for

Some quick tells, roughly in order of reliability:

Check for an explicit version stamp. Good references say which build they apply to. The absence of one is itself informative.

Look at the belt marks mentioned. If the top belt discussed is Mk.5 at 780/min, it predates Mk.6.

Look at what it says about overclocking generators. If it treats it as costly, it is describing pre-0.7.0.0 behaviour.

Check whether it mentions Game Modes or Creative Mode. Neither existed under those names before 1.2.

Watch for “Update 8” or “U8” branding. Some active third-party tools still carry it, which tells you their data has not moved since well before 1.0.

What did not change

Worth stating, because it means most older advice on these topics is still fine:

The map, since 1.0. Node positions have been stable from 1.0 onward, which is what makes interactive maps and planned builds usable. Note that 1.0 itself did move, add and remove nodes, so pre-1.0 map guides are unreliable. The other exception is 1.2’s world randomization, off by default and set at world creation.

Core production ratios. A Constructor makes the same thing at the same rate it always did. Recipe rates have been stable through 1.0 to 1.2.

Belt and pipe throughput ceilings. Unchanged across these releases.

The basic progression shape. Milestones, MAM research, Space Elevator phases — the structure is the same, even though 1.0 finished the endgame.

So a 2023 guide explaining how to lay out a smelter row is still useful. A 2023 guide telling you what overclocking costs is not.

Should you update mid-playthrough?

Yes. Saves carry forward across these releases and nothing in 1.2 rebalanced existing production.

Two things to expect on an older save:

Weather appears in a world that never had it. Adjust the preset or the fog slider in video settings if it bothers you.

World randomization is not retroactive. Your node layout stays as it was; that setting only applies to worlds created with it enabled.

Following updates going forward

Coffee Stain patch consistently after a major release — 1.2 saw four stabilisation patches in its first month. If something feels broken shortly after an update, checking whether a patch has already addressed it is worth doing before rebuilding anything.

For our part, every page on this site carries the game version it was written against, and the tool data is pulled from a version-tagged source so the figures move when the game does.

Why the console port matters to PC players

Easy to skip past if you are on PC, but the console work fed back into the game you are playing.

Porting to fixed, comparatively modest hardware forced a large amount of optimisation and controller polish that had no particular reason to happen otherwise. Patch 1.2.0.0 states plainly that all the changes originating from the console version, bug fixes included, became part of the PC version.

So the practical effect of the console launch on a PC playthrough is a run of performance work and hundreds of small fixes that arrived bundled into 1.2 rather than as their own release.

Reading patch notes usefully

Major releases get the attention, but the numbered patches after them are where most behaviour actually settles. 1.2 saw four in its first month.

Two habits make patch notes worth the time:

Check the small patches after an update before rebuilding anything. A behaviour that seems broken shortly after a release is often already fixed, or already known.

Watch for rebalanced settings rather than new features. 1.2.1.0 rebalanced the Extreme weather preset after launch feedback — the kind of change that does not make headlines but does change whether a setting is worth using.

Common mistakes

Following a pre-1.0 guide for numbers. Structure and layout advice ages well; specific figures do not.

Trusting a calculator without checking its version. Several active ones are several releases behind, and they do not always say so.

Confusing 1.1 with the console launch. 1.1 shipped on PC in June 2025; consoles launched that November on 1.1.1.0. They are separate events.

Assuming console is a different branch. Since 1.2 they are on the same version and update together.

Waiting to update before continuing a save. There is no advantage to staying behind.