#[1.0.0-alpha5-rc2] Train capacity in codex says space instead of machine level
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 35 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/
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.
Incorrect platform units number for buildings in Knowledge Panel
Done โข Priority: Medium โข Fix: Dimension Update [0.1.0] โข Resolution: Done
The Codex shows incorrect Space Platform unit costs for Structures. When placing buildings, the displayed cost does not match the actual Space Platform capacity consumed. For example, some buildings show 4 units but only consume 2 Space Platform foundation units. This creates confusion about actual platform capacity usage. The issue has been fixed by adjusting the chunk limit calculation so platforms now correctly cost 1 unit again.
Train loaders show wrong capacity in side panel after upgrading
Done โข Priority: High โข Fix: Dimension Update [0.1.0] โข Resolution: Cannot Reproduce
Train loaders and unloaders display incorrect capacity values in the side panel after purchasing capacity upgrades. The issue occurs when upgrading Train Capacity technology to level 4 or higher - the capacity number shown in the info panel does not update to reflect the new value. This is a visual bug only, as the actual capacity functions correctly. The displayed capacity corrects itself after saving and reloading the savegame. The report was filed in rc009 but later closed as unreproducibl...
๐ฌ Threads: [0.0.9-rc7] Train Capacity Upgrade Level
Space levels 0,1,2 showing up as 1,2,2 on build mode
Done โข Priority: Medium โข Fix: None โข Resolution: Done
When building on a Space Platform in Machine View, the level indicator displays as 1,2,2 instead of the correct 0,1,2 after the new Machine Level 0 build update. This occurs in Classic Mode when switching between levels using the E and Q keys. The issue has been observed in both the main game and Editor mode. Expected behavior is that the Machine Level numbers should correctly show 0,1,2 to match the recent changes that introduced level 0.
Incorrect title for long rail up in Codex train/rollercoaster pack
To Do โข Priority: Low โข Fix: None โข Game: 1.0.0-alpha4-rc1
The Codex entry for the long rail up in the train/rollercoaster pack section displays an incorrect title. It currently reads "Long rail up" but should say "Long Rail" or "Long Rail Up/Down." The issue can be reproduced by opening the Codex in Classic Mode and navigating to the train/rollercoaster pack section.
๐ฌ Threads: [1.0.0-A3-RC1] the title in codex/train/
Knowledge panel does not adjust operator levels in hexagonal mode
Done โข Priority: Low โข Fix: 4 - Early Access โข Resolution: Won't Fix
The Codex does not adjust Operator Level information when playing in the Hexagonal scenario. The displayed content remains the same as in the default mode rather than reflecting hex-specific values. This has been marked as won't fix due to the effort required to implement the change.
๐ฌ Threads: [1.0.0-A3-RC1] some codex information do