Updated Setting up the config file (markdown)

garbagemule 2014-11-23 14:39:42 -08:00
parent 1b152a9914
commit 1504b16999

@ -58,7 +58,7 @@ I recommended leaving the update notifications on, and disabling commands like `
## classes
The `classes`-section is slightly more complicated. It is divided into _class-branches_, where each branch denotes the _name of the class_, and each branch has mandatory nodes `items` and `armor`, as well as optional nodes `permissions`, `lobby-permissions`, `unbreakable-weapons`, and `unbreakable-armor`.
The `classes`-section is slightly more complicated. It is divided into _class-branches_, where each branch denotes the _name of the class_, and each branch has mandatory nodes `items` and `armor`, as well as optional nodes `price`, `permissions`, `lobby-permissions`, `unbreakable-weapons`, and `unbreakable-armor`.
**Note:** YAML is picky about how you type your items. Make sure you read the short [[Item Syntax]]-page and fully understand it before you attempt to modify the config file!
@ -81,6 +81,11 @@ The `classes`-section is slightly more complicated. It is divided into _class-br
Crusader:
items: iron_sword, hay_block:17
armor: 302,303,304,305
price: $5
### Price
The optional `price` node can be used to give classes a per-session price. When a player tries to pick a class that has a price, they will only be able to if they can afford it. The money is withdrawn when the arena starts, i.e. picking different priced classes in succession will not (necessarily) result in empty player wallets. In the example above, the **Crusader** class costs `$5`.
### Unbreakable weapons/armor