This would mean checking 12 Blocks around the one block which only makes sense if you are running the MySQL version. I can surely add it.
You just need to install Vault Plugin (Its a dependency for WatchBlock to ensure it works with all Permissionsystem)
New update available on : http://dev.bukkit.org/server-mods/multiloginblocker/files/3-multi-login-blocker-v1-0/
new update please see bukkit dev page: http://dev.bukkit.org/server-mods/watchblock/
add the permission node: watchblock.protect
Thanks for the notice. And I have a fix for you : http://dev.bukkit.org/server-mods/watchblock/files/28-watch-block-v2-10-rb/ That was an issue...
thanks for feedback ;) here is a new vault version : http://dev.bukkit.org/server-mods/watchblock/files/26-watch-block-v2-06-beta/ new update...
which version are you running? Do they have the required permission node? Which permission plugin are you running?
Can you guys with permission issues please try this version here: http://dl.dropbox.com/u/26081774/WatchBlock_Vault.jar This requires Vault...
can you try using groupmanager and report back? in the meanwhile i ll look at permissionsbukkit. a previous user was telling the same. so it seems...
hm thats odd. what permission system do you have? and do you have other plugins interfering with block placement? I guess you are op? sounds to...
give the groups you want to have protected blocks watchblock.protect permission node just use flatfiles in config.yml set flatfiles : true and...
New Update to v2.03 http://dev.bukkit.org/server-mods/watchblock/files/23-watch-block-v2-03-rb/
Again I say this is fixed in Version 2.01 of WatchBlock please go to http://dev.bukkit.org/server-mods/watchblock/ to fix that issue. Ah now I...
this is fixed in version 2.01 please update to that version
Separate names with a comma.