[INACTIVE][SEC] OwnBlocks v10.0 - Players may not break blocks placed by others [860]

OwnBlocks:
Version: v10.0

(7-10-2011) - Please see the latest branch of OwnBlocks, called OwnBlocksX. It is recommended you use OwnBlocksX now.

OwnBlocks keeps track of placed blocks, and who placed them. Players are not allowed to break blocks placed by other players. Note however, that indirect breaking may still occur (i.e. fire, tnt).

Features:

• Blocks you place cannot be broken by others
• Persistence; Server remembers who owns what blocks after a restart or "reload"
• Toggleability! Use /ownblocks or /ob to toggle OwnBlocks on and off
• Ability to exclude certain blocks from being protected
• Support for Permissions AND non-Permissions servers
• Auto-saving intervals for database protection
• Add (pre-placed) blocks to the database manually

Download OwnBlocks v10.0



please note - If you are using iConomy, only version 4.6 is currently supported.

Source Code
OwnBlocks is released under the WTFPL License.

Config File Options:
Please note that at any time you may move/rename/delete you config file, and restart your server to produce the example/default config file with these options pre-filled along with descriptions. Also remember that lines preceded by a '#' are comments, and are ignored.
exclude - enter comma separated integers of block-ids you wish to exclude from being protected and entered into the database. An example would be to enter the block-id for saplings, so planted trees do not have a single log at the bottom that is protected when a tree is harvested by another player.
iConomy - enter an integer greater than '0' (zero) to enable. The number entered becomes the 'Basic Rate' at which players are charged to place protected blocks. Players will not be able to place blocks if they have insufficient funds.
debug - If you are experiencing errors, and want to post them here to resolve them, or just want to spam your server log with information, set debug equal to 'true'
status-message - Set this to 'disable' to not receive the message "[Username] - OwnBlocks is now activated for you....". Set this to 'simple' to receive a simple "OwnBlocks activated/deactivated" instead. Lastly, set this to 'disable' to disable messages entirely. Now that I think of it, disabling status-messages seems like a really bad idea......but the choice is yours.
save-interval - Enter the number of seconds specifying the interval between database saves. The default is 60 seconds. Increase this number if you have an obscenely large database that takes a long time to write to disk. Decrease this number if you are paranoid and/or have very fast disk IO.
info-id - Enter the integer representing the ID of the material or tool you would like to use as your "information tool" which will display the Owner of a block you right click with specified tool. Default is 269, which is the wooden shovel.
add-id - Enter the integer representing the ID of the material or tool you would like to use as your "add tool" which will add the block you left click with the tool to the database. Default is 268, which is the wooden sword.
enabled-on-login - True means that OwnBlocks is automatically activated for every player as soon as they log in. False means that OwnBlocks must be activated manually by each player when they want to start building protected blocks.


Permissions Nodes:
You will need to add these nodes to your Permissions configurations if your server uses Permissions:
'OwnBlocks.ignoreOwnership' - Allows player to break blocks placed by others. This node is typically given to admins.
'OwnBlocks.use' - Allows a player to even use OwnBlocks. If you want everyone to be able to protect blocks with OwnBlocks, and assuming you have a "normal" Permissions configuration, then add this node to your "default" class.
'OwnBlocks.info' - Allows a player to use the info-tool to display who owns a protected block.
'OwnBlocks.add' - Allows a player to use the add-tool to add blocks to the database for protection.


Changelog:

• Version 10.0 (5-20-2011)
  • Added configuration to set whether OwnBlocks is activated for players upon login
  • Added tool to add pre-built blocks to the protection database
  • Improved process of saving database
  • Fixed status-message configuration options (inconsistent verb tense)
  • Default to protecting all blocks when Permissions is not detected

• Version 9.0 (5-5-2011)
  • Added support for Servers without the Permissions plugin
  • Added 'OwnBlocks.use' and 'OwnBlocks.info' nodes

• Version 8.2 (5-4-2011)
  • Fixed NullPointerException when right clicking with empty hand

• Version 8.1 (5-4-2011)
  • Added ability to use tool to display who a block belongs to. use info-id in your config file

• Version 7.0 (5-3-2011)
  • Added database auto-saving intervals
  • Added ability to enable/disable 'status message'

• Version 6.5 (4-29-2011)
  • Added iConomy support for charging a basic rate for each block placed
  • Added config option for debug mode

• Version 5.0 (4-23-2011)
  • Added Permissions Integration
  • I think I fixed a bug that occurred when the 'reload' command is issued

• Version 4.0 (4-23-2011)
  • Added properties file (/plugins/Ownblocks/OwnBlocks.properties)
  • 'exclude'
  • Blocks are now removed from database when broken by their owners

• Version 3.0 (4-22-2011)
  • Added the ability to toggle OwnBlocks on and off
  • Added commands: /ownblocks or /ob

• Version 2.0 (4-21-2011)
  • Moved data directory from main folder to the plugins folder
  • Added/fixed serialization (Persistence)
  • Made database searching more efficient

• Version 1.0 (4-20-2011)
  • Initial Testing Release

ToDo: Should there be continued interest in this plugin, I will consider looking into:

• MySQL support
• Support for group projects
• Add configuration option to prevent "adjacent construction", where a player builds blocks on blocks owned by another player
• Add support for Metadata values
• Area Selection
• Update this iConomy shenanigans.
• Look into solution for chest protection
• Add command to check the database for blocks that have become air because they were deleted externally by something like WorldEdit

 

People could use this for griefing so easily... :S

 

Updated to v3.0 *yawn* now I can get to sleep...

 

I have an good ToDo Request... Something like, you can set the Time, how long blocks will be saved. ex: I want that a Block saves 7 Days. After 7 Days the block gets deleted from the Database and has no owner anymore. Whats about that?

edit: Plugin works perfectly with b.709

 

Can you add a toggleable "player pass event from sky to bedrock" or some kind of height limit option? To prevent players to pass over and under.

I've been waiting for a plugin like this. Very awesome! Thanks! You saved me a lot of arguments with my players on the server.

EDIT: Oh and add a tool to see who's protected block it is. Like Worldguard's string.

 

Nice idea! Very nice idea!

It would be a great plugin for a underground rail system! Don't want that player can destroy the rails so I would place them with this plugin. Better than a big Residence zone because it would go through many other user zones.

If the plugin has permission nodes, I will use it for my server.

 

I tested this on my server and i think this won't work for people who don't use Regions for their players where they are able to build on. People can easily abuse this. Spamming blocks all around the map for example, or blocking peoples doors...

 

Hello, didn't work

i place a bloc, and all people can break it, creeper and all



what's happened ??


Thank you

 

Updated to v4.0. Added Properties file and 'exclude' support per the request of BigBlueGER

Interesting idea. Why exactly would you want to do that? I think its a cool idea, but I am not sure if that would be something that should be incorporated into this plugin. Maybe a separate plugin with a different design goal would be better suiting. And thank you for informing us about 709

Not sure about the sky to bedrock, but I like the string idea. Thanks

I dont know if that is something that this plugin can compensate for. Sounds like those players shouldnt have build privs in the first place.

Well, it sounds like you didnt install the plugin.

Sorry for spamming, but OwnBlocks is now updated to v5.0 which now has Permissions integration!

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

I really like this plugin. I have been searching for something like this forever. I am not a programmer so I don't know if this is possible, but could you make it so that I can set whether blocks already in existence before I install the plugin and blocks in new chunks can be broken? I have a lot of buildings on my server already and I would like them not to be broken, along with blocks in new chunks as my server is set up for people to only get resources via jobs, but for any new blocks placed by players, I would like for those to only be broken by whoever places them. Even if that isn't possible it's still a great plugin.

P.S. One final question (sorry for making this post so long): I don't use permissions, but rather only use ops.txt, and I would like my ops to be able to break all blocks. Is that currently the way it works without the permissions plugin? I don't want to ask too much, but if it isn't could you make it that way?

 

I will look into adding the ability to add existing blocks to the database. There are other plugins that can do that, but I understand that people may not want to have two separate protection plugins. Regarding ops.txt, Ill look into that as well, but it may just be easier to get Permissions. :\

 

Should add iConomy support..

Pay to protect blocks etc

Would be a neat way of charging for a house, without having to protect actual surrounding land etc. I like the idea tho :3

 

I WOULD LOVE IF THIS HAD ICNONOMY and charged a basic rate for placing each block!

 

It isn't just that I don't want to have two separate protection plugins. The problem is that If I blanket protect it with another plugin then people can't destroy any block, but I want them to be able to only destroy blocks they place. And I appreciate you looking into the ops thing, installing permissions and getting it set up for all my plugins rather than using ops would be a real hassle for me. Thanks.

 

looks like this could have a lot of possibility, please consider these suggestions.

+iConomy support
+limits on total number of protected blocks a player can have
fine grain limits (per block limits) on how many blocks a player can own.
+admin/mod overrides (can break protected blocks, place unlimited blocks)
+protection wand/tool (ability to protect already placed blocks if not owned)
+world guard intergration (can only place protected blocks inside a defined region, or outside of one only)
ie: players can only place protected blocks outside of any world guarded area, or only inside a defined world guard area
+lifespan, protected blocks only stay protected for a specified time period.
(ability to define lifespan on individual block type, ie dirt lasts a day but cobble lasts a week)
(auto prunes old protected blocks from players that don't play any more)
+based on something like factions power level, each player has a power level, allowing them to control blocks, if they die they lose power, and control of blocks, they gain power back over time at a configurable rate.
+option to do the opposite of this:
'Properties file support. Ability to exclude certain blocks from being protected'
+'Properties file support. Ability to protect these blocks only'

EvHub's suggestion is very interesting, if the world were to be protected in a way such that players can only place protected blocks but not destroy any they have not placed. This could be useful in this way, have a pvp/mob fighting resource world, use a multiworld mod to create a second build world, users would have to bring everything with them and build, and would not be able to change others work, admins could create areas to build for players or do land edits like normal, or have a flat empty world with a bedrock floor.

 

+on command remove however many blocks a player placed.

 

does theis support mysql?

 

Hello, I'm at a confusion. I have access to all commands and I'm oped. Permissions set to '*'
No matter what I cannot destroy another persons block

 

I have the same problem, the plugin works but admins can't destory people's blocks.

 

What you should do is add a permissions system like trust 1 would be just using the block trust 2 would be building on the block and destroying your own blocks you placed. and trust 3 would be people destroying your blocks.

 

I'm seriously waiting on selecting the already added blocks and protecting them from breaking :/

 

im seriously waiting on pricks like you to realise plugins are gifts NOT a purchase...

 

I took a look at iConomy, and it seems that adding support for it would be easier than I originally thought it would be. So I'll take a whack at it

Thanks, Ill look into your suggestions

OwnBlocks does not use SQL, nor does it care whether your Minecraft Server uses it or not. So, if by "support" you mean "work with a MC Server that uses SQL on the backend" then the answer is yes.

You must be an Administrator or the like as configured in your Permissions configuration file (access to '*' or 'OwnBlocks.ignoreOwnership'). If you can confirm this is true, then are you sure that you "reloaded" Permissions or your server after you made the changes?

Can anyone else confirm or deny that Permissions is working correctly with OwnBlocks?

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

TY I LOVE YOU! :}

 

I don't know if anybody else is truly having my issues.
However, I can help clarify.
I use the '*' for admin, I am able to destroy people's blocks.
However, after a certain period of time I am not able to destroy other people's blocks anymore.
This could be due to me reconnecting. I am not the expert though

 

Hey i need help on my server peapole build some shits in town and me op of the server cannot destroy it

 

I just pressed the "like" button because the thread uses verdana font, which I like XD I can barely read this other font.

 

@cvenomz Why cant a Admin break blocks placed by other players? Shouldnt that be default?

 

Yes, I'm the owner and have "*' permissions and I'm also in the ops.txt file; I restarted the server multiple times but it still does not allow me to remove those blocks. I disabled the plugin for now because it's great for griefers atm ... Otherwise this would be the perfect anti grief plugin.

 

Is there a way to add a admin permission node? Like an admin can destroy anyone's blocks and it will be deleted from the database?

Also what will happen if I used WorldEdit to destroy someones creation, does the data stay in the database?

 

And because it's a gift I'm asking the person to add a feature, if I had bought it, it would already have what I need, you ignorant *****, don't flame me out of nowhere, I haven't done anything bad to you.