Yay! Glad to see GriefPrevention here 
1 Like
Add items? Like what? Sorry, I just donāt follow. Are you talking about new items added by mods?
In the config, you have to add specific blocks that you want to protect inside a claim.
Huge relief to see you back, @BigScary! GP was becoming quite a problem child on my server to the extent where I tried to re-write a similar thing myself, although due to various circumstances like hard drive loss and lack of electricity at my house, I think Iāve just about given up developing for the time being. GP was quite a bit more usable and stable before the new developers. No offence to them, assuming they just had a different idea of how it should have been setup.
I hope you donāt get too exhausted working with the Sponge API for a while!
I also wasnāt quite happy with BC_Programmingās changes as well, however I was unable to work on the project during that time. I even thought about pulling his access as he kept adding new features instead of fixing bugs.
2 Likes
Glad to hear Iām not senile. Was starting to wonder if certain issues were specific to my server as it didnāt seem to be getting resolved. @.@
Thatās only necessary for modded servers which add entirely new types of blocks. Even then, GP is smart enough to make intelligent guesses about blocks and entities based on whether they have inventory, are animals or not, etc. The config options are a stopgap for types of blocks that manage to slip through the cracks. Iāll be reassessing that whole feature set after sponge gets up and running.
Very interesting to know, thanks! If your system can do everything WE can do, then I guess thatād be fine too. Just donāt see why we should re-invent the wheel, especially when WE does it so well and has a lot of extra functions such as flags, adding groups as members, parents, etc.
Either way, Iām sure itāll be great.
About reinvention, itās a moot point now because itās already done, but it does carry some value anyway. I started GP because I thought that other anti grief options were not as easy to use as they could be (for players and for admins), and didnāt completely solve all solvable grief problems. On that first point regarding ease of use, one of the big benefits of GP is that itās just one download, and for most servers no editing the config file is needed either. Taking a dependency on WG, which then has a dependency on WE, would mean giving up a lot of that āease of useā for admins, because now itās a 3-download process which adds lots of features that may not be needed. Thatās my major reason for not wanting to heavily hook into WG for sponge (although a light hook would be good for avoiding land protection overlaps between the two plugins).
1 Like
Valid points too, and at the time, there was little else that had protection up to GPās standards. I look forward to future updates! 
I donāt feel GP was trying to do WEās job, personally (assuming ya mean WorldGuard). WorldGuard certainly isnāt as user friendly in comparison (most people just seem to be more familiar with WG), and Iām not even sure how to scale it to fit player purposes. It seems like more of an admin tool in my mind. The only associating of WG and GP Iād like to see is to prevent people claiming inside WG claims they donāt have permissions to modify (soft-dependency of course), but I suppose thatād hold true to other protection plugins as well. I guess GP just seems more geared towards player use, more so than WG. I even tend to use WG on my server along side GP to protect admin structures, but not something players have access to.
On that note, and slightly going off topic, Iād be interesting if Sponge would implement a canBreak() method or variable into the VoxelEvent, which may be able to come in handy for protection plugins to somewhat detect if another plugin is kicking in to protect the block. Not a well fleshed out idea, though.
https://github.com/Nentify/Protect
I was working on this before @bigscary returned, which functions very similar to GP but uses the WorldGuard 6 API to save me having to create my own extensive protection system. It worked better than I expected during the creation, but itās far from complete. Either way, GPās systems have been very good in comparison as well.
A better example is the ProtectionStones plugin amongst others.
Just realized that the one I was writing has completely disappeared D: It would seem I never committed it to GitHub, and after I lost my last few hard drives, itās gone forevrawr >.< That was coming along quite nicely for a while as well.
Knowing how hard it is for plugins to track mods, would it be easier to make a mod that can help gp protect mod blocks?
What I didnāt like about the chat features are as follows:
All of them.
I completely disable the chat features on my servers (and have since their inception), as I use GP to replace lokette/protect claims and thats it. While I understand it is the āultimate grief prevention pluginā and supposed to stop ALL kinds of āgriefā, getting into chat was just starting to go to far. Most chat plugins are small, and relatively simple to use for the same functionality, or you can even break it into modules like other plugins. Iāve been with GP from early the start (you may or may not remember some of our early conversations from way back when, on either my Maruchan or mrcheesete0 account idr what i used on dbo. I also agree with the streamlining of the configs, it used to be much simpler to configure your plugin and I LOVED it. That was when I hosted servers nearly three years ago. Now, while I use your plugin and have it installed, I have been absolutely DREADING the customization of it to my specific needs, due to wading through the configs to reconfigure it all. And in the mean time because I keep putting it off, my users keep asking me why they canāt trade with these villagers they ran into while exploring, or why they canāt place water for whatever legitimate purpose they had, and I tell them itās because Iāve been too busy to configure GP properly.
I loved GP back in the day, and I will probably always use it, but Iāve been hesitant with the newer features.
Maybe in your streamlined config, divide the plugin into sub-sections where you can completely enable/disable each section of the plugin with a single on/off, then ballooned under that the actual configs for it if you want it on, so you can easily pick and chose which forms of āprotectionā you want to use. On a whitelisted server for a private community that is nearly free of requiring moderators, a lot of the plugin becomes bloat, while some of it still being necessary.
Rather than forcing no overlap, maybe make it give a warning of the overlap and ask for comfirmation? I specifically deliberately use WG regions and GP regions concurrently.
I think it should depend on whether the claim creator has permission to modify the WG claim. Most people Iāve seen ask for this feature want it to prevent users from placing claims they canāt use in WG regions. But if that can be done, then perhaps a confirmation would be nice, although I canāt think of a reason off the top of my head why itās necessary. It would seem that if you had a WG and GP claim overlap, youād want GPās protection, but I think WG can handle most of that as well in one of their claims.
And about chat features, I didnāt care for them much either at some point. I did use them for a while, but at some point, just seemed to ignore permissions and started forcing lower case for everyone and blocking links posted by mods, admins, etc, so was eventually forced to disable them entirely. I think Iād use them again if they worked correctly, but itās not a priority for me. Although I suppose blocking links was a bit useless. If it detects a URL, Iād think itād remove it or obfuscate it, but instead just remove dots, which doesnāt fool anyone.
I thought that was essentials
Iām not sure if Essentials moderates chat like that. Iām not familiar with the extended functionality of the Ess Chat plugin, but I always figured it was geared towards parsing ā&ā color codes and displaying nicknames and such. I was always under the impression that GriefPreventionās chat features were blocking cap-rage and links. As far as I can recall, disabling those seemed to fix it.