jordan4ibanez wrote:0gb.us wrote:jordan4ibanez wrote:I had to dig this out of your game mode to get it to work, but this, this is a fantastic protection plugin, I highly recommend this if you're scared of someone being able to grief with sand in a protected area, this fights everything! I don't know if it works against pistons and tnt though, but if you claim far enough from where you're building, that shouldn't be a problem. Fantastic plugin.
It does not protect against pistons or TNT (or anything non-default). I do take support requests though, so if you have something you need protection against, let me know. I assume you are referring to mesecons pistons, but there are so many TNT plugins available, you'll need to provide a link to the one you use if you want support for it.
I request mesecons pistons and pilzadam tnt
Okay. I'll work on that when I have time. Keep in mind that if the claim protects against pistons, pistons will basically have no effect inside claimed areas, as the piston won't be able to push any block within a claim. I'll make it configurable.
Come to think of it, I need to make the rest configurable as well.
4aiman wrote:gb.us, can you tell me about you mod?
I mean, as far as I understand (didn't try to read all your explanation), you operate with chunks but set meta for every block inside "owned" chunk. Isn't it simpler to operate with areas? Or you have to switch to meta because of some performance issues?
I asking because, if you'll use areas, you won't have to worry about "supporting" blocks from any mod, so there should be a good reason to not use areas.
"Support" is what to protect AGAINST. As in, TNT operates outside the node digging methods, and therefore requires separate functions be modified. Otherwise, TNT can blow things up if placed just outside the claimed area. Same with pistons. They can be placed just outside the claimed area, and push things that are just inside. If a piston is placed INSIDE, no one can steal it, as it itself would be protected.
I do not set node meta data. I *WANT* to set map chunk meta data, but to the best of my knowledge, there is no such thing.
This plugin does some simple math to find the map chunks, and saves claims to an external file. Unfortunately, this means the entire list of claims is loaded at all times. If I had map chunk meta data to work with, only the data for loaded chunks would be loaded. Maybe one day, once I learn C++, I can get that feature added.
The reason for working with the chunks is that they can be found with math. That makes it so unlike protector, it doesn't have to check a bunch of nodes for a claim each time a node is placed or dug. While saving data to every node would have benefits, it would make working with chunks pointless, and would have problems with falling nodes and flowing liquids. Both could wipe out air nodes (I think without any callbacks), wiping out the claim on those air nodes as well.