Updated Home (markdown)

Home.md

@@ -1,13 +1,17 @@
 # NBT Mappings
-## Changing item and entity names
+Since 4.6.0, mapping files are stored in a new, compact format, so editing them has become slightly more difficult. The general editing process is as follows:
-Since 4.6.0, mapping files are stored in a new, compact format, so editing them has become slightly more difficult:
 1. Open the ViaBackwards jar (with a program like 7zip or WinRAR) and navigate to `assets/viabackwards/data`.
 1. Look for the mapping file you need, e.g. `mappings-1.19to1.18.nbt` for 1.19 -> 1.18 mappings and copy it into ViaBackward's plugin folder.
 1. Open the NBT file with an NBT editor program or website, for example https://irath96.github.io/webNBT/ or the [Minecraft Dev Plugin for IntelliJ](https://mcdev.io/).
-1. Look for `itemnames` and `entitynames`, edit the values you want to change, and save the file. Now ViaBackwards will load the file from its plugin directory if present.
+1. **Remove all the tags you do not want to modify so you won't have to update the file every time the original is changed in ViaBackwards**. Only the tags present in the NBT file you put into the plugin directory will be taken and merged with the original data.
+1. Say you want to edit item and entity names: Look for `itemnames` and `entitynames`, edit the values you want to change, and save the 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
+Follow the steps above.
 
 ## Adding custom model data
-Add a new compound tag under `itemdata`. 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:
 ```nbt
 	itemdata: {
 		"123": {