WorldEdit

WorldEdit

42M Downloads

Classify Allays as an ambient mob

baailey opened this issue ยท 4 comments

commented

The Problem

Currently /butcher will kill Allays without having to specialise a specific butcher flag.

A Solution

Making it so using /butcher to kill an Allay requires -b will prevent any accidental deaths when using it to kill hostile mobs when an Allay is nearby. An Allay is considered a passive mob, so I think this is reasonable.

Alternatives

No response

Anything Else?

No response

commented

This isn't something where we really want to stray from the way vanilla behaves too often. We currently use vanilla classifications, which classifies it as a mob rather than an ambient creature

commented

ultimately i'd like to have entity masks with some builtins so you can list out entities directly or use entity tags. that way people can make their own tags or use the api to register arbitrary entity mask parsers for subjective things like what "hostile"/"passive" mean which tends to be a big point of contention since we go by mojang's categories. we're not the one deciding if allay is hostile or not.

commented

Hmm, that sucks. It'd be nice if server owners could modify what the basic /butcher command actually kills. I'd probably need to make a separate feature request for that, but just throwing out ideas.

The Allay is a friendly, non-hostile mob, which I think goes against what /butcher is supposed to kill by default? My understanding is that butcher is focused on 'hostile mobs', but I understand if you don't wish to change the default label the Allay has.

commented

I'd like to second that! I use //butcher often to clear hostile mobs and prevent lag, and I have to subsequently teleport around and respawn allays for my players that have collected them.