Upstream/ViaBackwards
1
0
Fork 0
mirror of https://github.com/ViaVersion/ViaBackwards.git synced 2024-11-28 13:15:24 +01:00
Code Issues Packages Projects Releases Wiki Activity

Updated Home (markdown)

EnZaXD 2024-04-29 00:50:27 +02:00
parent f9cd18276a
commit 71e6f6fe76
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
Home.md

@ -8,7 +8,7 @@ Since 4.6.0, mapping files are stored in a new, compact format, so editing them
Now ViaBackwards will load the file **from its plugin directory if present** and merge it with the rest from the original NBT mapping file. Now ViaBackwards will load the file **from its plugin directory if present** and merge it with the rest from the original NBT mapping file.
## Changing item and entity names ## Changing item and entity names
Follow the steps above. For 1.14+, follow the steps above.
## Adding custom model data ## Adding custom model data
As explained above, create a new NBT file in the plugin directory. Add a new `itemdata` compound tag. Similar to the `itemnames` field, the key is the registry id of the item (same as in the `itemnames` tag), the value in this case is another compound tag, which can contain a `custom_model_data` number tag. An example of this looks like: As explained above, create a new NBT file in the plugin directory. Add a new `itemdata` compound tag. Similar to the `itemnames` field, the key is the registry id of the item (same as in the `itemnames` tag), the value in this case is another compound tag, which can contain a `custom_model_data` number tag. An example of this looks like:
@ -29,6 +29,13 @@ You cannot easily edit these from the NBT mapping files. The human readable diff
We'd suggest simply creating a pull request to change the json file mappings if you think different mappings would be more suitable, so they can be changed in ViaBackwards proper. We'd suggest simply creating a pull request to change the json file mappings if you think different mappings would be more suitable, so they can be changed in ViaBackwards proper.
# JSON Mappings # JSON Mappings
## Changing 1.13- item and block mappings
Item/Block mappings are located inside different json files, e.g. ``1.12 mappings`` for ``1.11 clients`` are located in `item-mappings-1.12.json`.
You can move them into the plugin folder and directly edit them. Each json file can contain three different types of mappings:
- `items` for item mappings (raw id:raw data -> new id/data and custom name)
- `block-items` same as items but will only replace blocks
- `blocks` internal mappings to fix blockstate issues (mainly used in ViaRewind). DO NOT EDIT THESE UNLESS YOU KNOW WHAT YOU ARE DOING.
## Changing 1.16+->1.15 biome mappings ## Changing 1.16+->1.15 biome mappings
Similar to the mappings from above, you can move the `biome-mappings.json` file into the plugin folder and directly add mappings for custom biomes to map them to legacy biomes (the static biome names that existed until 1.15.2). Make sure to keep the file up to date with ViaBackwards updates. Similar to the mappings from above, you can move the `biome-mappings.json` file into the plugin folder and directly add mappings for custom biomes to map them to legacy biomes (the static biome names that existed until 1.15.2). Make sure to keep the file up to date with ViaBackwards updates.