[MC-118430] Vex summoner is not stored in NBT despite being used for AI task

Partwise based on 1.11.2 decompiled using MCP 9.37

The bug

The summoner of a vex is not stored in the NBT data of the vex despite it being used for the AI task net.minecraft.entity.monster.EntityVex.AICopyOwnerTarget.

How to reproduce

Spawn an evoker
Summon a villager next to it
```
/summon villager ~ ~ ~ {NoAI:1b}
```
Wait for the evoker to summon vexes
→ The vexes attack the villager
Reopen the world
→ The existing vexes are not attacking the villager anymore

Linked issues

Comments 8

bemoty 2017-08-11T11:12:53Z

Can confirm for MC 1.12.1.

Oval 2018-09-12T22:42:06Z

Confirmed for 1.13.1.

Bunnyblock2 2019-02-21T00:10:14Z

I can confirm this is still the case in 19w08a, a snapshot for 1.14

Bunnyblock2 2019-11-25T00:49:26Z

Can confirm this is still an issue in 1.15 Pre-Release 1, sorry for not posting an update in a while!

CookieWookie7 2020-04-08T22:42:35Z

can confirm for 20w15a but only if you use the command

/summon villager ~ ~ ~ {NoAI:1b}

because mobs no longer attack villagers that are Invulnerable

Avoma 2021-01-29T12:36:48Z

Can confirm in 21w03a.

Avoma 2021-02-08T08:35:12Z

Can confirm in 21w05b.

ampolive 2021-08-02T00:31:53Z

Can confirm in 1.17.1.

Vex summoner is not stored in NBT despite being used for AI task

The bug

How to reproduce

Linked issues

discovered while testing 1

is duplicated by 1

relates to 1

testing discovered 1

Comments 8