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 19, 201511.6.1 Updates
@Jikodis
See dutch's comment below. If that doesn't help, you can eliminate other plugins interfering as a possibility by temporarily disabling everything except grief prevention. If even that doesn't solve your problem, please share your config file's content, and explain exactly what you're seeing that you don't want (inside/outside claims? sea level or beneath sea level? tnt or creepers?).
@TJW28
You mispelled it, and I forgot to add an alias for that common mispelling. I will add an alias. It's /separate.
-
View User Profile
-
Send Message
Posted May 17, 2015@Jikodis
The latest build is 421, try using the latest build.
http://www.spigotmc.org/resources/griefprevention.1884/updates
PLEASE be sure you're on a VERY recent 1.8.3 server version. Earlier versions of Spigot/CraftBukkit will not work with latest versions of GriefPrevention, due to breaking changes the Spigot team made somewhere along the way in 1.8.3 development. Symptoms of an outdated server build include errors logged during boot, explosions destroying blocks they shouldn't, and entities like item frames, animals, and armor stands not being protected.
-
View User Profile
-
Send Message
Posted May 16, 2015Loving the updates bigscary, though cant seem to get the new /seperate command to work, I have the Permission, griefprevention.separate, though just get unknown command in game.
-
View User Profile
-
Send Message
Posted May 16, 2015I have the plugin installed and recently it seems to have stopped working. Specifically Creeper explosions and TNT do damage. I have explosions disabled in the area. The plugin still runs, but protection from explosions is not working.
I am using Spigot 1.8.3 Build 373. My plugins are the following and are all up to date:
-
View User Profile
-
Send Message
Posted May 16, 201511.6 Updates
Added /ignore, so players can help themselves when there's no admin online to use /softmute and shut down a problematic chatter. Also helpful in reducing drama, which nobody likes. In addition to ignoring standard chat messages, an ignored player also can't use any whisper commands (see GP config file) targeting the player who's ignoring him.
Added /separate, an administrative command which forces two players to ignore each other. They are not notified, and can't see the force-ignored player on their /ignorelist. When two players can't get along but you don't want to totally /softmute either of them, this is a good option. Required permission: griefprevention.separate
@MotheMan
Maybe, let me check on that. I think it's a permission node you can take away.
@Bobcat00
Great!
@a1mbot
Sorry I don't think I will. I get why you want it, but it's a small payoff for a really big change (any change to the file format is a big deal). If those players are in your world\playerdata folders, then you should still see their names in-game rather than UUIDs. But I guess that's not the problem you're solving?
@Kepler_
Sorry, it's too expensive (cpu cycles). :( Unless you have a somewhat severe problem that I haven't thought of as a result of liquids flowing out...?
On nature regen, there's an option to toggle that for survival worlds but not for creative. The reason is this grief:
Auto-restore makes this impossible. There's a warning message and a waiting period before anything gets regenerated, to give players a chance to re-claim the area if they want to keep their work.
@GodsDead
Yeah, I know about that one. :\ It's a spigot bug - cancelling the teleport doesn't cancel the ender mite spawning. I logged the bug on hub.spigotmc.org. When it's fixed, a server update will fix this problem for you.
-
View User Profile
-
Send Message
Posted May 15, 2015Small Bug, if you have enderpearls disabled in claims, which you should, people can just spam them since it gives the enderpearl back, there infinite, so they can just spam them until endermites spawn killing the person inside!
-
View User Profile
-
Send Message
Posted May 14, 2015@bigscary
Alright. Also, do you can add an option to stop liquids from flowing out of a claim? As well as an option to disable nature regeneration, so that unclaiming land doesn't remove what was built?
-
View User Profile
-
Send Message
Posted May 14, 2015@bigscary
Hi,
Can you add the player's name into PlayersData file? I cannot get trusted players' name on offline servers, because I get the UUID only.
-
View User Profile
-
Send Message
Posted May 14, 2015@bigscary
I wrote a small Java program which goes through the claim files offline and produces a csv file that can be read by Excel. It lists each claim, the coordinates, area, owner, days since last login, info about managers, builders, container trust, access trust, and even the .mca filename. Excel allows me to sort it any way I want. This works great for me. I set my startup script to run the program every time I start the server. So I'm good.
-
View User Profile
-
Send Message
Posted May 14, 2015Is there any way to turn off the PVP override that OP players seem to get? Best solution would be /ignoreclaims also turning being able to hit people in claims on/off not sure if that's possible or not. Would be amazing though
thanks
-
View User Profile
-
Send Message
Posted May 14, 2015@Bobcat00
Ouch - what you ask for would be hugely resource intensive, since it would involve opening the player data file for every player ever on your server and parsing it (db mode is easier, but I have to offer the same feature set for both storage modes). What if you used either a custom sql query or the "last modified" timestamp on your player data files to identify players who have been gone a long time?
@Jikoo_K
Sure, on the todo list.
@Coolbannana44
See siege enabled worlds setting in your config file. It's off on all worlds by default, since it allows players to (situationally) destroy another player's protected work.
@xbenas
Noted - will do my best to limit it so that you don't have to turn it off entirely. There will be an option to disable, though. Agreed disconnecting is the right thing to do, but some don't and get griefed because of it. Always better to prevent a preventable issue if the cost isn't too high. :)
@GodsDead
I really wish I knew what was happening on your server. This baffles me. Still working on the better logging, it's right behind the ignore feature on the todo list. I'd already have it done if I hadn't gotten really sick this week.
@jenks1999
Please give me some details about how exactly players are able to bypass GP when that plugin is installed. I want to see if there's anything at all I can do on my end to fix the problem, because I don't like waiting for other devs to act on important problems like this one. Thanks for doing the investigation!
I won't add the feature you ask for because it's not anti-grief. Gotta keep GP lean, doing only what it's supposed to do and not wasting cycles on any fluff.
@Kepler_
Yep, I'm OK with that. It's not supposed to be centered - one appears every few blocks, unless it's too close to a corner.
For the grass thing, update your sea level in GP's config file (see "sea level override").
@ajaids
UUIDs.
@MALONN
ProtectCreatures, VillagerTradingRequiresPermission
Delete your "worldconfigs" folder. It is not used.
See my answer to kepler about islands. This is also answered on the troubleshooting page linked above. It's not 100% fixable but I do have a mitigation on my todo list.
Everything is in griefpreventiondata\config.yml. The other folder is not used and should be deleted. If you put your connection info in the config file as described on the setup page, then migration will happen automatically on next boot. Pro tip: Don't use the database. You'll have same performance and less headache if you stay in file mode.
Can't /untrust super old people. Until spigot guys make a fix in the platform, turning that on would be crashing servers. It's a cpu cost thing - it takes too long to search through all players since your server was first booted, so long that spigot gives up and crashes the whole server. So all commands only target recent (30 days I think) players. It's not a non-issue, but a lesser-issue, since the player probably won't be back anyway. If the claim owner is desperate, deleting and recreating the claim would also do the trick.
@Kepler_
It's an auto-correction for old bugs. Players who have more land claims than land claim blocks (negative amounts) are auto-corrected back to zero by adding accrued blocks, bonus blocks, or both so that they're back to balance zero without losing any land claims. If you check your own count again, you'll see that it corrects back to zero from -221 on its own.
-
View User Profile
-
Send Message
Posted May 13, 2015Players are having blocks removed while they're offline. Many of my players have zero blocks after having been offline, and I have -221 blocks that I can claim.
When I hold a gold shovel: "You may claim up to -221 more blocks."
-
View User Profile
-
Send Message
Posted May 13, 2015@Bobcat00
/abandonclaim is mostly used by players who want to delete their own claims, while /deleteclaim is an admin-oriented command for deleting claims in general.
-
View User Profile
-
Send Message
Posted May 12, 2015@Bobcat00
I'm not sure if they are the same or not. I know they use different permissions (griefprevention.deleteclaims vs griefprevention.claims However, it does appear I am wrong. The regen chunk error does not seem to be repeatable every time, just most of the time. My error was performing the same tests using both /abandonclaim and /deleteclaim and the error would only happen on /deleteclaim. However, after some more testing, eventually /abandonclaim produced the same issue
-
View User Profile
-
Send Message
Posted May 12, 2015@MALONN
What's the difference between /deleteclaim and /abandonclaim? I thought they did the same thing.
-
View User Profile
-
Send Message
Posted May 12, 2015Question #1 ... 11.5.2 Updates
What are the names of these options in the config file? Do I have to regenerate the entire config file to see these, because I'm not finding them in config.yml or the WorldConfigs/world.yml
Question #2 ... @Kepler_ is right Not really a question, just verifying. What @Kepler_ said about large regen chunks floating in the air is happening all the time on my server. Seems to happen with /deleteclaim not /abandonclaim. The claim must also be owned by a person, using /deleteclaim on an admin claim does not produce the bug.
Question #3; MySQL Migration Can someone provide an example how to migrate to MySQL? I have every other SQL compatible plugin running as such, but the instructions for the config.yml for GP seem to be lacking and I can't figure it out. dataconfig.yml always just says "flat: {}"
In my config.yml I have (snippit):
Console boot report:
Question #4 Any info on being able to /untrust "old" players from claims? I have people which are currently trusted in a claim but cannot be removed because they "haven't signed in recently".
-
View User Profile
-
Send Message
Posted May 10, 2015Does this still use player names for the player claim data, or does it use UUIDs now?
-
View User Profile
-
Send Message
Posted May 10, 2015I'm getting these blocks of grass in the air whenever someone makes a claim. I can't figure out why they're there, and players are finding them annoying. Is there a way to stop them from generating?
EDIT: This might not be the case, but it only seems to be happening when a player abandons a claim.
Another EDIT: I dabbled through the source a bit and found that it's the chunk regeneration. I think it's trying to reset the chunk at sea level, and since that's far in the sky, a flat piece of land is generated over all the chunks the abandoned claim was in.
http://imgur.com/Q99Qldw
-
View User Profile
-
Send Message
Posted May 10, 2015When the plugin shows the player where a claim is with the stick, the middle gold block is offcenter. This isn't a problem with the admin claim visualization though.
-
View User Profile
-
Send Message
Posted May 10, 2015@jenks1999
"world guard it prevents any mobs entering a flagged area" - WorldGuard doesn't do that.