mojira.dev
MCPE-44342

Bug with /kill @e[r=10,type=!villager] still kills villagers after the villager change

Update 1.11.0.9 Beta, April 3, 2019 release...

 

I have 9 Always Active, Repeating command blocks with almost the same commands, which I have some problems with...

kill @e[r=7,type=!player,type=!xp_orb,type=!villager,type=!item]

It was in my Advanced Skyblock Map with Trading and Conversion Structures.

 

Unfortunately, the insta-kill command indicated above kills all villagers since the villagers themselves got updated. I have tried to run the same command with the same command block, but have been set as Impulse and Need Redstone. I have spawned the villager on the main module of the villager summoning structure, and it didn't die. When I powered up the command block in Impulse Mode via a button, the villager died. The previous output window displayed this text...

Killed Villager.

I think it was a bug that got produced because of the villager's data update. xp_orb, player, and item in the command above still didn't get killed by the kill command indicated above.

Linked issues

Comments 3

New villagers are called "villager_v2" in the commands

As revealed by the command prompts, in 1.11 newly generated villagers and those upgraded from an earlier release now have the internal name "villager_v2". I believe this works as intended, because the version 1 villagers are still present in the game (although they can only be found or spawned in a world generated from a template, such as a Marketplace pack). However, I will leave that determination until it has been confirmed.

Thank you for the comments.

 

Just tried adding type=!villager_v2 on the list of insta-kill exception list, and it stopped killing the newly spawned villagers.

 

I think this can be marked as resolved now.

Thank you for the help provided!

Marc John

(Unassigned)

Unconfirmed

Android

Android 6.0

1.11.0.9 Beta

Retrieved