usage is handled internally due to the number of subcommands.
…member without the friendly fire permission being enabled for both. Not sure this can happen except for when an entity is made agressive to a player, then friendly fire is removed later and the player returns in range of the agressive tamed entity. Thought: Move the permissions check for friendly fire into isFriendlyPet? Not sure where else this is used, but if we always do a permissions check for friendly fire afterwards, it would make sense to move that check.
command name. The use of /p, /pc, /a, and /ac is still supported.
this prevents us from creating DB entries for players that get caught by a whitelist.
versions that use a String for the SkillName rather than the SkillType enum values
to use a 1.0 base for any entity with an UNKNOWN type.