Server kicks client when using request pipe, crafting pipe with chip, and interface pipe with no chip
nanoblack opened this issue ยท 3 comments
Server kicks a client that tries to use a request pipe to request an item from a crafting pipe if there is an interface pipe on the network with no chips inserted.
Using 4.3.7 b32, CodechickenLib 1.0.0.62, CodechickenCore 0.9.0.9
19:16:19 [SEVERE] A critical server error occured handling a packet, kicking 304
java.lang.NullPointerException
at mrtjp.projectred.transportation.RequestBranchNode$$anonfun$doCraftReq$1$$anonfun$apply$mcV$sp$1.apply$mcV$sp(requests.scala:191)
at mrtjp.projectred.transportation.RequestBranchNode$$anonfun$doCraftReq$1$$anonfun$apply$mcV$sp$1.apply(requests.scala:155)
at mrtjp.projectred.transportation.RequestBranchNode$$anonfun$doCraftReq$1$$anonfun$apply$mcV$sp$1.apply(requests.scala:155)
at mrtjp.projectred.core.utils.LabelBreaks.label(LabelBreaks.scala:13)
at mrtjp.projectred.core.utils.LabelBreaks.label(LabelBreaks.scala:25)
at mrtjp.projectred.transportation.RequestBranchNode$$anonfun$doCraftReq$1.apply$mcV$sp(requests.scala:155)
at mrtjp.projectred.transportation.RequestBranchNode$$anonfun$doCraftReq$1.apply(requests.scala:154)
at mrtjp.projectred.transportation.RequestBranchNode$$anonfun$doCraftReq$1.apply(requests.scala:154)
at mrtjp.projectred.core.utils.LabelBreaks.label(LabelBreaks.scala:13)
at mrtjp.projectred.transportation.RequestBranchNode.doCraftReq(requests.scala:153)
at mrtjp.projectred.transportation.RequestBranchNode.doRequest$1(requests.scala:50)
at mrtjp.projectred.transportation.RequestBranchNode.<init>(requests.scala:52)
at mrtjp.projectred.transportation.RequestRoot.<init>(requests.scala:341)
at mrtjp.projectred.transportation.RequestConsole.makeRequest(requests.scala:669)
at mrtjp.projectred.transportation.TransportationSPH$.handleRequestSubmit(packethandlers.scala:246)
at mrtjp.projectred.transportation.TransportationSPH$.handlePacket(packethandlers.scala:159)
at codechicken.lib.packet.PacketCustom$ServerTinyPacketHandler.handle(PacketCustom.java:201)
at codechicken.lib.packet.PacketCustom$CustomTinyPacketHandler.handle(PacketCustom.java:233)
at cpw.mods.fml.common.network.NetworkRegistry.handleTinyPacket(NetworkRegistry.java:433)
at cpw.mods.fml.common.network.FMLNetworkHandler.handlePacket131Packet(FMLNetworkHandler.java:429)
at net.minecraft.network.NetServerHandler.func_72494_a(NetServerHandler.java:2674)
at net.minecraft.network.packet.Packet131MapData.func_73279_a(Packet131MapData.java:61)
at net.minecraft.network.TcpConnection.func_74428_b(TcpConnection.java:470)
at net.minecraft.network.NetServerHandler.func_72570_d(NetServerHandler.java:233)
at net.minecraft.network.NetworkListenThread.func_71747_b(NetworkListenThread.java:54)
at net.minecraft.server.dedicated.DedicatedServerListenThread.func_71747_b(DedicatedServerListenThread.java:34)
at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:910)
at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:330)
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:777)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:659)
at net.minecraft.server.ThreadMinecraftServer.run(ThreadMinecraftServer.java:16)
You said that you request an item from crafting pipe if there is an interface pipe in system with no chip inserted right ???
But in my system i have interface pipe with cip inserted- i have broadcaster chip and item responder chip in my interface pipe and crafting chip in my crafting pipe, but i still get this error. Only if i use just one Liquicrafter in on crafting system, everything works fine, but if i have more then one liquicrafter in one system i get this error.
Yes, I was testing to make sure I had an understanding of how it all worked with just one crafting pipe and auto workbench and anytime I'd request the item the server would kick me with the above error. I then realized I forgot to put a chip in my supply chest pipe, dropped a broadcaster in, and it worked fine.
I did have the same error happen after I added another crafting pipe to the network, but I was able to trip it with only one crafting pipe.
Fix via 68da9c0