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 Oct 2, 2014@McLive0
Please share your complete report, and not as an image (so I can expand and see the other details, as well as what other plugins are doing). Also make sure you're measuring at least a complete 24 hour period.
Will need more information about this broken pipe thing too. More logs?
Will check on the offlineplayer() thing. Really wish Bukkit guys hadn't made those calls blocking.
-
View User Profile
-
Send Message
Posted Oct 2, 2014Finally converted everything but you should change this: http://hastebin.com/abajucetow.sm
EDIT: The new version is laggy. http://img.mclive.eu/20141002173013.png + http://img.mclive.eu/20141002183340.png
EDIT2: Sometimes, it just kicks everyone of the server. "java.io.IOException: Broken pipe" Started happening after updating to the latest version.
-
View User Profile
-
Send Message
Posted Oct 2, 2014@Bobcat00
bobcat00 ...bobcat00.. somehow that name sounds familiar to me (kaise?).
@dutchrastacraft
Does that test server have regular visit(or)s? =P
-
View User Profile
-
Send Message
Posted Oct 2, 2014@dutchrastacraft
ouch. It's still running. Will stop it in 1 hour.
-
View User Profile
-
Send Message
Posted Oct 2, 2014@McLive0
I've ran it for 3 days then realised there were too many players and ran a query on my database to remove the inactive ones. Then I ran the converter again for 2 days :)
-
View User Profile
-
Send Message
Posted Oct 2, 2014Currently updating to 8.1.7 UUID convert is already running for 90 minutes O_o
-
View User Profile
-
Send Message
Posted Oct 1, 2014@bigscary
I actually don't. But I can provide you a testserver?
-
View User Profile
-
Send Message
Posted Oct 1, 20148.1.7 Update
-
View User Profile
-
Send Message
Posted Oct 1, 2014@dutchrastacraft
Well, I'm jealous. We've had a survival server since March 2013, and we get a max of 8 players on at once. Most of the time, it's 0.
-
View User Profile
-
Send Message
Posted Oct 1, 2014@dutchrastacraft
Any tips for server advertisement? I'm struggling to get players for my test server.
-
View User Profile
-
Send Message
Posted Oct 1, 2014@bigscary
I will provide you with a full 24hour + report.
The problem is I have a pretty big server, with tons of claims and tons of players. Over 110k players have joined my survival server only since april 2014... (based on essentials stats that were reset 1st of april) I have no idea where the pistons would be and it would be impossible to remove them or find them :/
-
View User Profile
-
Send Message
Posted Oct 1, 2014@dutchrastacraft
Oh, I read misread your comment. That's an incredible improvement, I doubt I can attribute that to my recent minor changes - maybe something BC did in the beta versions killed the boot perf.
Will definitely do something to address piston tracking expense this week. Thanks for the timings, I will look at them closely, but will you please provide me a report for a full 24-hour period? Both of these are for less than one hour, so they're not a fair assessment of GP's overall impact to your server.
EDIT: Seriously, somebody's doing a bad thing with pistons. Try asking your players if anybody knows anything about a really big piston contraption. I will still take action to streamline GP's handling of pistons, but I don't think efficient code can completely solve a problem of this magnitude. Definitely some investigation on your part is warranted. If you find such a contraption, make sure it's inside a land claim. If it is (or if claiming the area around the thing doesn't solve your lag problem), then you may have to disable it to solve the problem. If it's not claimed, try claiming the area as admin and not giving anybody build permission. Then the builder might give himself away by asking why he can't change his build.
-
View User Profile
-
Send Message
Posted Oct 1, 2014@bigscary
Yes, they can still build in them. Offline AND online players. Just the claimblocks and bonusclaimblocks are not converted correctly.
Also the startup went from 45 to 2 minutes, that's 77,5% improvement! Not 20% :D
EDIT: First timings report (20 players online only): http://timings.aikar.co/?url=8474457
EDIT 2: More urgent! Continuous lagg and laggspikes leads into this second timings report (after a /timings reset) http://timings.aikar.co/?url=8474550
Information related to the timings report: Spigot version: 1627 Griefprevention version: 8.1.6
PistonExtend and Retract :/
-
View User Profile
-
Send Message
Posted Oct 1, 20148.1.6 Updates
@dutchrastacraft
20% improvement is pretty huge, that's good news. I still have another optimization in mind for DB mode, will try to get it in this week.
Did you confirm that players still have access to their land claims after the boot? Meaning they can still build in them, etc?
@jahangir13
I'm confused, now. Are you the GPDynmap dev or no? If not, please check with that project owner - changing the base plugin to make an extension work is backward.
-
View User Profile
-
Send Message
Posted Oct 1, 2014@bigscary
Convertion completed. I've found one problem: - Claimblocks aren't being converted to the new format. All players start with 100 accrued blocks. No problem tho since I ran another query to make sure everyone has 10k now.
I updated to the latest 8.1.6 and I've had these messages on griefprevention boot. (So 2 minutes startup, which is 43 minutes faster than the beta builds.)
[20:00:08] [Server thread/INFO]: [GriefPrevention] Enabling GriefPrevention v8.1.6 [20:00:08] [Server thread/INFO]: GriefPrevention: Grief Prevention boot start. [20:00:08] [Server thread/INFO]: GriefPrevention: Finished loading configuration. [20:02:37] [Server thread/INFO]: GriefPrevention: 15270 total claims loaded. [20:02:38] [Server thread/INFO]: GriefPrevention: Customizable messages loaded. [20:02:38] [Server thread/INFO]: GriefPrevention: Finished loading data (Database Mode). [20:02:38] [Server thread/INFO]: GriefPrevention: Boot finished.
-
View User Profile
-
Send Message
Posted Oct 1, 2014@jahangir13
If you look here on my dynmap:
http://crafttekk.de/dynmap/
This is GP 7.6.2 on Tekkit Lite. In the middle of the map (the big Admin claim) there are several subclaims (created by a Moderator - normal user. So these show up red (as intended, I guess).
In the new GP versions a normal big user claims shows up red...but any subclaim I create inside this claim shows up blue (as an Admin claim).
-
View User Profile
-
Send Message
Posted Oct 1, 2014@jahangir13
It could be that BC put that in, and I rolled back that change with the bugs. For now, adjust to "if has parent, call parent.isadminclaim()". I'll try to remember to check on that code for the next version.
-
View User Profile
-
Send Message
Posted Oct 1, 2014@bigscary
Hi bigscary: maybe. But in previous versions it was always possible with claim.isadminClaim() to see if it's an admin claim. In these version I tried now (> 8) for an subclaim of a normal player on a normal user claim the function returns that it is an admin claim. That's what I am wondering. If I am the only one who has this issue then the problem may be on my side.
-
View User Profile
-
Send Message
Posted Oct 1, 2014@TJW28
Maybe Jenkins is busted - I'll ask Tux to have a look. Grab the latest file from the BukkitDev files. Yes, I think you're right about what's in those builds.
-
View User Profile
-
Send Message
Posted Sep 30, 2014@bigscary
I see the latest builds on jenkins appear to be without the UUID conversion, and the version in-game reports as 8.0.3.
Am I right in assuming these updates are with latest fixes, but not including the UUID migration?