Steps to reproduce
Set up a repeat command block with a teleport command to keep vexes trapped in a particular spot.
Start a raid on hard difficulty.
When you get to a wave with evokers, allow them to spawn vexes.
Do not kill the vexes, but kill the rest of the raid.
Expected result
Vexes spontaneously start taking damage at a rate of 1 health/second after existing for 30-119 seconds.
Observed result
Vexes never spontaneously start taking damage.
After a raid that includes evokers is long over, any vexes that were summoned will continue to hang around, becoming aggressive if approached, but otherwise bobbing up and down and doing nothing else.
Linked issues
is duplicated by 3
Attachments
Comments 19
Vexes should start taking damage after 30 to 119 seconds but in Bedrock they don't. Vexes should despawn by taking damage after 30 to 119 seconds.Also notice how the vex's arm position is different. Yes, it's is using the bow/crossbow animation. I have made multiple reports about vexes being very slow, and using an incorrect arm position. See MCPE-42933, MCPE-44029 and MCPE-46220.
Confirming bedrock 1.12.0.9 BETA [Win10] [Android] forced a raid. towards the end 3 evokers. Legit had like 40 vex flying around killing all of us as soon as we spawn back. Had to put in peaceful. Couldn't even get a screenshot.colored text
In the current version vexes follow normal despawn rules, so they do despawn after a raid if you travel far enough away or wait long enough. I tested this in Java and the behavior is the same. Here is my test:
Set up a village (one villager, one bed).
Set up command blocks to instantly kill all illagers and witches except for evokers.
Set up command blocks to teleport evokers and vexes to specific spots every tick, to hold them in place.
Give yourself bad omen.
When evokers spawn, switch to survival to get them to spawn vexes, and then kill the evokers and switch back to creative.
After the raid ends, observe the vexes.
Teleport yourself 200 blocks in the air and fall back down.
Results: In both Java and Bedrock, the vexes remain after the raid ends, and despawn when you teleport 200 blocks in the air.
I looked back in the vanilla behavior files, and vexes were given the current despawn component in 1.16.0 and it has not changed since then.
Can confirm for all 1.11 versions, on win 10 and xbox one. However, its vex's from any evoker, not just ones in raids🙂
You can see a demo of this issue in my recent bugrock episode here:
https://bugs.mojang.com/browse/MCPE-46317