You will need to add these nodes to your Permissions configurations if your server uses Permissions: False means that OwnBlocks must be activated manually by each player when they want to start building protected blocks. Default is 268, which is the wooden sword.Įnabled-on-login - True means that OwnBlocks is automatically activated for every player as soon as they log in. Default is 269, which is the wooden shovel.Īdd-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. 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. Now that I think of it, disabling status-messages seems like a really bad idea.but the choice is yours. Lastly, set this to 'disable' to disable messages entirely. Set this to 'simple' to receive a simple "OwnBlocks activated/deactivated" instead. Status-message - Set this to 'disable' to not receive the message " - OwnBlocks is now activated for you.". Players will not be able to place blocks if they have insufficient funds.ĭebug - 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' The number entered becomes the 'Basic Rate' at which players are charged to place protected blocks. IConomy - enter an integer greater than '0' (zero) to enable. 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. Username - the MySQL user with which OwnBlocksX will authenticate with the MySQL databaseĮxclude - enter comma separated integers of block-ids you wish to exclude from being protected and entered into the database. 'localhost' unless you are running the database on a separate serverĭatabaseName - name of the MySQL database you will use on the MySQL server Also remember that lines preceded by a '#' are comments, and are ignored. 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. If you are having problems, you may need to have the MySQL JDBC driver installed OwnBlocks is released under the WTFPL License. If you are upgrading from the test builds (OwnBlocksMySQL) then you need to rename your database table from OwnBlocks to OwnBlocksX.If you are using MySQL, the command is: toggle command is now /obx or /ownblocksx Permissions nodes are now OwnBlocksX.* (note the X) If you are migrating from OwnBlocks, you will need to convert your database unless you are starting fresh. Add (pre-placed) blocks to the database manually.Support for Permissions AND non-Permissions servers.Ability to exclude certain blocks from being protected.Blocks you place cannot be broken by others.See original plugin thread for more information Such features include MySQL support (completed), iConomy 5 support (completed), and group project support (in progress). OwnBlocksX is intended to add support for many features which may not be suitable for the original plugin. OwnBlocksX is a branch off the original OwnBlocks plugin.
0 Comments
Leave a Reply. |