Malte Langkabel e3eb70d416 stop the output chips second-guessing the buffers they stand for
The output chips tested each item against the unlock state before drawing it.
That was the right guard when the chips were flattened from a recipe's full
group list, locked groups included -- but the cycle now carries only the groups
the building can be handed, so every producible id reaching this loop is already
one the player can have.

Nor could the buffered ids need it: an item enters an output buffer only by
being yielded by a group the building was picking from. A chip dropped for being
locked would therefore never be hiding a locked item; it would be hiding a
buffer with something in it, which is the one thing the section exists to show.

The input-side test stays for now, though it is close to dead for its own
reasons -- see the note in the follow-up rather than reading anything into its
survival here.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ne3mejABZoLWKLh8fgpM3x
2026-08-20 22:50:23 +02:00
2026-07-12 09:16:49 +02:00
2026-07-22 21:44:20 +02:00
Description
No description provided
8.7 MiB
Languages
C++ 96%
CMake 2.2%
Python 1.1%
C 0.7%