[1.0.0-A5-RC2] Insane Mode and Ck Shape report

[astral cloak]

pre: I love to play without Secondary and Tertiary Color Fluid Patches and without colorfulness shape (as in Colorfulness 0%)
i noticed that the Ck Shape (which is need in jobs and Pre-Milestone shapes) is spawning so rare that the game becomes hard if you need them)
Here are my Test Saves and results:

Test 01 : Default Settings:
Ck Asteroids are there, but no black Fluid Patches
Also other black shapes where popup : Wk, Rk Sk (all Rare, intended?)

Test 02 : Colorfulness to 0%
Ck Asteroids only 3 times around the home-Grid from 9|A 0|-I till -10|A 0|K,
then nothing (searched; 50|A 0|-BW till -50|A 0|BY)
Also no Black Fluid Patches

Test 03 : Default Settings but Spiral off
Ck Asteroids are there, but no black Fluid Patches
Also other black shapes where popup : Wk, Rk Sk (all Rare, intended?)

Test 04 : Colorfulness to 0% and Spiral off
Ck Asteroids only 3 (same Locations??) times around the home-Grid from 9|A 0|-I till -10|A 0|K, then nothing (searched; 50|A 0|-BW till -50|A 0|BY)
Also no Black Fluid Patches

after tests, my opinion:
In Insane Mode, without colorfulness/tertiary colors selected, spawn Black Fluid Patches and more Shape Asteroids that contains the Ck shape anyway or forbit the (C)ROS algorithm to make shape with Ck or ck (Red. As of now: seams fixed, but still happen in CROS), as the END Milestone can be got from the research Station

Or:

In whatever mode that has Ck in (Pre) Milestone let Black (or White in RYB) Fluid Patches spawn (whatever setting is selected)

(just for notification : @opal wharf / @whole pebble)

Regards

[keen valve]

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 17 reports awaiting team review. Due to the high volume, it may take a little longer for us to get to yours.

📋 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-5690] — 👀 72% similar

For manufacture mode the first random operator level shape can require black crystals in a standard save
Done • Priority: Highest • Fix: 1.0 Release [1.0.0] • Game: 1.0.0-alpha3-rc1 • Resolution: Fix Verified

In Manufacture Mode, the first randomized Operator Level shape can require black crystals in a Regular scenario savegame, which should not occur when map generation has not been modified. This can be reproduced by starting a new Regular Manufacture Mode savegame, enabling cheats, and repeatedly advancing Operator Levels until a black crystal appears in the required Operator Shape. Black crystals should not be part of required random Operator Shapes under default settings. This issue was not o...
💬 Threads: [1.0.0-alpha3-rc1] CROS can generate bla

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

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

In Classic Mode on Hard or Insane scenarios, the Milestone 7 shape never becomes an Operator Shape. This can be observed by starting a new savegame, enabling cheats, opening the Milestones Screen, scrolling to Milestone 7, and comparing it to the Operator Shapes listed at the top. The Milestone 7 shape should become an Operator Shape but is missing from the list. The fix added Operator Levels for missing Hexagonal, Insane, and Hard milestones and ensured Operator Shape alignment with mileston...
💬 Threads: [1.0.0-A3-RC1] Insane Milestone 7 do not

3. [SPZ2-5649] — 👀 40% similar

Insane mode won't start if the "no straight stacker" challenges option is enabled
Done • Priority: High • Fix: 1.0 Release [1.0.0] • Game: 1.0.0-alpha3-rc1 • Resolution: Fix Verified

When starting a new Insane scenario with the "no Stacker (Straight)" challenge option enabled, the game fails to load and becomes stuck on a black screen with an infinite loading spinner. The issue prevents players from entering the game and viewing The Vortex as expected. This problem occurs specifically when creating a new save file in Insane mode with this particular challenge setting activated. The issue has been fixed and verified across all difficulty settings.
💬 Threads: [1.0.0-A3-RC1] Insane Scenario not start

4. [SPZ2-5851] — 👀 38% similar

No hard-coded green fluid asteroids in manufacture mode when patch likelihood set to 0%
Blocked • Priority: Medium • Fix: 1.0 Release [1.0.0]

In Manufacture Mode with the Regular scenario, setting the Fluid Asteroid Extraction Spots likelihood to 0% in Map Generation causes green Fluid Asteroids to not appear. Only red and blue Fluid Asteroids are visible. The expected behavior is that hard-coded green Fluid Asteroids should still appear alongside red and blue ones regardless of the likelihood setting. A fix has been developed and is awaiting merge.
💬 Threads: [1.0.0-alpha5-rc1] No hard-coded green f

5. [SPZ2-5543] — 👀 35% similar

Moving back Shape Asteroids Patch Likeliness to 0% will cause the game to not have any more shape asteroids
Done • Priority: High • Fix: None • Resolution: Not A Bug

When the Shape Asteroid Extraction Spots Likeliness slider is moved to 100% and then back to 0% in the Map Generation settings during new game creation, all Shape Asteroids disappear from the map. At 0% initially, Shape Asteroids appear normally, but adjusting the slider to 100% and returning it to 0% removes all asteroids, preventing the Operator from mining Shapes. This was determined to be intentional behavior rather than a bug, as the custom map generation options are designed to allow cr...

6. [SPZ2-5438] — 👀 33% similar

Changing shape asteroid settings causes all the shape asteroids to vanish outside the vortex chunk in map generation
Done • Priority: High • Fix: None • Resolution: Not A Bug

When modifying Shape Asteroid settings in the map generation screen (excluding Patch Likeness), all Shape Asteroids disappear outside The Vortex chunk, leaving only Fluid Asteroids visible. This occurs in both Manufacture Mode and Classic Mode when creating a new game under Founder's Journey. The user expects Shape Asteroids to remain present outside The Vortex or Waste Provider chunk area regardless of configuration changes. However, this appears to be intended behavior when Patch Likeliness...

Found 6 similar reports • Searched 3,218 reports • Use /check-duplicates to recheck

[astral cloak]

[1.0.0-A5-RC2] Insane Mode and Ck Shape report

extra note : If Black (or White in RYB) Fluid Patches spawn in whatever modes/color choice then let the (C)ROS algorithm use all Black (or White) shapes as well, so it have a need

Yes i know if this happen also an other color can be created

[astral cloak]

Still for those who like to play the way i do... can be a problem then ...
and this report / bug is requested to made, we will see 😄

[whole pebble]

Okay, so I had a thorough review. In general:

• Classic - Insane is the only scenario that requires black shapes in jobs / milestones
• There are 3 hardcoded black shape patches in insane, so the scenario should always be 'completeable' no matter of your map settings
• With default settings black shapes can spawn in chunks farther away from the center, of any shape type
• It might be more difficult if you choose to disable colorfulness, as then you only get the 3 hardcoded ones, but it should always be possible (also - being hard is kinda the idea of insane, not? 😅 )

So I'd say works as intended - the ROS/CROS issue I'd treat as a separate part, looking into that now

[whole pebble]

Okay for the ROS issue - (C)ROS will keep needing black shapes.
But with the next alpha you'll be able to produce black/uncolored fluid.

So marking it as fixed for now 🙂

[keen valve]

✅ 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.