[Bug] Entangled ME Controller
Lousheng opened this issue ยท 5 comments
This would result in the ME Interface being blacklisted as well, so if possible could you whitelist just that block?
I really don't see this as deserving a blacklist.
Entangled forwards capabilities, no? It makes sense for RS, AE2 etc to be unable to form networks through entangled blocks. That's fine, they have their own wireless solutions.
But what they don't have solutions for is wireless moving of items, fluids etc.
If a pattern provider were to push into an entangled machine, that'd work fine. But then if that machine wanted to eject...
The natural solution to that is to entangle the pattern provider, but that's not doable with the blacklist.
Yeh.. running into the same thing... Can't entangle controller, can't entangle p2p tunnels, cabels... Or you can but it doesn't do anything.. Latest AE2 on 1.19.2 (ATM8)
Not sure if anyone actually reads these issue logs as this one seemed to have been from 2021 already.
I do read all these issues. I just have a lot of mods to maintain and update, and not a lot of time. This issue is relatively minor, so I prefer to work on higher priority stuff in the time I have.
In regards to the actual issue, the entangled blocks are not intended allow connecting Applied Energistics (AE2) networks through them. It is simply incompatible with AE2's network discovery.
The cable connected to the entangled block will tell the bound block 'hey I've been placed here on your west side, let's connect our networks'. Then when the bound block later tries to check for a block on it's west side, it won't find the cable or it might even find a different cable. This inherently leads to issues.