You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Shift+RMB on pipes should disable input and arrows should point only in configured direction.
The Reality
Pipe input is disabled correctly, but arrows appear going both sides making it unclear how pipes are actually configured. As far as I can tell this happens only when pipes are placed above the player and they are going in east-west direction. See video for demonstration.
Arrow should point arrows in configured direction(s).
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.
The text was updated successfully, but these errors were encountered:
Your GTNH Discord Username
munemune
Your Pack Version
nightly 893, 895
Your Server
SP
Java Version
Other versions in between
Type of Server
Single Player
Your Expectation
I am using Java 23.0.2.
Shift+RMB on pipes should disable input and arrows should point only in configured direction.
The Reality
Pipe input is disabled correctly, but arrows appear going both sides making it unclear how pipes are actually configured. As far as I can tell this happens only when pipes are placed above the player and they are going in east-west direction. See video for demonstration.
Video:
https://github.com/user-attachments/assets/af301543-7548-4d59-baf8-e3d33130851a
Your Proposal
Arrow should point arrows in configured direction(s).
Final Checklist
The text was updated successfully, but these errors were encountered: