#No achievements being unlocked
19 messages · Page 1 of 1 (latest)
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 65 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/
Achievements - Technical Implementation
Done • Priority: Critical • Fix: 1.0.0 Release • Resolution: Done
Multiple achievements in shapez 2 are failing to unlock or tracking incorrectly due to various implementation and content issues. Shape-matching achievements like DungeonKeeper1, DungeonKeeper2, FlyMeToTheMoon, and Smile were broken because Support Pins and rotations were not handled consistently with other shape deliveries. Throughput-based achievements such as UsainBolt, Radcliffe, and JenniferPierce had imprecision issues in their statistics tracking, causing them to trigger at incorrect t...
In game achievement notifiers don't always work
To Do • Priority: Low • Fix: None • Game: 1.0.0-RC2
In-game achievement notification popups do not always appear when an achievement is unlocked. The cause is unclear, as some achievements trigger the notification while others do not. To reproduce, delete the achievement.bin file from the local app data folder, load a savegame, confirm an achievement is still locked via the debug console, then unlock the corresponding milestone. The expected behavior is that every achievement unlock should display an in-game notification.
In-game achievement notifications are missing when triggering achievements in game.
Done • Priority: Critical • Fix: 1.0.3 release (Hotfix 1) • Game: 1.0.2-rc1 • Resolution: Not A Bug
When achievements are triggered in shapez 2, no in-game notification toast is displayed to the player, although the Steam achievement still unlocks. This can be reproduced by deleting the achievement file, starting a new game, and triggering any achievement such as traveling a large distance from The Vortex. The expected behavior was that an in-game notification would appear alongside the Steam achievement. However, after discussion this was confirmed to be by design: as long as Steam is conn...
Achievements are triggered multiple times between sessions
Done • Priority: Critical • Fix: 1.0.0 Release • Resolution: Fix Verified
Achievements are triggered multiple times between sessions. Starting a game and unlocking any achievement, then stopping and restarting the game, allows the same achievement to be unlocked again. The expected behavior is that achievements should only be triggered once and persist correctly across sessions. The issue was related to achievement state not being saved properly between sessions. This bug has been verified as fixed in a later build.
FloorBase/JackOfAllTrades/Excellency achievements are all unlocked after the 2nd operator shape is claimed
Done • Priority: Highest • Fix: 1.0.1 Release (1.0 Fix 1) • Resolution: Fix Verified
The FloorBase, JackOfAllTrades, and Excellency achievements all unlock prematurely after the second Operator Shape is claimed, instead of at their intended thresholds. FloorBase should unlock when all Operator Shapes reach level 5, JackOfAllTrades at level 10, and Excellency at level 15. The issue is triggered by claiming the second Operator Shape on the Operator Screen. A fix was merged into version 1.0.1 and verified.
💬 Threads: [1.0.0-rc2] FloorBase/JackOfAllTrades/Ex
Marathon and Can't Stop achievements not triggering on reaching required Operator Levels
Done • Priority: Critical • Fix: 1.0.3 release (Hotfix 1) • Game: 1.0.0-rc2 • Resolution: Fix Verified
The "Marathon" and "Can't Stop" achievements do not trigger at the correct Operator Levels. "Marathon" should trigger at Operator Level 100 but instead triggers at approximately 200, and "Can't Stop" does not trigger at all upon reaching Operator Level 250. The issue is reproduced by clearing achievement data, loading a savegame, and claiming Operator Levels on the Milestones Screen. The root cause was a code change that broke the "count" counting mode initialization for this achievement type...
💬 Threads: [1.0.0-rc2] 1.0.1-RC1 Marathon and Can't
Are the achievements showing up on steam?
The steam overlay being off would be a reason why you aren't seeing them trigger.
No they’re not. They are definitely triggering in-game, but nothing is registering within Steam itself.
I also am using the Steam overlay, I’ve been using the shift-tab to try and view the achievements when I had realized none had triggered.
I went straight into manufacture mode and skipped the tutorial and vortex mode if that makes any difference
Are you using any launch options like --disable-store-sdk?
Nope I am running the game normally by just clicking “play” on steam
Running Windows 10
I can try and grab my logs tonight if that would help at all
✅ Thank you for providing further information, our team will have a look again!
@distant void
Yes, if you don't mind, the log file and the save if possible.
Things to try that might help:
- Check if Steam is in offline mode
- Verify the integrity of the game files
- Restarting steam itself and/or doing a PC reboot (jokes about general I.T. turn off/on again aside, I have seen user's with similar issues on steam discussions say this has occurred for other title and fixed it).
If none of this works, there may be an issue with the game data itself, but I'd prefer to check other avenues first.
Thank you,
Josh
It appears I WAS using the --disable-store-sdk flag. After I removed that it was fixed. I think I had to enable this during the beta for some reason in order to be able to play, but it appears to be fixed now! Thanks again!
✅ Thank you for providing further information, our team will have a look again!
Thanks for the update 🙂
Closing as not a bug.