... | @@ -18,7 +18,21 @@ And all of the generated files will be put into the `Generation/` folder inside |
... | @@ -18,7 +18,21 @@ And all of the generated files will be put into the `Generation/` folder inside |
|
The resulting resourcepack will be put in `../plugins/MythicMobs/Generation/resource_pack.zip`.
|
|
The resulting resourcepack will be put in `../plugins/MythicMobs/Generation/resource_pack.zip`.
|
|
|
|
|
|
## Merging
|
|
## Merging
|
|
A resource pack in `MythicMobs/Generation/merge` will automatically be merged into the generated pack, including any item overrides and atlases
|
|
A resource pack's assets in `MythicMobs/Generation/merge/assets/` will automatically be merged into the generated pack, including any item overrides and atlases.
|
|
|
|
```
|
|
|
|
MythicMobs
|
|
|
|
|-- Generation
|
|
|
|
|-- merge
|
|
|
|
|-- assets (.json or .bbmodel files, can use subfolders to organize)
|
|
|
|
|-- minecraft
|
|
|
|
|-- models
|
|
|
|
|-- textures
|
|
|
|
|-- pack.mcmeta
|
|
|
|
|-- pack.png
|
|
|
|
```
|
|
|
|
For example, `MythicMobs/Generation/merge/assets/minecraft/textures/item/diamond_sword.png` would override the vanilla diamond sword texture in your Crucible's pack output.\
|
|
|
|
Top-level elements, such as `pack.png` and `pack.mcmeta` can also be merged, but still require the asset folder present to activate merging even if it has no asset contents.
|
|
|
|
|
|
|
|
|
|
# Packs
|
|
# Packs
|
|
[Packs] can now contain an "Assets" folder with the following layout:
|
|
[Packs] can now contain an "Assets" folder with the following layout:
|
... | | ... | |