Updated Setting up the config file (markdown)

garbagemule 2011-07-07 16:08:02 -07:00
parent ba370e1c5e
commit c8a518820c

@ -75,6 +75,10 @@ I recommend using the data values, because it is much less prone to error. It is
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.
### Subtypes (cocoa beans, bone meal, colored wool) ###
For items like cocoa beans, which are a _subtype_ of `ink_sack` (both items are dyes), an extra piece of data is required. Using the [data values](http://www.minecraftdatavalues.com/)-link, cocoa beans appear to have the data value 351. They also appear to have a _metadata value_ of 3 (subscripted to the right of 351). To grant cocoa beans to a class, use the notation `<item>:<metadata>:<amount>`, i.e. for 10x cocoa beans: `ink_sack:3:10` or `351:3:10` or even `ink_sack:brown:10`. Note that the amount is _required_ when using this notation.
## arenas ##
This section is by far the largest, and it is divided into several smaller branches. In the above example, `default` denotes the _name_ of the default arena. This name can be altered, but it must contain no spaces (use underscores instead). The arena name is significant when a server has multiple arenas and no Master Lobby (will be featured later). Let's go over the different branches: