Region blocks the minecraft:kill-command
LadyCailinBot opened this issue ยท 7 comments
WORLDGUARD-3350 - Reported by LordRazen
Simple bug: If you try to use the minecraft:kill-command in a worldguard-region it wont kill anything.
If you use the same command in an unprotected region it works.
minecraft:kill @e[r=10,type=EntityHorse]
Comment by wizjany
blocks it how? do you get a message saying you don't have permission? a different message? what happens if you're in a region but the entities are outside the region?
Comment by LordRazen
The command is in a Commandblock and there's no message at all.
If the commandblock is in the region it kills the horses outside of the region, the horse inside the region stays unharmed
Comment by wizjany
Can you try it manually? it seems that the way the command is coded is causing entity damage or some similar event to be firing, which worldguard is blocking to protect the mobs (as it would if you say, attacked them with a sword).
Comment by LordRazen
Exxact same behaviour as with the commandblock: Horse in the region stay alive, outside the region is killed
Comment by sk89q
This is a Spigot bug, but the newest build of WorldGuard provides a workaround.
Comment by LordRazen
erm, can you tell me how this is a spigot-bug? Should I report it to spigot? Is the workaround permanent so do I have to worry about this in future?
Comment by sk89q
A damage event is raised... with no information on what block is causing it. The workaround lets the damage event through if WG can't tell what block caused it. The workaround will be in place for most likely eternity because it's possible for a plugin to make the same mistake, and plugins have raised events with incomplete information many times before (though not with this event in particular).
Though at the moment, it seems WG applies region protection on command blocks, so if the bug with the event had not existed, the kill command would have worked but it would have not worked on other regions. However, that is a different issue.