[SPZ2-6193] [1.0.0-rc2] 1.0.1-RC1 Marathon and Can't Stop achievements not triggering

[kindred chasm]

I have reached operator level 256 in Classic Mode (and over 100 in Manufacture mode), and the Marathon and Can't Stop achievements (for reaching operator level 100 and 250, respectively) did not trigger. I have had no issue with other achievements as of yet.

[swift blade]

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 14 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
• macOS: ~/Library/Logs/tobspr Games/shapez 2/Player.log
• Linux: ~/.config/unity3d/tobspr Games/shapez 2/Player.log

[swift blade]

💾 Classic RC101

Started in

1.0.0-rc2

Last played in

1.0.1-rc1

Scenario

Classic - Regular

Seed

87315

Research

100%

Buildings

136,804

Completed

Yes

[1.0.0-rc2] 1.0.1-RC1 Marathon and Can't Stop achievements not triggering

1. [SPZ2-5576] — 👀 55% similar

Achievements - Technical Implementation
Done • Priority: Critical • Fix: 1.0 Release [1.0.0]

Multiple achievements in shapez 2 fail to unlock correctly due to various implementation and content issues. Shape-specific achievements like DungeonKeeper1, DungeonKeeper2, FlyMeToTheMoon, and Smile were broken because Support Pins and rotations were not being normalized the same way as other shape deliveries, causing shape codes to not match. Throughput-based achievements such as UsainBolt, Radcliffe, and JenniferPierce had imprecision issues in their statistics tracking, and the Certified ...

2. [SPZ2-5620] — 👀 45% similar

Achievement Fixes
Done • Priority: Critical • Fix: 1.0 Release [1.0.0] • Resolution: Fix Verified

Multiple achievements were not triggering correctly. "Certified" triggered prematurely when non-tutorial savegames existed, "VanDamme" failed due to misconfigured and missing mirrored structures, "Whale" failed because Blueprint Credits were not consumed for blueprints containing Space Platforms, and "MAMmon," "MAMmoth," and "MAMma" were incorrectly configured. Additionally, "Emerging Operator," "MakingCash," and "Train Delivery" had issues with accepting any shape instead of research-related...

3. [SPZ2-4797] — 👀 40% similar

Achievement - MVP Release Milestone - GD
Done • Priority: Highest • Fix: 1.0 Release [1.0.0] • Resolution: Done

This is a development task to implement and manage achievement data in the Unity project and on Steam for the MVP release milestone. The task includes creating various milestone achievements such as reaching specific Operator Levels, obtaining Operator Shapes at certain levels, earning the Operator License, saving Blueprints, maxing Speed Multipliers, spending Research Credits, and completing Milestones in different Game Modes and Difficulties. Achievements include progression-based goals lik...

4. [SPZ2-6124] — 👀 30% similar

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.

Found 4 similar reports • Searched 3,471 reports • Use /check-duplicates to recheck

[kindred chasm]

Adding player log

[swift blade]

📋 Log File Analysis

Thanks for attaching your log file — no errors have been found at a first glance.

[cursive surge]

it seems the version you're playing in is 1.0.1-rc1 though?

[swift blade]

🎫 Many thanks for reporting this issue! We have created an internal ticket for further investigation and will keep you updated. The internal ticket ID is SPZ2-6193 for reference. If you want to provide further information, just comment on this thread.