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

Discussion in 'Inactive/Unsupported Plugins' started by cvenomz, Apr 19, 2011.

  1. Offline


    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).

    • 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.

    • 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
  2. Offline


    yea im still not able to get OwnBlocks working.. i may try a clean install of bukkit and work from there..
  3. Offline


    Alright, try that and let me know how it goes. I find it weird how OwnBlocks wont even initialize
  4. Offline


    If you could make group projects a top priority that'd be great. Number one most requested feature on my server.
  5. Offline


    If the MySQL version works properly, then group projects should be right around the corner. However, I haven't gotten even one report back about the MySQL OwnBlocks Dev build. :( As soon as it is cleared, I want to finalize it and start working on group projects. Hint: group project support will require MySQL.
  6. Offline


    I could possibly try it out soon.
  7. Offline


    I have a problem, i have installed the plugin ownblocks 10.0, and i exluded this blocks in the cfg
    #exclude=2,3,6,50,12, but when the users try to broke this blocks of other users, they cant, and the plugin not display any mesage, simply you cannot broke the blocks.
    Yes, i restarted my server and i put a block of dirt before the restart and the users can´t broke the block.
    My plugins: http://i869.photobucket.com/albums/ab251/Zephjroth/Minecraft/Plugins.jpg
    I hope you can help me, thanks in advance.
    bye, and sory for my bad english.​
  8. Offline


    It sounds like you did almost everything right. Your line in the cfg should not have the '#' sign. As soon as you uncomment the line it should work. So try something like: exclude=2,3,6,50,12
  9. Offline


    If what you are saying is if we go with MySQL then we will get support for groups to build, then i might be persuaded to use sqlite.
  10. Offline


    I have tested a new install aka removing old db and config and it seems OwnBlocks works.. However im not able to use my current db with all my ownblock saves for some reason.. seems it has been corruput somehow.. This makes me very pissed and have no idea how this could have happened.
  11. Offline


    Nice plugin sir but can u make the cuboid build protected too? And the old blocks
    u made b4
  12. Offline


    update this plugin on bukkit version 860?
  13. Offline


    Works fine on 860 for us.
  14. Offline


    really?ok than ty i will tested :)
  15. Offline


    updated thread title
    Do you have any recent backups?
  16. Offline


    I have several back ups. None of them seem to work when i try and use a new server with OwnBlocks loaded. Once i replace the DB it does not even start OwnBlocks.. ( we are talking about the database.db im assuming)
  17. Offline


    Thats really weird. I have no idea what could be causing such an error
  18. Offline


    I would use this, but it would stop people building together.
  19. is there a way you could make this compatible with worldedit's wand?
  20. Offline


    i have a sugerency.
    1.A player can decide if his building will be protected or no enabling and disabling the plguin with a code.
    2.There is a problem, when two players decide to build a building, if one pleer want break a block placed by his frined , he cant so it has a solution:
    when two players wants to build something they must write a command for exmaple like this /enable ownblock romanturbo cvenomz this commands will do that this two players can break his blocks for example romanturbo can break venomz blocks and venomz can break romanturbos blocks, and when they finish the building ther write /unable ownblcok romanturbo venomz and the plugin will be enable
    sorry if you cant understand me, jajaja, im very bad talking in english because im not english jajaja
  21. Offline


    @cvenomz The DB does not work after I updated to 860, i think. No errors, it is just not working. I NEED A FIX, THIS IS URGENT.
  22. Offline


    Yes, this is the major downside at the moment
    Probably not, but what do you mean by compatible?
    This actually sounds very similar to the implementation I was planning on using for group projects.
    It sounds like you and killj0y are having the same problem. I upgraded to 860 on a test server of mine and the database seems to load fine :\ I cant find get the same error as you guys. Is there anything that you did that may have triggered the bug? Because if I cant find what is causing the problem, then I dont know what to look for to fix :(
  23. Offline


    He means that blocks placed with worldedit would become that person's owner just as if the placed it like normal.
  24. Offline


    I see. Yes, this has been requested before, but I dont even know how this could possibly be programmed. So unfortunately, no, I dont think we will be seeing this feature any time soon.
  25. Offline


    I did not do anything i just upgraded to 860. :\

    I'll try reinstalling it. Will the DB be reset?

    EDIT: Did not work to re-install.

    EDIT 2: When i place a block it is protected. The blocks i placed before the upgrade is not protected.
  26. Offline


    I am thinking of upgrading to 860.

    Will my database still be working? Or will it reset?

    I have a lot of building who are protected alone by OwnBlock. Is it safe to upgrade?
  27. Offline


    I dont know what to say; I cant reproduce the error. Maybe you could send me your database file?
    I thought so, but apparently there may be some issues
  28. Offline


    Sure. Where should i send it?
  29. Offline


    You could upload it to mediafire or something, or if you prefer you can email it to me. I will pm you my email address.
  30. What if players want to allow their friends to break their blocks, could you add a command that would add a player to a "whitelist" So if you do: /ob allow <player> so that player could always break your protected blocks? :D
    Also, does this prevent from people placing blocks on top of protected ones?
  31. Offline


    I think a group system would be better, like:

    /group create (group name) Makes a group that you "own".
    /group add (player) add's player to group.
    /g [message] Displays a message to everyone in the group.
    /group promote (player) Promote player to group admin
    /group info Displays name of group and player/admins in your current group.
    /group leave Leaves curren group

    /chest add add's chest protection, so that only you and your group can open the chest.

    This would be an awesome system! :)


Share This Page