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 Aug 28, 2013By any chance does #163 have something to do with these two BS (backspace) ASCII characters appearing in everybody's chat randomly? Started happening when I updated my plugins which is why I think it may be GP.
Ingame: http://i.imgur.com/x266MGb.png
Log: http://i.imgur.com/sZwzASZ.png
-
View User Profile
-
Send Message
Posted Aug 27, 2013@deleted_9935739
Thanks! The first looks like a general error that would occur anytime the command is used outside a claim. Will have to look into the latter.
EDIT: #164 should fix these two issues
-
View User Profile
-
Send Message
Posted Aug 27, 2013@erik1988
That would allow it. Your confusion makes sense though. "BlockDamageTNTExplosions" doesn't 'block' anything, but rather it refers to the damage to blocks resulting from those explosions. (Explosions have two rules: one that controls whether the explosion can occur, and one that controls whether the explosion can damage a block).
-
View User Profile
-
Send Message
Posted Aug 27, 2013Using build #163, someone tried doing /giveclaim even though they have no permission and caused this http://pastebin.com/bjjaJEs2
This also appears randomly http://pastebin.com/2VREURjU
-
View User Profile
-
Send Message
Posted Aug 27, 2013Are the dev builds on GitHub stable enough to use on a live server? I'm having trouble with Mystcraft worlds not being detected, and it seems to be fixed in the later GP code. (I'm currently running GP 7.7 and MCPC+ Legacy with FTB Unleashed)
Thank you for your time =)
-
View User Profile
-
Send Message
Posted Aug 27, 2013Just a question, Does allow means that tnt is blocked or allowed in this setting? So If I want people to use tnt to damage blocks this should be deny?
BlockDamageTNTExplosions: Wilderness: AboveSeaLevel: Allow BelowSeaLevel: Allow SeaLevel: '-1'
-
View User Profile
-
Send Message
Posted Aug 26, 2013@BC_Programming
Okay so locking claims is the solution usint /lockclaim thank you very much. :)
-
View User Profile
-
Send Message
Posted Aug 26, 2013@ThisUsernameIsMine
FWIW almost all the existing Permission nodes were refactored a few builds ago to make them (ideally) easier to assign and manage, by putting them in a proper tree. All Commands require griefprevention.commands.<commandname> where <commandname> is the command name, but some require additional permissions. Some of these map to older permission nodes whereas some do not. here are all the permission nodes currently in use:
griefprevention.admin.claims
griefprevention.admin.eavesdrop
griefprevention.admin.lock
griefprevention.admin.reload
griefprevention.claimblocks.buy
griefprevention.claimblocks.sell
griefprevention.claims.allow
griefprevention.claims.ignorelimit
griefprevention.claims.give
griefprevention.claims.create
griefprevention.claims.delete
griefprevention.claims.ignore
griefprevention.claims.investigatearea
griefprevention.claims.lock
griefprevention.claims.transfer
griefprevention.placement.lava
griefprevention.placement.water
griefprevention.eavesdrop.standard
griefprevention.spam.login
griefprevention.spam.chat
Note that most of the documentation is out-dated and I honestly have no idea what needs to be edited. Some pages are so old they weren't even relevant when I became a maintainer on the project, even. At the very least the "7,8 Configuration" page is probably the closest to being relevant to current development builds.
the plugin.yml requires "griefprevention.commands.giveclaim" permission. This will be checked by bukkit.
the actual logic for giveclaim will check for this permission again. If it fails, it will abort. This won't show a message in the console at all.
Then, if the player in question doesn't have either griefprevention.claims.give or griefprevention.admin.claims. Though it looks like this test might be inverting a condition, which might be the cause of the issue. I've made that tweak (removed the inversion) so hopefully that will resolve your problem for the next dev build.
@Awsmpossum1313
/lockclaim locks claims. Admin claims are never cleaned up. It looks like somewhere/somehow your claims were changed from being admin claims to being player claims belonging to a non-existent "an administrator" player
Confirmed: I've changed the visualization code (probably useful to begin with actually) to show Emerald blocks instead of gold blocks when visualizing the border of admin claims. When I reload my test server an administrator claim becomes a "player" claim. If I had claim cleanup on, since there is no player called "an administrator" it would automatically say they were last on a year ago and cleanup that claim.
-
View User Profile
-
Send Message
Posted Aug 26, 2013Admin claims being purged at reboot.
Every admin claim is being purged at reboot regardless if i create it 1 hour or 24 hours earlier. This is the error i get in the log file:
All of an administrator's claims have expired. Removing all but the locked claims.
I can not find anywhere to actually LOCK claims. I suspect that its doing the purge because when i right click with a stick it says that the last logon for that player (me) was 365 days ago. This has become a huge source of frustration.
I have the chest claim to 7 day reclaim and the others to 45 days. Thanks in advance for the help!! :)
-
View User Profile
-
Send Message
Posted Aug 26, 2013@BC_Programming
I know u've said it before, but my transferclaim node was wrong so that's my sloppy mistake... :S
I think i'll leave it to this as i'm afraid to be confronted with more stupid mistakes for not getting /giveclaim to work.. =P
griefprevention.adjustclaimblocks
griefprevention.admin.adminclaims
griefprevention.admin.claims
griefprevention.adminclaims
griefprevention.claims
griefprevention.claims.give (old /giveclaim node?)
griefprevention.claims.ignore
griefprevention.claims.transfer
griefprevention.commands.adminclaims
griefprevention.commands.giveclaim (new /giveclaim node but doesn't do anything for me)
griefprevention.commands.ignoreclaims
griefprevention.commands.transferclaim
griefprevention.createclaims
griefprevention.deleteclaims
griefprevention.giveclaim
griefprevention.ignoreclaims
griefprevention.nopvpimmunity
griefprevention.pvp.noimmunity
griefprevention.transferclaims
Thanks for everything btw! :) +1
-
View User Profile
-
Send Message
Posted Aug 26, 2013@BC_Programming
Thank you for the disable fix! Another issue with the block break call is, a player can place blocks in a normal world where GriefPrevention is setup, but once a player goes to break the block, it says they must be in a claimed area to do so.
Also, when the player places a chest for their initial claim, (I'm not sure if this is intentional), when the player goes to abandon the claim, and then place another chest, the plugin won't give them their initial starting claim.
If there's a proper bug tracker for the dev builds please link it, as I couldn't find it in the Jenkins page.
Thanks for the quick responses!
-
View User Profile
-
Send Message
Posted Aug 25, 2013@BC_Programming
After I installed the Dev build (#161), I set 'GriefPrevention.Claims.Enabled' to 'false', and the plugin won't allow me to break anything in the world, but I can build anywhere.
-
View User Profile
-
Send Message
Posted Aug 25, 2013@BC_Programming
Fantastic thank you. Working like a champ now.
-
View User Profile
-
Send Message
Posted Aug 25, 2013@ThisUsernameIsMine
Ahh here's the thing... Every command has the perm of GriefPrevention.Commands.<permname> now. Some of the older perms were removed or moved here.
So /GiveClaim and /TransferClaim will need GriefPrevention.Commands.GiveClaim and GriefPrevention.Commands.TransferClaim permissions respectively.
TransferClaim also requires "griefprevention.admin.claims".
@Awsmpossum1313
http://dev.bukkit.org/bukkit-plugins/grief-prevention/pages/7-8-and-later-grief-prevention-configuration/
It looks like it's missing that node though, but you are looking for GriefPrevention.Claims.Enabled within the World config.
-
View User Profile
-
Send Message
Posted Aug 25, 2013I am trying to disable grief prevention on some worlds. The documentation here says to use the claim.worlds node however that node is not existent in my config.yml file which was built from scratch on build 158.
I have tried to add it into claims directly in my config.yml
Claims:
Worlds:
- world
MaxAccruedBlocks: 2500
AutoSubClaimsSwitch: false
DeleteWithUnrecognizedOwner: false
InitialBlocks: 100
However it gets stripped from the code. How do i disable grief prevention on some worlds?
-
View User Profile
-
Send Message
Posted Aug 25, 2013@BC_Programming
Yes that node is in my perm plugin's groups.yml.
It also seems build 168 of GP has changed (solved) the adminclaims / ignoreclaims problem i was having i.e. we can use those commands again without needing Op ;-)
Still having permission problems with /transferclaim, and /giveclaim simply outputs /GiveClaim <TargetPlayer> when choosing the name of an existing/online player :-/
Below are all the GP nodes i could find in my perm plugin's groups.yml:
griefprevention.adjustclaimblocks
griefprevention.admin.adminclaims
griefprevention.adminclaims
griefprevention.claims
griefprevention.claims.give
griefprevention.claims.ignore
griefprevention.claims.transfer
griefprevention.commands.adminclaims
griefprevention.commands.ignoreclaims
griefprevention.commands.transferclaim
griefprevention.createclaims
griefprevention.deleteclaims
griefprevention.giveclaim
griefprevention.ignoreclaims
griefprevention.nopvpimmunity
griefprevention.pvp.noimmunity
griefprevention.transferclaims
Also, are GP nodes case-sensitive?
-
View User Profile
-
Send Message
Posted Aug 25, 2013@BC_Programming
i loaded it up and tested it out and it works find now with no explosions. it just doesn't do anything when touching a block inside the claim when placed right outside of it. Thanks!
-
View User Profile
-
Send Message
Posted Aug 25, 2013I was wondering how I can make myself (the admin) be able to place and break blocks anywhere, without creating claims. Is there a permission for this? Sorry if it's in the documentation, TL;DR. :p
-
View User Profile
-
Send Message
Posted Aug 25, 2013@Sparcticus
It should be on jenkins now... let me check... yep.
It includes a Pull Request from Di3mex, which I've not tested after merging, but shouldn't cause any problems.
-
View User Profile
-
Send Message
Posted Aug 25, 2013@BC_Programming
Thanks for looking into this and addressing it! When will the dev build be available for download from your jenkins page?