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 Jun 4, 2013@BC_Programming
Very well, if you say the database isn't removed, then when can we access it again, i now have a completely unprotected 1.5.2 server, since i can't access my database any longer.
So again, when do you think you have a fix for that little problem?
-
View User Profile
-
Send Message
Posted Jun 4, 2013@dllis
Craft it, use the creative inventory, or use /give.
-
View User Profile
-
Send Message
Posted Jun 3, 2013@BC_Programming
How do I get the shovel?
Keep calm and carry on!
Dlljs.
-
View User Profile
-
Send Message
Posted Jun 3, 2013@ArtBorax
You're conclusion is premature. This may surprise some folks, but when you move hundreds of options around in the source sometimes you miss some :P
Those options were not being written back. Should be fixed in next version.
@GamersSynergy
With 7.7 you can change the world names in the "claimsenabledworlds". With more recent dev builds each world configuration should have a 'GriefPrevention.Claims.Enabled' setting.
@IsaacRij
Yes, if the location has no Claim, null is returned.
-
View User Profile
-
Send Message
Posted Jun 3, 2013If I used:
and the player wasn't in a claim, would it return null?
-
View User Profile
-
Send Message
Posted Jun 3, 2013Permanently removed from the config database information. I conclude that the plugin is no longer supported database mySQL.
-
View User Profile
-
Send Message
Posted Jun 3, 2013Is it possible to prevent people from claiming on other worlds? I just want it to work on one world. How would I go about doing that?
-
View User Profile
-
Send Message
Posted Jun 3, 2013Helpful! Will use this!
Keep calm and carry on!
Dlljs.
-
View User Profile
-
Send Message
Posted Jun 3, 2013I've been getting a lot of requests from my user base for a way to display a top list ordered by the people with the highest number of total claim blocks. I'm not sure if a dev has already integrated a plugin that could do this through the API. If so, I'd love to get my hands on that plugin. Thanks for reading! Also, GP is a perfect plugin, thanks for the hard work. Jack
-
View User Profile
-
Send Message
Posted Jun 2, 2013@IsaacRij
You need to get a reference to the GriefPrevention main class. Either add GriefPrevention to your LoadBefore, softdepends or depends lists in your plugin.yml.
With a GriefPrevention instance you access the dataStore field, and then call it's methods. The one you would want is getClaimAt().
You can find examples in other plugins that use or extend GriefPrevention or otherwise interact with GP Claims.
@Nuinethir
I don't know what version you are using; I'm guessing one of the dev builds that allows adjustments for various Explosions? There is supposed to be a "OtherExplosion" setting that is used for Explosions GP otherwise cannot "explain" (as it would for Withers, Creepers, etc. which are separate settings). I say "supposed" to be there but turns out it hasn't actually been properly read/written to the configurations. Build #63 should let you edit that setting.
of course this all relies on whether GP is actually getting events fired for those explosions. If those Explosions don't actually get fired to GP it has no way to stop them.
Quarries do not fire any Bukkit API events when it breaks blocks, so GP has no way to intercept them.
-
View User Profile
-
Send Message
Posted Jun 2, 2013This plugin is working great since I switched over to MCPC+ from BukkitForge. Needed to adjust a few settings but all is well. However, few things:
Any help here? I know this plugin isn't meant specifically for Tekkit but I was hoping there would be some way to ban BuildCraft from claims UNLESS I gave it rights. Possible?
Thanks much!
-
View User Profile
-
Send Message
Posted Jun 2, 2013@BC_Programming
I've got it setup now, thanks, but how do I get claim information for a specific location?
-
View User Profile
-
Send Message
Posted Jun 2, 2013@BC_Programming
I mean make disallowing buildings in claim in pvp configurable
actually I can compile for myself verson without pvp anti build, but I can't find how to import code to eclipse
-
View User Profile
-
Send Message
Posted Jun 2, 2013@IsaacRij
There is no separate API, you reference the GriefPrevention.jar.
-
View User Profile
-
Send Message
Posted Jun 2, 2013Where can I download the API?
-
View User Profile
-
Send Message
Posted Jun 2, 2013@GodsDead
I don't think there is a easy way around that particular issue, at least none that I can see. Best I can think of would be to make sure the player "can see" the chest they are opening.
Basically it sounds like the client is able to fire off a "open this chest" packet before it get's told that the block is actually still there, and the server (for whatever reason) doesn't add any checks except to make sure they are at least a given distance away
-
View User Profile
-
Send Message
Posted Jun 2, 2013@BC_Programming @Tux2 Chest protection is off, But users shouldnt be able to access chests by breaking a block and quickly right clicking a chest which stays open on their screen when the block replaces itself. I recently installed groupmanager for permission management, would I need to set permissions for GriefPrevention.Claims.PreventButtonsSwitches??
-
View User Profile
-
Send Message
Posted Jun 2, 2013@daddeo69
No. It's not. Can I get the actual error message please? In fact, if could you create a new Defect Ticket and provide as much information as possible, that would be appreciated :)
-
View User Profile
-
Send Message
Posted Jun 2, 2013I am have noticed since you changed the configuration in build 39, subclaims are not being stored properly and exceptions are occurring during load indicating not all coordinates are saving (something about needs 4). The next time I can start the server I will get the error. This problem does not occur with build 38 and prior. Is this a known issue?
-
View User Profile
-
Send Message
Posted Jun 1, 2013@RandomQuark
GriefPrevention isn't designed for granular control over individual Containers, so it not having granular control over individual containers isn't a flaw :P