Matteo Morena
- imamo
- imamo
- Europe/Stockholm
- Yes
- No
MC-73913Basically, it is possible to teleport outside the world (for example at x=40M and z=40M). Eventhough it is not possible to do it directly with "/tp @p 40000000 ~ 40000000", it is possible to get to this situation by using relative telepot:
/tp @p 20000000 ~ 20000000
/tp @p~20000000 ~~20000000
I remember that before 1.8 this issue was already fixed (Minecraft automatically checked if with relative teleportation you would go outside the world, and if so, deny the teleportation), but for some reason now there's this bug again.Basically, it is possible to teleport outside the world (for example at x=40M and z=40M). Eventhough it is not possible to do it directly with "/tp @p 40000000 ~ 40000000", it is possible to get to this situation by using relative telepot.
What I expected to happen was... :
I shouldn't be able to teleport outside the world.What actually happened was... :
I teleported outside the world, causing illegal position and client crash.Steps to Reproduce :
1. Execute "/tp @p 20000000 ~ 20000000";
2. Execute "/tp @p ~20000000 ~ ~20000000".I remember that before 1.8 this issue was already fixed (Minecraft automatically checked if with relative teleportation you would go outside the world, and if so, deny the teleportation), but for some reason now there's this bug again.
Basically, it is possible to teleport outside the world (for example at x=40M and z=40M). Eventhough it is not possible to do it directly with "/tp @p 40000000 ~ 40000000", it is possible to get to this situation by using relative telepot.
What I expected to happen was...:
To get an error message because I shouldn't be able to teleport outside the world.What actually happened was...:
I teleported outside the world, causing illegal position and client crash.Steps to Reproduce:
1. Execute "/tp @p 20000000 ~ 20000000";
2. Execute "/tp @p ~20000000 ~ ~20000000".I remember that before 1.8 this issue was already fixed (Minecraft automatically checked if with relative teleportation you would go outside the world, and if so, deny the teleportation), but for some reason now there's this bug again.
Can teleport outside MC world, causingclient crash.Can teleport outside MC world, causing "Illegal position" message and kick from the world, which becomes unplayable.
Basically, it is possible to teleport outside the world (for example at x=40M and z=40M). Eventhough it is not possible to do it directly with "/tp @p 40000000 ~ 40000000", it is possible to get to this situation by using relative telepot.
What I expected to happen was...:
To get an error message because I shouldn't be able to teleport outside the world.What actually happened was...:
I teleported outside the world,causing illegal position and client crash.Steps to Reproduce:
1. Execute "/tp @p 20000000 ~ 20000000";
2. Execute "/tp @p ~20000000 ~ ~20000000".I remember that before 1.8 this issue was already fixed (Minecraft automatically checked if with relative teleportation you would go outside the world, and if so, deny the teleportation), but for some reason now there's this bug again.
Basically, it is possible to teleport outside the world (for example at x=40M and z=40M). Eventhough it is not possible to do it directly with "/tp @p 40000000 ~ 40000000", it is possible to get to this situation by using relative telepot.
What I expected to happen was...:
To get an error message because I shouldn't be able to teleport outside the world.What actually happened was...:
I teleported outside the world, so I got the "Illegal position" message and got kicked from the world. When I tried to open the world again, I was still outside the world, so I got kicked one more time.Steps to Reproduce:
1. Execute "/tp @p 20000000 ~ 20000000";
2. Execute "/tp @p ~20000000 ~ ~20000000".I remember that before 1.8 this issue was already fixed (Minecraft automatically checked if with relative teleportation you would go outside the world, and if so, deny the teleportation), but for some reason now there's this bug again.
If in the region target selectors, @something [x=X,y=Y,z=Z,dx=DX,dy=DY,dz=DZ] , you put big DX, DY, and DZ values, Minecraft hangs.
For example, doing "/say @a [x=-500000,y=0,z=-50000,dx=1000000,dy=256,dz=1000000] " causes the game to hang. This isn't noticeable in gameplay, but only when you try to send somewhat in chat or to close the world.What I expected to happen was... :
To get an error message because I shouldn't be able to teleport outside the world.What actually happened was... :
I teleported outside the world, causing illegal position and client crash.Steps to Reproduce :
1. Execute "/tp @p 20000000 ~ 20000000";
2. Execute "/tp @p ~20000000 ~ ~20000000".
If in the region target selectors, @something[x=X,y=Y,z=Z,dx=DX,dy=DY,dz=DZ], you put big DX, DY, and DZ values, Minecraft hangs.
For example, doing "/say @a[x=-500000,y=0,z=-50000,dx=1000000,dy=256,dz=1000000]" causes the game to hang. This isn't noticeable in gameplay, but only when you try to send somewhat in chat or to close the world.What I expected to happen was...:
To get an error message because I shouldn't be able to teleport outside the world.What actually happened was...:
I teleported outside the world, causing illegal position and client crash.Steps to Reproduce:
1. Execute "/tp @p 20000000 ~ 20000000";
2. Execute "/tp @p ~20000000 ~ ~20000000".
Weird, can't seem to reproduce the situation, now I just get the illegal position message and get kicked from the world. I tried more than once. Before reporting the bug, Minecraft hang and I had to use task manager to close it. Maybe I just didn't wait enough as sometimes it hangs for 2-3 secs before you get kicked. I'm going to correct the report.
Oops, just did a mess... I copied the preset from another bug report and forgot to remove the ending part. I just wanted to point out the region bug.
Anyhow, it still sounds weird that it takes so long. I mean, even if you check for the whole world, 99.99% of the chunks aren't even loaded. I think it would be better either to review the code for the regions or to deny the execution if the selection is too big. I was messing around with that in my vanilla server and it took a while before I understood what happened and restarted the server.