-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Register (check).silent permission #353
Comments
Build 1048 is supposed to fix this. |
Running build 1054, it seems it's still applying the .silent perm to me when I'm op, despite negating |
I overlooked one point:
NCP will update the permissions in the first server tick (scheduled task!), after plugins enabled. Not sure this makes such a difference but technically it's different to set the permission default to false, than to deny the permission for indivudual players. Another thing, ave ou considered also changing the following permissions?
The defaults of the summarizizing permissions should be set to false, actually, OP is meant to have effect on the original permissions already, for another point to make for myself. |
Well, as op, I'd like access to the That code I mentioned in the chat is run in the join handler. And yes, using Java code to set "negative" permissions. I'm not aware of any other way to "deny" a permission for a player other than what I mentioned? |
Major
Minor
Might have to reproduce and see what's happening. |
No I haven't. Are you implying that NCP also checks for op instead of just the permission for NCP-related commands?
Ah, I listen at low priority. I'll try this. |
NCP doesn't check for players being op, it just relies on what is supposed to be registered. If you negate a permission, another permission could re-enable having that permission.
In Bukkit you can't reliably override a given permission, Bukkit does not know permission priorities ( - which is why i had priorities implemented in the plugin RegionSpecificPermission). So it's still possible that the permission is given by another permission that would grant it as a child permission.
|
EDIT/scissors-cut: Latest dev build counts. |
Does this work now? |
Sorry, just had time to test now. Unfortunately, it does not with NCP build 1057 (with no changes on my end though). Still only receiving messages about myself when deopp'd. |
Alright.
I need to rework all the permission defaults in the plugin.yml too, in order to make removing permissions for ops easy. ~ So only one/two permissions need to be negated, e.g. a shortcut nocheatplus.op . |
Means I haven't done anything other than what I stated in this issue. So I haven't tried anything else yet. I'll get to it this weekend, hopefully. |
Could be this is better with build 1082. Looks like there has been (check).silent.silent permissions assumed before that build. |
ASsume fixed - can'T be sure though. |
Sorry, I've been busy - if someone reminds me to test after a couple weeks from now I'll be able to. |
Now in plugin.yml. |
The text was updated successfully, but these errors were encountered: