In the latest Bedrock beta (1.19.0.28), the associated description in the changelog is same with 22w17a's, but the warden's ranged attack is affected by difficulty in Bedrock Edition. Seems not a WAI.
Additionally, the "minecraft:coal_ore" is included instead of the "minecraft:copper_ore" in this tag (see "tags/blocks/snaps_goat_horn.json"), it means the goats will rammed into coal ore instead of the copper ore, which is inconsistent with their behavior in Bedrock Edition (1.18.30.26+) and the description in changelog (which mentioned above).
Seems resolved now, since the JSON file of this version is updated.
Ref: https://twitter.com/gegybeans/status/1649059466300588034?s=46&t=52yR2vVNtD6L-cStuNZGvA
Seems resolved now, since the JSON file of this version is updated.
Ref: https://twitter.com/gegybeans/status/1649059466300588034?s=46&t=52yR2vVNtD6L-cStuNZGvA
Yes, even crashes when using ESC to quit.
I think its not a good idea to change the title to focus a case while ignoring another case.
In the latest Bedrock beta (1.19.0.28), the associated description in the changelog is same with 22w17a's, but the warden's ranged attack is affected by difficulty in Bedrock Edition. Seems not a WAI.
Additionally, the "minecraft:coal_ore" is included instead of the "minecraft:copper_ore" in this tag (see "tags/blocks/snaps_goat_horn.json"), it means the goats will rammed into coal ore instead of the copper ore, which is inconsistent with their behavior in Bedrock Edition (1.18.30.26+) and the description in changelog (which mentioned above).
@Solo Alguien It's seems caused by a wrong auto-generated options.txt, see the differences between 22w11a's and 22w12a's default options.txt below:
The options.txt is attached.
Is this a 21w16a bug fixed in 21w17a? It seems like a typo (fix version is "20w17a" currently)
This report is focused on "crop could generated on farmland", not "ruined portal can intersect with village".
Can confirm.
@Lucas Hurst I marked the place which they talking about, and obviously it is completely floating.
Still exists on 1.18.0.23.
Fixed, I tested on a clean 1.18.0.23 installation (on Application/External) with the updated 307.9 MB music pack just now, it can play as normal.
See this:
Not duplicate, because the advancements mentioned in this ticket are not same with the advancements in MC-237954.
And that ticket not mentioned inconsistency with Namespace ID and translation key at all, it just says that two advancements are miscategorized.
Maybe I should revert this ticket back to my original content? If so, these two tickets should be considered to be related with each other.
Affects 1.17.11 and 1.17.30.22.
Still existed in 21w06a.
Yes, I also think they need to solve the problem for real, not just simply change its definition.