mojira.dev
MC-49623

/setworldspawn behaves like old multiplayer spawn

when cheats are enabled, using /setworldspawn sets the world spawn to a roughly 20x20 area around where the player was when the command was executed rather than at the exact location as expected.

to reproduce:

1. create a cheat enabled world
2. go somewhere to use /setworldspawn
3. die several times, using /kill will be faster. notice you are always near the coords of the spawn, but very rarely AT them as expected.
4. take note of the location you spawn each time by marking it with wool or something untill the whole roughly 20x20 area is filled. this step is only necessary to know exactly how big the area is in order to solve the issue.

Linked issues

Comments 4

Working as intended.

why is it intended like that? it has been working in my expected way for several versions now. (actually, it's been that way pretty much since the /setworldspawn command was added, however long that is.)

i really think it would be more useful for map-making for the worldspawn to be exact, so that i don't have to build a big square area around the spawn just to make sure the players don't spawn outside my map's starting area.

It's always been a 20x20 box on 1.72 for me. Might it be different behavior between "/setworldspawn" and "/setworldspawn x y z" ? I always use the first one.

It's mostly so that everyone logging into a fresh world won't be all spawning directly on top of each other and are spread out a bit. It's a good feature. It's always been around for multiplayer servers. It's actually MORE consistent this way since there aren't different behaviors between multiplayer and single player now. It's not a big deal to respawn in a random area around worldspawn in single player.

Antonio Knapp

(Unassigned)

Unconfirmed

Minecraft 14w08a

Retrieved