-
Bug
-
Resolution: Unresolved
-
None
-
Minecraft 1.12, Minecraft 1.12.1, Minecraft 1.13.1, Minecraft 1.13.2, Minecraft 18w48a, Minecraft 18w48b, Minecraft 18w49a, Minecraft 18w50a, Minecraft 19w07a, Minecraft 19w08a, 1.15 Pre-release 1, 20w15a, 20w18a, 20w19a, 20w46a, 21w03a, 21w05b, 1.17.1, 1.19.3, 23w04a, 1.20.2, 1.21
-
Confirmed
-
Mob behaviour
-
Low
-
Platform
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
- discovered while testing
-
MC-118403 Vexes summoned by evoker do not have evoker team applied
- Resolved
- is duplicated by
-
MC-259358 The summoner of a vex is not stored to NBT
- Resolved
- relates to
-
MC-110424 Vexes don't actively attack villagers, wandering traders and iron golems when spawned vex spawn eggs, spawner or "/summon"
- Open
-
MC-256289 AngryAt tag is not used by certain neutral mobs, causing them to forget their target upon reloading game
- Open
-
MC-250059 Active target is not serialized after world reload
- Reopened
- testing discovered
-
MC-118432 Vex summoner is not reset once it is dead
- Open