miziragamez
Assigned
Reported
MC-304341
Using_item advancement trigger still occurs even when spear returns to upright (non-damaging) position
Won't Fix
MC-299782
Zombie villagers saved in jigsaw structures forget their biome variant and profession upon world generation
Fixed
MC-298690
Bundle animation type on consumable component does not match bundle throwing animation
Confirmed
MC-297075
Enchantments with 0 anvil cost still increase their anvil cost via the enchantment's level
Awaiting Response
MC-296748
Potion Contents component still overrides the item name even when the ToolTip Display hides the component.
Invalid
MC-296446
Movement speed modifiers and flight speed modifiers do not affect Happy Ghasts or Ghastlings
Duplicate
MC-280115
Cactus flowers cannot be placed on leaf blocks
Duplicate
MC-279958
Shields and wolf armor with a damage_resistant component take durability damage after receiving an attack their damage_resistant tag matches
Confirmed
MC-279060
Errors with certain translate strings when used in tellraw or title commands
Duplicate
MC-276651
damage_item does not repair items when the value is negative
Fixed
MC-276587
Custom enchantments with slot "any" doesn't account for saddle slots
Invalid
MC-276041
Protection-like enchantments can only be made all compatible or none, with datapacks
Invalid
Comments
Tested in 1.21.11 Pre-release 2, and this still appears to not be “fixed”.
Giving the player a base entity interaction range of 10 and then attempting to hit a mob from 10 blocks works (including attack indicator) but this fails when holding a spear/item with attack range component.
I’m curious if this is supposed to be flagged as “Works as Intended” instead, since the post on Pre-Release 1 states that attack reach component directly overrides the player’s interaction range.
The ideal fix is to simply let the max range of the component scale up if the entity interaction range is increased while still respecting the min range and the resulting disjoint hitbox, but if it’s working as intended then I’d argue it should be flagged as such.
Okay yeah just tested it in my own pre-release version, this is indeed fixed. Thank you for the correction, and apologies for the trouble.
As shown as slicedlime in their snapshot video, this was not actually fixed despite being flagged as such: https://www.youtube.com/watch?v=CH_mI68_Ljk
I recommend this bug report being reopened until it is actually fully addressed and fixed.
As shown as slicedlime in their snapshot video, this was not actually fixed despite being flagged as such: https://www.youtube.com/watch?v=CH_mI68_Ljk
I recommend this bug report being reopened until it is actually fully addressed and fixed.
Seems to still occur as of up to 1.21.10
Tested and reproduced in 25w32a
Forgot to attach the example datapack to the report, but here it is.
Glass was reported to me by another user, but yeah I can't reproduce it either.
Will edit the bug report to specify it as leaf blocks being the main issue
Also applies to 25w06a
Can confirm up to the most current snapshot 24w40a
Edit: Removed erroneous photo, now has the correct screenshot attached, showing the bugged output.
Can Not Reproduce. Tested against a fire-immune mob (Zombified Pigmen) and they still drop xp. The user likely made the bug report since fire ticks from ignited mobs that are killed by the Fire do not drop xp since fire is not inherently a player kill.