If the server uses SQL for PEX or changes the permissions file to use (via PEX's config.yml) then the compatibility implemented will not work.

Some brainstormed ideas are to instead of checking each value (current solution), warn the server that they have PEX (as we do currently) and tell the server to change the permissions.

These are the permissions that are currently "affected" by the bug (copy and paste from tester):

    - AntiShare.affect.creative
    - AntiShare.affect.adventure
    - -Antishare.affect.survival
    - -AntiShare.deny.*

Also, configuration option to turn off spam (hide it well :P )