Version: (make sure you are on the latest version before reporting):

• Minecraft: ... 1.18.2
• Forge: ... 40.1.31
• Powah: ... 3.0.1

Issue description:

when trying to directly attach a flux plug(fluxnetworks) to a reactor the plug isn't extracting. Only reason I mention this is because it worked in the original mod.

Steps to reproduce:

set up a functioning reactor
set up a flux network
attach a flux plug to one of the slots.
attach flux point to any storage and what should happen is the plug extracts and point sends it to storage.

Is this a crash?, please includ it here: (Recommended to use Gist)

...

https://www.curseforge.com/minecraft/mc-mods/powah-rearchitected/files this version of powah.

Can confirm I have the same issue - the only way flux plugs work is to use mekanism cables. Powah cables and Energy Pipez didn't work.

Probably a bug with these cables because I see no reason why it shouldn't work.

Put aside this issue first, your https://github.com/Technici4n/Powah/blob/1.18/forge/src/main/java/owmii/powah/forge/ForgeEnvHandler.java#L135 should better return a cached value rather than a new LazyOptional. And you should call

event.addListener(() -> { //lazyOptionals.invalidate() })

to invalidate these LazyOptional objects.

I am deliberately ignoring the contract of LazyOptional because I think the design is stupid and the benefits are unclear. I don't think it's related to the issue, since I am just querying the capability and trying to push energy to it. Unless maybe I got the direction wrong?

Yes, it seems like I forgot to add .opposite somewhere... Should be an easy fix.