Problem with Pin-Pusher

[slow wigeon]

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 25 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

💾 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-2048] — 👀 72% similar

Pins don't count as empty for the pin pusher
Done • Priority: High • Fix: 4.1 - EA Prototype • Resolution: Done

The Pin Pusher is not treating Support Pins as empty quarters when processing shapes. When a shape with Support Pins is processed, the Pin Pusher generates output with Support Pins in positions that should be empty gaps. For example, the output shape is P-P-P-P-:CuCuP-P- instead of the expected P-P-----:CuCuP-P-. This affects shape processing accuracy when working with shapes that have Support Pins. The report was marked as not a bug.

2. [SPZ2-3568] — 👀 55% similar

Randomized Operator Goal algorithm code bug
Done • Priority: Medium • Fix: Dimension Update [0.1.0] • Resolution: Done

The Randomized Goals algorithm in the Make Anything Machine has a code bug on Line 231 where it uses the wrong variable, causing the randomly generated stacked shape to be lost and replaced with a copy of the current shape plus pins. Additionally, when pushing pins, the code increases the total height by 2 but doesn't account for this, potentially creating more layers than the maximum allowed. This affects how randomized operator shapes are generated in the endgame progression.

3. [SPZ2-6227] — 👀 45% similar

Prediction breaks for self feeding pin machine
To Do • Priority: Low • Fix: None • Game: 1.0.2-rc1

Shape Previews break for a self-feeding Pin Pusher when the machine's output is stacked back into itself. The issue occurs because the circular dependency in the contraption prevents the prediction system from resolving the expected shapes. Shape Previews for Support Pins are not displayed when the machine feeds on its own output. The problem does not occur if the machine is initially populated using a separate production line. This can be reproduced in a Regular scenario by placing the bluep...
💬 Threads: [1.0.2-rc1] cycles break shape predictio

4. [SPZ2-3087] — 👀 35% similar

Simulate Unstacker works wrong
Done • Priority: Medium • Fix: 4 - Early Access • Resolution: Won't Fix

The Simulated Buildings Unstacker appears to work incorrectly when processing a specific 5-layer shape. The reporter observed that the bottom layer seems to be unstacked first and then last again when analyzing the shape code SuSuCuWu:RuRyRyRy:CuSwCwP-:P-P-P---:SuSuCuWu. However, the issue could not be reproduced by QA testing, and the provided screenshot shows the Stacker working as expected. The original Discord report was deleted or vanished, making verification difficult. The issue remain...

5. [SPZ2-5422] — 👀 30% similar

There is a 3 layer shape restriction for manufacture mode when the Lailazus Tri-Porter requires a 4 layer shape
Done • Priority: High • Fix: None • Game: 1.0.0-alpha2-rc1 • Resolution: Obsolete

In Manufacture Mode, there is a 3 Shape Layer restriction that prevents creating the 4 Shape Layer shape required for the Lailazus Tri-Porter Trade Station. When attempting to stack a 4th layer onto a shape, the top layer is destroyed, leaving only 3 layers. This makes it impossible to legitimately create the required shape for this specific converter. The issue can be observed by comparing a shape from a Signal Producer (which bypasses the restriction) versus a manually stacked shape. The ga...
💬 Threads: [1.0.0-ALPHA2-RC1] Manufacture mode is r

Found 5 similar reports • Searched 3,719 reports • Use /check-duplicates to recheck

[drifting elm]

it's intended, shapes have a limit of 4 layers (also see the stacker codex page)

[blazing sorrel]

thanks, but this shape is a goal to unlock milestone 8 in the manufacture mode. Or I missed something to create this shape?

[drifting elm]

the shape asked doesn't have pins on the second layer (unlike what you're making)

[blazing sorrel]

Sorry but... I think I'm producing towards the right goal ( with pins on the second layer)

[drifting elm]

the shape asked has pins on the third layer, but what you are making has pins on the second layer

note that you can click on a belt then in the tooltip on the right, click on one of the shapes displayed to open them in the shape viewer and see what you are making

[blazing sorrel]

Of course I know the belt has a preview function. And it doesn't even matter, if you call it 2nd or 3rd layer, where pins lay on. The point is: the top layer (of a 3-layered shape) is destroyed when stacked onto a new layer. Thanks for your reply but it's really not helping

[drifting elm]

that's the point tho, your shape is not 3 layers, it's 4, there are pins below the white and uncolored squares 😅

[blazing sorrel]

Now I get it. I added a pin-layer unintendedly. That solves my problem. Thanks a lot for your help and sorry for the stupid mistake 🙃. Have a nice weekend 🙂