On-Aquire doesn't work in blacklist
LadyCailinBot opened this issue ยท 5 comments
WORLDGUARD-2661 - Reported by cdj9325
So the blacklist option on-aquire doesn't work for me. Everything else works, just not that option. Any ideas?
Edit: pretty sure it doesn't work at all I started a test server with the 1.5.1 dev build (2691) and the lastest builds of world edit and world guard. created a blacklist file with the following:
[bone]
on-drop=notify
on-use=notify
on-acquire=notify
The drop and use events work, but the acquire doesn't.
Comment by cdj9325
Doesn't work meaning the line "on-aquire=notify" does not function.
What is unclear about that?
I tried the deny action and it does work.
Only supposed to block picking up the item? Says who? Certainly not the description?
If it is working as designed, then you should change the description of how its designed to work.
Neither the documentation nor the wiki mention anything about on-notify only being compatible with the deny action and, in fact, imply the opposite.
Here is a link to the description:
http://wiki.sk89q.com/wiki/WorldGuard/Blacklist
According to this any event should be able to trigger any action.
Personally, I want the plugin to trigger a warning to moderators when illegal items have been acquired and display a message for them. And also notify when players are handling suspicious items too much.
If you don't want the plugin to be capable of that, and just didn't make the description specific enough, that's fine. But don't act like i'm an idiot just because i'm expecting the plugin to do what it says it can.
Comment by wizjany
Doesn't work meaning the line "on-aquire=notify" does not function.
Thanks for giving a synonym of work, that doesn't answer the question though.
Only supposed to block picking up the item? Says who? Certainly not the description?
It's always been like that, ever since the blacklist was written years ago. It hasn't changed since.
Comment by cdj9325
All you had to say was "I know it doesn't work, but it never has and we aren't planning on fixing it."
You don't have to be an ass and play stupid when you know full well what my question meant and that the documentation suggests the whitelist should work as i'm attempting to implement it (as I've illustrated with the example config.) Instead of taking my report professionally, you decided to insult my intelligence by acting as though I was attempting to use the plugin incorrectly, and almost sarcastically marking the issue as unable to duplicate.
I don't know anything about you but with your poor attitude I find it hard to believe you have many productive professional relationships with clients. The functionality of the plugin isn't even that important as its a free project and the desired plugin effect isn't difficult to code, but if you treat prospective clients anything like you treat someone trying to help you improve your work, you are in for a hard life.