As soon as I push a minecart thru a cart assembly another player gets disconnected from the server.

When the player is near (around 50 Blocks perhaps if he has theoretical line of sight) the cart that went thru an assembly another player gets disconnected.

The player's game doesn't crash and the server is still running, for me everything runs normally.
The error says something about index 5 or sometimes 6 being out of bounds.
The log files of the player who got kicked just says "null, null, null, null ....."
We use the newest version (released 2 days ago).
He is able to use the cart assembly in a singleplayer world.
The Server is not showing any errors in the console.

We tested multiple things:

• Same game settings
• Empty inventory
• We switched around who places the rails, carts, lever, block on top, pushed the cart.

That is a known bug to do with NBT data exceeding the maximum, which causes that error. I'm not sure why it happens with simple contraptions, and only to some people. Hopefully it'll be fixed soon.

Thanks for giving me some info.
If there are any workarounds like deleting some files that would be nice.

If it happens by accident you can kill the minecarts with a command.

Same issue here. But it's just that one guy on my server who gets kicked. It's weird

I replicated this bug, and when another player came to look at it, they crashed as soon as they went near it as well.

So at the moment I have the following:
We have Player A, B, C and me
Player B and me don't get kicked from the server.
Player A and C get kicked and can only join if the minecart gets broken or goes thru the cart assembly again powered off.

As a work around:
Place the cart assembly from South to North or revers when creating a minecart contraption.
The cart can move along the rails to the west or east afterwards.
One can place a cart assembly from west to east if the rail forms a small "3x(3+N)" loop.

Patterns that should work:

We were having this issue last night even tried the north and south. Had our guy glitching restart his client and came back fine. Hope that helps

This issue appears to have the same root cause as #579 .

Can confirm the above N/S workaround works fine for me

This was addressed in 0.3c, please re-open if this is still an issue.