I am running a server with quite a few plugins, all of which were working perfectly until I tried to create a restricted area with ButtonWarp. Using the command '/bw access administrators' I should be able to restrict access to the administrators group (I am using MyMCAdmin to export permissions to Permissions Bukkit), however everyone is denied access. It is as if the groups simply do not exist to the plugin. I was informed that this was an issue with Vault, and was in fact fixed in the last update, nothing could be further from the truth. At this point I am extremely aggravated with Vault; if this issue was truly fixed, why am I still experiencing it? I'm at the point where if I can't get this fixed within a few more days, I'm just going to switch to another plugin as far away from this ridiculousness as possible.

From what i understand making changes with mcma will mess/upset permission additions through the api. Can you verify the issue without using mcma for adjusting your permissions.

Im sorry if you're having issues with your permissions, pbukkit has one of the more difficult systems to get working completely due to how it handles groups.

Thanks for your time, hopefully we can get this solved.

I'm not sure I am certain what you are telling me to do if anything. From what I understand you're saying there is no real fix. The server is run on Fragnet so there is no real way for me to disable MyMCAdmin without trashing hours of server settings.

well from what I understand McMa overwrites any changes done to the permission file while the server is on.

So can I use McMa to make this access change? Or write it into a file manually? I only need like three non-public warps.

probably, you'd have to check with ButtonWarp on what permissions it uses.

@Rajada - Sleaker is correct, MCMA takes complete control over your permissions configuration if you have its Permissions export mode set to something other than none. This has been the biggest drawback of MCMA since day one and there is no indication that the developer will change it despite the numerous requests. In short, any plugin that dynamically changes permissions such as ButtonWarp will suffer since permissions will eventually get reset to what MCMA says it should be. Thus, your only recourse is to configure such permissions through the MCMA GUI.

In short, this is not a Vault problem.

@javacraft - thanks for the response, you described the issue much better than I could since I have never used McMa! - I'll be closing this issue since there isn't much I can do in Vault to solve it.