Updated Setting up the config file (markdown)

garbagemule 2011-08-23 01:50:52 -07:00
parent a7285d3f18
commit 2811dffe35

@ -55,7 +55,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 an `items`-node and an `armor`-node. These nodes specify which items and armor pieces each class has, respectively.
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 an `items`-node, an `armor`-node, and an optional 'permissions'node. These nodes specify which items and armor pieces each class has, as well as any extra permissions.
The items can be written as either their [data value/type id](http://www.minecraftdatavalues.com/js.php), or as their [Material name/type](http://jd.bukkit.org/apidocs/org/bukkit/Material.html). They are written in the form `<item>:<amount>`. If the colon and amount are left out, the amount will default to 1. In this example, the **Archer** gets a wooden sword, a bow, 128 arrows and a grilled porkchop from his `items`-node (in Material names), and leather armor from his `armor`-node (in data values). Conversely, the **Knight** gets only a diamond sword (note how if there is only _one_ item, that item _must_ be enclosed in apostrophes!), written in data values, as well as iron armor, written in Material names.
@ -63,6 +63,9 @@ The items can be written as either their [data value/type id](http://www.minecra
Archer:
items: wood_sword, bow, arrow:128, grilled_pork
armor: 298,299,300,301
permissions:
EffectiveArrows.use.*: true
mobarena.use.leave: false
Knight:
items: '276'
armor: iron_helmet, iron_chestplate, iron_leggings, iron_boots
@ -72,6 +75,10 @@ The items can be written as either their [data value/type id](http://www.minecra
I recommend using the data values, because it is much less prone to error. It is very easy to miss a letter or type a wrong name when using Material names.
### Class-based permissions ###
Using the optional 'permissions'-node, you can give classes special permissions to customize them even more. In the example above, the **Archer** class will be able to use the EffectiveArrows plugin, but won't be able to use `/ma leave` (meaning it's impossible to leave the arena without dying).
### Pet classes ###
For every bone (Material name: `bone`, data value: `352`) in a class' items-list, one wolf pet will spawn upon arena start. In the example above, every player that picks the **Wolf Master** class will have 2 wolves spawn upon arena start. The wolves are invincible, but deal less damage than normal wolves.