DeGriefer
This plugin is designed to prevent on-the-spot griefing. It works by protecting each block on placement. No messy setting points, protecting more area then required, and no heading into the middle of nowhere to protect some random player's house! This means you can have players running around your server building things without worry of griefers destroying their stuff as they build it.
The plugin has three ListModes. The first is simply "None", which means any player who builds has their blocks protected and other players are unable to destroy them with the exception being OPs (configurable in the perms). Setting the ListMode to "None" or anything besides "WhiteList" or "BlackList" will put it in "None" mode. When a player destroys their own block, anyone can build there and once someone does, the block is protected under that new player.
The second ListMode is "BlackList". This allows OPs to add or remove players from a list. Under BlackList, the player is allowed to build freely and such but their blocks are not protected. You can also add a player to the list to deprotect their blocks. However if they're added to the BlackList and the removed from it, any remaining blocks belonging to the player are re-protected.
The third ListMode is WhiteList. This mode turns off protection for everyone (even OPs) unless they're on the WhiteList. Adding a player to this list will protect their blocks as they build and only they or an OP will be able to destroy their blocks. Removing a player from the WhiteList will unprotect their blocks, but if you add them to it again, any remaining blocks placed by them will become protected once again.
The reason re-adding someone to the WhiteList, or re-removing them from the BlackList protects their blocks once again is because this plugin handles protection on a per-block basis, and I'm unable to remove all protections for them without burning through a ton of system resources.
http://forums.bukkit.org/threads/sec-degriefer-protection-as-you-build-1-0-1-r3.58753 Forum Thread
please i need that plugin very much :( update to MC 1.2.3 :)
1.2.3 please?
Ive also noticed that this plugin is causing excessive amounts of cpu usage on placing and breaking of blocks. Unfortunately im going to have to stop using this.
Im starting to think that i just used a protection system that is going to be forgotten about and then all my players things will be in limbo. If you are not going to continue updating and working on this please let us know now.
Can you make this simpler? Just auto protect th# # e blocks placed. And a option to place unprotected blocks like:
Also my players are having some glitches where after they place something they cant break it and also that when they break something they cant place anything in that spot.
Hello i love the simplicity of this plugin. Im just wondering when we will see the next update. My players would love to add ppl to a friends list or such. Thanks.
[Server] INFO java.lang.UnsupportedClassVersionError: me/Prometheus/DeGriefer/DeGriefer : Unsupported major.minor version 51.0 13.02 20:12:25 [Server] SEVERE Could not load 'plugins/DeGriefer.jar' in folder 'plugins':
Thats brill thanks, Last two questions that I forgot. If I was to copy and paste a building that I created block by block would it protect the pasted version too?
Also does it work in creative mode?
Many thanks for your help
@drob2897
1. Only players who are on the whitelist will be protected.
2. When the plugin is enabled (and if whitelist is on and the player is on the whitelist), any blocks they place will be protected as long as you don't /purge that player (coming in latest build), turn the plugin off, or remove them from the whitelist. Any previously placed blocks are not protected as there's no way to track who places a block unless the plugin is running.
3. Yeah, imo this plugin works best with a large-area protector.
With the Whitelist, Will it mean that all my players blocks are not protected unless they are on that list? I plan on this plugin being used for donators you see.
Also when I add them for the first time will all there currently placed blocks be protected or just new blocks that they place?
Can I still use world guard on the protected blocks? Or will this cuase issues?
Many Thanks :D
@nebenezer
Yep I read all that. You're right, I missed the answer to my question about friends building together - it works as long as they're both online at the same time and communicating about which blocks should be built or broken. Sounds like a serious communication overhead.
Agreed its not a complete solution, that was the point I was trying to make. Why spend time making an incomplete solution that taxes admins when there are many more complete solutions which don't require you to manage a team of admins?
Big scary, did you read R3AP3ROFTH3SCYTH3's post? He hasn't edited it and answered a few of your questions already :/
I think it's a novel idea and could find a niche. It's not a complete solution, I don't think it's intended to be. I can see this being a nice reward for players who have already built some cool stuff. Also we have a member who is building a Nether Transportation System, this might be perfect for him to build the portals and stations and paths...
Seems like too much effort for admins - trying to figure out who should be on what list, then monitoring those players to see if you need to move them to a different mode.
If you start all new players in "no protection" mode by default, then you have to be around all the time watching players to put them on the whitelist once they start building, otherwise they'll be vulnerable to grief.
On the other hand, if you start everybody on the "protection" list, then some of those will be griefers, and they'll put blocks in places just to grief other players (around the spawn, on top of other players' chests, in front of other players' doors). Because those blocks would be protected, again the admin has to get involved to undo the damage, and in the meantime, players just have to live with the problem.
You could always recruit some volunteers to help with administration so you can have somebody online all the time, but how do you know who to trust?
Also does this require database? If yes, that's a config headache. If no, are you sure it scales up to large servers? Tracking every placed block is a big deal.
Also are you doing anything to stop spammers, tree toppers, fire starters, lava dumpers? Thieves? Creeper baiters and TNT? Crop trampling, farm animal killing, theft from chest carts and furnace carts?
Can players allow their friends to edit their blocks?
@nebenezer
If you enable whitelist then you can just add players to the white list so their blocks will be protected. Any griefers building around a house won't have their blocks protected and can just be destroyed. A friend could freely build within an area however the original builder within that area couldn't destroy his blocks. The original idea I had in mind when making this was for each player to have his own protection while OPs can handle the issues. OPs should be able to handle everything just fine, as long as one of the list modes has been enabled by the server admin. In its current state, the plugin doesn't support more then one person being able to destroy a block a person placed, but I'll see what I can do. The entire storage method I'm using will get phased out for a database.
Very interesting concept.
I agree that you need to work on the post but who am I to talk? I haven't even posted my servers IP on my own website yet :P
I am desperate for a player administrated protection solution. I may give this a try but I am very curious if it is configurable. If there are no limits or restrictions I could see this getting out of hand and in some cases being used as a tool for greifers, locking someone out of their house for example.
Another thought... I know many of my players would want to add their friends to their protected areas.
Sounds awesome, I loved the per player block protection, 'bananaprotect'...all the best servers had it.
"Sounds like an old plugin that was discontinued. Please make this a little bit more organized and add something like a change-log. It's juts one big description."
yup, I'll try it later
Sounds like an old plugin that was discontinued. Please make this a little bit more organized and add something like a change-log. It's juts one big description.