I LOVED this game before the 1.0 update, i had a MAM and all! now i cant play my old worlds which is

[jolly ether]

Thank you for reporting this bug! Our team will review your report soon.
Feel free to add more details in follow-up messages — we're also scanning for duplicate reports automatically now.
📨 There are currently 44 reports awaiting team review. Due to the high volume, it may take a little longer for us to get to yours.

📋 Log files help us investigate issues. You can find yours here:
• Windows: %USERPROFILE%\AppData\LocalLow\tobspr Games\shapez 2\Player.log

💾 Savegame files (.spz2) are very helpful if relevant to the issue!
Export via Main Menu → Play → click the download icon on the relevant savegame.
You can also find them here:
• Windows: %USERPROFILE%/AppData/LocalLow/tobspr Games/shapez 2/

1. [SPZ2-5239] — 👀 72% similar

Old saves are unlocked on Milestone 0
Done • Priority: High • Fix: None • Game: 0.1.0-pre8-dev • Resolution: Won't Fix

Old savegames from previous versions load with all structures blocked and reset to Milestone 0, even though shapes are already counted toward goals. This occurs specifically in Classic Mode when loading saves from earlier game versions. The issue is caused by renamed milestones in the game's progression system, resulting in a version mismatch that prevents proper milestone recognition. Players expect their savegames to load at the correct milestone level matching their actual progress. This w...

2. [SPZ2-3097] — 👀 65% similar

Loading old insane games (100%) does load the straight stacker
Done • Priority: High • Fix: 4 - Early Access • Game: 0.0.0-alpha23 • Resolution: Done

Loading old Insane savegames from before the Stacker changes incorrectly provides access to both the Stacker and Stacker variants. When loading pre-update Insane scenario saves, players gain access to the Stacker that should be restricted by the game rule. The expected behavior is that old Insane savegames should only have the Stacker available, not the Stacker variant, as these saves are not being properly migrated to apply the correct game rule restrictions.

3. [SPZ2-3053] — 👀 62% similar

Fatal Error: Savegame does not load (from Friday)
Done • Priority: Highest • Fix: 4 - Early Access • Game: 0.0.0-alpha23.1 • Resolution: Done

Savegame files from Friday with 100% completion fail to load with fatal errors. The issue occurs when trying to load these saves, with errors indicating the menu Savegame is below the minimum supported version (1032 vs 1082) and null reference exceptions in FluidPortSystem. Savegame files at 5% completion with 100 Structures load without issues. The problem may be related to Mods, though all old Mods and Savegame files were removed from the drive. The issue has been verified as fixed after a ...

4. [SPZ2-3739] — 👀 60% similar

[0.0.9-rc5] Unable to load a saved game
Done • Priority: High • Fix: Version 0.0.9 • Game: 0.0.7 • Resolution: Done

Player on Windows 11 with Direct3D11 was unable to load multiple Savegames in shapez 2 version 0.0.9-rc5. The log analysis revealed three types of failures: some save files had invalid Base-64 content, others failed to decompress due to DEFLATE stream errors or GZIP CRC mismatches, and one backup failed because it contained an invalid color code "p" during Shape Code parsing. The invalid color code caused game initialization to fail completely. The issue has been fixed in master and version 0...

5. [SPZ2-3649] — 👀 55% similar

Savegames Failed to Read
Done • Priority: Highest • Fix: Version 0.0.9 • Resolution: Done

The game was unable to read any Savegame / Save / Save File / Save Game files in shapez 2 / Shapez 2 / shapez2 / the game. This issue prevented players from loading any of their saved progress or data. The bug was initially not reproducible by the development team, but after the affected player provided a rough reproduction scenario, the issue was identified and fixed. The bug has been verified as resolved.

6. [SPZ2-6192] — 👀 52% similar

Save games from 1.0.1-rc1 are incompatible on the 1.0.0-rc3 build.
To Do • Priority: Medium • Fix: None • Game: 1.0.1-rc1

Savegames created in the 1.0.1-rc1 build cannot be loaded in the older 1.0.0-rc3 build. To reproduce, create a savegame in 1.0.1-rc1, then attempt to load it in 1.0.0-rc3. The savegame appears blacked out and displays an "unsupported savegame" message. Expected behavior is that savegames should only become incompatible between versions after a planned compatibility bump.

Found 6 similar reports • Searched 3,618 reports • Use /check-duplicates to recheck

[summer folio]

You can switch to old pre 1.0 version via steam settings. "Game Version and Betas"

[indigo rune]

Unfortunately 1.0 is not compatible with older saves.
And if you copy the MAM elements as blueprints in older versions you will have some issues with some of the machines/buildings repositioning their input/outputs (improvements)

Not a Bug I am sorry to say.