Updated Configuration (markdown)

Configuration.md

@@ -58,12 +58,14 @@ Bluemap offers a lot more options to render your maps. Here is a more advanced e
 ```yml
 maps: [
    {
-      id: "world"
-      name: "World"
+      id: "my_world"
+      name: "My World"
       world: "world"
+
       renderCaves: false
       ambientOcclusion: 0.25
       lighting: 0.8
+
       minX: -4000
       maxX: 4000
       minZ: -4000
@@ -71,6 +73,7 @@ maps: [
       minY: 50
       maxY: 126
       renderEdges: true
+
       hires {
          tileSize: 32
          viewDistance: 4.5
@@ -82,4 +85,11 @@ maps: [
       }
    }
 ]
-```
+```
+- If `renderCaves` is `false`, bluemap does not render any face that has a sun-light/sky-light value of 0. This removes unnecessary geometry and improves render-speed and most importantly the web-client performance by **a lot**! It might however sometimes remove faces you would see from above, e.g. the bottom of oceans or the wall below a big overhang.
+- The `ambientOcclusion` field controls the amount of "shadow" you see in corners. This gives the geometry much more depth, but has a small impact on render-time.
+- `lighting` uses the light data from minecraft to make blocks with lower light-levels darker. Despite it's name, `lighting` defines the amount of "shadow" that is added, so a value of `0` makes every block fully lit.
+- The fields `minX`, `minY`, `minZ`, `maxX`, `maxY` and `maxZ` define the "bounds" of the rendered world. So if you only want to render a specific area of your world you can do this here. With the y-fields you can also render only blocks in certain heights. You can use that to - for example - remove the ceiling of the nether to be able to see the lower areas in the render.
+- If you limited the bounds of your map with the fields above, you can use the field `renderEdges` to define how those "edges" of your map will be rendered. This is best explained with an example:
+
+![renderEdgesOnOff.jpg](https://bluecolored.de/paste/renderEdgesOnOff.jpg)