When I use command "/tp" to somewhere hasn’t been loaded (completely), the game wouldn’t correctly identify the blocks under player (maybe the whole chunk cannot be identified? I dont know).
See an example.
In some adventure games there are some levels. If there is a lobby at (0,100,0) and a level at (1000,70,1000) (this position has a slime block), and then I’m teleported to (1000,100,1000) to play this level.
Regularly and reasonably, I shouldn’t suffer the falling damage, because there exists a slime block.
But when it comes to 1.21.70 (or 71, 72, 73), the truth was that the chatbar will tell you the chunk is still loading and there will be some performace problems. (This message has existed since 1.21.60 or earlier, but before 1.21.70 it worked well)
Then:
1.21.70 - you see that you directly died for falling from a high place when the chunk you’re located in was just loaded. It seems there are some moving wrongs.
1.21.71,72,73 - chunks have been loaded and you have gotten in touch with slime block once, and you’ve been bounced into the air. Then you died, for falling from a high place.
That’s the problem. It influence gaming a lot…
Someone says using the command "/tickingarea" is OK. It surely solves the problem…
However, oneday, creator’s map owns 10 or more levels. (/tickingarea allows 10 constant loading region at most)
Then we need mojang to fix this bug.
Comments 0
No comments.
