Bukkit

@kitkat179

Short answer, it's already permissions compatible.

Please Submit a ticket with as much info as possible included and i'll try to help you out more.

Thanks

@Reptar_

Not until the next version of minecraft, which i believe is 1.3 in 3 weeks or so.

@kolpy99

Alright, apologies - I mis-read what you originally posted.

@jblaske

J I did experiment with making the global zone configs "Read-Only" and on our server it gave no errors and stopped the plugin reverting the default globals.

However, i'm not going to recommend doing this on a production server. This does temporarily fix the problem, but i'm not certain if it will/won't crash the server with different combinations of plugins.
Anyone who does try this, backup your server beforehand.

If people DO try this, post your results back to us.

@kolpy99

Have you enabled pvp in the zone configs?

@CeramicTitan

Yeah, EpicZones has internal permissions that hooks into your server perms plugin.

Just use the following commands in game;

/zone edit zonename

/zone perm groupname flagname flag

So for example, to disallow building to Default group (ungrouped players) you type....

/zone perm Default build deny

You can use build , destroy and entry as flagnames and allow/deny respectively.

Just remember the group name is case sensitive, so if the group in your perms plugin is "Default" you must use "Default" when linking to epiczones, (Remember the capital letter at the start)

Alternatively, you can do it manually via FTP.

Look for plugins/epiczones/zones/zonename.yml

Look for this line;

permissions:
  default: {destroy: deny, entry: deny, build: deny}
  group2: {destroy: deny, entry: deny, build: deny}

You can change the flags manually there.

Hope this helps.

PS. You cannot edit global zones in game, you have to do them manually via FTP then reload the plugin.
(ie. world.yml, world_the_nether.yml)

@Derjyn

No problem :)

It might not necessarily be PEX or EZ. It could be the way PEX speaks to EZ and back again. Both plugins are meant to flush memory or "garbage collect". Sometimes it doesn't work out that way, all it takes is a node or poor syntax or even a slightly poorly drawn zone and it can trip up the whole server. The beauty of Java my friend.

In the line of work i'm in (without sounding patronising), I like to think of a Memory leak or I/O loops in java; not as a leak, but a blockage. Until you clear that blockage (bad perms node), the misc. crap and sewerage will back up the pipes until it's pissing out the plugholes (server freezes or does weird stuff due to confused plugins).

Decent analogy and it fits most of the time. Post in the ticket your same response and also post which perms node(s) you changed.

Try and attach the server startup log if you can so i can see what your server is doing on startup. Might be worth attaching your PEX Configs and EZ Plugin folder too, i might be able to figure out where the slipup is.

@Derjyn

1) This isn't a buggy release. You are the only person with the problem as far as we know. Also the fact removing EpicZones fixing it could just be coincidence, you've provided very little info on the issue for us to even consider that it may/may not be EpicZones causing it.

2) "2012-06-25 13:27:58 [INFO] [EpicZones] Usage statistics are being kept for this plugin. To opt-out for any reason, check plugins/PluginStats/config.yml 2012-06-25 13:27:58 [INFO] [EpicZones] version 0.36 is enabled."

It says that in the server log everytime the server and plugin starts, always pay attention to the log of your server. Besides that, it's nothing scammy - all it does is ping to create stats showing how many servers are using the plugin. No personal data of any kind.

Please update your ticket with the info requested. Thanks