I'm running an Attack of the B-Team server using MCPC+. I understand that you might not support it, but I would greatly appreciate it if you would help me with my issue. I have tried multiple versions, and they all have the same results. What is happening is that when a group/player is given -vanish., they have no permissions, but when they are given just one node, such as vanish.vanish, it gives them every permission in VanishNoPacket. I have tested this without being an OP and in player permissions versus group permissions. The result is the same. No, I am not using the "" node on any of my groups and neither am I using the vanish.* node.

I guess just closing it works too! \o/

Sorry, it turns out I forgot my MCPC password for the forums, and they're "forgot your password" email thing isn't working at all. I'd rather not go through making another account, so I'll just wallow in the pit of having bats and lightning. It would be super cool if you could be able to disable in the config though :P Just a thought

It's a thought that comes up often, but to add those to the config would be making everyone's lives harder. Now, to change whether a feature is enabled or disabled, you'd need to check two places instead of one, when the already existing one is 100% sufficient. :(

That sounds like a bug in whatever permissions plugin you're using, or MCPC+ may have modified how permissions work in a horrible way. I have a perm testing command built in that you have to enable. Set the permtest value in the config to true and either restart or do the command vanish reload in console. Then you can do permtest username permission.node from the console to see if a user has a node assigned according to the perms system. Assign vanish.vanish and then test something like vanish.silentjoin to see what's happening.

I would like to first thank you for your speedy reply. I would like to point out that I was never OP during testing. As soon as I turned permtest on in the config, permissions were working as they should have. I restarted the server, because I believed this was too good to be true, and, of course, the permissions were all wack again. I tried the permtest command, as suggested, and only gave myself vanish.vanish. I checked permissions for all the other vanish permissions, and I only had permission for vanish.vanish. I relogged to see if the fakequit and fakejoin were still working, and too my surprise, when I relogged the permissions were fine again. Now that I have realized this, I see that it might not be a problem with VanishNoPacket after all, but I can't help but think it is, because I haven't had any issues with other plugins on the server.

If VNP's permissions were all screwy like you're describing, I'd have thousands of tickets like yours by now. Try removing your perms plugin, just test with OP. See what happens.

I've updated my permissions plugin to the latest build. Still having issues with VNP. There are no issues when I don't use a permissions plugin, but, of course, a permissions plugin is necessary. I suppose this is where your support ends?

I'm happy to offer help, though it isn't a bug in VNP. Perhaps asking in the MCPC community might give more info?

What about trying other perms plugins to test?