Tim Shaw

I realize this is not a true fix by any stretch of the imagination, because it requires foregoing a major part of minecraft functionality, but try breaking all redstone clocks. I noticed a few months back that an active clock would cause the game to slow down considerably, but left them running because I didn't mind it. Then we wondered if that drop in performance could be causing out timeout problems, and lo and behold, since interrupting those circuits, we haven't had a disconnect yet.

This has not been resolved.

I host my singleplayer world through LAN for my roommate to join. Since slightly before 1.7 my roommate began getting kicked for no apparent reason roughly every 15 minutes. Once 1.7 hit, he began receiving the io.netty.handler.timeout.ReadExceptionTimeout error when he got dropped, and drops increased to roughly once every five minutes or so.

This holds true as long as he doesn't wander very far from me. If he does, he drops almost the moment he enters the world.

Nothing of any significance has been done to my network over the last year, so I would be hesitant to believe this is my network's problem in the first place. Add to this the fact that dozens of other people all started getting this at roughly the same time, and this has to be a coding bug. I do not understand why this has been marked as resolved without explanation twice.