Details
-
Bug
-
Status: Open
-
Resolution: Unresolved
-
1.15, 1.15.1, 1.15.1 Pre-release 1, 1.15.2 Pre-release 2, 1.15.2, 20w06a, 20w08a, 20w09a, 20w11a, 20w12a, 20w13b, 20w18a, 20w19a, 20w20b, 20w21a, 1.16 Pre-release 2, 1.16 Pre-release 5, 1.16 Pre-release 6, 1.16 Pre-release 7, 1.16 Release Candidate 1, 1.16, 1.16.1, 20w27a, 20w30a, 1.16.2 Pre-release 1, 1.16.2, 1.16.3 Release Candidate 1, 1.16.3, 1.16.4 Release Candidate 1, 1.16.4, 20w46a, 20w51a, 1.16.5, 21w05a, 21w05b, 21w06a, 21w07a, 21w11a, 1.17, 1.17.1 Pre-release 1
-
None
-
Confirmed
-
Commands, Mob behaviour
-
Low
Description
The bug
The trader llama's DespawnDelay tag is active, even when spawned with commands or with their own spawn egg. After spawning a trader llama with commands or spawn egg, the tag starts at 47999 and begins to go down to 0 instead of the tag being default to 0 similar to wandering traders spawned by commands and their own spawn egg (and also makes them not despawn).
How to reproduce
- Spawn trader llama using a spawn egg (untamed)
- Run
/data get entity @e[type=trader_llama,limit=1] DespawnDelay
→
The trader llama's DespawnDelay tag is active as it is not default to 0. - Spawn a wandering trader with a spawn egg
- Use the /data get again
→ It's DespawnDelay is default to 0
