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 Jan 21, 2014So, yeah i have the same claimblock issue everyone else has had.
So far with build #260 doinging /gpreload isnt loosing peoples data, so fingers crossed.
Is there anyway to en-mass check if players have negative claimblocks, and then if so add the number of negative claimblocks to their total count?
This would at least set everyone back to the point where they can at least make a claim.
-
View User Profile
-
Send Message
Posted Jan 21, 2014Chainmail helmet is somehoe binded to the admin tool, This wont cause problems with users getting chainmail helmets in kits will it?
-
View User Profile
-
Send Message
Posted Jan 21, 2014@BC_Programming
So basically around 200 of my players are screwed unless I simply start the plugin over entirely? Rather than "calculating" a claim, wouldn't it make more sense for the plugin to just see that they have a claim, and let it be? Not subtract it? If that's the case does a players total blocks go down if someone transfers a claim over to someone else? They'd have a claim worth X many blocks, would that be subtracted as well? Regardless of all this the little disclaimer at the bottom
won't have the opportunity to check if that actually fixes something or if it manages to make things even worse
makes me quite nervous to try and update and fix this problem less I screw things up further and lose more of my community. Guess I'll make some backups and try it. Here's hoping nothing negative is permanent...
-
View User Profile
-
Send Message
Posted Jan 21, 2014Is there documentation somewhere for how you handle horses? I see in messages.yml there is a "PlayerReceivesHorse" message that seems to indicate the plugin can assign owners to horses?
Are there commands to deal with this? Or is there some other way a horse is assigned as "owned"?
-
View User Profile
-
Send Message
Posted Jan 21, 2014@Turqmelon
Create a Visualization first: (griefprevention.visualization.visualization)
Then apply that visualization using the static method:
re: claim blocks:
Remaining claim blocks are never 'stored' but are calculated based on the sum of the area of all claims owned by a player.
eg. Imagine a normal setup. a player has 1100 claim blocks, and has 700 used in 2 claims of 350. Their 1100 claim blocks are 1000 that they have accrued and another 100 that they were awarded. (via adjustbonusclaimblocks).
Bug is encountered. This causes the data to be reset, So let's say they get reset to 100 claim blocks and no bonus blocks.
This means that they have 100-350-350 claim blocks remaining, making it show as them having -600 remaining claim blocks. This is because claims are (thankfully) not affected by this issue but they are used in calculating the remaining claim blocks for a given player.
I unfortunately don't have the time at the moment to look into it further too extensively. Anyway here is how it's supposed to work by my recollection.
When player data is loaded, it looks for both files. Let's go with a user named UserName. It checks for a file named UserName as well as a file called username. if they are not the same file (which would be true on Windows/non case sensitive File Systems as well as if the user's name is actually lowercase) than it will take the data from the case sensitive version (UserName) and ignore the lowercase name. (username) and then it will delete the case-sensitive version (UserName).
That said I just looked over the relevant location (the getPlayerDataFile method) and it looks like the codepath where it determines both the uppercase and lowercase names exist, it's supposed to copy the 'uppercase' version over the lowercase version and use that (that is, if an uppercase name exists it is used in preference to the lowercase one, which makes sense given that before I addressed this particular issue the lowercased file was always populated with only default settings.). The problem is that copyFile() might not let you copy a file if the target exists (I'm too lazy to verify this tbh) so I changed it to delete the target file first; second, it was also deleting the wrong file. (it was supposed to copy the cased file over the lower-case file, then delete the source (cased) file,but it ended up copying it and them deleting the lower-case file. Since it them returned that filename to be used for reading data, the appropriate routines would find the file didn't exist (since GP had deleted it...) and would act accordingly (eg player had never been online, and all settings return to the default as if they had joined for the first time as a result).
I've hopefully fixed those two particular issues with a quick commit, though I won't have the opportunity to check if that actually fixes something or if it manages to make things even worse. So bear that in mind if testing #260 which makes those changes.
-
View User Profile
-
Send Message
Posted Jan 21, 2014GPTownship
Hey guys I wanted to let you know that I have launched a first version of my plugin GPTownship which builds on top of the existing GP Real Estate.
My plugin extends Real Estate with daily rent collection instead of just a one time fee. And some more options (planned)
Check it out here
- Leo
-
View User Profile
-
Send Message
Posted Jan 21, 2014Is there a way to add a feature to allow people to TP to one of their plots? Other than having multiple /sethome's...
Thx.
-
View User Profile
-
Send Message
Posted Jan 20, 2014Through your API, is it possible to force a claim to visualize itself? My CombatTag plugin hooks in to ensure that a player doesn't run to a PVP-free area, and visualizing the claim automatically when they try to enter it would be awesome.
-
View User Profile
-
Send Message
Posted Jan 20, 2014Running into the same issues as RustyDagger & Smac3223.
From my findings, it appears that only players with upper and lower casing in the player names are having this negative claim block issue. I did find duplicate entries in the player data folder and erased all duplicate entries and restarted. However this did not fix the negative blocks. Maybe this data is also stored elsewhere? I could be way off with this error stemming from case sensitivity, but why else would it only happen to select members?
-
View User Profile
-
Send Message
Posted Jan 20, 2014@Smac3223
Id have to agree with the frustrating part its a wonder all my players have not rage quit.
Iv been thinking of just disabling the accruing of blocks and just starting players out with a nice chunk of claim blocks but i some how think that wont fix this issue.
-
View User Profile
-
Send Message
Posted Jan 20, 2014After following all the advice given so far, it seems my previous claim data was erased.
However...my players are STILL in the negative numbers when it comes to claim blocks.
I've accepted the fact that the "Total" value of blocks is restarting at 100 and I'll just edit that manually. However people can't claim because the "remaining" value is still stuck in the negative values. As it stands this is pretty much how everyone's /claimslist looks
100(+0)=100 (Area:xxxx) World(xx,xx,xx) - continued for however many claims they had Remaining blocks: = Some vast negative number
I myself am -42,506
If I award myself say...42,706
I now have a new total of 42,706 blocks.
If I create a claim that's 12x15=180 blocks, I have 20 claim blocks left over.
However when the server restarts or I use /reload...
The claim states I was last online 365 days ago.
And I'm back to having -42,706 blocks.
Any way to remedy this? Extremely frustrating.
@Alshain01
Is that the latest list of permissions? I've been trying to find an up-to-date version for my mods
EDIT: I tried uninstalling the plugin completely. Installed it again and ONLY copied over the "Claim Data" folder. Same problem. Negative numbers, claims all still there but no one can claim. When looking in the "Claim Data" folder it's just a series of numbered files. Not much I can do with them really
-
View User Profile
-
Send Message
Posted Jan 20, 2014@Eelviny
Quick tip: https://github.com/Tux2/GriefPrevention/blob/master/plugin.yml
However you should be aware that permissions do not necessarily have to be registered in the plugin.yml. In fact they don't have to be registered at all, though it is good practice to use either plugin.yml or register them with the PluginManager object.
-
View User Profile
-
Send Message
Posted Jan 20, 2014@GodsDead
Quick tip: I generally never look through the permissions guide here, it gets outdated with all the new dev builds. If you turn the GriefPrevention.jar into a .zip, then opening the plugin.yml shows up all of the up-to-date permissions. I don't have time to double check the permissions you're using right now, but hopefully this helps ;)
-
View User Profile
-
Send Message
Posted Jan 20, 2014@BC_Programming
Superb, I will try the Egg Fix tonight, for the perm trouble, this is my "admin" config inside my groupmanager, I added all the perm's and so far the only one to actually work was the Lava perm, I also tried adding all inheritance groups just in case GP was relying on a specific perm to use ACB.
-
View User Profile
-
Send Message
Posted Jan 19, 2014thanks for the response, I was thinking what if people use the nether (or twilight forest) to spawn a portal in other peoples claims? it might be possible for the generate process to override claimed area's.
another form of grief/harassment done by players is simply standing there and following them, waiting for them to accidentally drop things or purposely dropping items to flood their inventory.
easiest way around that would be some sort of claim eject command that can eject other players from a claim that doesn't have a mod permission to avoid/ignore that. it can be bad if 10+ people purposely crowd into new players houses and just stand there
Idea's?
-
View User Profile
-
Send Message
Posted Jan 19, 2014@ravand Sry but you clearly don't really realize how stupid minecraft players can really be, your plugin is far from easy and user friendly in the usual minecraft players scale.
The How to claim message is customizable via messages.yml.
You want the people to go and watch your video to figure out how it works
That video was made years ago and not by me. I don't even know how applicable it is today, though most of the underlying stuff is similar. The default is as generic as possible. Administrators can either change the message via messages.yml to be more specific ("use a golden shovel or place a chest to make claims") or something. However because the config could disable the chest claim feature, disable making claims, or use a different claim tool, a simpler message simply cannot be made the default.
but i can tell you from experience that 80+% of the people won't do it
I've never watched the video it links... and somehow I was able to use GriefPrevention. This is because the server I played on had smart administration that had changed the messages to indicate what to do to make a claim. (eg. if a player asks how to make a claim the message stated to use a golden shovel to start claiming).
when (from my experience) most of the players won't even read 1 single sign or chat message on your server.
And admins don't always examine the configuration capabilities of a plugin and assume default messages are hard-coded- such as the aforementioned link.
The only fail proof protection system that doesn't require time to get used to or to understand is a fully automated system that claims a chunk or blocks or an area where you interact with (for example building)
"fail proof" makes no sense in this context. (fool-proof?) GP is not necessary designed to be fool proof. It's designed to be fool resistant. It isn't automatically so, either- it requires competent administration. messages.yml can be changed both for the purposes of showing messages in a different language or for the purpose of making the default messages more specific for that servers configuration- the default, generic claim help message to which you refer being one such example.
that your plugin isn't really much different from other plugins since it's not gonna make it easier for other people.
As I recall GP is the only land protection plugin that displays the border of claimed land, and it does so either by request (to visualize claims), or for various error conditions (such as claim overlap). It has been used successfully by many server administrators and players going back several years, and I was one of the latter and I knew nothing of the plugin and was able to grasp the basics reasonably easily, and I'm no MENSA member.
A suggestion on my side would be to add a feature that automatically extends their region by chunks when they build outside their initial area.
Claim blocks should not be automatically consumed without the explicit action of the user to do so. This "feature" existed in the form of a Pull Request that never materialized before I was ever part of the project. It 'worked' but it was infuriating and had no usability- it automatically expanded claims exactly as suggested here, using up that players claim blocks without consent, and changing the shape of the claim in the process. It made nothing easier, and I never actually issued a PR because after investigation the seeming "simplicity" of such a feature for players was not simple but infuriating. When a player places a block in an unprotected location they are given a message. Adjusting messages.yml can allow the message shown when placing a chest as well as the advertisement shown when a player mentions trying to claim to specifically indicate to use the appropriate claim tool, based on the configuration of the server.
@Smac3223
If you have a backup of that data, restore it. Otherwise it has been probably been lost.
Just to clarify, however:
...Erased when I updated to a newer build that was listed as both successful and stable in hopes of bug fixes.
No build on the CI lists itself as "stable" because any CI-available build has the possibility of these sorts of bugs. If using development builds it is ideal to have a reasonable backup strategy for any server-critical data particularly when switching to builds- and especially when switching to newer builds. Based on what you've posted it sounds like you do have a backup of the playerData. Though previously the files were doubled-up on Linux but with different casing. Either the lower-cased or standard-cased files will have the "real" data for each player (which should be easy to determine by looking at a few) and you can remove the others and it should work from there.
@Purpleantilope
That should work as is. However I would recommend waiting until the next beta release. Most of the major issues seem to be resolved, and most of those having problems are having problems due to the use of interim development builds which had issues.
-
View User Profile
-
Send Message
Posted Jan 19, 2014@BC_Programming
Upon using your latest build using the /claimslist command now shows our claims as intended. Unfortunately our claim blocks are still at 100 since it apparently saved over our original files...
Furthermore while my total blocks are 100(+0)=100? My remaining blocks are in the negatives. As are other users. Not sure what to do about this...
-
View User Profile
-
Send Message
Posted Jan 19, 2014Hello i am currently on greifprevention 7.8-beta-b197 using flatfiles. I am looking to update to 7.8-beta-b213 How do i do so without loosing all there claims? I have a mysql database if that helps just not using it for this plugin yet. Can someone please help me.
-
View User Profile
-
Send Message
Posted Jan 19, 2014Sry but you clearly don't really realize how stupid minecraft players can really be, your plugin is far from easy and user friendly in the usual minecraft players scale. You want the people to go and watch your video to figure out how it works but i can tell you from experience that 80+% of the people won't do it, when (from my experience) most of the players won't even read 1 single sign or chat message on your server. The only fail proof protection system that doesn't require time to get used to or to understand is a fully automated system that claims a chunk or blocks or an area where you interact with (for example building)
Don't get me wrong i don't want to "flame" on your plugin im just standing out the fact, that your plugin isn't really much different from other plugins since it's not gonna make it easier for other people. A suggestion on my side would be to add a feature that automatically extends their region by chunks when they build outside their initial area.
-
View User Profile
-
Send Message
Posted Jan 19, 2014@temporizer
Perhaps a configurable list of blocks that cannot be claimed?
One problem being that this would mean every attempt to make a claim would have to check that the claim area doesn't have any of those blocks.