WorldGuard has a number of features to protect your server from either griefing or accidents or add a few new cool features. It can selectively disable fire spread and lava fires, among many other protection features. You can make the sponge block actually work and simulate classic water.
Any feature can be enabled or disabled!
[*:1i77t48p]God mode with /god
[*:1i77t48p]Adjustable spawn protection and login protection
[*:1i77t48p]Creeper explosions from taking out terrain
[*:1i77t48p]Lighters from setting fires
[*:1i77t48p]Control fire spreading:
[*:1i77t48p]Block ALL fire spreading, OR
[*:1i77t48p]Prevent it from spreading to some blocks (your choice!)
[*:1i77t48p]Prevent lava from starting fires
[*:1i77t48p]Restrict lava to spreading to only some blocks (your choice!)
[*:1i77t48p]Use a powerful block and item blacklist:
[*:1i77t48p]Choose what you want WorldGuard to do when (1) a player attempts place a block, (2) a player attempts to destroy a block, (3) a player attempts to left click with an item in their inventory, (4) a player attempts to right click a block (such a chest), (5) when a player attempts to drop an item or block, or (6) when a player attempts to pick up an item
[*:1i77t48p]Choose to deny; notify admins; log to console, file, or database; kick; ban; and/or tell the player
[*:1i77t48p]Simulate Classic-esque water by letting water infinitely expand (only if there is a block underneath)
[*:1i77t48p]Simulate the sponge from Classic (blocks water in its general area)
[*:1i77t48p]Enforce only one session for a player on a server (so a person can't login twice)
[*:1i77t48p]Stop all fire spread globally with /stopfire in chat or fire-stop from console
[*:1i77t48p]Allow the placement of portal blocks anywhere
[*:1i77t48p]Prevent gravel and sand from falling**
Using the Blacklist
In worldguard-blacklist.txt you can make WorldGuard perform actions if:
[*:1i77t48p]A player tries to destroy a block
[*:1i77t48p]A player is about to break a block
[*:1i77t48p]A player tries to place a block
[*:1i77t48p]A player tries to use / right click a block (i.e. chest)
[*:1i77t48p]A player tries to use a tool or object (left click)
[*:1i77t48p]A player tries to drop an item
[*:1i77t48p]A player acquires an item
Possible actions include:
[*:1i77t48p]Notifying all administrators
[*:1i77t48p]Logging it to a database, to a file, and/or to console
[*:1i77t48p]Telling the player that s/he can't do it
[*:1i77t48p]Blocking the player from doing it
[*:1i77t48p]Kicking the player
[*:1i77t48p]Banning the player
For example, if you didn't want players to be able to use diamond pickaxes or diamond axes and you wanted to announce to administrators when a player tried to destroy obsidian, you could use this:
The block lag fix works well except for leaves. If leaves do not spawn saplings then you need to keep hacking at them until they do. It's the only way to destroy them. Dont know why this is. If it is the mod itself or Hey0 or the combo of the two. Only an issue with leaves tho.
I would love to implement this on my server, but unfortunately I'm running the stats/achievements plugin which requires patches to hey0's mod. I'm not 100% on how to patch this manually, so I'm using the pre-patched 125 version. Obviously, if I used this 126, it would break the stats/achievements. If you could either provide just the standalone block lag fix, or patch your 126 for the stats plugin people, it would be very greatly appreciated! (Or maybe someone who knows how to patch it point me in the right direction).
Im good I allow water and buckets - why block them from users who really use them for good and not grief if your plugin does anything like griefalerts we should get notified who used it and if there not trusted with it simply tp to them and check it out.
being lazy and blocking everything fails for people who actually are responsible.
Just noticed if I was to use this id be using all of plugins minus the craftAPI.
I also notice your plugin can deny placing of blocks so why cant users simply just add water and lava to the list of how it handles the block when placed. seems like a simple solution to me unless u rather spend extra time to add a config option to enable or disable buckets when.
I don't know if mean that the plugin it self has no support for the item ID's or just you have not added ability to block buckets if its the later then my above idea is just as a decent temp solution for those who just want to stop people placing water and lava.
The problem is that you cannot block buckets at all in any reliable or safe way from a plugin. The only possible method is currently used by GriefAlert but it can be easily bypassed and worse, it risks the stability of the server.
I'm very confused by how you setup the log file I dont know how to give it a directory to save in or how to make it save in a txt file just plainly I fail to use this lol. I worked out I could name it tho
But it saves it in the ROOT of my server directoy as "worldguardlog0.0" instead of "worldguardlog0.txt" and the system pic the file type up as 0.file as well (you know in win7 how it shows the filetype column that is what it shows there)
Also for some reason my blacklist is being stupid
My diamond tools have the desired deny, "block replacement upon Leftclick" but it applys the effect to the ignored group but not groups that are NOT! ingnored.
It also will sometimes tell the player its not allowed even when set to deny but it allowes them to do it anyway. Meanwhile it wont even pick up tnt,adminum being placed or destroyed and it wont kick players.
I could explain more but I think my Config file would be better for you to see.
we ended up fixing the blacklist to be pretty much perfect but for some reason its Diamond tools slip past the Ignore groups list and admins and mods cant use the diamond tools the blocks bounce back to the deny option. I also made a post on your Hey0 forums topic with some ideas and issues we are having working things out.
Here is our updated blacklist, It still has some issues but overall its much cleaner to work with. These issues being as I said it ignores the Ingnored option for tools and these tools are not denyed on group that are not ignored!. Other then this I think its working as intended.
# This is the blacklist for WorldGuard. Comments start with # and they
# are ignored so you can put your own notes.
# - ignore-groups (comma-delimited list of groups to not affect)
# - on-destroy (when a block of this type is destroyed)
# - on-left (when this item is held and the player is left clicking)
# - on-right (when this item is held and the player is right clicking)
# - deny (deny completely)
# - notify (notify admins)
# - log (log to console/file)
# - kick (kick player)
# - tell (tell a player that that's not allowed)
# Some examples follow.
#Actual Data Below!
#Blocks and Carts,dangerstuff
#Diamond Item Control
We also made one with Item Id's instead of names as we did not know if you could use item Id's as well - the first version of this blacklist was a rushed one by me just to get it up there and testing. But as I have said the one issue we notice with the blacklist now is how it handles the tools ignore groups.
most of our confusion with the log file is simply the % options and there usage we would prefer to make use of the cycle and unique but as for the temp %t and couple others we have NO idea what they do in relation to how it would handle the log file.
Going by your post tho we can now fix the log file to actually work and store data properly and im guessing u just any of the % to end of its name like logs/log%u.txt. when I first created the log I gave it the drive letter as well like this, C:\DirectoryA\DirectoryB\logs\log%u.txt - < this="" did="" not="" work="" out="" so="" well="" as="" it="" ended="" up="" calling="" the="" log="" file="">
Just tried the log file setting exctly as u posted it and its still saving in a format as .0 with or with out the %u before the .txt makes no difference with it it saves as wordguardlog0.0, I realoded the mod via console but It might need a full restart and a clear of the LCK and old log before it works maybe ...., you might wish to look into it tho.
Nope and not that I have done any testing but I gave it 2.5gig and its trudged along just as it always has running on java 64bit not 32java and using all those lovely java command lines for opimization.
Quote from sk89q »
I am going to write my own log rotation rather than use Java's.
Also, to block TNT, use on-destroy instead of on-left (on-left considers the block that you are holding).
I think your avoiding a lot of my inquires :tongue.gif:
[*:1jnz08ok]/stopfire and /allowfire disable and enable fire spreading globally.
[*:1jnz08ok]I significantly improved the blacklist! More events to catch (item drop, block 'use' for chests, etc.)! Database support! New file logger (note: you will have to change your configuration) that can even create a log per player!
[*:1jnz08ok]LeafDropper and other similar plugins are now supported by the block lag fix.
More features are listed below:
[*:1jnz08ok]/stopfire and /allowfire disable and enable fire spreading globally.
[*:1jnz08ok]Block lag fix slightly improved in accuracy for item drops.
[*:1jnz08ok]Sponge updated to remove water when the sponge block is set. Sponge radius can now be controlled using the 'sponge-radius' parameter and the default is now set to simulate Classic.
[*:1jnz08ok]Updated for a newer build of "b126," meaning that lava spread control now works well!
[*:1jnz08ok]A new summary of the status of some core protections is now printed on start. Disable this with 'summary-on-start'.
[*:1jnz08ok]Blacklist system has been overhauled. Check README.txt for changed configuration settings!
[*:1jnz08ok]The blacklist's method of preventing notification repeats is now better, instead waiting 3 seconds before notifying again (before it didn't notify again at all unless the user started using another blocked action).
[*:1jnz08ok]To give users the ability to receive notifications, the command to give permission to has been changed to /worldguardnotify, although the old one (that was never mentioned anywhere) still works.
[*:1jnz08ok]Water and lava buckets are now psuedo-blocked using an unreliable method that risks the stability of your server (no other plugin does it better though). Use it as your own risk.
[*:1jnz08ok]Added on item drop and on item use (i.e. chest) events.
[*:1jnz08ok]Chests, signs, and furnaces can now be blocked better with the blacklist system.
[*:1jnz08ok]The event names in the blacklist configuration have changed but the old event names should still work. The new names should make "more sense."
[*:1jnz08ok]A new "ban" action has been added to the blacklist.
[*:1jnz08ok]Action messages have been improved, now longer saying "destroyed" for everything.
[*:1jnz08ok]Logging to file has been completely changed, allowing you to use the date and time and the player's username in the log filename. It no longer rotates log files based on size, however.
[*:1jnz08ok]Logging to database is now supported.
[*:1jnz08ok]Tools can now be destroyed on drop to alleviate the durability cheat. You can do this with either with the blacklist or with the 'item-drop-blacklist' configuration option. The configuration option prints more friendly messages than the 'tell' action of blacklists.
A NEW build of the unreleased b126 version of hMod is required. If you downloaded a previous version from me, YOU MUST UPGRADE. Get it here: hmod-b126-early3.zip