Duplicate "ghost" interfaces
tomm2000 opened this issue · 6 comments
Describe the bug
The network reports the existance of "ghost" interfaces on the network, these are duplicates of other interfaces. Even after removing the original interface the "ghost" is still present (and still shows in the interface terminal list). I've notice this happen mostly with interfaces inside compact machines.
To Reproduce
from what i gathered this is when it happens, tho im not sure if it happens all the time:
-
create a compact machine (https://www.curseforge.com/minecraft/mc-mods/compact-machines)
-
connect an interface inside the machine using ME capability adapters (https://www.curseforge.com/minecraft/mc-mods/capability-adapter)
-
put a crafting pattern inside the interface
Expected behavior
There should not be duplicates of the interface
Additional context
The interface is duplicated, both the ghost and real interface show up in the terminal and both are in the same location:
After removing the real interface the "ghost" is still there, it still shows in the terminal and with the highlight:
Environment
The modpack is https://www.curseforge.com/minecraft/modpacks/enigmatica-2-expert-extended version 1.29.1
The modpack is hosted on a server
- Minecraft Version: 1.12
- AE2 Version: ae2-uel-v0.56.2
- Forge Version: 14.23.5.2860
Have you tried using quantum bridge internally? If this is the case, the display is normal. It's just an adapter problem @tomm2000 @PunishedBadger
Tested with quantum bridge and it worked fine on server restart. Suspect you're right and it's a capability adapter issue. Found a similar issue from a while ago ruifung/MECapabilityAdapter#13
Tested with quantum bridge and it worked fine on server restart. Suspect you're right and it's a capability adapter issue. Found a similar issue from a while ago ruifung/MECapabilityAdapter#13
I recently realized that the Part variant of this adapter cannot connect to the ME network. So I guessed this question
glad to help you
It appears that something was broken when capability adapters was rewritten for 1.1. Reverting to 1.0 fixes the problem.
Since this is confirmed to be more of a capability adapter mod issue, I'm closing this for now.