FTB Infinity Client Disconnect on login "A fatal erorr has occurred, this connection is terminated"

[John Freeman]

Title:

FTB Infinity Client Disconnect on login "A fatal erorr has occurred, this connection is terminated"​

Launcher Version:

​

Modpack:

FTB Infinity​

Modpack Version:

2.3.5​

Log Link:

http://pastebin.com/aZQVdvpV​

Details of the issue:

There would be a typical issue of the client disconnecting when trying to remove upgrades from a resonating barrel with additional upgrades like hopper or redstone. After moving the barrel away from what it was depositing into then attempting to remove upgrades again, the client disconnects with "A fatal erorr has occurred, this connection is terminated." Trying to relog results in the same issue, as does re-downloading the pack and connecting. World loads up for a second, see everything briefly with just enough time for the UI to show and then another disconnect. The error in particular is:

[22:21:50] [Client thread/ERROR] [FML]: There was a critical exception handling a packet on channel JABBA
java.lang.NullPointerException
at mcp.mobius.betterbarrels.common.blocks.StorageLocal.readTagCompound(StorageLocal.java:186) ~[StorageLocal.class:?]
at mcp.mobius.betterbarrels.common.blocks.TileEntityBarrel.func_145839_a(TileEntityBarrel.java:509) ~[TileEntityBarrel.class:?]
at mcp.mobius.betterbarrels.network.Message0x00FulleTileEntityNBT.channelRead0(Message0x00FulleTileEntityNBT.java:46) ~[Message0x00FulleTileEntityNBT.class:?]
at mcp.mobius.betterbarrels.network.Message0x00FulleTileEntityNBT.channelRead0(Message0x00FulleTileEntityNBT.java:10) ~[Message0x00FulleTileEntityNBT.class:?]
at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:98) ~[SimpleChannelInboundHandler.class:?]
at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:337) ~[DefaultChannelHandlerContext.class:?]
at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:323) ~[DefaultChannelHandlerContext.class:?]
at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) ~[MessageToMessageDecoder.class:?]
at io.netty.handler.codec.MessageToMessageCodec.channelRead(MessageToMessageCodec.java:111) ~[MessageToMessageCodec.class:?]
at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:337) ~[DefaultChannelHandlerContext.class:?]
at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:323) ~[DefaultChannelHandlerContext.class:?]
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785) ~[DefaultChannelPipeline.class:?]
at io.netty.channel.embedded.EmbeddedChannel.writeInbound(EmbeddedChannel.java:169) ~[EmbeddedChannel.class:?]
at cpw.mods.fml.common.network.internal.FMLProxyPacket.func_148833_a(FMLProxyPacket.java:77) [FMLProxyPacket.class:?]
at net.minecraft.network.NetworkManager.func_74428_b(NetworkManager.java:212) [ej.class:?]
at net.minecraft.client.multiplayer.GuiConnecting.func_73876_c(SourceFile:78) [bcx.class:?]
at net.minecraft.client.Minecraft.func_71407_l(Minecraft.java:1661) [bao.class:?]
at net.minecraft.client.Minecraft.func_71411_J(Minecraft.java:973) [bao.class:?]
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:898) [bao.class:?]
at net.minecraft.client.main.Main.main(SourceFile:148) [Main.class:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_11]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_11]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_11]
at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_11]
at net.minecraft.launchwrapper.Launch.launch(Launch.java:135) [launchwrapper-1.12.jar:?]
at net.minecraft.launchwrapper.Launch.main(Launch.java:28) [launchwrapper-1.12.jar:?]​

 

[AuricPolaris]

Definitely Jabba. Is this on a server? If so, you could possibly have someone remove it for you (perhaps with World Edit). If this is in SP, then McEdit is always an option, assuming you know the relative coords.