[MC-73450] When quiting a world, you leave before chucks unload

When you quit a singleplayer world, the game will recognize you as "gone" for a little while before the chunks unload. It's also possible that when entering, the chunks load before the game recognizes you as "there", there is no way to tell the difference. This is very annoying when having command blocks check for players online, they will register no players online when you quit the world. To replicate, just hook up a testfor command to a 20 Hz clock, then quit and re-enter the world. The command will momentarily not find you.

Linked issues

relates to 1

MC-409 Worlds not saving upon exit (single player) Resolved

Comments 7

Sonicwave 2014-10-22T04:24:32Z

Probably a duplicate of MC-409.

KingSupernova 2014-10-22T06:53:56Z

It's not a duplicate, but it is probably related.

Samuel Shank 2015-10-22T03:26:27Z

idk about that

KingSupernova 2016-01-11T20:16:53Z

How is this possibly intended Mojang? Incorrect information is being sent.

Torabi 2016-01-12T16:08:47Z

This is perfectly logical, considering that singleplayer runs a server internally. When you quit, you leave the world, and then it shuts down the server. Why would you want it to shut down the server first? You'd probably get a message that you were disconnected from the server then.

KingSupernova 2016-01-12T18:50:41Z

I guess I can get behind that explanation. It still seems a little odd. The problem with it is that it can mess with redstone mechanisms. I actually had to redesign some stuff due to this bug.

Torabi 2016-01-12T19:20:26Z

Singleplayer is multiplayer, but with only one person. And it could turn into multiplayer at any time, using "Open to LAN". Design for multiplayer, and it should work in both.