This is still reproducible with the specified environment of Zorin OS 16.3 Core and the XFCE desktop environment. I have just been able to reproduce it by booting into the "Live environment" for Zorin OS 16.3 🙂
I can no longer reproduce this in 1.20.5
[media]
I am also unable to reproduce this in 1.20.5 (
)
The issue can still be reproduced in water, as per the comment from @unknown below
Can no longer reproduce in 1.20.5. Azaleas now pop off when placed in water.
If you want to reproduce this, note that the player's hitbox has to be entirely within water to reproduce the issue. Can confirm in 1.20.5.
This bug appears to have been caused by my launcher, as I cannot reproduce it with the vanilla launcher.
I haven't been able to reproduce this issue: a boat placed on ice while the player is facing ±180° also faces ±180°, as expected. Could you provide specific steps to reproduce the bug?
[media]"First position set to" is a message from WorldEdit, a third-party mod. If you're playing on a server, its admins may have added that mod without you realising.
Regarding being unable to mine single blocks of trees, I was unable to reproduce your issue in a vanilla environment, so that behaviour is also likely to have been caused by a server-side mod.
Hi! This seems like a technical support request, which the bugtracker can't help you with. I suggest heading to the Minecraft Community Support Discord server, where volunteers can assist you, or contacting your ISP. Alternatively, changing the "DNS server" that your computer uses may solve your issue.
@unknown As I understand it, the unexpected behaviour described in MC-225839 is that trees (and mushrooms etc) can generate floating, not that they can generate close enough to a lava source to start burning.
Can confirm in 1.20.4
Can confirm in 1.20.4
Can confirm in 1.20.4
This behaviour is present in 1.20.4
Can confirm in 1.20.4
I have been unable to reproduce this bug in an actual in-game scenario. The translation string hasn’t changed, but the behaviour of {{/locate}} seems to have changed, because it now reports biomes as being at least 32 blocks away if you are not already in the biome. For example, in the screenshot below, I walked one block in between running the locate commands:
[media]I did some testing to attempt to find a point that will report as 1 block away from a
[media]beach
biome, but didn’t find any. The results are shown in the image below, with emerald blocks placed where the biome was reported as 32 blocks away, melon blocks where it was 45 blocks away, and chiseled stone bricks where it was 0 blocks away.This means that it is now impossible for the command to report “1 blocks away”, meaning this issue is now impossible to observe.
Alternatively, it’s possible that the new behaviour of
/locate
is itself a bug - do let me know if there’s a report I am unaware of.