Game crashing when connecting longer lengths of cables to Network receiver in different (Modded) dimensions.
Closed this issue · 1 comments
Describe the bug
I had a Mekanism manufacturing area built in a compact cube - I connected quite a few machines to the network receiver * this caused the network receiver to turn off - When broke the cable linked to a long stretch of cable (Which wasn't connected to any importers, exporters or crafters) the game crashed.
I managed to get the Network receiver to come back online once before the crash by reloading the world but when I added an exported the receiver turned off again so I disconnected the exporters and the crash occurred when breaking a cable nearer the receiver.
How can we reproduce this bug or crash?
- Travel to another dimension
- Set up a network receiver (And connect it to your controller)
- Connect multiple cables to the receiver and some importers, exporters & autocrafters.
What Minecraft version is this happening on?
Minecraft 1.21.1
What NeoForge or Fabric version is this happening on?
21.1.168
What Refined Storage version is this happening on?
RefinedStorage2
Relevant log output
Latest.log:
https://gnomebot.dev/paste/mclogs/lwBVN46
Debug.log:
[debug.log head](<https://gnomebot.dev/paste/mclogs/XcObG9A>) / [tail](<https://gnomebot.dev/paste/mclogs/rNskYJN>) (~36k lines)
Crash-Server.txt:
https://gnomebot.dev/paste/mclogs/XfwZ3N1
Curseforge-Launcher.log:
[launcher_log.txt head](<https://gnomebot.dev/paste/mclogs/Jco3HU9>) / [tail](<https://gnomebot.dev/paste/mclogs/68dbX5b>) (~54k lines)
KubeJS: client.log:
https://gnomebot.dev/paste/mclogs/UA0Qqw2
KubeJS: Server.log:
https://gnomebot.dev/paste/mclogs/tKs5hp0
KubeJS: Startup.log:
https://gnomebot.dev/paste/mclogs/PUdFN0J
Crash_Assistant_App.log:
https://gnomebot.dev/paste/mclogs/O4wqk54
All the Mods 10 - 2.47 crashed.
### Mod list changes beyond the modpack:
�[2;34mMod list wasn't modified.�[0mDuplicate of #949