Closed Sitmobedaf closed 1 year ago
That's not really a fix for the issue itself... the AuthMeListener should be updated to work with the latest version, not just the error caught and ignored without any information at all to the user.
Also please use proper PR and commit messages...
Then fix its non-disableable. I have Autnte 3.1.1 or a completely different plugin but called AuthMe. It's wrong that it immediately tries to connect to Api v3 without checking. Why not v2 or v1? if (!Properties.AUTHME_HOOK) { Plugin authMe = getServer().getPluginManager().getPlugin("AuthMe"); if (authMe != null && authMe.isEnabled()) { registerEvent(new AuthMeChestShopListener()); } }
Well the aim is to be compatible with the latest version. If the error is that the latest version doesn't work properly then that can of course be fixed.
Being compatible with plugins that wrongly identify as AuthMe isn't really possible though. They need to make sure to provide a compatible API in that case. You are kinda right though that all dependency integrations should probably fail less loudly (just with an error message) so if you want to expand the PR to catch errors with the enabling of all dependencies I would be willing to accept it, otherwise I will try to add that (and maybe even a more advanced hooking mechanism) eventually.
Yes, add these 2 f_____g lines of code so that I have a working plugin. It hasn't worked for me for half a year now. Do it right now.
Yeah, no, that's not how this is going to go. Feel free to open a new PR if you have decided to be productive and civil about it...
What? Did I offend you? It's all a text translator! But okay, I'll do it just for myself.
bb