I was playing with a friend on Minecraft 14w32d and I got disconnected with a io.netty.handler.timeout.readTimeoutexception. When I connected back on there was a second copy of me with my exact skin and everything. I got kicked off again not too long after with the exact same error and sure enough when I connected back on there was another copy of me where I crashed off.
We decided to upload the world to my server and try that except the exact same thing happened except it happened on his side.
You can attack these glitch players and if you kill your own "clone" your game will crash. I do not have a crash log because I didn't crash, my friend did and we didn't think of saving the crash log.
After a while the server will eventually catch back up and all players will see a "Left the game" message for all the "clones". That player will disappear from the TAB list except they are still in the game and all other players can see them.
For the record I can run a 1.7 server perfectly fine on my system and friends can connect to it with no lag at all. So what is going on?
Related issues
Attachments
Comments
migrated
migrated
I got the same issue on an unofficial super craft bros. server on 1.7.2. The clone was in the place where you wait for the game to start. When ever the game would start, it would put the clone into the game. This bug happened when I did /hub while a game was going. I also didn't spawn with any items (character shop emerald, ect.). It seemed that every think that CraftBukkit did to manipulate the player happened to my clone.
Erik Broes
That is how timeouts work, the server thinks you are still there until it doesn't anymore.
migrated
We have the same issue with 1.8 vanilla server and clients. Also, ghosts cannot be kicked, but mobs do attack and kill them, and when the character logs on later, he dies immediatly. And it leads to item duplication when there are multiple ghosts. And the chance for recreating bug is increased when using teleport (to 1000-3000 blocks away) commands by command blocks (they was fine and well-used in 1.7.10,). The affected player knows the bug a few seconds beforehand the actual disconnect by not able to use anything. The server's response time to this (1~5min) is also unnacceptable in many situations.
migrated
This is also a dupe of MC-34947 as the player was experiencing a TimeoutException.