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).
Bigscary have you updated GP to 1.10? any link ? Jekins? GitHub ?
tested GriefPrevention.14.7_MC.1.9 on spigot 1.10 - its working fine, TY...
@bigscary
Is there a way then to restrict building outside of playerclaim?
do we still need tuxtwolib installed ??
@BrawlerFighter
That's very odd, I'm sure it must be a bug on my end. I will try to figure it out for you. In the meantime, you could increased the number of players allowed to share an IP address to a very high number in your config file.
@TheDianite
By default, golden shovel claiming should work. If it isn't, make sure you downloaded a version of GP which was made for your sever's version of Minecraft.
@nixbeast
You can use /acb [permission.node] amount . The square brackets are required (you have to type them).
@MightyMooshroom
Sorry, the WorldGuard integration doesn't work that way. If WorldGuard says a player can't build in an area, GP will not allow a player to claim land in that area.
@This_sucks_on_ice
I'm not sure about that, I hope someone who knows command blocks better than I do can help you with that. :)
Is it possible to /accesstrust a player inside of an administrative land claim using command blocks and pressure plates?
Hello,
I'd like to know, how to give my players the opportunity to build inside WG regions, but only after they've claimed an area inside that region.
TCS
Hi, I'm looking for the source code of Color Shuffle, since its abondoned, I'll provide it to my developer which he will take it back and maybe credit you. Had to post it here due it'll be ignored in its plugin page. Thanks in advance
EDIT: Just noticed Tux2 is a contributor... I thought he was an author... damn...
Is it possible to set the amount of regions(like in WorldGuard) for groups(from PermissionsEX) or for each player separately, rather than globally?
I added this plugin to my server and it works but how do u setup claiming with a golden spade?
Hi,
I already disabled the AntiSpam configuration, but when my players relogin to often, it will stay says this:
Too many players with your IP address online
This problem makes the player cant join the server, and fixed after the server has been restarted (every 8 hours)
Any how to fix it? Thanks ^^
Using the 1.8.x GriefPrevention version
@MCMaricopaAZ
Sounds like all generic server problems or other plugins, not specific to grief prevention. I don't happen to know the answers to any of your questions, sorry. :\
@SilicaAndPina
If by "grief" you mean - places snow? :) And only in a snow biome, right?
hi, i found a way to greif. spawn a snow golem push it into a claim.. and it greifs...
Hello,
I'm working on my first MC server ever. Having fun. I have a question about the Grief Prevention plugin
The Grief Prevention plugin is working great and helping me with one bug that just wouldn't go away.
Briefly, I created a world in single player (normal,Survival). I imported it into my server and and I want it to be Adventure. However, no matter what I tried new players can break blocks.
Really, I tried everything I could find such as spawn protection, setting default game mode in server.properties, Forced Gamemode = true, command_blocks with fill clocks setting game mode, pressure plates, etc. NOTHING WORKED.
I found GriefPrevention and used /ContainerTrust and it worked!!! I'm nearly there. It got me 99% of the way.
PROBLEM: Players cannot use my Multiverse Portals.
Question: Is there a way to allow all players to use the Multiverse portal to teleport to my other worlds?
I already tried..... Using a command block with /mv tp @p survival (doesn't work)
HOST: Fluctis MC: 1.9.2 spigot Plugin List
ChestRegen ChestRegen.jar 3.2.2 Citizens.jar 2.0.17-SNAPSHOT (build 1338)Configuration EnjinMinecraftPlugin EnjinMinecraftPlugin.jar 3.0.14 GAListener GAListener.jar 1.3.2 GriefPrevention GriefPrevention.jar 14.6 Multiverse-Core Multiverse-Core-2.5-b717.jar Multiverse-Portals Multiverse-Portals-2.5.jar 2.5-b725 PermissionsEx PermissionsEx-1.23.4.jar "1.23.4" Shop Shop.jar 1.5.3.16 Vault Vault.jar 1.5.6-b49 Votifier2 2.0-SNAPSHOT
B.Rgds, Scott H Owner: MCMaricopaAZ
@Kira_Kun
Robo's comments are good, see those. About the documentation problem, please be more specific so I can find and correct the problem.
@Sabbertran
No, it would lag the server and possibly disconnect players. You'll need tighter integration with GP - maybe customize GP to open some ports so your web interface can talk directly to the plugin instead of having the web UI change files, then have GP re-read them.
Is it possible to add a command to reload the data from the database? Because we use a custom webinterface to manage claim permissions and this doesn't work if we can't reload the data
@Kira_Kun
I haven't checked to see if Notepad++ can do YAML validation, but you can use an online web service to validate YAML files and point out errors, just search for a YAML parser. It's possible you might need to wrap it in single quotes.
As for setting trust in admin claims, make sure you're inside the admin claim when setting trust. It works the same way as setting trust on a private claim.
@bigscary
i did use notepadplusplus, are there any specific settings i must instruct notepadplusplus to do prior to editing?
i know that each text has a expand and compact +/- sign beside it to indicate if anything is wrong like if i make the text 2 lines instead of 1 continuous line.
to be exact here is what i tried to do,from the default i simply added japanese texts with the original english texts in 1 continuous line,unless it doesnt like me to do things that way,could you tell me how i could add dual languages instead of converting all texts into 1 language?
Additional Notes;
ive looked high and low about adminclaims but it seems there are certain parts of your written guide having some commands mislabeled. plus im confused on how to set public on trust for admin claims,apparently with accesstrust or trust it ends up setting my private claims as public instead of adminclaims as public.am i missing any vital command steps?
it would be nice if you could have your wiki on GP updated
@Qballl
Yes, that's right. Unless you count code comments, which you can see on github.
@Kira_Kun
When it reverts back to defaults, that means you made a yaml syntax error. Use a yaml editor like notepadplusplus which will highlight errors when you make them, and always back up your file before you restart the server.
@natureclub2016server
Yes, latest versions are for 1.9.2.
Is greif prevention for 1.9.2?
i noticed that there is a messages.yml in the config folder which led me to think i could localize the language as appropriate but after translating the texts and starting the server i noticed that it reverted back to english.
can someone tell me how i can go about localizing the language if editing messages.yml simply doesnt work?