Support for CoreProtect, a good majority of people have moved on from older logging plugins such as hawkeye and logblock and have started using CoreProtect. It offers nearly the same features(plus some) and is much more light-weight and doesn't often fully break with updates.

If CoreProtect becomes supported an addition to the "flag" parameter that can tell OtherDrops to NOT log info for that block change would be nice too.

Change the potioneffect parameter to require specification(and allow) to be used on either the victim or the player. Also(may need a new parameter all together) allow mobs to spawn with potion effects already on them.

New parameter - Money - You're already hooked into vault for money, why not use it a little more and put a money parameter in that allows drops to only trigger if they have an
equal, less than or greater than amount of money then specified.

New parameter - Level - Drop will not trigger unless the player has an equal, lesser than or greater than amount of levels then what is specified.

Will look into CoreProtect.

Not sure what you mean by "require specification" for potioneffect but I'm
planning to add "potioneffect.attacker" and "potioneffect.victim".

Allowing mobs to spawn with potioneffects has been mentioned too but that
will have to wait until I get a "custommob" section up because it's too
hard to squeeze into the same line as the drop and doesn't suit being a
parameter (as it's related to the mob, not the drop).

Not sure what you'd use it for but I could probably add a condition for
having a certain amount of money before allowing a drop.

Definitely thinking of adding a "player.level" condition as well as some
mcmmo level conditions.

On Wed, Feb 13, 2013 at 10:50 AM, charlie1990 [email protected]:

Support for CoreProtect, a good majority of people have moved on from
older logging plugins such as hawkeye and logblock and have started using
CoreProtect. It offers nearly the same features(plus some) and is much more
light-weight and doesn't often fully break with updates.

If CoreProtect becomes supported an addition to the "flag" parameter that
can tell OtherDrops to NOT log info for that block change would be nice too.

Change the potioneffect parameter to require specification(and allow) to
be used on either the victim or the player. Also(may need a new parameter
all together) allow mobs to spawn with potion effects already on them.

New parameter - Money - You're already hooked into vault for money, why
not use it a little more and put a money parameter in that allows drops to
only trigger if they have an
equal, less than or greater than amount of money then specified.

New parameter - Level - Drop will not trigger unless the player has an
equal, lesser than or greater than amount of levels then what is specified.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/123.

Support for CoreProtect added in a local build.

"If CoreProtect becomes supported an addition to the "flag" parameter that can tell OtherDrops to NOT log info for that block change would be nice too." - can you provide an example of what you would use this for?

...um. If you have multiple suggestions, make a separate ticket for each one.