I've been doing tests on my plugin and suddenly a flood of "PEX is not working with Vault" reports came in.

I've run tests with other permission plugins with and without Vault, and PEX + Vault is the only issue, so here it is:

Permissions seem to be ignored.

If you need more info, let me know.

can't do anything with a 'permissions seem to be ignored' issue. It is known that reloading PEX will break bukkit support completely (shouldn't affect Vault), or has in the past. Other than that I need something more to go on than it simply doesn't work, Vault checks permissions internally to PEX and unless PEX has changed it's API or format recently everything shouldn't just all of a sudden break.

I've restarted the server, as I am aware of the /reload issue.

The specific plugin is "AntiShare", by default it blocks all actions to creative players by a configuration (diamond block place for example). I tried my plugin without vault, and only pex, and it worked fine. I stopped the server, put vault in, and turned it back on, and suddenly nothing works as it did a few minutes prior (no changing of any config, just drag and drop Vault in).

I did the same test with other permissions plugins (and lack of), and could to produce similar results.

There is no apparent change in PEX's API, or Vault's code.

I can't isolate the issue to only my plugin though.

So something went wrong between PEX and Vault :/

Unless "perms.playerHas(world, player.getName(), node);" is incorrect...

generally you shouldn't use Vault's built-in has methods unless you need to do group specific checks. If all you're looking for is per-player checks continue to use bukkit's built-in methods. The Vault methods will check very specific permissions (in the case it may only be checking world-specific not globally) if you run the method you gave me.

I'll dig around Vault's API then, thanks for your help