Disclaimer
I Was Requested by HenryLoenwind to make an issue if this makes no sense or is completely inaccurate it because i have no idea what I'm talking about

Whats going on?
On server reload Ender IO Conduits disconnect from spatial pylons due to "AE2 blocks change what they can provide to connect to and don't notify their neighbours about it"

To Reproduce

1. Install AE2, Ender IO and Ender IO AE2 Conduits
2. Make a basic pylon setup
3. Disconnect and rejoin world

Expected behaviour
For the API to notify neighbours on restart / For Ender IO Conduits to reconnect to spatial storage on restart like smart cables

Environment

• Single player
• Minecraft Version:
• AE2 Version: rv6-stable-2
• Forge Version: 14.23
• EnderCore 0.5.41
• Ender IO 5.0.36

Additional context
Request from HenryLoenwind

Before Restart

After Restart

@EpicSquid linking you in here

Ender IO assumes that every single conduit has full control over exposing connections depending on various conditions like how it's configured, available neighbours and so on, thus requiring that everything else has to notify them about changes.
AE2 on the other hand assumes full control about how a network is constructed and each part/block just announces the connectable sides in a static way, regardless of any neighbours and instead the block itself notifies the network once it wants to change. E.g. to avoid having thousands of cables constantly sending neighbour updates for mundane stuff.

As long as these opposed design approaches exist, it's pretty much impossible to have it work perfectly in every case.