Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[1.10.2] Using ActuallyAdditions Phantom Energyface with Energy Conduit voids energy #4083
Energy is voided.
What you expected to happen:
Steps to reproduce:
Affected Versions (Do not use "latest"):
Yea, I know. And I still don't know why this would be an Actually Additions problem. All I do is pass on the capability / energy values of the block that the Phantomface is connected to, so this would just generate somewhat of a loopback or whatever, but it shouldn't void power.
First guess would be that you are exposing the capability of a conduit-side that is not connected to anything. But I need to get into the debugger to see what actually happens. Just wanted to link you in.
I'm just surprised this doesn't give an endless loop. As the phantomface is no conduit block, our loop detection doesn't work here. It's probably a bad idea to link blocks to themselves...the endless loop would actually be the correct behavior for conduits here.
EnderIO should not accept energy when it doesn't want to accept energy.
I literally don't check if you want to accept energy, I just push energy. I assume you're doing something similar with conduits?
This is just a guess, but I assume connections start uncached, so you cache them. While caching them, connections start connected. So when you replace the conduit the phantomface is linked to, it sees itself and goes "I can push power here" and caches it like that. Then it just attempts to push power and for some reason that causes power to be voided.
Keep in mind Forge itself doesn't let you push power when you're not allowed to push power, regardless of if you've checked if you can push power.
I haven't tested with PowerCrops but I doubt I'd be able to reproduce race conditions with it. Only phantomfaces can expose race conditions like this.