This bug causes problems for map makers. I have recently been working on a map which had a lobby above the world. In previous snapshots you'd spawn when you logged onto the server in the lobby and now you spawn underneath it.

I have investigated this further. It seems that there is now a #minecraft:valid_spawn tag and it only has grass_block and podzol in it and this tag determines what is a valid spawn place. If you change the fill command in the description to be grass_block instead of dirt, it works like 1.12.2. Is this an intentional change that only glass and podzol are valid spawn blocks? It seems like other blocks like stone, dirt and sand use to work and occur naturally on the surface of a world.

EDIT: I think I misunderstand how the valid_spawn tag is used. If I use a datapack to override it it doesn't change where you can spawn. Also, podzol doesn't work as a replacement to dirt with the fill command in the description to reproduce the 1.12.2 behaviour.

Confirmed 1.13-pre6

Affects 1.13-pre7

Affects 1.13-pre8

Can confirm for 1.13.1

Still present in 1.13.2

Affects 19w12a

Still an issue in 1,14

There is no 1.14.2 yet. And this report is talking about the world spawn, the individual player spawn point was always able to spawn you anywhere.

Are you sure about that? /setworldspawn should ignore the y level completely.

The hight of y is only used if no spawnable blocks are found. If a spawnable block is found at any hight that block is used to respawn the player on. If no spawnable block is found it also only respawns you at the exact x and z of worldspawn. /setworldspawn can alter the y. Tested now in 1.14.1

This is still broken in previously mentioned usecases, such as buffet presets, as well as changes in the world by the player. Y is to be used in order to create a prefferense for the game when respawning in case of buffet presets and mapmaking?

Can confirm in 21w40a.