
Non-intutive input bus sharing between different multiblock controller types
SeanMASilva opened this issue ยท 2 comments
Your GTNH Discord Username
No response
Your Pack Version
2.7.0 & 2.7.2
Your Server
SP
Java Version
Java 17
Type of Server
Single Player
Your Expectation
With the introduction of steam multis, I built a steam centrifuge and squasher that wall shared a single input bus for a benzene setup (running cells -> compressed air and compressed air -> N2 + O2 cell). I expected this system to work with empty and compress air cells sharing the input bus, but eventually this system stalled because compressed air cells refused to enter the input bus.
I believe it is each of the multis claiming the input bus, and when the compressor claims the bus, since compressed air cells aren't a valid compressor ingredient, they aren't allowed in the bus. Manual interactions still work.
Steps:
- Build steam centrifuge and compressor wall sharing an input bus, do not turn them on. (They are also sharing output and steam input)
- Manually update compressor's structure
- Now automated forms of insertion fail for compressed air cells on the input bus (EI conduits, hoppers, GT pipes tested)
- Manually update centrifuge's structure
- Now automated forms of insertion work again
Separating the input buses between the multiblocks makes them work as expected.
The Reality
Steam Compressor and Centrifuge seem like they should share the same input bus with empty cells and compressed air cells.
But automated IO refuses to insert compressed air cells after the Steam compressor runs a recipe, and either machine is running
Your Proposal
I believe this claiming may be a performance thing/hard to change, so add a note in the quest book and in the tool tip on the input bus that "Steam multiblocks may not share input busses nicely"
Final Checklist
- I have searched this issue tracker and there is nothing similar already. Posting on a closed issue saying the bug still exists will prompt us to investigate and reopen it once we confirm your report.
- I can reproduce this problem consistently by follow the exact steps I described above, or this does not need reproducing, e.g. recipe loophole.
- I have asked other people and they confirm they also have this problem by follow the exact steps I described above, or this does not need reproducing, e.g. recipe loophole.