This behavior remains true even if the Lava Bucket is given the use_remainder component.
Still occurring as of the latest snapshots
Can confirm for 26.2
Also affects the vanilla ancient city, so this issue affects not just custom structures.
Further testing reveals that there may be multiple bugs at play. Because giving a nautilus a diamond horse armor (as listed in the command in the post) but with edited entity tags so that nautilus can wear it. And in this case the nautilus armor still cannot receive durability damage.
Even a diamond chestplate that has only been edited to allow nautilus to wear it, also cannot be damaged when worn by a Nautilus.
So it would appear that not only is the component not working in all cases, but the nautilus itself isn’t transferring it’s damage events to any data onto the item in the body slot.
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.
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.
False alarm, this was found to be a Misode / Datapack Helper error
I ask for a moderator to close this as “Invalid” please.