It also affects the official 1.16.
After watching some videos, I concluded that the bug started at 1.5 (Aquatic Update).
Affects the official 1.16.0.
This error affects multiple platforms.
...And I totally agree that it is very annoying, I felt there was something wrong, but I didn't know what it was until I compared it more closely with Java.
I'm glad I'm not the only one to have noticed that. 😃
This error is still valid, although disabled.
Is there any more specific place to report translation errors?
In 1.12.1, after testing the bug again I noticed that there was a "fix": an aspect that allows entities to be inside blocks if we try to suffocate them, however, when invoking an entity using commands, there seems to be a search for own command to find an "empty" place.
Affects 1.12.1
It's true. The bug affects all versions ... and then we have to use resistance effect or slow fall to not kill everyone.
You can close this instance!
Happens to me too! Except in my case, the whole computer crashes and I have to close the game by the Task Manager. 😞
I believe it happens because it lowers all cache content of the Store and servers at the same time, generating a tremendous lag and crashing the game ... (Images).
In this case, only the realm owner decides who will play. Because he needs to add the players to the access list. O reino era seu?
Are they still in the "games" folder? (If you play in External mode).
This is actually not quite a bug, the detail also exists in Java, and I did not even remember that it existed ... Just do not spread this ninja localization technique. : D
This happens because of your connection status and the way the world has been set up. (Enable the world's Multiplayer mode).
Nothing is truly infinite. The worlds have a limit of 9 million blocks.
It's not a bug (you'll never be able to do this in survival, so do not bother yourself so much ...)
Haha, did not think of a function to relate a ticket to two platforms. : D
Anyway ...
In fact ... The bug affects ALL blocks with more than just water.
Still affects 1.5.2.1 ... T.T
Still affects 1.6.0.8 ... T.T
@GoldenHelmet thank you. I did new tests and apparently everything is normal. It had happened in the realm, if it happens again, I will try it.