Satisfactory Patch 1.2.2 Update — What's New & Server Impact
Satisfactory Patch 1.2.2.0 (EXPERIMENTAL) shipped on April 28, 2026 — the latest in the 1.2 development cycle that started with 1.2.0.0 in March. This article covers what changed and what dedicated-server admins should know.
TL;DR
- New Game Modes with Cost Multipliers + World Randomization.
- Selfie Mode — in-game photo mode with positioning controls.
- Sign Zooping — signs can now be placed in zoop chains like other building parts.
- Vehicle Path Automation v2 — remade automation system replaces the old recordings.
- EXPERIMENTAL branch — expect breakage; production servers should consider waiting for stable.
What Changed
New Game Modes (1.2.0)
The big-ticket feature from the 1.2.0 release that 1.2.2 continues to refine. Two new toggles when starting a save:
- Cost Multipliers — scale resource costs across the entire game (lower for casual builds, higher for hardcore megabase challenges).
- World Randomization — resource node positions get reshuffled each save, breaking memorized layouts and encouraging exploration.
Selfie Mode
Free-camera photo mode. Position the pioneer, frame the shot, snap. Mostly cosmetic but a frequently-requested feature for showcasing megabases.
Sign Zooping
Signs can now be placed in zoop chains (the click-and-drag-to-place-multiple system used for foundations and walls). Massive QoL win for labelling factory rows.
Vehicle Path Automation v2
The old "drive once, vehicle records the path" system has been replaced with a new automation system. Existing recorded paths from 1.1.x and earlier may need re-recording. Worth testing on a copy save first.
Server Impact — What Admins Need to Know
1. EXPERIMENTAL vs Stable
Patch 1.2.2.0 is on the EXPERIMENTAL branch. The "stable" patch from this cycle is still on 1.1.x. If you run a production server with active players, consider sticking with stable until the 1.2 line goes stable.
2. Vehicle Path Compatibility
Recorded vehicle paths from 1.1.x may not transfer cleanly. Action plan:
- Before patching, document your factory's vehicle routes (screenshot the map markers).
- Patch on a save copy first.
- Re-record critical routes if needed.
- Verify automation is functional before pushing the patched save back to production.
3. Save Compatibility
Forward-compatibility (1.1.x save → 1.2.x) is generally maintained. Backward-compatibility is NOT: a 1.2.x save cannot be opened in 1.1.x. Backup before patching.
4. Mod Compatibility
The Satisfactory Mod Loader (SML) usually catches up within 1–2 weeks of an EXPERIMENTAL patch. Until then, expect mod breakage. Check each mod's page on ficsit.app for 1.2.2 compatibility flags before updating.
5. Pre-Patch Checklist
- Notify connected players (use the panel's broadcast or stop the server cleanly).
- Backup your save directory:
~/.config/Epic/FactoryGame/Saved/SaveGames/server/on Linux servers (path varies on Windows). - Update game files via SteamCMD with the EXPERIMENTAL beta password if applicable.
- Restart the server.
- Connect with a test client first; verify world loads + automation runs.
- Re-record any broken vehicle paths.
Should You Update Right Now?
| Your situation | Recommendation |
|---|---|
| Casual server with 1–2 friends, on EXPERIMENTAL already | Update. Selfie + zooping signs are immediate QoL wins. |
| Active community on 1.1.x stable, complex factory automation | Wait for stable. Vehicle path system change can break factories. |
| Test/sandbox server, no production save | Update aggressively — experimentals need testers. |
Resources
- Official Satisfactory Wiki — Patch 1.2.2.0 for the full notes.
- Coffee Stain Q&A patch notes.
- Our setup guides: Dedicated server setup · Configuration guide · Auto-restart.
Run a stable Satisfactory factory. Host a Satisfactory server with Supercraft — one-click rollback if an EXPERIMENTAL patch breaks your factory automation.