#[1.0.3-rc3] Delivered shape is counted as a different shape in Classic Mode Hard Scenario Milestone

19 messages · Page 1 of 1 (latest)

left dove
#

Description:
While playing the Hard Scenario in Classic Mode (Milestone 4), the shape I deliver does not match the shape that gets counted by the game.

I am delivering the required shape, but after delivery, it is recognized as a different shape.

Expected Behavior:
The delivered shape should be counted exactly as the shape delivered.

Actual Behavior:
A different shape is counted after delivery.

Delivered Shape (Shape Code):
P-CcRcCc:P-CwRwCw:Rw------

Counted As (Shape Code):
--CcRcCc:--CwRwCw:--------:Rw------

Additional Info:

Mode: Classic Mode (Hard Scenario)
Milestone: 4

Attachments:

  • Screenshots
  • Savegame
20260502213828_1.jpg 20260502213835_1.jpg 📎 backup-v181-2026-5-02--21-51-05--0323520.spz2
quick flumeBOT
#

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 58 reports awaiting team review. Due to the high volume, it may take a little longer for us to get to yours.
⏰ Our team is off on weekends, so it may take a bit longer for us to review your report. Thank you for your patience!

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

quick flumeBOT
#
1. [SPZ2-5127] — 👀 72% similar

Research shape clasification not working correctly
Done • Priority: Critical • Fix: 1.0.0 Release • Resolution: Done

Research shape classification is not working correctly, where only a specific rotation of a shape is recognized as a valid delivery toward goals. Rotated shapes do not show the correct classification and are not accepted. The issue was traced to a change in the research shape unifier that broke rotational independence mapping. In Manufacture Mode, Operator Level shapes were not mapped as rotationally independent, unlike in Classic Mode where they reuse milestone shapes. A fix was applied to a...

#
2. [SPZ2-1507] — 👀 55% similar

Hud icons don't display correct input when the same shape unlocks two features.
Done • Priority: Medium • Fix: 2 - Demo • Resolution: Duplicate

When two consecutive Milestones require the same Shape goal, the Input indicators on The Vortex do not display the correct shapes, even though the Milestone counter functions properly. This occurs at Milestone 3 and 4 which both require Cu------. The issue appears to be related to having identical research goals back to back. A potential fix may involve preventing duplicate consecutive Milestones or creating an exception rule for Randomized Goals.

#
3. [SPZ2-2952] — 👀 45% similar

Wrong shape goal Milistone8
Done • Priority: High • Fix: 4 - Early Access • Resolution: Done

The Milestone 8 goal shape is incorrect. The displayed shape code RyRyRyRy-RmRmP-:CmRwRwCm-----P-:--CmCm-- shows support pins on layer 2 and 3, but the visual representation in layer 4 does not contain the expected support pins. This is a mismatch between the shape code string and the visual preview of the goal shape, which could confuse players about what they need to deliver.

#
4. [SPZ2-5666] — 👀 40% similar

The milestone 7 shape never becomes an operator shape in insane/hard
Done • Priority: Highest • Fix: 1.0.0 Release • Game: 1.0.0-alpha3-rc1 • Resolution: Fix Verified

In Classic Mode on Insane or Hard scenarios, the Milestone 7 shape does not become an Operator Shape as expected. This can be observed by opening the Milestones Screen and comparing the Milestone 7 shape against the Operator Shapes listed at the top. The shape for Milestone 7 should become an Operator Shape but is missing from that list. The fix added Operator Levels for missing Hexagonal, Insane, and Hard milestones and ensured Operator Shape entries match Milestone shapes. The fix has been ...
💬 Threads: [1.0.0-A3-RC1] Insane Milestone 7 do not

#
5. [SPZ2-5363] — 👀 35% similar

Shapes entering the vortex via trains aren't always counted if saving and reloading a save
Done • Priority: Critical • Fix: 1.0.0 Release • Resolution: Fix Verified

Shapes delivered to The Vortex via trains are not always counted after saving and reloading a savegame. In a fresh savegame using cheats, train deliveries to The Vortex count correctly, but after a save and reload, the shapes often fail to register. The issue is inconsistent but reproducible, and once a train enters The Vortex with uncounted shapes, even conveyor belt deliveries to The Vortex may stop counting. This may be related to trains doubling their simulation time on each save load, ca...
💬 Threads: [1.0.0-A3-RC1] Vortex Train Delivery - L

#
6. [SPZ2-4567] — 👀 30% similar

Insane difficulty milestone shape reset counter from pre4 to pre5
Done • Priority: Medium • Fix: None • Game: 0.1.0-pre4-rc1 • Resolution: Won't Fix

When loading a savegame from pre4 in pre5, the milestone counter for a specific shape in Insane scenario resets to 0. This occurs with the shape RmCcWcCm:--cm--cc:RcccCmcm:cmcccccm:cw--cw--. The reset allows the player to gain more milestone levels than intended by resubmitting shapes that were already counted. The issue affects progression tracking across game versions. Migration is not supported and players are recommended to start new saves.
💬 Threads: [0.1.0-pre5-rc1] Operator level: Insane

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

you're delivering {P-CcRcCc:P-CwRwCw:P-------:Rw------} instead of {P-CcRcCc:P-CwRwCw:Rw------} (1 too many pins in the corner)

hollow windBOT
placid sinew
#

but the statistics menu does also show the pins missing which is funky

left dove
#

Thank you for your response.

As you pointed out, my shape was indeed incorrect.
I think I also figured out why the pins were missing.

I was unintentionally creating the white pinned rectangle using a rather unusual method, and I suspect that this caused the issue.

Specifically, this setup is located at 3|-H.
There, I intended to create Rw------, but I was actually producing P-------:Rw------.

I meant to use the platform that extracts the top-left part, but instead I mistakenly used the platform that extracts only the pins.
Because of this, the result became a pinned rectangle.

I believe this process might be related to the pins disappearing after delivery.

When I created the white pinned rectangle using the normal method, it was counted correctly.

left dove
quick flumeBOT
hollow windBOT
quick flumeBOT
#

❌ Your bug has been closed as not a bug. If you believe this is an error, please use the /reopen-bug command.

left dove
#

Thank you for the clarification.

I understand that the originally reported issue was not considered a bug. However, I still believe that the disappearing pins are unintended behavior.

Therefore, I will create a new bug report with an updated title focusing specifically on the pin disappearance problem.

patent swallow