I've been avoiding posting this bug for a while now but its to frustrating to avoid.
AngryAt NBT Tag only works with 3 mobs Wolf, Iron Golem, Polar Bear. (aka they can attack any mob/player)
(note mobs also don't attack with increased follow range unless within default attack range probably a separate issue or intended)
Working mobs are Wolf, Iron Golem, Polar Bear.
If I want a skeleton to attack a villager nope doesn't work. However I can make Wolf, Iron Golem, Polar Bear attack the villager or any other mob. AngryAt also doesn't work with increased follow range for any mobs with modified AngryAt a player or mob would still have to be in attack range.
Command example that doesn't work but should using skeleton attacking a villager.
/data modify entity @e[type=minecraft:skeleton,sort=nearest,limit=1] AngryAt set from entity @e[type=minecraft:villager,limit=1,sort=nearest] UUID
Another one using llama a neutral mob attacking a pig.
/data modify entity @e[type=minecraft:llama,sort=nearest,limit=1] AngryAt set from entity @e[type=minecraft:pig,limit=1,sort=nearest] UUID
Working command as Intended works with the 3 working mobs (wolf attacks villager)
/data modify entity @e[type=minecraft:wolf,sort=nearest,limit=1] AngryAt set from entity @e[type=minecraft:villager,limit=1,sort=nearest] UUID
To replicate AngryAt not working.
Summon any mob that can attack (excluding the 3 mentioned above because they work) (example zombie) then summon any other mob that the first mob wouldn't normally attack (example pig). Then run command
/data modify entity @e[type=minecraft:zombie,sort=nearest,limit=1] AngryAt set from entity @e[type=minecraft:pig,limit=1,sort=nearest] UUID
(note change zombie and pig to the mobs you chose if you chose differently)
The zombie doesn't attack the pig. If AngryAt is only intended for neutral mobs it still doesn't work for the other 8 (Panda, Bee, Dolphin, Llama, Trader Llama. then kind of neutral mobs Enderman, Goat, Snow Golem.
To replicate mobs not attacking with increase follow range
run command
/summon wolf ~ ~ ~ {PersistenceRequired:1b,Attributes:[{Name:generic.follow_range,Base:64}]}
Go 48 blocks away then run command
/data modify entity @e[type=minecraft:wolf,sort=nearest,limit=1] AngryAt set from entity @p UUID
The wolf won't attack unless within attack range.
Linked issues
is cloned by 1
Comments 8
Dharanios
The tag also doesn't work for some neutral mobs though. Even if the tags only purpose is to solve that one loading issue it would be nice if it worked as intelligent tag for the community as well.
Which neutral mobs does the AngryAt tag not work on? Endermen are already being tracked in MC-188506.
ampolive
Panda, Bee, Dolphin, Llama, Trader Llama. then kind of neutral mob Goat
would be nice if the tag worked on hostile mobs as well
Cannot reproduce for bees, I was able to make a bee sting a villager and another bee to sting a strider by altering the AngryAt tag (the bee has to be angry first).
Can confirm for the remaining mobs. They don't seem to use this tag altogether (when harming them, the AngryAt tag is not altered as it is for the other mobs).
Perhaps create a new report for the neutral mobs in question that do not use/allow the use of AngryAt; nothing in this report, except the comments were addressing that. (Which I believe is why Moesh resolved this as a feature request; as the description of this report is absolutely that.)
If the mobs actually don't use it; that means target is forgotten on leaving and entering the world, which was the exact reason that tag got added.
I've created a new ticket for it: MC-256289.
AngryAt is only for neutral mobs, not hostile mobs. That is not a bug.
Its purpose is to save what entity is currently being targetted do they don't stop attacking when closing and opening the world. Just like hostile mobs, visibility is required to target.
None of these things you reported are a bug.