The bug
Whenever I put in a number for the y-axis over 4096, it lets me teleport there. The +-30 million x and z limit is gone as well.
Inadvertently requesting to teleport out of bound can cause the game to crash or the player to be continuously kicked.
To reproduce
Just run /tp @s 100000000 ~ 100000000
and the game will freeze.
Linked issues
is duplicated by 23
relates to 3
Attachments
Comments 13
Confirming on 19w07a after exiting perspective view of a Wither boss. Coordinates close to spawn (~1,000X ~90Y, ~0Z). Singleplayer world forever crashes upon loading and gives the option to return to server list.
Didn't start new thread as another user with a similar bug was classified as a duplicate of this one.
https://photos.app.goo.gl/P44eHDFqXwCVTpMp6
IMO the y axis limit should become 30 million, for parity with the x and z axes, even if you can't build there and lighting is glitched. Alternatively, it could be made to be 2^31.
The problem is caused because neither
net.minecraft.server.commands.TeleportCommand#performTeleport(CommandSourceStack, Entity, ServerLevel, double, double, double, Set<ClientboundPlayerPositionPacket.RelativeArgument>, float, float, TeleportCommand.LookAt)
nor
net.minecraft.server.network.ServerGamePacketListenerImpl#teleport(double, double, double, float, float, Set<ClientboundPlayerPositionPacket.RelativeArgument>)
are checking if the target would be inside the world border
this bug is related to MC-170951
The same problem occurs with the X and Z direction past the world border. Teleporting entities past the 32-bit limit (plus or minus a couple hundred blocks) will crash the game and can potentially crash the game indefinitely. My suspected theory is that when changing syntax to many commands in 1.13, the +-30 million x and z limit as well as the 4096 y limit for teleportation wasn't implemented (at least not yet).