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
Trying to convert a "Dual interface p2p" back into a "ME interface" e.g. using "advanced memory card". the placed "Dual interface p2p" converts into an "ME interface". And returns a Dual interface back to me.
The Reality
the placed "Dual interface p2p" converts into an "ME interface" as it should be doing. but this time it returns a "Dual interface P2P " back to me. so I got 2 p2p now, a ME interface p2p and the Dual interface p2p
Your Proposal
return a Dual interface instead of another Dual interface P2P
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
Christian2B
Your Pack Version
2.7.1
Your Server
private server
Java Version
Java 21
Type of Server
Vanilla Forge
Your Expectation
Trying to convert a "Dual interface p2p" back into a "ME interface" e.g. using "advanced memory card". the placed "Dual interface p2p" converts into an "ME interface". And returns a Dual interface back to me.
The Reality
the placed "Dual interface p2p" converts into an "ME interface" as it should be doing. but this time it returns a "Dual interface P2P " back to me. so I got 2 p2p now, a ME interface p2p and the Dual interface p2p
Your Proposal
return a Dual interface instead of another Dual interface P2P
Final Checklist
The text was updated successfully, but these errors were encountered: