I updated to v2.3, start playing and then 5 minutes later v2.4 comes out. I update to v2.4 and now every time I join I join invisible even though it was working absolutely fine in 2.3 and 2.2! EDIT: Same issue in 2.3! Am back to 2.2 and no problems..

Also I really think using permissions for this is a bad idea! It would be much more user friendly to define in config if to join vanished or specific players or ranks. Or even better a config file for each user and a toggle option!

Here are my permissionsEX:

Admin:
    prefix: '&a[Admin]&e '
    permissions:
    - -vanish.silentjoin # Join silently for regular users, on /vanish will announce join
    - -vanish.silentquit # Quit silently for regular users
    - -vanish.nointeract # Prevents pretty much everything you could do with either mouse button, as well as pressure pads. Includes block breaking, placing.
    - -vanish.nochat # Prevents you from accidentally chatting, including the /me command
    - -vanish.preventoutgoingdamage # Prevent accidentally hitting people/animals/monsters while invisible
    - '*'

Any ideas?

Updated. Also having problem with 2.3 but not 2.2

Depending on how pex handles its negation feature, you might need to also negate the sub-nodes of vanish.silentjoin

http://dev.bukkit.org/server-mods/vanish/pages/permissions

These were added recently

Still no luck, tried both of these permissions seperately

    - -vanish.silentjoin.* 
    - -vanish.silentjoin.joinvanished

It was working absolutely fine, so are allother negative nodes, I guess I'll stick with v2.2 since you don't have an answer :(

I would suggest you ask the PEX folks for help with your negation. I write my plugin to be compatible with the bukkit standard permissions system, with which PEX is supposed to be compatible. I'm sure there's some negation setup that will allow you to do what you want :)

OK anybody have permissions to share? this sucks I've looked at all the permissions on the page and tried various but its always join vanished FFS!

Then talk to the PEX folks. Ask them for help. This is purely a PEX issue. I'm sorry that I can't help further, but I don't use PEX.

I do have an answer. You need to adjust your permissions to negate all the relevant permission nodes. Read the documentation, the nodes have changed since 2.2. If you're convinced you have done it correctly yet it won't work, contact the PEX folks for help because they'll be able to help you make PEX work better than I can.