Updated Configuring mods (markdown)

Lukas Rieger 2021-01-16 15:33:18 +01:00
parent 253c55cdef
commit 5f6cf361fa

@ -2,7 +2,7 @@ If you render a world with custom blocks added by mods, BlueMap does not know ho
![Unknown block render example](https://pbs.twimg.com/media/ENeQqrbX0AElXmJ?format=jpg&name=large) ![Unknown block render example](https://pbs.twimg.com/media/ENeQqrbX0AElXmJ?format=jpg&name=large)
If you don't want that, you can try to add and configure the resources of those mods to tell BlueMap how to render those blocks. Unfortunately for 1.12.x this is not that easy. Here is how it works: If you don't want that, you can try to add and configure the resources of those mods to tell BlueMap how to render those blocks. **Unfortunately for 1.12.x this is not easy and very tedious.** Here is how it works:
## General ## General
@ -15,11 +15,11 @@ BlueMap will then load that mod like a resource-pack: Try to parse the block-sta
> **Info:**<br> > **Info:**<br>
> Some mods might use resource-formats that are not supported. *([Forge's blockstate.json](https://mcforge.readthedocs.io/en/1.14.x/models/blockstates/forgeBlockstates/) just has very limited support)* For this blocks to be rendered you will have to override the resources with alternative resources using the normal format. > Some mods might use resource-formats that are not supported. *([Forge's blockstate.json](https://mcforge.readthedocs.io/en/1.14.x/models/blockstates/forgeBlockstates/) just has very limited support)* For this blocks to be rendered you will have to override the resources with alternative resources using the normal format.
After that you might need to do some more configuration. Go through the chapters below and prepare the config files. After that it could already work! But especially on 1.12.2 you might need to do some more configuration. Go through the chapters below and prepare the config files.
## Configs ## Configs
### Block-id config ### Block-id config (1.12.2 only)
**File:** `blockIds.json`<br> **File:** `blockIds.json`<br>
**Example:** **Example:**
```json ```json
@ -53,6 +53,9 @@ Currently, there is no general way how to find this info, but here are some thin
### Block-properties config ### Block-properties config
> **Info:**<br>
> If there are no properties defined for a block, BlueMap looks at the model and "guesses" its properties. This is usually accurate and you can ignore this config.
**File:** `blockProperties.json`<br> **File:** `blockProperties.json`<br>
**Example:** **Example:**
```json ```json
@ -80,8 +83,6 @@ To render blocks correctly, BlueMap needs to know if a block is:
- `occluding` near blocks: This is basically used to determine if the block is "occluding" light when calculating the [ambient occlusion](https://en.wikipedia.org/wiki/Ambient_occlusion) on neighbor blocks. - `occluding` near blocks: This is basically used to determine if the block is "occluding" light when calculating the [ambient occlusion](https://en.wikipedia.org/wiki/Ambient_occlusion) on neighbor blocks.
- is `flammable`. This is currently only used in 1.12.x to calculate the appearance of fire. - is `flammable`. This is currently only used in 1.12.x to calculate the appearance of fire.
If there are no properties defined for a block, BlueMap looks at the model and "guesses" its properties. This is mostly accurate, but you can configure it in this config if you need to.
### Block-colors config ### Block-colors config
**File:** `blockColors.json`<br> **File:** `blockColors.json`<br>
**Example:** **Example:**