Grief Prevention
AUTOMATICALLY PREVENTS ALL FORMS OF GRIEF, including build/break, theft, spam, fire, spawn camping, lava dumping, chat trolling, advertising and more, so you don't have to undo any damage after the fact. It even teaches players how to use it so you don't have to! No configuration or database required. Stop responding to grief and prevent it instead. Grief Prevention will solve your grief problems without requiring you to manage a roster of trained administrators, juggle 10 different anti-grief plugins, take away cool standard game features, publish a training manual / tutorial for players, or add explanatory signs to your world. You can also choose to integrate PvP elements into build design to finally get a PvP experience befitting a sandbox game about creative building.
Grief Prevention stops grief before it starts automatically without any effort from administrators, and with very little (self service) effort from players. Solve all your grief problems with a single download, no database, and no configuration step.
Got a question or found some random bug? Check the documentation!
Got a problem or bug you can reliably reproduce? Or a feature request? Report it on the issue tracker!
Also, you might be able to catch me/others on the #GriefPrevention IRC channel for help (please state your question and exercise patience if you use this option).
Downloads for older Minecraft Versions
You may also view recent update notes on Github
The Manual
Feature List
Yes, everything is customizable.
- No database or world backups required.
- Extremely efficient CPU / RAM usage.
- Land claims are easy to manage.
- Players create and manage their own land claims, so you don't have to do it for them.
- New players get automatic claims around their first chests so they're protected even if they don't know how to create land claims yet.
- Players who ask for help in chat get an instant link to a demonstration video.
- Resizing claims and creating new claims is done with ONLY the mouse, no slash commands (slash commands are also available).
- When a player appears to be building something nice outside his claim, he's warned and shown his claim boundaries.
- Claim boundaries are easy to see, and don't require any client-side mod installation.
- Extremely easy-to-remember, single-parameter slash commands for giving other players permissions.
- Claim subdivision and granular permissions are available to organize towns and cities. Watch this video.
- It's IMPOSSIBLE to grief a land claim. Watch this video.
- No building or breaking.
- No stealing from ANY containers.
- No sleeping in beds.
- No button/lever usage.
- No adjusting redstone repeaters or other configurable blocks.
- No pushing blocks in with pistons.
- No pulling blocks out with pistons.
- No TNT damage (including cannons).
- No creeper damage.
- No explosive damage from other plugins, like Extra Hard Mode or Magic Spells.
- No enderman/silverfish block changes.
- All doors may be automatically locked (optional, see config file).
- No killing or luring animals away.
- No stealing water (e.g. buckets).
- No trampling crops by players, animals, or monsters.
- No building overtop, all claims reach to the max build height.
- No placing or breaking paintings / item frames / armor stands, etc.
- Fluids will not flow into a claim from outside.
- No placing blocks via TNT/Sand/Gravel cannon.
- Pets and death loot are protected.
- Players can't pick up what another player dropped on death without permission.
- All types of pets are protected everywhere, even outside of land claims (can be configured per-world).
- Excellent anti-spam protection
- Warns, then mutes, then may kick or ban spammers (configurable - you choose).
- Most spammers get only one message out before they're muted.
- Blocks server advertising (IP addresses).
- Blocks repeat message spam.
- Blocks ASCII art (ex. Nyan Cats) spam.
- Blocks similar message spam.
- Blocks unreadable (gibberish) message spam.
- Blocks CAPS.
- Blocks macro spam (very different messages in quick succession).
- Blocks login/logout spam, even when the spammer has multiple accounts.
- Blocks death spam.
- Blocks bot team spam.
- Blocks slash command spam, including /tell, /emote, and any more you add.
- Wilderness Protection and Rollback
- Fire doesn't spread or destroy blocks.
- Creepers and other explosions don't destroy blocks above sea level.
- TNT doesn't destroy blocks above sea level.
- No planting trees on platforms in the sky ("tree grief").
- Instant, point and click nature restoration for not-claimed areas. Watch this video.
- Insanely easy and fast fixes for penises, swastikas, and anything else unsightly.
- Point at what you don't like and click, and it's fixed. Even from far away.
- Never accidentally changes blocks inside land claims.
- No need to investigate who built it, who broke it, or when they did it.
- Doesn't matter if the griefer built with "natural" blocks, it will still be fixed.
- No database.
- No backups.
- No chunk regeneration (it's dangerous for technical reasons).
- Fixes bad chunk generations, like floating islands. It will be better than new.
- Fills holes, even next to water to correct big spills.
- Smooths noisy terrain.
- No griefer construction is safe. If it's unnatural enough to be noticeable by players, it will be removed or filled-in.
- Land claims can't be used as a griefing tool.
- It's impossible to get a player "stuck" inside a land claim.
- Land claims beyond the first require a golden shovel.
- Minimum claim size prevents sprinkling small claims to annoy other players.
- Max claim allowance grows with time played on the server, and can't be cheated by idling.
- A simple administrative slash command will instantly remove all of a griefer's claims, no matter where they are.
- Catches clever griefers.
- Enhances the /ban command to ban ALL a griefer's accounts (not just his IP address).
- Logs sign placements.
- /SoftMute command to shut down chat trolls without them knowing they're beaten.
- Abridged chat logs make reviewing what happened while you were away super-quick and easy.
- Automatically mutes new-to-server players who use racial or homophobic slurs.
- PvP Protections.
- When PvP is off, no setting fire or dumping lava near other players.
- Absolutely bullet-proof anti-spawn-camping protection including bed respawns, which requires no configuration.
- No logging out, stashing items, or using plugin teleportation to escape combat.
- Optional siege mode, to answer players who hide in their claimed houses to avoid combat.
- Supports your server growth.
- Permit players to exchange server currency for claim blocks (requires configuration and other plugins).
- Grant claim blocks automatically for votes, donations, etc (console command provided, other plugins required).
Please Vote for Grief Prevention
I've also posted Grief Prevention on the Spigot site, where plugins are ranked based on reviews. If you love GP, please take a couple of minutes to give GP your rating and leave a short review. Better rating and positive reviews will help server owners who look for plugins on the Spigot site make the safe choice (GP) instead of downloading something sketchy or incomplete. :) Thanks so much for all your support!
http://www.spigotmc.org/resources/griefprevention.1884/
Got a question or found some random bug? Check the documentation!
Got a problem or bug you can reliably reproduce? Or a feature request? Report it on the issue tracker!
Also, you might be able to catch me/others on the #GriefPrevention IRC chat channel for help (please state your question and exercise patience if you use this option).
-
View User Profile
-
Send Message
Posted May 26, 2013@Senophoe
I can't repro the lava buckets outside claims, though it might be something I've changed since. Inside claims neither option seems to take effect, will have to figure out why.
Thanks for your help and patience testing these changes :)
EDIT: incoming build #49 should:
-fix the Water and lava bucket configuration options not working for claims (claim permissions may still override them). -Implement Golem and wither spawn configuration rules -add new message for certain operations when disabled through cfg (currently used for buckets)
-
View User Profile
-
Send Message
Posted May 26, 2013I cannot use dispenser or droppers in a creative world. It will only remove the item from dispenser/dropper. Any ideas how to fix it?
-
View User Profile
-
Send Message
Posted May 26, 2013Water buckets and lava buckets still seem to be problematic.
-
View User Profile
-
Send Message
Posted May 26, 2013@nathanlevi
That sounds interesting, but I'm neither the author nor a maintainer for the 'GriefPrevention Flags' Plugin. You might want to leave a comment or enhancement request ticket on the GPFlags page so it's authors can see it more promptly :)
http:dev.bukkit.org/server-mods/gpflags/
-
View User Profile
-
Send Message
Posted May 26, 2013Just an idea but what about adding into the gp flags plugin a way where being in your own region gives you certain benefits for the duration you stay in your area, that way you can still pvp but have an advantage in your territory
-
View User Profile
-
Send Message
Posted May 26, 2013@65416516516514
you can set GriefPrevention.Claims.AutomaticNewPlayerClaimsRadius to 0 to disable the creation of first-claims with chest placement.
-
View User Profile
-
Send Message
Posted May 26, 2013Is there anyway to get this to respect factions so that a member of a faction can't place a chest in faction territory and have it claim land within that territory?
-
View User Profile
-
Send Message
Posted May 26, 2013@Senophoe
Nope, that would be a typo in the source on my part. There should only be the GriefPrevention.Claims.BlocksAccruedPerHour
@RMMontage
Not a bad idea at all. It will almost certainly require deleteclaims permission as well as issuing a warning confirmation (needs to be entered twice).
-
View User Profile
-
Send Message
Posted May 26, 2013Can you please create a command to delete in a single time every claim present in a world? Because the claims' files are not divided by worlds and it's hard to find what claims I'd like to delete. The command could be like this: /deleteallclaims <World Name> Thank you and have a nice day :D
-
View User Profile
-
Send Message
Posted May 26, 2013@BC_Programming
Just edited my post. Read it again, please. XD
-
View User Profile
-
Send Message
Posted May 26, 2013@Senophoe
Yeah, the Require<trustlevel> entries indicate required perm levels to do that action, eg RequireAccess would require AccessTrust or Higher, RequireContainer would require ContainerTrust or higher, etc.
-
View User Profile
-
Send Message
Posted May 26, 2013@BC_Programming
If I set RequireAccess to the behavior, then the player will only be able to do a certain action as long as he has access to that claim? Is that it?
@edit There seems to be two BlocksAccruedPerHour: 100 entries on the default config file. Is that normal?
-
View User Profile
-
Send Message
Posted May 26, 2013Latest Dev build (#48) fiddles with how the configuration.Claims are handled in the cfg options with a 'Behaviour' option. This can be None- indicating that the configuration doesn't do anything special for claims, or it can be ForceAllow (which should force the attached behaviour to work regardless of claim permissions, but due to the way the logic is arranged this is probably not the case yet) and RequireOwner,RequireManager, RequireAccess, and RequireContainer, which require that the player performing the action has the respective permission. These settings only apply to Player Actions or actions for which a player is attached, such as placing water or lava, and so forth.
It should resolve the issue where water and lava bucket placement was not respecting the configuration setting for the wilderness, as well as an NPE as a result of the new "LootChests" feature that I added (because evidently it wasn't enough work to completely rewrite how configurations are handled).
I accidentally left a bit of console debug spam in for the configuration loading, which only occurs when a world configuration is loaded.
I'll probably cleanup or find a way to show users more descriptive denial messages based on the new configuration settings.
-
View User Profile
-
Send Message
Posted May 26, 2013@BC_Programming
I'll try websend, thanks for the clarification.
-
View User Profile
-
Send Message
Posted May 26, 2013@kemmeo You can't. They are basically internal data structures that are cached for performance reasons, rather than hitting the file or database for every retrieval. They are, however, exposed through the API so it is possible to create your own plugin or ask an existing plugin to support GriefPrevention interactions through dataStore.adjustGroupBonusBlocks.
Also, could you not use websend to issue an /acb command?
-
View User Profile
-
Send Message
Posted May 26, 2013@BC_Programming Okay but then, how do I then dynamically change the claim values without access to the in game console or server console? I can use plugins like Websend to make console commands but I need a way to keep track of the used claims and the available ones. I am trying to make automatic donations.
Thanks for answering.
-
View User Profile
-
Send Message
Posted May 26, 2013@kemmeo
Don't change the values while the server/plugin is running.
-
View User Profile
-
Send Message
Posted May 26, 2013Hey Tux2.
I have been trying to update my player's Bonusblock count on a mysql database, however the change in the database is not carried over to the game server. using commands on console or as player still works fine and updates the mysql database, example: /acb kemmeo 100 updates the Bonusblocks field on mysql server but if I put in a number in the mysql Bonusblock field directly it doesn't update and is being corrected to the original numbers automatically.
Can you help me understand how this works, how will I be able to manipulate the numbers other then using in-game or console commands?
Thanks very much in advance, I appreciate the help.
-
View User Profile
-
Send Message
Posted May 26, 2013@Senophoe
As I said, not all of the options are fully implemented. The golem spawn information is currently unused.
Also currently, the "Claims" part is currently redundant (samed with "OwnedClaim" ) and they will likely be removed, leaving only the wilderness configurations, since claim capabilities revolve around claim permissions rather than these settings.
EDIT: I'm reworking the configs a bit. Basically, the 'wilderness' config idea is simple- just have it above or below sea level. But when it comes to claims I want a bit more control. Right now claims always take precedence, whereas it could be useful to force certain actions to only be permissible in a claim by owners, or players with a specific trust. For example, setting fires could be possible everywhere in the wilderness above sea level, but require access trust to do inside of a claim (just as an example); summoning withers could only be possible by claim owners, (assuming that event provides the creator for testing), etc. Basically, there will be an extra piece of data for how the Claim-side of each permission set works that is relevant for entries that can involve players, such as setting fires, placing/taking lava, etc. It could also be useful to "forcibly allow" actions within a claim that the claim logic would otherwise not allow.
-
View User Profile
-
Send Message
Posted May 25, 2013Another three issues.
Also, what does that OwnedClaim option do?
@edit BuildIronGolem, BuildSnowGolem, BuildWither don't seem to be working as supposed too.