When the TGS is idle due to a full output bus, it should just sit there and not consume anything. Standard multiblock behavior.
The Reality
I got to watch it tick durability off the saw I inserted into the input, just while idle. I assume the behavior is that it's taking the durability off the saw first, before it checks whether or not it should run. It finds that it shouldn't run, waits a second to check again, finds the same, and rinse-repeat to just void saws.
Your Proposal
It should.... not do this?
Final Checklist
[X] 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.
[X] I can reproduce this problem consistently by follow the exact steps I described above, or this does not need reproducing, e.g. recipe loophole.
[X] 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.
Your GTNH Discord Username
Shadows#4865
Your Pack Version
2.6.1
Your Server
private
Java Version
Java 17
Type of Server
None
Your Expectation
When the TGS is idle due to a full output bus, it should just sit there and not consume anything. Standard multiblock behavior.
The Reality
I got to watch it tick durability off the saw I inserted into the input, just while idle. I assume the behavior is that it's taking the durability off the saw first, before it checks whether or not it should run. It finds that it shouldn't run, waits a second to check again, finds the same, and rinse-repeat to just void saws.
Your Proposal
It should.... not do this?
Final Checklist