[1.0.0-BETA6] Belt Filter doesn't show conflicts

[dark crest]

The belt filter doesn't show conflicts when shape input, signal input or shape outputs are obstructed

[gaunt harbor]

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 22 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-4462] — 👀 55% similar

No conflict indicators between space belts and platforms
To Do • Priority: Medium • Fix: 1.1 Release [1.1.0]

Space Belts do not show Conflict indicators when they intersect or overlap with Space Platforms. The issue is visible when Space Belts connect to Shape Wagon Loaders, where the visual appearance suggests an intentional connection but no conflict warning appears. Players expect to see conflict indicators when structures overlap improperly to identify placement issues. This makes it difficult to distinguish between valid and invalid Space Belt placements in relation to platforms.

2. [SPZ2-4711] — 👀 50% similar

Space Belts missing Wrong Connection warning
To Do • Priority: Medium • Fix: 1.1 Release [1.1.0]

Space Belts do not display a wrong connection warning when connected to Space Pipes on the same line. The issue can be reproduced in any game mode by enabling cheats, placing a Space Belt and Space Pipe connected to each other, and observing that no conflict or warning appears. The expected behavior is that connecting incompatible transport types (belts for shapes and pipes for fluids) should trigger a warning to alert the player of the invalid configuration.
💬 Threads: [0.1.0-PRE8-RC1] Space Belts missing Wro

3. [SPZ2-3403] — 👀 48% similar

Simulated Buildings conflicts not shown as conflicts
Done • Priority: High • Fix: None • Resolution: Won't Fix

Simulated Buildings such as Rotator and unstacker do not properly display Conflict when their Output is connected to their Input. Instead of showing a Conflict, the Signal propagates through the circuit, causing flickering. The expected behavior is that this circular connection should be detected and displayed as a Conflicting Signal, similar to how conflicts are handled in regular Wire systems. This issue was marked as Won't Fix as of November 13, 2025.

4. [SPZ2-3515] — 👀 42% similar

Reporting of Conflict on swapper if output is one sided
Done • Priority: Medium • Fix: Future • Resolution: Won't Fix

The game reports a conflict warning on the Swapper when the output is blocked by a Belt Catcher, even when that particular output side will never produce any shapes in the current configuration. This occurs when one output of the Swapper is intentionally left unused or blocked. The player expects no warning in this case since there will never be actual output on that side. The issue causes unnecessary conflict warnings for valid one-sided Swapper configurations. A feature to ignore conflicts ...

5. [SPZ2-5531] — 👀 38% similar

Conflicts showing up on launcher and catchers not connecting platforms
Done • Priority: Critical • Fix: 1.0 Release [1.0.0] • Resolution: Fix Verified

Belt Launchers and Belt Catchers incorrectly display Conflict indicators when placed over other Structures, even though they are functioning correctly. This occurs when building Conveyor Belts perpendicular over existing buildings with the Conflicts challenge enabled. The issue also caused placement problems where belts would auto-connect to launchers inappropriately and visual glitches with end caps. The fix disables conflict rendering entirely for Belt Launchers and Catchers as a compromise...

6. [SPZ2-4785] — 👀 35% similar

Conflict error sign shown on swapper with no production
Done • Priority: Medium • Fix: None • Resolution: Done

A Conflict error sign is displayed on Swappers that have no production because they are being used as Stackers. This primarily happens when building Belt Lifts on the unused sides of the Swapper. The game currently cannot detect whether there will be an Output or not, so it shows the Conflict signal by design. The expected behavior would be to either mark non-producing Swappers as exceptions to Conflict signals or leave it as intended. This issue has been marked as working as intended and won...
💬 Threads: warning appearing when output is always

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

[pure rock]

iirc happens with painters too, seems to be on buildings where some inputs/outputs are expected to be unused in some configurations

[dark crest]

I understand why it is the case with paint inputs on painters, because they will probably not all be used, but with belt filters i'd assume the signal input and shape input will always be used

[civic orchid]

That is expected, it is disabled for painters and belt filters. since you can use belt filters as a simple gate for example (i.e. 0/1 input signal) that never uses the side output

[pure rock]

then shouldn't the conflicts be disabled only for the side output, and still work for the other inputs and outputs ?

[civic orchid]

I don't think we support that rn

[faint briar]

I really like the fact that the side output doesn’t show conflict.

[drifting wasp]

Working as Intended for the time being. I recommend adding this to #💡suggestions 🙂