The bug
After setting a new world spawn point, it is impossible to set blocks or summon entities there until the spawn point has been visited by a player. If the area is visited and then left, then it is possible to /setblock and /summon to those locations.
How to reproduce
Create Superflat world
/tp 0 60 0/setworldspawn 10000 60 10000/setblock 10000 60 10000 stone
→ "Cannot place block outside of the world" if the region has never been loaded or "The block couldn't be placed" if it has/tp 10000 60 10000/tp 0 60 0/setblock 10000 60 10000 stone
→ Block placed
/setworldspawn should actively move spawn chunks to the new location and load/generate it; as it is currently working, the command is only useful for avoiding using an NBT editor for moving the world spawn coordinates.
Linked issues
is duplicated by 1
relates to 2
Attachments
Comments 18
Confirmed for 14w03b. The new spawn chunks correct themselves when you save and exit and return in singleplayer, and when you shut the server off and back on for multiplayer.
You're attempting to use setworldspawn as a mobile chunk loading mechanism. Somehow, I doubt that was the intention behind its creation. The purpose of it is to give a non-third party method of moving the world spawn coordinates. It does exactly what it's supposed to do.
There is a logical continuity issue when "spawn chunks" are not at spawn. The command DOES NOT do what it is supposed to do; running this command will break the active spawn chunk region and make it work unreliably if a new player logs in after world spawn has been changed (this is an uncontrollable situation), or when a player happens to visit the new location (controllable, but an irritation). Until Mojang allows map makers to set the region of loaded chunks manually and independently of the world spawn, this is a real bug. I would appreciate it if you didn't inject your own personal opinion into someone else's bug reports.
None of that is your decision to make, any more than it is mine. It's Mojang's. You do not own issues that you submit. The bug tracker is open to the community so that they may comment on issues, and help with triage. I am as free to add my personal opinion as you are. But ultimately, it's Mojang that will decide what is and is not intended behavior.
Confirmed in 1.9.1-pre3. Relates to MC-74966.
Is this still an issue in the most recent versions (currently that is 1.10.2, or 16w42a) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time.
Confirmed.