Panik Pansen
Assigned
Reported
Comments
" (...) What is there to fix about it? It's caused by no data on the socket."
So in other words, this is a new bug that is just not going to be fixed?
On our server noone did anything with minecarts / rails, the error just started popping up as soon as the first player entered the end. We reverted to our 1.7.4 backup which worked out fine for the night, except that today the same error appeared after staying for about 4-5 minutes at an (admittedly CPU/RAM intensive) ender farm.
Occurrences of this error started happening on our small server in snapshot 14w03b. For the first time players started dropping out with this error message when entering the end. Logging in is impossible afterwards, usually they just get this error message before being disconnected. In rare cases the world starts loading for about 1-2 seconds before they are disconnected with the same error message.
From the server selection screen the server still reports dropped players as active on / connected to the server.
Present in 13w09b as well.
Works for higher amounts of hopper minecarts; works for stacks of items; no need to press Q to drop single items.
I have followed the instructions provided in the screenshots, and was able to successfully duplicate diamond blocks, tnt, sand and minecarts/hoppers in 13w09b SMP.
All hopper minecarts were placed rapidly on the same spot (curve of the l-shaped track), using about 10-20 minecarts in one place and then breaking them with a pickaxe one by one.
//edit: this video was linked here previously; following the instructions will yield same results for 13w09b.
https://www.youtube.com/watch?v=RBseHC2v2b4
Thanks for your comment, I'll look into what other bugs might affect our server here.
On the other hand, there is some similarity with other user reports based on this 'bug's' occurrence in 14w03b, as this error message seems to be encountered mainly (exclusively?) now when in the end.
In addition, while there are of course a lot of things I might not be aware of and I might be simply overlooking in this case, the only change in our server setup before the error message started popping up was the upgrade to 14w03b.