63975d9ca87ce0e5b580e0397215dd376de83fe0
The output chips stopped testing the unlock state last commit; the input ones were left doing it, on a comment that had outlived its design -- buffers have been sized for the selected recipe alone for some time, not unioned over every recipe of the building's type. With the summary and the dialog now offering only recipes the player can run, the test is dead for a miner, smelter or assembler: step 4 unlocks a recipe only if it produces something unlocked, and step 2 has then already unlocked its inputs. It could still fire for a reprocessing plant, whose inputs no traversal propagates -- and firing is the bad case, not the good one. It would empty the input section of a plant that is running, while the summary directly above went on naming the material it eats. Both sections now say the same thing: one chip per buffer the building has. Whether a buffer exists is a fact about the building rather than about the player's progression, and one they cannot fill yet reads 0, which is what it holds. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ne3mejABZoLWKLh8fgpM3x
Description
No description provided
Languages
C++
96%
CMake
2.2%
Python
1.1%
C
0.7%