#[1.0.0-A3-RC1] the label cannot vertical paste
8 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 19 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/
Mirroring a Platform with label does not rotate the text
To Do β’ Priority: Low β’ Fix: None
When mirroring a Machine Platform that contains a Label, the text does not rotate correctly. Using the standard Mirror function moves the Label to the correct position but leaves the text at its original rotation instead of flipping it. Using Inverse Mirror rotates the text 180 degrees, causing it to appear upside down. The expected behavior is for the Label text to mirror appropriately along with its position, similar to how Conveyor Belts rotate when mirrored. This affects the readability a...
Placement behaves differently depending from which direction you drag
Done β’ Priority: High β’ Fix: Dimension Update [0.1.0] β’ Game: 07.40.15 β’ Resolution: Done
When dragging to place structures, the Placement behavior was inconsistent based on drag direction. Dragging from right to left would incorrectly keep a Split in the placement, while dragging from left to right would not. In both cases, only a turn should have been placed without any Split. This affected the autosnapping feature during building placement. The issue has been fixed and verified, with autosnapping now working correctly regardless of drag direction.
The selection border snaps to a centered position over the mouse pointer on rotating
Done β’ Priority: Highest β’ Fix: None β’ Resolution: Duplicate
When rotating a copied Area Selection, the selection border incorrectly snaps and centers itself to the Cursor position, even though the Cursor hasn't moved. This happens when using Copy/Paste functionality in Classic Mode - after selecting and copying structures, repeatedly pressing R to rotate causes the border to reposition. The expected behavior is that the Area Selection border should remain in its original position relative to the Cursor during rotation, rather than jumping to center on...
Placing a blueprint then deselecting deselects the entire blueprint toolbar
Done β’ Priority: High β’ Fix: Dimension Update [0.1.0] β’ Resolution: Done
When placing a Blueprint from the Blueprint Toolbar and then deselecting it, the entire Toolbar gets deselected instead of remaining open. This makes it very tedious to place multiple Blueprints in succession, as the player must reopen the Toolbar each time. The expected behavior is that the Toolbar should remain open and active after placing a Blueprint, allowing for quick successive placements. The issue was initially reported as occurring with Labels specifically, but appears to affect the...
Placement does not override rotation after placement
Done β’ Priority: Critical β’ Fix: 1.0 Release [1.0.0] β’ Game: 19.00.35 β’ Resolution: Fix Verified
When a player rotates a structure to face one direction, then hovers it over a conveyor belt which auto-rotates it to face another direction, and confirms placement, the structure incorrectly reverts to the original rotation when moved to a different tile. The expected behavior is that after confirming placement, the current rotation should be updated to match the placed structure's rotation, so the structure maintains that same orientation when the cursor is moved. This issue has high priori...
β
This bug has been already fixed on internal builds and should be fixed with the next release. Should this bug not be fixed with the next build, as the reporter, you can use /reopen-bug to reopen it again. Alternatively you can report a new issue.