Omni directionally connected network breaks up into disparate networks when modifying/extending the same network upon world reload
Fatmice opened this issue ยท 7 comments
Issue type:
- ๐ Bug
Short description:
Steps to reproduce the problem:
- Create a new omni-directionally connected network, say for energy. Make sure it is working so that the sources and sinks are pushing and pulling energy.
- Have some extra omni connectors created with the same id. Save world and leave
- Reload world.
- Existing omni-directionally connected network should still be functioning.
- Add a new node to this network with the omni connectors crafted from before.
- Observe that this new node is all by itself and disconnected from the rest of the omni-directionally connected network even though the new one shared the same id.
- Break and replace the omni connector serving the energy sources.
- Observe that the sources are now all alone and soon all of the sinks will run out of power when they are all on the same network id...
Expected behaviour:
This really shouldn't happen?
Versions:
- This mod: 1.12.2-0.11.17
- Minecraft: 1.12.2
- Forge: 14.23.5.2768
Log file:
Can provide world + config + mods on request where this is happening.
I can't seem to reproduce this on the latest release (1.0.1). I tried multiple things, including your steps, but I can't seem to make it break.
@Fatmice Could you retry it with the latest version and see if you can reproduce it? (preferably with only ID (and optionally IT) installed)
Btw, how did you obtain your extra omni connectors? Did still they show the same group id in the tooltip after copying?
I will try later today. Extra connectors were created by copying the source. Yes they had the same group id in the tooltip.
Extra connectors were created by copying the source.
In creative-mode? Or via the crafting table copy recipe?
(both should work, but just to make sure I replicate it correctly)
Okay I've tested it in several ways, your new version fixed the problem...whatever you did.
Great!
Be sure to let me know if you (or anyone else) would encounter this problem in the future.