Configuration
Most of the configs generated are meant to be maintained by the server. With this being said, there are still some that should be changed by the player.
First: config.yml
General: #Wand item ID. Blaze rod at first. wand: 369 #The name of the wand item wandName: '&aHouse Wand' #The name of the deed item deedName: House Deed #The key item id. Gold nugget at first. keyItemId: 371 #Does not work. Planned for a future update. checkForUpdates: false Homes: #Should POH overwrite homes if a new one of the same name is created overwriteSameNames: true #Can players place blocks in the home world? buildInHomesWorld: false #Can players break blocks in the home world? breakInHomesWorld: false #Only allow players to build inside of their home buildOnlyInsideOfHome: false #The radius around the door that counts as 'inside of their home' insideOfHomeRadius: 10 #If true, a player will not be allowed to break blocks that came with the home, and will only be able to break blocks placed by players. staticHomeBlocks: false #Placed blocks will only be breakable by the player that placed them. playerBasedBlockLock: false #Should POH try to find a spawn block inside of homes? lookForSpawn: false #What radius should POH search in for the above lookForSpawnRadius: 10 #What block should the spawn search target. Set to sponge at first. spawnBlockId: 19 World: #The name of the home world. name: Homes #Should the home world be generated empty? Setting this to false will generate a flatgrass map. Setting it to true will generate nothing as a floor. empty: true TimeLock: #Should the POH world be locked to a set time? enabled: true #What time value should the world be locked at. Only use values from 0 to 24000. toValue: 6000 #How many blocks of spacing should be between each home displacement: 128 #What is the maximum value that POH should place homes at on the Z axis. MaxZ: 10000 #What is the minimum value that POH should place homes at on the Z axis. MinZ: -10000 Invite: #Should invites be removed after they are used? consumeOnUse: true #The name of an invite that has not been finished unsetName: '&7Incomplete Invitation' #The name of a finished invite setName: Invitation #Can a player use an invite even if the owner is offline? enterWithoutOwnerOnline: false Keycard: #The name of a keycard that has not been finished unsetName: Blank Keycard #The name of a finished keycard setName: Keycard Econ: #Should the block economy be enabled? enabled: false #How many blocks should each player start out with? startingBlocks: 25 Buyback: #Can players sell blocks to the server? enabled: false #How much should the server pay the player for each block? pricePerblock: 5 SellToPlayer: #Can players buy blocks from the server? enabled: false #How much should the server charge the player for each block? pricePerblock: 10 #Do not modify this. currX: 0.0 #Do not modify this. currZ: -9872.0
Now you can change three other things! These are found within the Recipes folder
invite.txt is a shaped recipe, so the items must be formated as such
SSS PPP SSS P PAPER S STRING
The first three rows are the shape that the recipe will use. Almost any symbol can be used in these spots if there are only three per row. After the first three you must define what each symbol means. For instance, on the fourth line the config tells the plugin that it's going to define the symbol 'P'. Then, there is a word that defines what material should be put in all the P spots of the crafting table. The same is repeated with S. This file controls the recipe for invites
- - - - - - - - - - - -
keySR This is a shapeless recipe, so all you must do is write out the materials used in the recipe (one per line) in the file. Here is an example
STICK GOLD_NUGGET
This will make a recipe in the crafting table that uses one stick and one gold nugget. To add another gold nugget, simply make a new line that says "GOLD_NUGGET". This file sets the recipe for new keys
- - - - - - - - - - - -
keycard.txt
is a shaped recipe, so the items must be formated as such
SSS PPP SSS P REDSTONE S STONE
The first three rows are the shape that the recipe will use. Almost any symbol can be used in these spots if there are only three per row. After the first three you must define what each symbol means. For instance, on the fourth line the config tells the plugin that it's going to define the symbol 'P'. Then, there is a word that defines what material should be put in all the P spots of the crafting table. The same is repeated with S. This file controls the recipe for keycards
Comments