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 Dec 24, 2013Hi really great plugin !
I dont understand where to change the Claims.InitialBlocks: 100 I cannot find it in the config files
Thanks
-
View User Profile
-
Send Message
Posted Dec 24, 2013@ha11oga11o
Player dont die after PVP hit, and log out.
They do, it was changed. When PVP punishment is enabled and a player either in a siege or in PvP logs out, there will be a 10 second delay before the punishment is enacted.
After that timeout occurs, the PvP Logger's equipment is drained and given to the Player they were last in combat with. When they next log in their inventory will be deleted and then they will be killed. (at least that is how it is supposed to work, and it worked in my testing, though I only have two accounts to experiment with).
The reason this was changed was to fix some issues regarding server restarts, which would punish the player's being forcibly logged out, which is not desirable and can be quite infuriating.
have this error on DEV build, is it mine mistake or it will be fixed in some point?
Based on the stacktrace, it looks like Essentials is causing an Entity Explosion event, but the Entity is null. I'm not sure if that is even possible normally. It probably is. the line causing the exception is simply debugging code that I've since removed so it shouldn't be in the next build.
-
View User Profile
-
Send Message
Posted Dec 24, 2013Hello,
have this error on DEV build, is it mine mistake or it will be fixed in some point?
http://pastebin.com/Z0RpnU6d
Spigot-1193
GP DEV build 218
Also, cfg setting
does nothing. Player dont die after PVP hit, and log out.
Many thnx for great work, im just contributing by adding some error logs to light.
Cheers :)
-
View User Profile
-
Send Message
Posted Dec 24, 2013Is there any possibility (including version 7.6.2) to auto-trust any players new or existing claims OR give player permission to automaticly start in /ignoreclaims-mode? This would be extremely useful for Fake-Players like [Buildcraft] or [Redpower].
Oh, and Merry Christmas :D
€DIT: Found out myself, it's Mods.PlayersIgnoringAllClaims: ['[RedPower]','[RedPower2]','[Buildcraft]','Buildcraft']
-
View User Profile
-
Send Message
Posted Dec 24, 2013Are you guys able to fully document the new nodes ? I can't figure out the adjust bonus claim blocks node
or the node for changing other players claims. Thanks =]
-
View User Profile
-
Send Message
Posted Dec 24, 2013Hi,
Is there any possibility to disable the /ignore command and disable the message coming on the screen about that command when saying "ban" in the chat? I just want the whole command to be disabled so that essentials.ignore works again...
A few weeks ago I also tried to use mysql but on startup griefprevention crashed, any tips?
Thanks in advance!
-
View User Profile
-
Send Message
Posted Dec 24, 2013This plugin is working flawlessly with the CraftBukkit Beta Build 1.7.2-R0.2 EXCEPT for the item frames.
Can you just fix that one line in code which is responsible for the Item Frames and release it as 7.7.1?
This is the only issue I have.
I don't think this is too hard, c'mon man!
-
View User Profile
-
Send Message
Posted Dec 24, 2013@Luficer
I think GP handles connections pretty badly. I seem to remember that it would literally re-establish the connection for pretty much every single query. I think I removed/fixed that but there might be some left or I may be misremembering.
-
View User Profile
-
Send Message
Posted Dec 24, 2013@BC_Programming
Well I thought there may be some fundamental difference in how HawkEye handles SQL udpates because I never have any lag due to HawkEye queries, which have several thousand queries it seems, much more frequent than GP, but GP will somehow halt the server during queries (or if not during queries, intermittently during claim modifications)
-
View User Profile
-
Send Message
Posted Dec 23, 2013@Luficer
The purpose of an SQL database is to be faster and more responsive than the flat file data store.
More importantly, no, it's not reasonably possible to make the SQL queries concurrent. And I don't think it is particularly wise to do so.
-What if an Exception occurs? Who handles that error? The method that knows best, the caller, has already moved on. The only reasonably course of action is the swallow and log, really.
-Many methods rely on the query results in some fashion, even for updates and inserts.
it may help to queue SQL queries and update tables in fixed intervals from a flat SQL file. Just a suggestion because I happen to have this issue on my server. I've managed to disconnect several users because creating new claims causes the server to stop responding long enough for it to kick users.
If a database server stops responding long enough to DC players with queries as simple as those that GP issues (which only update a single record at a time) I'd argue the problem is with the database server or it's connection with the game server.
Ignoreclaims requires griefprevention.claims.ignore as well as griefprevention.commands.ignoreclaims.
@switorik
I do have a question regarding horses. How do you trust someone to ride your horse? Can you allow the public to ride your horse if you choose to? Can you transfer the horse to someone else?
Yes and no. GP works with Claims. That is, players get trust or permissions on claims. Horses are, of course, entities. They have owners. GriefPrevention.ExtendedHorseTrust in the more recent development builds enables some added hard-coded functionality surrounding horses. A player that has build trust can ride a horse on a claim owned by the owner of that claim. When they do, the horse becomes theirs (ownership is transferred to them). Horses will be mostly invulnerable to damage on a claim except when being ridden- purpose being to prevent players from riding around and exploiting their horse being invincible in some fashion. @Flashman014
The development builds are built with Java 7.
@aceyxx
You could revoke most griefprevention.claims.* permissions, preventing them from creating new claims or from resizing their existing claims.
-
View User Profile
-
Send Message
Posted Dec 23, 2013Just updated to beta 214 and got this error. pastebin.com/Ppgy24tv Also got the same error with dev 218.
-
View User Profile
-
Send Message
Posted Dec 23, 2013Is there a way to lock all of a players claims as an admin?
-
View User Profile
-
Send Message
Posted Dec 23, 2013Thanks for keeping it up to date and the improvements are phenomenal!
I do have a question regarding horses. How do you trust someone to ride your horse? Can you allow the public to ride your horse if you choose to? Can you transfer the horse to someone else?
edit: I have a suggestion. Can you make it so the sign logs to a file and not just notifies in chat? I had a griefer put down a couple signs to the place he griefed saying a few things about how he deserved it.
-
View User Profile
-
Send Message
Posted Dec 23, 2013Would it be possible on a future update to enhance the SQL support by externalizing SQL queries in a different thread? If a server happens to have a somewhat slow SQL database connection, it becomes rather problematic to do anything with claims. Creating, altering, trusting, expanding, or almost anything with claims will halt the server entirely it seems (including the chat somehow). Also, for plugins that frequently access the SQL, it may help to queue SQL queries and update tables in fixed intervals from a flat SQL file. Just a suggestion because I happen to have this issue on my server. I've managed to disconnect several users because creating new claims causes the server to stop responding long enough for it to kick users.
Also, has the permission for ignoring claims been changed? I'm using the one listed on the new documentation page, but doesn't seem to work.
-
View User Profile
-
Send Message
Posted Dec 23, 2013How can I make it so that every permission group has a maximum amount of claimable blocks?
-
View User Profile
-
Send Message
Posted Dec 23, 2013@Purpleantilope
I have the same problem..
-
View User Profile
-
Send Message
Posted Dec 23, 2013Hello i updated to the last GreifPrevention release 7.8-beta-b213 and got this error : http:pastebin.com/ib1JhgRC could someone please help me?
-
View User Profile
-
Send Message
Posted Dec 22, 2013@CoolGamrSms
If memory serves when BlockRevert is enabled it can break almost any block, idea being that the damage will be reverted. Additionally, the idea was to allow otherwise unsiegable walls such as stone brick to be breeched using explosions, making TNT a bit more useful. I seem to recall some separate list for what blocks cannot be broken by explosions in a sieged claim but I don't recall if that was configurable off-hand.
-
View User Profile
-
Send Message
Posted Dec 22, 2013@Sargewood:
I can't find BlockPlacement and BlockBreakment PLEASE HELP!!!!
-
View User Profile
-
Send Message
Posted Dec 22, 2013Thanks for that last fix, worked perfectly.
We're considering enabling TNT for sieges on our server, but we realized that it seems to disregard the "ExplosionBreakableBlocks" list in the config. Is this a bug or do we need to restrict it to the list with another flag?
Also, how hard would it be to implement a time limit on sieges?
Thanks again for all the help!