Updated Setting up the config file (markdown)

Setting-up-the-config-file.md

@@ -13,6 +13,7 @@
 * [Overview](./Setting-up-the-config-file#an-overview)
 * [`global-settings`](./Setting-up-the-config-file#global-settings)
 * [`classes`](./Setting-up-the-config-file#classes)
+  * [Unbreakable items](./Setting-up-the-config-file#unbreakable-weaponsarmor-v096)
   * [Per-class permissions](./Setting-up-the-config-file#per-class-permissions)
   * [Pet classes](./Setting-up-the-config-file#pet-classes)
 * [`arenas`](./Setting-up-the-config-file#arenas)
@@ -88,19 +89,50 @@ The `classes`-section is slightly more complicated. It is divided into _class-br
             items: stone_sword, grilled_pork, bone:2
             armor: 298,299,300,301
 
-### Unbreakable items/armor (v0.96+)
+### Unbreakable weapons/armor (v0.96+)
 
 The optional `unbreakable-weapons` and `unbreakable-armor` nodes can be used to toggle on or off the unbreakability of class items and armor. The nodes _default to true_, so they are really only necessary if you want to toggle OFF the feature, i.e. if you want items to deteriorate and break! If that's what you want, set the nodes to false.
+<pre>
+classes:
+    FrailTank:
+        items: diamond_sword
+        armor: 310,311,312,313
+        <font color="blue">unbreakable-weapons: false</font>
+        <font color="blue">unbreakable-armor: false</font>
+</pre>
 
 ### Per-class permissions
 
 Using the optional `permissions`-node, you can give classes special permissions to customize them even more. Each permission must be listed with a dash (-) in front of it. If you want a class to _not_ have a permission, put a dash/minus at the very beginning of the permission node. 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).
+<pre>
+classes:
+    Archer:
+        items: wood_sword, bow, arrow:128, grilled_pork
+        armor: 298,299,300,301
+        <font color="blue">permissions:</font>
+        <font color="blue">- EffectiveArrows.use.*</font>
+        <font color="blue">- -mobarena.use.leave</font>
+</pre>
 
-(v0.96+) The optional `lobby-permissions`-node gives players special permissions while they are in the lobby _after they have picked a class_. This feature can be used e.g. in combination with a shop plugin and a base class that perhaps has nothing but a few potions.
+(v0.96+) The optional `lobby-permissions`-node gives players special permissions while they are in the lobby _after they have picked a class_. This feature can be used e.g. in combination with a shop plugin and a base class that perhaps has nothing (maybe except for a few potions).
+<pre>
+classes:
+    Basic:
+        items: ''
+        armor: ''
+        <font color="blue">lobby-permissions:</font>
+        <font color="blue">- shop.buy</font>
+</pre>
 
 ### 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.
+<pre>
+classes:
+    Wolf Master:
+        items: stone_sword, grilled_pork, <font color="blue">bone:2</font>
+        armor: 298,299,300,301
+</pre>
 
 ## 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: