[MC-188497] AngerTime and AngryAt cannot be set on summon

The bug

Mobs can't be summoned with AngryAt; this immediately resets their AngerTime to 0.

How to reproduce

Spawn in any mob where you know its UUID
```
/summon pig ~ ~ ~ {UUID:[I;1,2,3,4]}
```

Summon a wolf

/summon wolf ~ ~ ~ {AngerTime:10000,AngryAt:[I;1,2,3,4]}

❌ The wolf is not angry on spawn

Using data get shows that its AngerTime has reverted to 0 and it is missing AngryAt altogether

Note that Endermen are unreliable candidates for testing this bug, as their behavior when manually setting anger tags is inconsistent with the other neutral mobs (MC-188506).

Linked issues

relates to 2

MC-88181 Entity NBT isn't always synchronized with clients immediately, rendering the entity incorrect for a brief moment Open

MC-188506 AngryAt cannot be manually applied to endermen Resolved

Attachments

MC-188497.mp4

Comments 13

user-a4a49 2020-06-19T02:58:48Z

Confirmed in 1.16 Release Candidate 1.

Happy Camper 2020-08-12T08:15:15Z

Confirmed to still be a problem in 1.16.2.
The AngerTime tag is completely ignored when custom set for any neutral mob. Doesn't matter if it's spawned/summoned, has the data modified, or has specific UUID set to be angry at. Reverts back to zero.

Happy Camper 2020-08-12T21:25:35Z

Just looked into it - this can be fixed if gamerule universalAnger is set to true

Avoma 2020-11-25T16:18:38Z

Can confirm in 20w46a.

Avoma 2021-01-16T13:29:54Z

Can confirm in 20w51a.

3 more comments

Avoma 2021-04-27T15:22:25Z

Can confirm in 21w16a.

Avoma 2021-12-31T12:03:04Z

Can confirm in 1.18.1.

Avoma 2022-05-09T08:42:25Z

Can confirm in 1.18.2 and 22w18a.

Avoma 2022-06-23T14:29:11Z

Can confirm in 1.19 and 1.19.1 Pre-release 1.

Avoma 2022-10-02T18:08:20Z

Can confirm in 1.19.2.