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 Mar 8, 2015I understand why its a good thing, but i run a shop, it has public accesstrust therfore anyone can enter my shop, siege someone and burn down everything i own, this has happened now,on a few occsasaion to players meaning they have left. we installed grief prevention to the server without this as a feature, i understand your chage but it should be toggleable, you have changed the entire way our server now runs and quite honestly its ruined a large portion of gameplay.
-
View User Profile
-
Send Message
Posted Mar 8, 2015We are really thankful for adding the claims mode "SurvivalRequiringClaims", but for some reason only operators get the "NoBuildOutsideClaims"-Message when trying to build or break in a not protected area.
Do you know the reason of this problem?
-
View User Profile
-
Send Message
Posted Mar 8, 2015@bigscary
I removed index's (there were two!) using heidisql, do I need either of them?
Was what was performed
-
View User Profile
-
Send Message
Posted Mar 7, 2015@Ragnorok98
For me WorldGuard is an essential plugin that I start out with.
-
View User Profile
-
Send Message
Posted Mar 7, 2015@PrimerBlock
I do not know if I should install, another plugin, as my server is running about 1GB and I have 17 pl's running already: Playerheads, adminfun, keepitems, signurls, anticheatplus, essentials, perms. bukkit, essentialschat, clear lag, marriag master, tree assist, lavafurnace, lottery, lockette, essentialsspawn, multiverse core, and grief prevention, currently running spigot 1.8 with 4 worlds, I do not know how much more my server can take.
-
View User Profile
-
Send Message
Posted Mar 7, 2015@Ragnorok98
Worldguard would do that.
-
View User Profile
-
Send Message
Posted Mar 7, 2015I'm getting some wrong UUIDs during the conversion process. Specifically during "Checking local server data for UUIDs already seen..." It is not all the UUIDs just some of them.
For example the conversion process sees for my account: [15:30:06] [Server thread/INFO]: GriefPrevention: PrimerBlock
> 6212af16-b2a8-358a-bb2c-b799f6224fc5When it should be "074730db-6498-426a-bbe3-cf6f028e1519"
Also checked the ClaimData directory and saw the wrong UUID is being used for the Claims too.
Does anyone know where GriefPrevention is picking up this local data? I would be will to just clear it out and let the conversion process take longer.
-
View User Profile
-
Send Message
Posted Mar 7, 2015also, is it possible to have pvp turned off on the server but have grief prevention area's still be pvp enable (if not, it would be a cool thing to add)
-
View User Profile
-
Send Message
Posted Mar 7, 2015is there a way to stop mobs from spawning in claims (1.8)
-
View User Profile
-
Send Message
Posted Mar 7, 2015@maclarenss
You can get that from the separate GriefPrevention flags plugin. I don't add anything to this base plugin that isn't important for anti-grief.
@Oneyedrooster
You have to update your server. You're running an old version of 1.8 that has a grief exploit.
@iamthereaper89
The point of /siege is to ensure players can't abuse land claims to hide from PvP, especially considering grief cases where a player builds something impenetrable like a tower, then fires arrows at his neighbors knowing that they can't do anything to him. If a player has any level of trust (even /accesstrust) in a land claim, he can potentially use the land claim as shelter from PvP (consider for example iron doors with buttons), so it's only fair that he can be /sieged there, even if it's not his land claim. If a player owns a land claim and doesn't want others taking shelter, then he must limit who he gives /accesstrust and other permissions to.
If this rule were not in place, two friendly players could simply "swap" land claims, where each builds in the other's claim, and then they would be invincible to /siege. This rule prevents that exploit.
@GodsDead
Please remove that key. Current versions of GP do not have any keys, and there definitely shouldn't be a key on that column because it's normal for all subclaims to have ID = -1.
@Gullum02
Were you standing inside the admin claim when you used the command? If not, you would have set all your personal land claims to allow all players container access. Also if you were standing in a subdivision of that land claim, your change would have only applied to that subdivision. Stand inside the land claim and use /trustlist to see who actually has permission there - you want to see "public" under the containers section of the output. If you have a look are you're still stumped, please share your /trustlist output with me.
-
View User Profile
-
Send Message
Posted Mar 6, 2015Is anyone else having trouble on Spigot 1.8 running griefprevention with /CT ALL on /adminclaims? It reports that I have opened the chests to the public, but absolutely no one but me can use them on the claim. Suggestions?
-
View User Profile
-
Send Message
Posted Mar 6, 2015Hi, Im also from Piratecraft, and having a seperate issue to that of @Godsdead,
We are having many complaints/threasts of leaving becuase of players being sieged in land that they are only trusted in, and do not own.
I have other players with subclaims with trust on an island of mine, unfortunately the reason they are claimed by me is to keep them safe from siege as i do not frequent the area, now that this is happening, my build are being destroyed when im not even online just because a friend with trsut is in the area.
this is happening to a number of players and it causing alot of issues
Can this be looked into, im sure it used to be Siegedefendable:requiredowner surely that means you can only siege an owner not a trustee?
Thanks Jon
-
View User Profile
-
Send Message
Posted Mar 6, 2015That's what I've written below. Delete the primary key index. In the SELECT statement which reads all the claims at once (with select * from claims_table) there is no where-clause. And without a where clause with at least the primary key columns or using SELECT * the primary key is not used anyways.
A primary key just speeds up searching/selecting specific rows as defined via the key fields in the where clause using an separate index table which just holds all the key columns.
Here without a where clause a full table scan is done, reading everything.
( If you really want to have a primary key, then add a new column to the table, set it to integer/auto-increment and tell the column that it's the new primary key. For every new data set inserted the db fills this field with a new value automatically (+1 from the last one)...I mean, if you then feel a bit better ,)) Or in case mysql does not allow a table without any key. Maybe that has been changed. )
-
View User Profile
-
Send Message
Posted Mar 6, 2015@bigscary
I removed the -1 row, Created a claim and it worked, but then the next person to create a sub-claim it fails because when the new claim was created it created the ID -1, Like I said you cant have a Primary Key with 2 of the same ID's! Subclaims will need their own unique ID to not conflict.
-
View User Profile
-
Send Message
Posted Mar 5, 2015add pls flag in griefpr. /spawnmob off/on pvp off/on in private claim
-
View User Profile
-
Send Message
Posted Mar 5, 2015I guess that will not help...as the next subclaim will also be stored with id -1 if I see that correctly.
I did not see in your create table statements that a primary key is declared:
CREATE TABLE IF NOT EXISTS griefprevention_claimdata (id INT(15), owner VARCHAR(50), lessercorner VARCHAR(100), greatercorner VARCHAR(100), builders VARCHAR(1000), containers VARCHAR(1000), accessors VARCHAR(1000), managers VARCHAR(1000), parentid INT(15));
So the question is where the primary key definition comes from in GodsDead's table (as you said maybe from a beta version). Technically it's possible to declare a table in mysql without primary key.
When you insert:
"INSERT INTO griefprevention_claimdata (id, owner, lessercorner, greatercorner, builders, containers, accessors, managers, parentid) VALUES(" +
id + ", '" +
owner + "', '" +
...and it's a subclaim it will produce the duplicate key error again (not for the first but the second subclaim).
@GodsDead: delete the primary key from the griefprevention_claimdata table structure definition in whatever tool you use and try again.
I think it should not matter what subclaim it is. With the SELECT * from this table all rows are taken and it should not matter in which order or if the entry is uniquely selectable.
-
View User Profile
-
Send Message
Posted Mar 5, 2015@GodsDead
Can you remove that key from your table? It might have been added by one of the beta versions. I don't have any keys set on any of the tables GP creates currently. It's normal for subdivisions to have -1 as their claim ID.
@Luficer
Right, potion damage is prevented. I'll double-check on the creeper damage.
-
View User Profile
-
Send Message
Posted Mar 4, 2015@bigscary
Under those circumstances, potentially not Zombies, although Creepers are probably still a liable way to damage them, even if they're completely concealed. And I'm assuming by now potion damage is prevented.
-
View User Profile
-
Send Message
Posted Mar 4, 2015I figured out the Sub-Claims not saving, I think this is only relevant to mysql saved claims, this is actually an issue I brought up when I was stuck converting from 7.8! Looking at the console when someone makes a subclaim:
-
View User Profile
-
Send Message
Posted Mar 4, 201511.0.1 Updates
Please take a few moments to vote for Grief Prevention. :) Thanks for your support! http://www.spigotmc.org/resources/griefprevention.1884/
@Phreag
Fixed. Sorry, stupid mistake on my part. :(
@Luficer
Maybe I'll add it to the config - can you describe a situation where a player without any permissions in a land claim could allow zombies to attack villagers when otherwise the zombies couldn't reach them?