Updated Configuration (markdown)

Configuration.md

@@ -56,6 +56,10 @@ webserver {
 - The `maxConnectionCount` field limits the max number of active connections that the web-server accepts simultaneously.
 
 ## Advanced
+
+> **Info:**<br>
+> If you change some of those settings, it is recommended to delete your previous renders *(delete the whole `web/data` folder)*. Changes will only affect newly rendered tiles!
+
 Bluemap also offers more advanced options for how to render your maps.<br>
 Here is an example of a map-configuration with all available fields used:
 ```yml
@@ -105,4 +109,9 @@ Here is the explanation for each of them:
 - Fields in the `lowres` object modify the low-resolution tiles. Those are the tiles you see if you zoom out on the map to get an overview.
   - This is a bit tricky now: The `pointsPerHiresTile` field defines the amount of low-res-points on a low-res-tile that each high-res-tile will occupy. So if the `tileSize` of the high-res tiles is `32` and the `pointsPerHiresTile` is `4`, each low-res-point will contain a `32/4 = 8` -> 8 * 8 chunk of your world. This is why you have to always choose values that result in an integer if you use that calculation!
   - The `pointsPerLowresTile` field is the amount of how many low-res-points each low-res-tile is wide.
-  - And finally the `viewDistance` defines the default amount of low-res-tiles the web-app will load at once in each direction. *(The view distance can also be adjusted in the web-app with a slider)*
+  - And finally the `viewDistance` defines the default amount of low-res-tiles the web-app will load at once in each direction. *(The view distance can also be adjusted in the web-app with a slider)*
+
+> **Important:**<br>
+> If you change `tileSize`, `pointsPerHiresTile` or `pointsPerLowresTile` you need to delete your previous renders! Delete the complete `web/data` folder! Otherwise you **will** get broken models.
+> 
+> *(Changing the `viewDistance`s is harmless to your existing models, you can do that at any time)*