Discussion in 'Archived: Plugin Releases' started by mbaxter, Aug 17, 2011.
You won't be able to break blocks if you've set yourself in nointeract mode. Read the documentation
hi on one of the updated vanish things when i log on i get hit by lightning :/ and every time i use ./vanish i get hit again how do i turn this off ?
The better question is why did you turn it on to begin with?
Check out the permissions documentation and only assign yourself the nodes you need http://vanishnopacket.github.com/
cant i make it easyer to like true and false stuff?
I'm sorry, I don't understand what you're asking.
I forgot to reply to say I fixed hehe
Good to hear it
like lightning: true/false and explosions: true/false
Much more flexible to enable it with permission nodes.
I don't believe operators can't disable the annoying effects without having to enter the command every time they join.. Also I support his suggestion of adding config options for it, it's much easier to control via config rather than permissions. (or both.)
Ops don't get the effects nodes. If you have the nodes then you've granted them on yourself. Check this post for more info http://dev.bukkit.org/server-mods/vanish/forum/37410-explode-lightning-read-me-first/#p1
I like having the "*" node, it makes it much easier to set things up. I see you stated that you are not willing to introduce a config line for it, but a lot of people want the "*" node without having to deal with the lightning, it may not be good practice, but it makes setting up permissions a lot easier instead of having to enter a bunch of permissions for OP's. In my case, I have to go to every plugins web page, gather the needed permissions just to end up having to rewrite the whole admin section of my permissions file just to compensate for this 1 plugin.
You should consider reading the "But I need a * node!" section of the post I linked
i dint i updated vanish then i started getting hit by lightning but dont worry i fixed it now
My point was that if you get lightning then you have enabled it on yourself. It comes disabled.
How the heck do you make it so there is NO lighting and NO explode for a rank, and why do you even have that? dont you use this plugin to spy on griefers? why explode and lighting? It is just a 'why' moment...
SOMEONE HELP PLEASE THIS IS SO FLUFFING ANNOYING
Check this post out: http://dev.bukkit.org/server-mods/vanish/forum/37410-explode-lightning-read-me-first/#p1
So what node do I put to disable lightning and explosion?
It's all right in that post
wait I got it but how Do i give permission to vanish for a rank but ONLY to do /v
[Not doing "pex group Admin+ add vanish.*]
then i have no ide ahow it was turned on :?
Give only the nodes for vanishing. http://vanishnopacket.github.com
Neither do I, unfortunately. What permissions plugin do you run?
i have pex/permissionsEX
Have you perhaps given yourself the * node?
Very nice plugin, recommend if you are running a server that you dedicate your time to. Great mix with FoundDiamond because when they find ores, you can vanish and tp to them to see if they x-rayed. Like I said, this plugin is very useful so you should download it.
This. In GM or other perms plugins. Remove certain perms (Effects of lightning are a perm) by doing:
Doing so removes the perm, even if you have given yourself * I honestly suggest that if you give your owners * you also give them:
- -bukkit.commands.gamemode or whatever the perm for it is. This will only allow the server console to issue gamemode command then. Gamemode can be extremely dangerous. (Similarly, worldedit.) With GroupManager, you can add/remove perms on the fly as it is.
Also, a suggestion to the developer. Can you add a feature where we can't even see ourselves (to make sure we know we're vanished) while in F5?
That one's impossible, sadly.
Ways to check if you're vanished:
Going to the inventory page while in survival mode (creative mode doesn't show it sadly) will show 'invisible'
So, you enabled it then
Next time read a plugin's documentation first and negate nodes that you don't want!
Separate names with a comma.