Have the following command triggered by a /setblock clock, in the spawn chunks in the Overworld: execute @a[score_timer2_min=200] ~ ~ ~ setblock 5 20 13 minecraft:redstone_block
As expected the command is executed in the End, the dimensions the player was at the moment, right after going through the portal.
However, i did not expect this to go on for another hour, even after having closed minecraft and login back in while still in the End, strongly suggesting to me that the spawn chunks where still loaded, and loaded back up even with no player in the Overworld. However cool i think this is, it does not match previous behaviour of Minecraft.
Had two accounts on, one logged out while it was in the Overworld but moved to the End to see if this was what caused it, but it was not. Spawn was moved to x0 z0 (way before any command blocks were up).
Attachment: the world.
Attachments
Comments 4
Seems intended, spawn chunks are always loaded, no matter what, this has been like this forever
If you want it to only effect the overworld, add this to the selecor: r=-1
As i have understood all previous information, and how spawn chunks have worked previously, a player is required to be somewhere in the Overworld for the spawn chunks to be loaded. Both in singleplayer and multiplayer.
You would have to drop an item through the appropriate portal, in regular intervals, to keep the spawn chunks loaded while the player was in another dimension. And if i recall correctly, it would only keep the single chunk the portal was in loaded, even if it was a spawn chunk.
If indeed spawn chunks are intended to always be loaded, no mater what, i would say that is pretty handy. But the difference is pretty big for mapmakers.
Just for completeness [Did just make another world with just a setblock clock to spam the chat, in the spawn chunks, entered the End, made breakfast and came back a little while later. It was still going, so probably nothing to do with cross dimensional setblock-ing acting as a chunk loader]
Firetick is not processed, but another command on a separate clock is...