Upstream/BlueMap
1
0
Fork 0
mirror of https://github.com/BlueMap-Minecraft/BlueMap.git synced 2024-11-25 03:55:26 +01:00
Code Issues Projects Releases Wiki Activity

Updated Configuration (markdown)

Lukas Rieger 2020-01-11 19:35:42 +01:00
parent 4e9b75dde9
commit 1a0bde3864
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Configuration.md

@ -94,7 +94,7 @@ 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.
- 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 *(see: [ambient occlusion](https://en.wikipedia.org/wiki/Ambient_occlusion))*.
- `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: