@TylerIsTooPro

What do you mean by "town type protection"? Do you mean something like what Burtthaman is describing below? You can create a "town" out of multiple claims using GriefPrevention, though it takes a little more effort and planning versus Residence (which in turn is very difficult for new users, and doesn't cover the whole grief problem).

@deleted_7036002

All data is on the server. Client crashes won't lose any data. Under the current system, server crashes don't lose data, either. I hope to keep it that way.

@deleted_7036002

I tried that, too. :) I have a floating island now with my house on it, because the TNT destroyed everything around and underneath my claim without damaging the claim itself. I was similarly happy to see that creating a giant lava fall next door didn't do any damage - the lava simply stops short of entering my claim. It wouldn't have caught anything on fire, anyway, but the liquid flow might have loosened some torches or redstone.

0.5 changes:

Fixed claims bugs, including pistons, bonemeal, mobile containers (on rails), and trampling crops. Also made /trust case-insensitive for player names.

Note that you can still push a block into a claim using a piston, assuming you're pushing it into air. Essentially, you'd be "giving" that block away though, because there's no way you're getting it back. Also, you won't be able to push it farther in, even by pushing another block into it. So don't be a dummy - try that grief, lose your blocks.

Also note that while I have allowed fluids to flow from one claim to another when the claims touch AND the owners trust each other, that doesn't apply for pistons. Even if your neighbor trusts you and your claims touch, you still can't use a sticky piston to take a block from your neighbor's claim, because you will have changed ownership of the block.

Also fixed boats. They can still be broken and pushed around (sorry, unavoidable), but they can't be ridden by others as long as they're on your claim. Fortunately, they're super cheap to replace.

There's a "bug" where a piston can be used to break an iron door, if that iron door is on the very edge of your claim. I was thinking on ways to fix it, but then I realized that if your iron door is on the very edge of your claim, that means anyone can open it by placing a redstone torch, anyway. So don't put your iron doors on the edge of your claim.

@burtthaman

I'm not sure what you mean exactly by "deleting a region". :) Please post a comment under PopulationDensity describing your whole problem, so that I can give you the best solution.

I will add a slash command to add or subtract bonus claim blocks. You can use that to monetize claims. I will consider optional economy support via integration with another plugin. But if I decide to do it, that will come after the rest of the anti-grief support I have planned for this.

I'll add a config option for requiring a permission to claim land. It will default to off.

While Residence might be more convenient for this "super community" scenario, it can be done with GriefPrevention:

• Build your outer wall and protect it with four (or more, for non-rectangular shapes) claims. One of has entrances. To give a player access to the inside of the structure, you grant access to that one claim.

• Build your workshop, pastures, crops, etc close together and enclose them in one claim. To give someone access to crafting equipment and food, then, you can use a single command.

• Divide the rest of your area up into plots so that it's all covered. If you want to allow someone to move in, one more command. Whether it's a prebuilt house with containers (/containertrust) or an empty plot (/trust) is up to you.

Yes, this means up to three commands per new community member. But with any land management plugin, if you define several areas which you want to manage separately (I want to grant access to one house without changing the rest, or the workshop without changing the farm), then you will have to do the work to manage each of those separately each time a new community member joins. I admit it would be nice to manage subdivisions rather than trying to "fit" adjacent claims together, I think my current plan is good enough almost all players, especially considering that this is a grief prevention plugin, and not a land management plugin.

Another plugin from you bigscary. Instant download ^_^

Keeping my eye on updates for use :D

@deleted_7036002

Claim owners can already use /trust to grant clan members access to the town. I understood your request to mean that you'd like owners to give permission for OTHERS to then give permission to others, and so on?

Yes, if you have any access to a claim, then by being in that claim, you'll be making it vulnerable to siege. So if you start a fight then go cower in your friend's house, you can be sieged there, and your friend might be upset when he logs in to find all his windows broken and half his yard dug up. :) It's only fair that when you're safe from death by sword, you're giving something up for that protection.

Hi all, based on the comments I've received over the weekend here, I've decided to change my plan a little. Instead of moving on to spam, treetops and PvP immediately, I'm postponing those functionalities until I've finished polishing the claims stuff. It seems to me that several of you are now literally waiting for me to finish claims, so I'll handle that first and then return to the rest later.

ETA for claims bug fixes and polish: This week. You can all help me finish more quickly by downloading releases as I publish them, testing, and posting your feedback here. :) I'll try to release daily.

@TylerIsTooPro

I'm very glad to hear that you think this is the best anti grief plugin you've been able to find, but I must caution you that I'm not offering any back-compatibility guarantees until I'm out of "Beta" releases. That means a future update might mean deleting all of your players' claims and having them re-create them. I know it sucks, but it's unavoidable for now. If you're comfortable with that risk, then carry on. You've been warned! :)

First, thanks VERY much for all your comments, especially Tyler and MrCheese for careful testing. As for the dev being on break - I didn't code this weekend because my friend got the game and we had a great time playing it. :) I'm back to coding this week.

I'll fix bonemeal, pistons, trampling and chest minecarts - thanks SO much for those bug reports! You're right about pressure plates, wooden doors and trapdoors, fence gates, and note blocks being accessible without permission by design. Note that if you want to keep somebody out of your fenced area, you can use an iron door with a switch - however your animals are protected from damage anyway (though they can be stolen by luring them with wheat).

About /trust, I'll check on that. I'm certain I tested it, but I'll look again. /trust should definitely grant full permission for another player.

About finding out who owns the claims and where their boundaries are - you can currently research claims using a piece of string. I'm planning to experiment with temporary blocks (glass walls) to illustrate the claim's boundaries. If it works cleanly, I'll tie it in with the string tool. I won't, however, notify on claim entry/exit. It's way too expensive, given that I've decided to track claims as a whole rather than individual blocks (thus dodging a database requirement). I'm also planning to update the error messages with claim owners' names so that you can check ownership without a string.

About administrative permissions, those are in the plans - admins will have the option to ignore claims and even delete them. It's not super-high on the priority list right now - I want to get the major features testable first, then come back for config variables, permissions, and performance tuning. I'm also planning "bonus claim blocks" to be granted by administrators for whatever reason - donating to the server, winning a contest, etc.

@Nazerb:

If the server crashes or shuts down, grief prevention shouldn't have the opportunity to run any disconnect code, so nobody will be penalized for logging out. I can't be certain yet because that bit isn't coded, but I'll test it when it's ready.

I don't think there's a good solution for picking a chest at random, and even if I could, I think most would want me to disable that feature because there's a chance a player could get seriously robbed (by chance). Players will work around it anyway by creating like 30 extra chests with nothing in them, or hiding all of their chests in walls, which would be an ugly result.

I know that many admins view tree topping as "grief", although not all of them. If I promise to make a plugin which will stop grief, I have to at least offer this feature. Of course it will be disable-able for anyone who doesn't want to use it, or prefers another tree top plugin. I'm not trying to do "everything", just "everything grief".

I think any list of blocks I choose to designate "soft" will be highly controversial. Nonetheless, I'll start with a list that can't be changed to see how much yelling there will be, then decide based on that. On the one hand, I want players to get a similar experience on every server so that when they change, they don't have to relearn. On the other, I don't want admins passing all the goodness in this plugin just because they disagree over what a "soft" block is.

Block replacement will be too expensive to implement, I think. Anyway the soft blocks will be easy to replace - I won't be designating any valuable, rare blocks as "soft". If you build a house of glass, well then that's a big risk you take (if you're on a PvP server, with this plugin and the siege functionality enabled, which will be off by default).

I won't add an option to delegate claim security to another player. I think very few players will ever use it, and then they'll almost always regret it. Besides, it feels too much like claim sharing, which I'm working hard to avoid so that griefers won't start using claims as a griefing tool. If I hear a lot of requests for that, I might change my mind, though. :)

There will be an option to have the claim extend to the bedrock. The default of having it extend only a few blocks into the ground is designed to prevent players from claiming ore they haven't found, yet. Imagine your annoyance if you find some diamond deep underground, only to discover that because some newbie built a dirt hut on the surface above you, those diamonds belong to him.

Allowing for teleportation is controversial because it often ends up being an easy-out to get out of combat or to avoid getting lost in your own mine (thus eliminating what little challenge there is in adventuring). If you want the convenience of teleportation balanced against other gameplay elements, consider PopulationDensity. :) I'm trying to keep this plugin strictly anti-grief.