Pack Making JSON Skins - DonBruce64/MinecraftTransportSimulator GitHub Wiki

No, this isn’t a new set of clothes for Steve. This is a new set of clothes for your vehicles instead. Skins are used to allow for cross-pack liveries to be added dynamically. In essence, what skins allow are for one pack to have a model with multiple definitions and liveries, and another pack to add-on their own livery to that model. For example: say a pack contains trailers. Rather than making their own trailer, packs can simply add skins to the trailers of the pack with them, forgoing the pain of making a model, a JSON, and doing updates. These skins will only be active if the pack containing trailers is present, and they will appear in the creative tab for that pack, which makes for a seamless addition and ensures players will see the new skins as they will be with the existing trailers. Skins inherit the definitions section, which acts as if those definitions were on the vehicle in the pack the skin is for. The only other parameters required for skins are in the skin section and tell MTS what item to apply the definitions to. They are as follows:

• packID – The packID of the vehicle/part/decor/etc. that this skin goes to.
• systemName – This is the registration name for the pack component that this skin goes to. Generally, this is the name of the JSON file for the component. If you don’t want to search for this value in a massive pack, you can always check the exported JSON file from devMode, as it contains this parameter.