Dave Akers

I’m adding more detail because it seems like the automated system is trying to ignore this and it keeps marking it as resolved.

I feel like this is a game breaking bug. Any server that relies on random re-spawns will be impacted. As the spawn radius game rule gets larger the more the actual random range gets clamped. The bug will show up with respawn_radius set as low as 32. I can reproduce this in multiple versions 1.21.9 up to latest snapshot 24w44a

note: the gamerule names have, previous versions use spawnRadius and doImmediateRespawn instead

Steps to reproduce:

create new world with commands enabled.

/gamerule respawn_radius 32

/gamerule immediate_respawn true

open F3 to watch coordinates

run /kill over and over the z coordinate will always be negative instead of the expected range of +/- 32. This shows that the randomness is heavily biased to -z. The x coordinate is also effected to a lesser extent, with the radius set to a very large number IE:10000 all randomness for Z is lost and will always be -9999.5 and X ends up staying in a small range (-9000 to -9999).

I’ve attached a video to demonstrate.

note: the gamerule names have, previous versions use spawnRadius and doImmediateRespawn instead

I noticed this first on my modded server, tested with vanilla single player. I set gamerule spawnradius to 1000 and /kill over and over. I respawned about 20 times X was random in a small range: 44.5 - 10.5 and Z was always 791.5

When set to 1000 the X range was larger, -900 through about 1500. but Z was always -1791.5

When set to 2000 Z was always -2791.5

Also tried it on 25w44a with the same results.