Marvin Krüger

Looks like you are using OptiFine. Please report that to the mod author and not to the Vanilla Minecraft bug tracker.

Well, it doesn't. The "PlayerKicked" packet containing the message that is displayed, does not indicate that the server has stopped. Only if the server goes down without sending that packet and your client is timing out, then it may notice that. But again the game may assume it's an error on your end because servers don't go down without notice, so no refresh either. Just click the "refresh" button and stop crying for help if everything is working as designed.

I know about that behaviour but it's not bugging me. Remember that your client does not know that the server closed. It just displays you a predefined message and kicks you, so your client is correctly assuming that the server might be online.

Click on the refresh button. Some servers may have scripts that allow them to restart quickly so they may be online just a few seconds after they stopped.

Well then, I think sending one packet per entity per tick is creating too much overhead (100 entities * 20 ticks = 2000 packets * ~100bytes = 200kBytes to the client and 2000 * ~54bytes ACK = 108kBytes, which I don't have; i only have 70kBytes) but I look forward to the next versions, maybe there is something done about that.

Yes I mean graphic settings in Minecraft and in the program that manages your graphics card (Catalyst for yours I think).

@Sonic I don't think so. I don't get such an error message. My problem is completely different from the one you linked.

This is common chunk/block update lag. I experienced it too whilst playing on my server. Just ignore it for now.

Please attach some more debug info. What graphics card, what driver and what (graphic) settings?

They probably went outside your laded chunks and got stuck there. Happens with all entities without AI.

Please be more accurate. Are there any error messages, log messages or are you just unable to get them because you did not get the achievement you need to unlock another one before?

Seems to be a bug with your graphics chip. If you can use a real graphics card instead of a built-in solution. I do not seem to have this problem at all