Would like to say: residence can prevent forest fires. Firespread has its own flag. So your statement is inaccurate. Also it can be configured to protect everything by default, although I will grant you that the commands are not as user friendly as your own, at the same time you lose a lot of the configurability.

@codezombie13

So you're suggesting say, no block changes near or above sea level, unless the area is claimed?

Also, I wonder what you think about this - it just occurred to me that a player could claim an area, make a mess, then move the claim to make a mess somewhere else. That's why in creative mode, I don't let players shrink or delete their claims. So I'm thinking that unless admins are creating claims for other players and not letting players create them for themselves, this config option (your version and mine) probably isn't very helpful.

5.1 Updates!

• New config option to disable building outside of claims even in survival worlds. I don't recommend it for classic survival style servers, but I can see where some "adventure" servers or other specialized servers might want this.

• The golden shovel tool is now configurable, so you can use a golden sword or whatever instead. Just remember to update your messages.yml, and somehow inform your players that what they see in the videos is not 100% correct for your server.

• Players can no longer get PvP immunity by emptying their inventory and logging out, then back in. Only by dieing. Players who have NEVER been on your server before will still get PvP immunity the first time they log in.

• Very short messages very close together are now considered spam, and will trigger a warning and later a ban if players persist.

• Performance improvements very large claims related to water cleanup, entity limits in creative mode, and visualizations.

• Very significantly reduced overall file write frequency.

• For anybody looking at the source code, you may notice that I've taken some steps toward the database support. It's not functional yet, though.

@snowy007

Okay, then use /containertrust public, and tell your players to do the same. Anyone can do that with their claim to give all players access to their containers and buttons/levers.

Yep, it's on my todo list, just not explicitly listed above.

@jamzam90

You'll have to ask the mod developer about that. If it were possible, I'd think it would be on by default. So it probably isn't, but you can request that feature.

@ajaids

Okay, I will allow you to configure the claim tool.

There's a config option called "claims require permission" or something like that. If you turn it on, then no one can create claims without having a specific permission. Read more details in the admin details page.

@cvxx7q

They shouldn't steal blocks anywhere. Are you sure they're stealing blocks in the wild? It's very hard to tell the difference between an enderman hole that's new versus one that was there before you updated the plugin.

Also welcome back, nice to see you. :)

@lambik

No sorry, that's not an anti grief feature so it's not in the core plugin. I'm still waiting for someone to develop a quick extension plugin to do things like disable pvp or disable monster spawning in a claim. If you want this for just a few specific adminstrative cases and not for all players, then WorldGuard is what you want (in addition to grief prevention). Just be sure to set WG so that only admins can use it, otherwise some players may create WG regions on top of other players' claims.

@snowy007

Use an admin claim (/adminclaims). Those allow playres to use buttons/levers and access containers. Or, you can use /containertrust public on the existing claim isntead of creating a new admin claim.

@re4397

Okay but the block doesnt stay broken, right? Then it's a Mojang bug that they need to fix, because the client says the player has gotten into the house, and the server believes him when it shouldn't because the block is in the way.

@bigscary

on my server the enderman never steal blocks from claims, but out in the wild they do of course, at worst maybe Steelsouls has found a duplication issue

the enderman picks up a BRICK_BLOCK without actually removing the BRICK_BLOCK hes picking up

@Steelsouls:

are you sure the enderman arent stealing bricks from abandoned claims or expired claims? ive seen full houses made without even he slightest protection (i suppose players hate chests? -.-)

so check into that :)

the edit button disapeard on my last post what i meant to say is there a way to make it so the plugin identifys the fake player as the player that placed the mod item.

i hadnt though of that bigscary would there be a way to set the mod items fake player thing to say it was the player that placed it

@HamiltonSam

Yes. Explosions will never destroy claimed blocks. Additionally, the default configuration prevents explosions from destroying ANY blocks above sea level, which inhibits resourceful griefers and eliminates the usual damage over time to your world's surface due to creeper explosions.

@TheCodePanda

Not exactly, but you can do something very close. When you give a group claim blocks with /acb [permissionNode], those players get bonus blocks up front, and also have their maximum limit increased by the same amount. For example, suppose you had a builders permission, and your max accrued blocks is set to 500. Then you do /acb [builders] 1000. Now anyone with the builders permission has 1000 extra blocks, and can get a total of 1500 blocks over time, while players without the permission don't get the bonus blocks and will never have more than 500 blocks.

@jamzam90

The fix you suggest for redpower isn't sufficient. If every redpower construction were anonymous (as you suggest, they would all use the same name, no matter who the real owner of the construction is), then allowing one machine to make a change in your claim would be allowing any machine built by another player (potentially a griefer) to also make changes.

When I add mod support, the best I can do is to allow you server owners to point out special blocks which should be treated as containers. To support machines without opening an opportunity for griefers, the mod developer has to update the mod so that machines have owners, and those owners are reported as the block changer when the machine makes a change. If the mod doesn't tell GP who the owner of the machine is, then GP can't safely allow the machine to make the change.

@Praqoon

I checked into this, and it's working properly. My first guess is that your config may be wrong - it's CreaturesTrampleCrops, not MonstersTrampleCrops. Second, it's normal behavior for a not-watered, not-planted soil block to revert to dirt over time (is that your situation?). Third, if a player or animal walks or jumps on a soil block, it will APPEAR to you that the block has returned to dirt, even though the server hasn't actually updated the block. If the planted crop doesn't actually fall on the ground, then the trampling was correctly blocked. The easiest way to test this is to plant some seed in a small fenced, claimed area, then spawn some monsters inside the fence using a spawner egg.

@Esaych

Thanks, I'll look into this. I can't imagine why a large claim would cause any problem. Why would you want to create such a thing? This is not a high priority for me, because the plugin is for protecting player builds, not for putting some kind of shield over the entire world. Are you trying to run a creative mode server? If so, consider the creative mode configuration, which prevents players from making changes until they've claimed land where they want to build.

@Steelsouls

Hmm that's a very good question. I'm almost 100% sure they're not actually removing any blocks, but seeing them walk around with blocks makes me wonder. It's hard to track these guys because the teleport around (ugh). Maybe I can construct a reasonable test environment for them in the end to confirm, but I suspect your guess is right - the server is probably updating the monsters even though I've cancelled the block change event.

@VietNg

Put an admin claim on top of the area where you don't want people claiming, then do /trust public inside the claim. Now players can do whatever they want in there (as far as GP is concerned), but they can't create claims of their own because it's already claimed.

@lambik

Yes, it's a very good replacement for WorldGuard, assuming you're only using WorldGuard for anti grief. Even if you're using WorldGuard for more (like creating a no-pvp zone), you'd still be better off by running GP to stop your grief, and then using WG for the very rare cases where it adds a little value. I recommend GP over WG for anti grief because GP prevents MANY more types of grief than WG does - many griefs are not about changing the world - chat spam and spawn camping are two examples. Also, GP is much easier for players to use for land claiming, and it even creates automatic claims for new players who may not know how land claims work, yet.

@PunJedi

I think you're assuming I'm recording every change - this isn't a logging and rollback plugin, so I don't need all those data. I only write to disk when a claim is created/modified/deleted, and one per 5 minutes per online player to update how many claim blocks they have available. The second part of that may theoretically not scale for large servers, I'm not sure (try it and let me know?), but anyway a database option is coming soon. If not having the rollback makes you nervous, there's no reason you can't run GP and a logger behind it, just as insurance for when players don't claim their land like they should.

@Steelsouls

Thank YOU for helping me get the word out. :) It's a shame so many players/admins are having to get by with block loggers and rollback. That's a lot of downtime for players waiting for investigation and rollback, and a lot of work for admins who could otherwise be actually playing the game.

@Steelsouls

That's not a bad idea. :) I'll put it in the brain bank.