Fixed creative world rules. Thanks

Can I disable this error: Unable to restore, player is in chunk.

Is this necessary? It just seems to hamper the efforts of the mods.

@bigscary

Hell, maybe I can whip up something with GP flags and the permission group assign plugin. Although looking through your API sheet, I didn't see exactly what I needed scanning through. Is there a more complete javadoc/API reference anywhere?

If you love this plugin, please go to your favorite server administration forums and spread the word! Too many server owners are still doing anti grief the hard way, like using an incomplete anti grief plugin or worse... having volunteers answer help requests all day and night to roll back griefs.

@Eyeball114

What do you mean 3.1.2? Did you mean 1.3.1? Anyway unless you configured the database options, wiping all GriefPrevention data is as simple as stopping your server, deleting the .jar file, and then deleting the GriefPreventionData folder. When you restart the server, GP will be gone (or if you've replaced the .jar file, it will re-create the data folder with fresh data, like a new config file).

@Impiryo

It's my impression that many players leave carts on tracks so other players can use the carts, whether for travel or for a roller coaster. Getting into and out of a cart doesn't require any permissions, but if your track has a "stopping point" which is activated by a button or lever, then the track owner can use /accesstrust public to allow everyone to use buttons and levers without allowing them to place/break minecarts, access storage minecarts, or change the track.

I think protecting empty minecarts is important. They do take 5 iron to build, and I promise that if you let players steal each others' minecarts, many players would complain that they keep building minecarts, and they keep disappearing. Griefers would "teehee" all over the place.

Those are protected by default to encourage players to get their own (especially the enchanting tables). A table owner can use /containertrust public if he really wants to share with everyone. If he only wants to share the table and none of the other containers, he has the option to either move the table to a separate claim, or create a subdivision around it and containertrust the public only in that subdivision.

@thecanadiansandbox

I would think that it's possible to fix whatever the problem is with that other plugin. But it's not mine to fix - Mikeprimm owns it. If it seems broken, consider contacting him. You can tell him that I will be happy to help him troubleshoot the root cause.

@Peregrin5

I decided to, instead of making that rather complex code change, simply notify players when they're building something which may be important to them in an unclaimed area. Have you tried it? It's on by default in the newest versions. :) Players aren't bothered when they place abundant blocks like dirt and sand, but will occassionally get a warning when they place more valuable blocks (bricks, wood planks, etc) that indicate real building on their part.

@pgirl

That "regenerating exploded terrain" sounds like CreeperHeal, a separate plugin. It's definitely not grief prevention doing that. What is the problem you're having with lava permissions?

@theorion

The last time somebody couldn't get the shovel to work, it was because they were using a 1.2.5 grief prevention on a 1.3.1 server. Did you maybe grab a 1.3.1 build of GP for your 1.2.5 server? Double-check the version compatibility in the downloads list at right.

@lol768

You want to allow players to build anywhere in creative mode? Then just take your world out of the "creative worlds" list in GP's config file. Be warned - those rules are actually important, and you may have a lot of wilderness grief to clean up without them.

Yes, not being able to drop items is a creative worlds rule from grief prevention, to prevent item spamming, and the above change to your config file will also turn that off. But not being able to interact with anything isn't GP (do you see an error message in this case?).

@Luficer

It's not meant to replace WorldGuard 100%, because WG has some features which are not anti grief features. I'm waiting for somebody to develop an extension plugin to add flags to grief prevention claims. I won't add it in the base plugin because there are no flags which are necessary for anti grief (for example, not spawning monsters in an area is convenient and cool to have, but has nothing to do with players griefing other players).

@BobaFett119

To clear all claims, delete the claimsdata folder and /reload. DO NOT delete the playerdata folder, unless you want to reset all the claim blocks all your players have earned. If you're using the database option, then you have to drop the claims data table (instead of deleting a folder on the file system).

@Praqoon

There's no /deleteallclaims command, because that would be equipping any player with the right permissions with an instant data nuke. Of course, you guys would never give anybody that level of permission, but... there are server owners who don't have a lot of common sense. :) So in the rare cases where you want to clear all claims, only people with direct access to the data can get it done. I think it's a reasonable security measure.

@MerlenMage

Sorry Merlen, but towny and GP don't fit well together conceptually because they BOTH give players a way to claim land. Short of a deep integration between the two (which I won't pursue for sheer amount of effort and future maintainability problems), there's no way to prevent cases where players will use Towny to supercede GP, or vice versa.

Maybe you could disable GP claims in the world where you're using Towny, and disable Towny in the worlds where you're using GP? For the anti theft, no, it's either on everywhere or off everywhere. You're actually the first ever to ask for this, despite the plugin being available for almost a year, so you can see where I wouldn't want to add that level of complexity to the config file (a world list for every option, instead of true/false) for a rare case like this. :) Hope you can find a way to make it work!

@Praqoon

To that end, there seems to be one command that somewhat fits that description, but it looks like it requires a player name and only deletes one person's claims.

http://dev.bukkit.org/server-mods/grief-prevention/pages/administrative-topics/#w-deleting-and-resizing

Could try it without the params, but doubt it'd cut it.

@BobaFett119

I'd bet that the new world has the same name as the old world, and in that case, you probably still have the old GP config files for that world saved in the Plugins > GriefPreventionData folder. You should be able to just delete the ClaimData and/or PlayerData folder to remove the claims I'd imagine

I'd like to suggest a feature or two. At the moment this is my favorite region plugin, but can't replace WorldGuard entirely because WG has flagging capabilities. So first suggestion is to implement some method of setting flags (ie. mob spawning, health regen, god mode, etc), and secondly, it'd be nice to implement a region setting that can apply a specific permission group to people who enter the region and restore the prior group upon leaving the region. Maybe even have it only replace a certain group with another group. And have a permission node to bypass region-specific group assignment. I've opened a thread looking for a plugin to emulate that last request, but it's not looking very good. >.< Cheers! Sorry if these have already been implemented, I just haven't figured out how to use them if so.