You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dedicated server
forge-1.12.2-14.23.5.2860
logisticspipes-0.10.4.49
Mekanism-Community-Edition-1.12.2-9.12.8 (Core, Generators, Tools)
Lots of others that are hopefully not relevant here
How to reproduce:
What I did was try to route a highspeed tube in parallel with a Mekanism Universal Cable transmitting power to the factory. When looking straight up however, the highspeed tube no longer oriented itself the right way and when placed it attempted to connect to the power cable instead, and crashed the client. (Handled by modded crash handler, so just kicked to main menu and could reconnect and play as usual).
I am a little surprised that this crashed the client and not the dedicated server, especially seeing the routing.pathfinder function being the last one in action here. I would have thought this code would have been run on the server instead, but the server didn't crash. Perhaps this is why? Run connection verification on the client first to avoid bringing down the server if something goes wrong?
Backtrace
java.lang.NullPointerException: Ticking block entity
at logisticspipes.routing.pathfinder.PipeInformationManager.isNotAPipe(PipeInformationManager.java:94)
at network.rs485.logisticspipes.world.WorldCoordinatesWrapper.connectedTileEntities(WorldCoordinatesWrapper.kt:60)
at network.rs485.logisticspipes.connection.AdjacentFactory.createAdjacentCache(AdjacentFactory.kt:47)
at logisticspipes.pipes.basic.CoreRoutedPipe.updateAdjacentCache(CoreRoutedPipe.java:177)
at logisticspipes.pipes.basic.CoreRoutedPipe.updateEntity(CoreRoutedPipe.java:378)
at logisticspipes.pipes.basic.LogisticsTileGenericPipe.update(LogisticsTileGenericPipe.java:214)
at net.minecraft.world.World.updateEntities(World.java:1838)
at net.minecraft.client.Minecraft.runTick(Minecraft.java:1847)
at net.minecraft.client.Minecraft.runGameLoop(Minecraft.java:1098)
at net.minecraft.client.Minecraft.run(Minecraft.java:6114)
at net.minecraft.client.main.Main.main(SourceFile:123)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.multimc.onesix.OneSixLauncher.launchWithMainClass(OneSixLauncher.java:243)
at org.multimc.onesix.OneSixLauncher.launch(OneSixLauncher.java:278)
at org.multimc.EntryPoint.listen(EntryPoint.java:143)
at org.multimc.EntryPoint.main(EntryPoint.java:34)
Mod versions
Dedicated server
forge-1.12.2-14.23.5.2860
logisticspipes-0.10.4.49
Mekanism-Community-Edition-1.12.2-9.12.8 (Core, Generators, Tools)
How to reproduce:
What I did was try to route a highspeed tube in parallel with a Mekanism Universal Cable transmitting power to the factory. When looking straight up however, the highspeed tube no longer oriented itself the right way and when placed it attempted to connect to the power cable instead, and crashed the client. (Handled by modded crash handler, so just kicked to main menu and could reconnect and play as usual).
I am a little surprised that this crashed the client and not the dedicated server, especially seeing the routing.pathfinder function being the last one in action here. I would have thought this code would have been run on the server instead, but the server didn't crash. Perhaps this is why? Run connection verification on the client first to avoid bringing down the server if something goes wrong?
Backtrace
java.lang.NullPointerException: Ticking block entity
at logisticspipes.routing.pathfinder.PipeInformationManager.isNotAPipe(PipeInformationManager.java:94)
at network.rs485.logisticspipes.world.WorldCoordinatesWrapper.connectedTileEntities(WorldCoordinatesWrapper.kt:60)
at network.rs485.logisticspipes.connection.AdjacentFactory.createAdjacentCache(AdjacentFactory.kt:47)
at logisticspipes.pipes.basic.CoreRoutedPipe.updateAdjacentCache(CoreRoutedPipe.java:177)
at logisticspipes.pipes.basic.CoreRoutedPipe.updateEntity(CoreRoutedPipe.java:378)
at logisticspipes.pipes.basic.LogisticsTileGenericPipe.update(LogisticsTileGenericPipe.java:214)
at net.minecraft.world.World.updateEntities(World.java:1838)
at net.minecraft.client.Minecraft.runTick(Minecraft.java:1847)
at net.minecraft.client.Minecraft.runGameLoop(Minecraft.java:1098)
at net.minecraft.client.Minecraft.run(Minecraft.java:6114)
at net.minecraft.client.main.Main.main(SourceFile:123)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.multimc.onesix.OneSixLauncher.launchWithMainClass(OneSixLauncher.java:243)
at org.multimc.onesix.OneSixLauncher.launch(OneSixLauncher.java:278)
at org.multimc.EntryPoint.listen(EntryPoint.java:143)
at org.multimc.EntryPoint.main(EntryPoint.java:34)
crash-2024-03-17_22.49.27-client.txt
MultiMC Modpack: Dead2's Reborn v3.5.1.zip
The text was updated successfully, but these errors were encountered: