Bukkit

(Pages didn't migrate gracefully from the old to the new curse site - fixed them.)

EDIT: Also I will look into updating ADM to both 1.8 and 1.11 in the near future. :-)

@AgentCortez

Sorry. As I've stated previously I'm currently only giving support on ADM, no active development. (I'm busy with real life things so I've taken a break from MC - it's been a rather long break, but I still see myself coming back to it eventually.)

If you have any specific issues you need help with feel free to ask.
I'll do my best to answer them. :)

@Zomblad

Hi, as I've said before I've taken a break from MC, so that's why there hasn't been any updates - I'm only interested in giving support atm. (Sorry for the slow reply.)

Anyway, regarding the compatibility, I had a look at the code for OtherDrops and I don't think there is any "hard" compatibility issue. OD is simply overwriting the ADM drops but from the looks of it this can be fixed in the OD config. (Most likely their documentation for the config is slightly inaccurate thus not really your fault. I didn't bother looking at their documentation - I read the code instead since that way I know what actually happens.)

Here is a short breakdown of what happens, why, and how you can easily fix it by changing the configs of OtherDrops:

1. My plugin intercepts all entity death events, checks them against ADM config and modifies drops accordingly. It does so at normal priority, and it preserves any other changes to drops made by other plugins by using a built in add-method to add additional drops specifically from ADM.
2. OtherDrops, having their plugin configured with high event priority, intercepts the drop event after ADM, and modifies it. Evidently with your current OD config, and I suspect it's by default* so it's not your fault, OD will overwrite the drops, disregarding any changes made by other plugins. (ADM can not stop OD from doing this - this is an OD issue.)
3. Also you mentioned that you saw ADM drops sometimes: well I saw in their code that OD ignores entity deaths where it doesn't know what killed the entity - this is a bug in OD and is why ADM drops sometimes doesn't get overwritten by OD. This happens when an animal dies of fall-damage or drowning or crushing or fire... I no longer remember exactly how the MC server code works since I haven't work on it for over a year so I'm not 100% sure anymore which condition(s) caused the server to not report the cause of lethal damage. If you want you can go ahead and experiment with different ways to kill animals and you will find out which conditions it was yourself. :P

To fix this you can do one of two things:

• I noticed in the OD code that there is some kind of drop-setting for letting default drops through. I suspect this feature is incorrectly documented (probably says that it will preserve default drops right?) since you haven't used it, but what it actually does is preserve whatever drop was in the drop-event before OD intercepted it, regardless of it being the "default" drop or a drop modified by another plugin. As I said I haven't read their documentation so you will have to consult it yourself for how you prevent OD from overriding drops from other plugins (which was misleadingly named "defaultDrops" in their code).
• The other solution, which is more powerful although less elegant, is to simply add the same drops that ADM would do into OD. This will work without issue as long as the item dropped is identical to items that ADM has been configured to drop (material, name, lore), because ADM does not place any restriction on the item being spawned by ADM itself.

Hope that helps and solves your problem, and if you want you can file a bug-report on OD for not handling all entity death events. The relevant piece of code is here: https:github.com/Zarius/Bukkit-OtherBlocks/blob/master/src/com/gmail/zariust/otherdrops/listener/OdEntityListener.java#L78
(Sorry if any of this comes of as rude - that's not my intention I'm just very stressed right now.)

Also you can give a dev gibe from me if you want: ask why the logging-calls have only been properly optimized in the core parts of the plugin, but in a lot of other places OD is wasting performance constructing log-messages before checking if it should log them or not. (I already know why ^^, I just want to make a friendly tease, and be moderately annoying so it gets fixed! :P)

*I didn't read through their config loading code to confirm it so maybe that's not the case? But if it is then it means that the default behavior of their plugin is to not be compatible with other drop-mods. That's a poor design choice if you ask me. But I'm getting ahead of myself - I haven't procured any proof. :P

@WinMillion20

Hi, as far as I'm aware it works for 1.8
As for removing my Lamb-Chops it can be done in the config (set all "Rate" for it to 0).

(I will do this update eventually, but since it is just a config change and I'm in a MC-break and busy with work its not a very high priority for me right now. It would become ADM v1.8b due to how minor a change it would be.)

@MeLittleUBigIWin

Does it not work at all? Or are you referring to the Lamb Chops?
(Btw, what server are you using? Bukkit, Spiggot, Couldron, Other..?)

(As a side note: According to mc-stats there have been people running ADM on MC1.8 for quite some time, so I assumed it was working...)

@MeLittleUBigIWin

I'm sorry, making minecraft mods is a hobby that I would like to spend more time on, but I spend 10~12h / day crunching programming at my work right now so I haven't had time to spare for keeping a server, doing testing and developing a new version. (Eye fatigue is an actual inconvenience when you stare at a screen of text +10h/day all week...) :/

However if you tell me what exactly it is that's broken maybe I can look into it... I'm not promising any delivery date though.

And as always I do appreciate the support and interest of the users using my plugins!
It really does brighten my mood a bit after a long day at work. :)

(Like today I wrote 1000lines of documentation, ugh...)

@eldayia

No problem, thanks for your kind words. :)

@eldayia

I'm not entirely sure what you mean, but I'm afraid the short answer is no.

The long answer:
I'm guessing you mean one of four things:

a) You want animals to only drop meats if the killer has permission.
This can not be done in a good way because determining who the killer was is unreliable. There are many situations where the server is unable to credit a kill to a player. This gives two choices: to drop anyway or not to drop when the killer is unknown. Not to drop: players are going to get irritated quite often. Drop anyway: Players without permission could very, very easily circumvent it making the whole thing pointless...
* As a side note I wish dying animals simply left a carcass that the player had to harvest resources from, then a hunting skill could make sense, and a skilled hunter would be able to recover more meat.

b) You want to prevent players from picking up meat unless they have permission.
This can be done. Not even that hard, but it has nothing to do with food-stuffs per see (and that is why it would be feature bloat / bad to put in ADM!). Such functionality (regulate what items players can pick up) would best be made as a separate plugin - and, I haven't searched, but I would guess one already exists since I don't think it would be very hard to make.

c) You want to prevent consumption of the meats unless the player has permission.
This is also easy. But I don't support it. My goal is realism. If you are holding a piece of cooked meat in your hand, what lore-friendly force is preventing you from eating it? Allergic? Server enforced vegetarian? (Also fairly sure regulating consumption in general, including potions etc, can be done with other plugins already.)

d) You want to prevent cooking meats unless the player has permission.
This can make sense and I've played with the idea myself. It's like you're not a good enough chef, your cooking skill is too low or something. Unfortunately, like a) this can not be done, because there is no obvious way to tell who is cooking. That's because cooking doesn't require player interaction at all! E.g. using hoppers you can build an automatic cooking oven. What player is cooking? None, it's more a consequence of mechanics.

v1.8 now has over 10k downloads, thanks everyone! ^^

(Yes, I'm still alive. I don't have time to actively develop for MC anymore, but I still check in every now and then so feel free to leave a comment, it's much appreciated!) :)