Discussion in 'Archived: Plugin Releases' started by mbaxter, Aug 16, 2011.
i mean edit, but can you help me maybe in a file you can send me?
Read your permissions plugin documentation and grant yourself the nodes you want.
ok so i have the permission node: "--vanish.effect.toggle.explode" and "--vanish.effect.toggle.lightning" and even then when i do /v lightning comes down and lights everything on fire....
Op doesn't get toggle permission, or even have the effects enabled. You must have granted those nodes separately. Maybe the * node? If it's something you don't want to edit, negate the nodes (vanish.effects.explode/lightning/smoke presumably) you don't want.
Op doesn't get * in any perms plugin I'm aware of, what plugin are you using?
Also, to quote my previous post: If it's something you don't want to edit, negate the nodes (vanish.effects.explode/lightning/smoke presumably) you don't want.
EDIT by Moderator: merged posts, please use the edit button instead of double posting.
Released version 3.11
Now with colored user name tags (over your head) on vanish!
Check the changelog for details on how to use it!
With my top staff rank i give them the *.* permission node in permissionsex so they get all the permissions but now i can not get rid of this explosion and lightning effects, so why is there not a part in the config for this cause i am going to have to switch to a different plugin.
I have no clue why people freak out over not having all permissions.
Thanks but no thanks i have already done that it still does the explosion and lightning
Paste YOUR permissions file and name what plugin its for
prefix: '&6Head-Admin &6'
So where's the negation?
Set yours up to look like this: http://forums.bukkit.org/threads/ad...-no-spout-1-2-5-r4.31960/page-63#post-1224648
I have already, as i said i have used this permissions plugin for around 10 months now and i know to use - in front of permission nodes to stop people from being able to use it like LWC but it does not work with your plugin. I put
- -vanish.effects.explode and yet when i join then do /v it still does it.
@alltra09 You didn't put it...
If it's an inheritance, then it won't work. PEX reads the permissions of a group before it reads the inheritance.
OKAY. Fourth try.
Still does the explosion and lightning
Ask in PEX help thread.
Ok but in the next update is there any chance of it being added to the config to turn it off?
No. The permissions work fine.
The plugin is great, but im an OP, i has '*' permission on my server and i has 88 plugins (and my own, so it's 89), so i can't give ALL permissions to myself from ALL plugins! It will take a week! So that must be set in config in next version.
I'm currently useing PermissinsEx or PEX with VainishNoPacket and i'm a admin aswell.
If you set this in your permissions.yml file it should work. Works for me atleast.
Hope it helped you out.
Yeah it helped me, but it must, (must and again MUST!) to be in config.
PS: I'm using PEX too
Why does it need to be in the config? The above linked permissions setup works fine.
mbaxter, I think that there is no way to configure it, but if there is no permission plugin installed (i have, but if somebody doesn't)?
If you don't have a permissions plugin, then everything is disabled by default (even if you have op, you only get the ability to /vanish, pretty much). And you can add it using permissions.yml which is a bukkit feature.
mbaxter, yes i can, but it's more easier to configure it using config-file
No, same number of lines to edit.
mbaxter, but it is easier, only 'true' or 'false'
Same thing as a permissions file, you say?
No, i must set all that permission nodes to permission file, it's harder than set true/false in config file
Separate names with a comma.