#[1.0.0-alpha5-rc2] Codex global transmitter description incomplete

8 messages ยท Page 1 of 1 (latest)

outer folio
#

It says the channel can be either a shape or a number but it can also be a color

cunning garnetBOT
#

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 39 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/

#

Controlled channel for global signal can only be shapes
Done โ€ข Priority: High โ€ข Fix: Dimension Update Patch 1 [0.1.1] โ€ข Resolution: Done

The Global Signal Transmitter and Global Signal Receiver could only use shapes to set their controlled channel, not numbers or other signal types. This occurred when players tried to use a Signal Producer with a number value to configure the channel for these wireless communication devices. Players expected to be able to use any signal type for channels, especially since Signal Producers support number output. The limitation was not clearly communicated in the game and was frequently criticiz...

#

Operator shape signal instructions are incorrect
Done โ€ข Priority: High โ€ข Fix: Dimension Update [0.1.0] โ€ข Resolution: Done

The Codex page for Operator Shape signals contains incorrect instructions. It tells players to build a Global Signal Receiver and set the channel to Operator Shape, when it should instruct them to build an Operator Signal Receiver instead. This causes confusion about which machine to use for receiving operator goal shapes. The issue has been fixed and verified in the latest version.

#

Wrong description of Belt Filters in Knowledge Panel
Done โ€ข Priority: Medium โ€ข Fix: Dimension Update [0.1.0] โ€ข Resolution: Done

The Codex / In-game wiki / Knowledge panel / Encyclopedia contains incorrect text in the Wires / Logic Wires / Signal Wires section about Controlling Conveyor Belts / Belts. The description of Belt Filter / Item Filter / Shape Filter behavior states that shapes / items are routed "to the right" when the input signal / digital signal is a non-zero number or when matching shapes are detected, but shapes actually go forward / straight in these cases. The text description became incorrect when an...

#

Layer Limit in Knowledge Panel inconsistent (5 layers on Insane)
Done โ€ข Priority: Low โ€ข Fix: 4 - Early Access โ€ข Resolution: Done

The Codex states that shapes can have 4 layers at most, but this is incorrect when playing the Insane scenario which allows 5 layers. The Knowledge Panel does not adjust its information based on the active scenario. Players in Insane mode see outdated or wrong information about the layer limit. The panel should dynamically show "5" instead of "4" when Insane mode is active, or include a note about the exception.

#

Rotator descriptiosn are inconsistent for CW and CCW
Done โ€ข Priority: Low โ€ข Fix: 2 - Demo โ€ข Resolution: Done

The Rotator machine descriptions are inconsistent between the two rotation variants. The 90 CCW Rotator description includes the additional text "by 90 degrees" while the 90 CW Rotator description is missing this same text. This inconsistency has caused confusion for translators working on the game. Both rotator variants should have matching description formats for clarity and consistency.

#

Delivery Indicators codex page lacks clarification that indicators use Shape Previews
Done โ€ข Priority: High โ€ข Fix: 1.0 Release [1.0.0] โ€ข Resolution: Fix Verified

The Codex page for Delivery Indicators does not clarify its relationship to Shape Previews. When opening the Codex in Classic Mode under the Regular scenario and viewing the Research section for Delivery Indicators and the Shapes section for Shape Previews, there is no connection drawn between the two features. The expected behavior is that the Codex should indicate that Delivery Indicators and Shape Previews are related. This has been fixed by consolidating The Vortex delivery page into the ...
๐Ÿ’ฌ Threads: [1.0.0-ALPHA3-RC1] Vortex delivery indic