6.5 Updates!

• Tekkit is now supported by default, without any need to edit the config file. Of course Tekkit admins are running MC 1.2.5, so it will be a while before you guys can enjoy this benefit. :)

• Many config options which previously applied to all worlds now only apply to worlds where claims are enabled, for example the rule for dispensers dumping water/lava, the creeper and TNT explosion protection, and so on.

ok, i've made further changes, this time to the EntityEventHandler and PlayerEventHandler classes.

Basically members in our member only world were complaining that TNT and creepers weren't causing any damage to the world.

Managed to fix the TNT one, but creepers still don't, not sure why.`

@fireblazt

If you don't see anything in the logs, the only explanation I can come up with is maybe your files are not getting saved, or are being deleted? Also be sure you're players aren't using /abandonclaim or /abandonallclaims, just to make sure - that's the only way to delete a claim that doesn't trigger a log message. When a claim is cleaned up because it's unused (which shouldn't be happening in your case, since your players are active), it generates a log message. Similarly, if an administrator deletes or resizes a claim belonging to somebody else, there will be a log message for that.

@Comoreto

The limiting buckets option effects worlds where claims are enabled, yep. You'll see that there's a config section for "claims". The rules in there impact only claims. The rest of the config file impacts either claims enabled worlds, or the whole server, depending on the option. You can read about all the options in the "administrative details" page linked above.

@Desertive

No, there's no reason to drop items on the ground as far as I know, and griefers will abuse it to spam items everywhere - can you explain this water bank thing?

@Tobyz28

Hmm so you want to allow players to be stuck if they're in an administrative claim... sounds reasonable, since creating a trap would only be creating a problem for administrators. :) Sure, why not. I'll do that in the next version.

Hey Bigscary, would like to see if you could add an additional feature for servers who are using administrative claims to contain users where needed. For example on our server, at spawn all players must pass through a maze and skills trial to demonstrate they've viewed our website rules. We've administrative claimed the whole start area. Many players will whine they're "stuck" in the maze, when a convenient message pops up telling them to type /stuck if they're stuck - allowing them to bypass the maze completely! :(

Would it be possible to have a config option to disable prompting of stuck helper messages while in administrative claims(As well as from them using the /stuck command too)? This would be a great help for our server :)

@bigscary

Not really an issue for us, Worldguard can protect regions that are in our non-claims worlds (does an excellent job of it) and PlotMe protects in our plots world.

Basically my changes to the event handling stuff was to the point of telling GP, if it isn't listed in the GP 'claims world' config, then GTFO and leave it to whatever other plugins we have.

@ray73864

I did look at your code, and you did some risky stuff. For example, I see you're skipping the block place code when you're not in a claims enabled world. That means that if you create an administrative claim in one of those worlds, that claim will not be protected (players will be able to build there).

Anyway, I'm integrating a safe version of your changes into the next version, including the updated /tr alias for /trust. :)

For the claims block change, you want to go into the task code where players receive claim blocks, and just add something like "if player not in a claims enabled world, skip and continue with next player".

@Comoreto

Yes, that's the default configuration. Players will be unable to dump buckets of water or lava above sea level unless it's in their land claim. This will eliminate the "douchebag teenagers dumped water all over my hills and trees" problem.

@Chaett

This is detailed in the administrative details page. Initially, claims are shallow (just a few blocks into the ground) but they automatically stretch downward as the claim owner either builds or breaks blocks under them. This means that if you protect your house today and add a basement or mineshaft underneath later, that new build will be automatically protected. However until you've explored the area under your house, other players can still mine there to look for diamonds and such. But once you've been down there, it's all yours.

EDIT: Are your survival mode players being told they can't build unless they claim first? If so, go to your config.yml and remove any survival worlds from the "creative rules worlds" list.

@1996BRECHT

You're using a version taht isn't compatible with Tekkit. Tekkit runs Minecraft 1.2.5, so you need GriefPrevention 5.5.1 at the latest. When Tekkit moves up to Minecraft 1.3.1, you can upgrade your GP to a later version.

@bigscary

Ummm, i'm not really sure how to use github, one of my mods suggested a pull request, but i'm not sure how.

it is available at: github.com/ray73864/GriefPrevention

Also had to change plugin.yml as the alias for trust was conflicting with the essentials command /tell.

Feature request is fun, our mods enjoy it too. We've got about 35 plugins, most are just informational style ones, others are gameplay ones such as PlotMe for our plotsworld, which is a worldgen and region plugin, creates a world with a configurable sized plot that players can claim.

Pretty much every single one of our players come from other servers where multiworlds are in use, they know about /warp, /tp, /tpa, etc...

I'm going to make the change to the claimsperhour code, mostly because on our server, we would rather them not getting claim blocks outside of the GP world, i fully understand if you don't want to make that change, but for our server, it is a necessity. From what i have looked at, it is just a simple 1 line change anyway.

@Jeanzl2000

Drop the colons. I don't have a complete list, but reading your comment there, it's likely you missed some, for example buildcraft engines which can store coal and other fuels. You'd want to protect them.

@tetrisd

Are you running a creative server? Players are required to claim land before they can build. If you're running a survival server, check your config file to make sure none of your worlds are listed under "creative rules worlds".

@ray73864

Thanks for the tips! If you've published that code, let me know where and I'll integrate it. Otherwise, I'll re-engineer it for the next version.

You don't consider having to request features a headache? If you're running servers for 10 years now, you're not a typical minecraft server owner. I have to optimize for the typical case.

Players already know how to connect to a different server. But you have to teach them how to change worlds on your server (and that information isn't transferable to other servers). That's why I say it's harder, because it involves player learning where the first option doesn't. But anyway I shouldn't have taken us in this direction, I didn't intend to sidetrack us on a general discussion. I just wanted you to understand why I said no, instead of just saying no. :)

@ChilleCharlie

3,000 admin claims? Damn. Sorry sir to cause you that headache, but you can imagine that other folks don't have even nearly so many.

Restore nature will only happen if you're running creative mode. Also the claim won't be deleted if the player has built anything there, so no worries about water cleanup. Plus, the player has to be gone two full weeks (granted, some take vacations for longer). But again, remember if something is built, the claim won't be removed.

If you allow for dumping water on the surface (see config about limiting buckets), then water won't be cleaned up when claims are removed. There's a warning message about water cleanup that actually tells players they can resize instead. If they ignore it, then they asked for that headache.

Again just want to re-iterate - the automatic claim cleanup after two weeks of inactivity only cleans up claims where nothing substantial has been built. No players should be upset about such cleanups, even if they do come back to play some more. The worst case scenario I can think of is if a player makes 3 claims instead of 1 to claim his home area, where two of them are just pieces of his yard where he didn't build antyhing. Then it's possible (but unlikely) that another player may come along between his 2 week absence and his return, and build something in his yard.

@user_151271

Nope, not grief-related. Add WorldGuard in addition to GP, and use WG for the few cases where you want to disable PvP or monster spawns or hunger.

@Jukkatibbs

Sir, I think that's the weirdest bug report I've ever heard.

@1996BRECHT

Yes to creepers, endermen, pistons, and LOTS of other stuff you didn't ask about, like trees growing into a claim from outside. Yes, those specific items are protected, but ONLY as long as they're inside a land claim. If you put a chest or chest cart OUTSIDE your land claim, it is not protected.

ok, because i couldn't wait, we love this plugin, i have forked it and modified the block event handler, yay.

Now, it only affects things in the GP world. Haven't touched the hourly claimblocks thing, that one is annoying, but didn't stop us from using the plugin.

took a while, never used git before.

Was a very simple change to, 1 line in each event.

@Bob3104558

The event stuff such as 'onDispense, onBlockBreak, onTreeGrow, etc...' doesn't look at permissions at all, since they are bucket events and some, as you can see from 'onDispense' and 'onTreeGrow' aren't player events at all, they are environmental events.