After placing a void fluid pipe connected to an MFR harvester (pipe taking sludge), the player that placed it gets disconnected from the server upon entering the game. Forge version is 7.10.118.1389.

[16:50:39] [Client thread/WARN] [FML/]: ****************************************
[16:50:39] [Client thread/WARN] [FML/]: * Null fluid supplied to fluidstack. Did you try and create a stack for an unregistered fluid?
[16:50:39] [Client thread/WARN] [FML/]: *  at net.minecraftforge.fluids.FluidStack.<init>(FluidStack.java:35)
[16:50:39] [Client thread/WARN] [FML/]: *  at net.minecraftforge.fluids.FluidStack.<init>(FluidStack.java:67)
[16:50:39] [Client thread/WARN] [FML/]: *  at buildcraft.transport.network.PacketFluidUpdate.readData(PacketFluidUpdate.java:87)
[16:50:39] [Client thread/WARN] [FML/]: *  at buildcraft.core.network.BuildCraftChannelHandler.decodeInto(BuildCraftChannelHandler.java:47)
[16:50:39] [Client thread/WARN] [FML/]: *  at buildcraft.core.network.BuildCraftChannelHandler.decodeInto(BuildCraftChannelHandler.java:22)
[16:50:39] [Client thread/WARN] [FML/]: *  at cpw.mods.fml.common.network.FMLIndexedMessageToMessageCodec.decode(FMLIndexedMessageToMessageCodec.java:77)...
[16:50:39] [Client thread/WARN] [FML/]: ****************************************

Partial log, because the full log somehow managed to become 192k lines long and causes pastebin to freeze upon trying to paste it. The very end of the log, with the errors, are in that log. Upon request I could figure out how to get the full log available. Why it's 192k lines is beyond me.

Because packets are sent a bit more often.

This is fixed in the 7.0 branch, but we'll backport it to 6.4.x soon enough.

Fair enough. Any tips on making our player able to get back on? Removing
the pipe?
On 25 Apr 2015 11:43, "Adrian Siekierka" [email protected] wrote:

Because packets are sent a bit more often.

This is fixed in the 7.0 branch, but we'll backport it to 6.4.x soon
enough.

—
Reply to this email directly or view it on GitHub
#2662 (comment)
.

@Lilylicious - wait. Why are you using an old version of BuildCraft? (Or seem to be, anyway.)

Good question, updating is first on the list. We are using a custom pack
based on an existing one, which included a requirement of a newer forge.
On 25 Apr 2015 11:54, "Adrian Siekierka" [email protected] wrote:

@Lilylicious https://github.com/Lilylicious - wait. Why are you using
an old version of BuildCraft?

—
Reply to this email directly or view it on GitHub
#2662 (comment)
.

Updated to 6.4.11, problem solved. Why do I forget to update before making issues?

Update.

Check the changelogs next time. They specifically mention fixing bugs for newer Forge.

(Also, update to 6.4.13 already.)