Completely screws up PEx about backup HOT 4 CLOSED

@applerox first, this is not a Backup issue. Luckily i do know PEX from the begining and i do know that you have to check your permissions. This has nothing to do with Backup!

Backup runs in background and the only thing that could happen, when you screw up you permissions is that you cant use the backup command. But even that wouldn't stop backup from working as it runs as system thread and not per user.

Please visit the IRC #PermissionsEx channel on esper.net . They will ask you for your permissions.yml or a dump of your database if you use mysql.

Some intel on your * nodes and promoting...

• Promoting works only for ranked groups (see the wiki on github)
• Permissions doesnt have to do anything with promoting its only a command that can set the users group to the next group.
• Adding the * node has to be done via console or with an admin user. Editing the config does not work as you may think (only if you use '*')
• Negating the * node is not done via -* you simply remove all permissions from that group so that its empty. (No permissions in list = no permissions)
• Deopping is a MC feature. You can restart the server only with OP or with a plugin.
• Beeing Opped does bypass PEX

from backup.

Actually, when I remove Backup, my permissions work perfectly. All my groups are ranked, and I am an admin (I own my server) so I can give the * node from the console.
Thanks for your input though!

from backup.

Well, last time i checked i didnt found any routine that could produce this kind of error but i will check again, maybe something changed i didnt checked.

from backup.

There's nothing that changes any other plugins in this one, it only reads from other plugins, but CANNOT change them.

from backup.