The command shows that tickingareas were placed at y = 0, but tickingareas seem to affect the entire chunk now (java parity).
The video shows that a riptide trident is used just 3-4 times before hunger reduction, but doing the same in the Java Edition only requires 8-10 uses before reduction.
Cannot reproduce in 1.19.0.24/25.
Confirmed on Windows 10, but I don't know if it's intended or not. Moving waterlogged blocks with pistons at all deletes the water, so it might also be intended with water straight up.
I can select a skin from an imported skin pack in the preview (classic UI), but not the beta (updated UI). In the preview, I had to wait a painfully long time for the Marketplace to sync after pressing the create skin button, but I was able to equip a custom skin eventually. If I select a marketplace skin then select a custom skin, I experience MCPE-152132.
I can't reproduce either. I tried all four combinations of +/- and x/z, and it no longer triggers.
I cannot reproduce this in 1.18.10.26 beta. Method 4 still occurs, but it's no longer endless (it's a different issue).
Now, items under the influence of the command only repeat the burning sound for 1 second.
The latest beta is already listed in the Affects Versions list.
@unknown, I can't reproduce in 1.17.40.20 Beta. What steps did you use to test this issue?
Can anyone confirm in 1.17.40.20 Beta?
@unknown, I can't reproduce in 1.17.40.20 Beta. What steps did you use to test this issue?
Turning biome blend in video settings completely off can improve performance (that is if you have it on or even high).
Turning biome blend in video settings completely off can improve performance (that is if you have it on or even high).
Because of snow's increased brightness, powder snow is very distinguishable in it's appropriate biomes.
[media]Confirmed for 1.17.11.
After I changed my Xbox username, my real name appeared under a new account as well. However, when I signed in yesterday, it seems that I have my original account back with the updated username.
Mojang has reported this issue to their internal tracker in July last year, and this has become a parity issue with the fix of MC-176615 since December last year (the Java Edition no longer has this affect; items pop out of shulker boxes when burned in the other game). Assuming that Mojang plans to implement a fix similar to the one currently in the Java Edition, your alternate reasoning of the current Bedrock Edition mechanics is not required.
Also, this is not a community forum. Comments should add information to diagnose the ticket so, if an issue in the game is discovered, that it will be addressed by Mojang.
The Bedrock Edition cannot currently partially rotate textures for any block. For example, the Java Edition flips the top and bottom textures for stone along the vertical and horizontal axis; however, this is not the case in Bedrock. Even stone experiences the same issue that deepslate experiences, regardless of it being placed or generated (this is all while stone is not a directional block in either game):
[media][media]
Both the Java Edition deepslate and stone side textures are able to rotate along the vertical axis, while there is no rotation for this case in the Bedrock Edition at all. This was hinted at in the changelog for 1.17.0.56:
— Due to tessellation limitations, we are limiting the isotropicness of Deepslate to when these textures are up and down (as this is a rotatable block) for now
In the short term, deepslate top textures in Bedrock may need to have their rotation removed to be better aligned with the way that stone currently works, but no full fix can occur until texture tessellation is changed.
The Mojira migration is still in progress. Legacy votes don’t seem to have carried over for this ticket just yet (it had over 133 votes according to the Wayback Machine).
I haven’t done testing in a while, but the Reddit post seems to match the client-teleporting behavior that I experienced in the 1.13 betas. To my knowledge, the changes were reverted just before 1.13 released, but they don’t seem to have been reverted this time.