Tips

Our collection of the best tips for Multipacks that we've found during internal use. Some of them are good (at least that's what we've thought) tips, so we've composed them into this wiki page.

The "Library Packs" model

Sometimes, you want to share your pack with other Multipacks users, and so there's something called "Library Packs". These packs are usually created without any post processing passes and mainly designed for others to use.

An example would be a collection of custom items in a form of Multipacks pack. Library users will have to include your library using include object, and then use custom-models with the from field points toward your library item models:

{
    "include": {
        "your-library": ">=1.0.0"
    },
    "postProcess": {
        "type": "custom-models",
        "from": "assets/your-library/models",
        "outOfSpace": [{"id": "minecraft:command_block", "start": 1, "end": 100000000}]
    }
}

Packs splitting

You can split your pack into multiple children packs (and include them as dependencies):

{
    "include": {
        "artifacts": "file:./masterofthestorm-artifacts",
        "weapons": "file:./masterofthestorm-weapons"
    }
}

An advantage is that you can initialize Git repository on each children pack and share it with your team (and only allowing several people editing part of your pack), or you can distribute those children packs as libraries (so others don't have to use delete post processing pass).