UNU Template Pack

This template pack allows you to easily create your own vehicle skins and publish your own Immersive Vehicles skin pack!

The benefit of making a skin pack is that you don’t have to worry about stealing models, updating json files, or anything! All that is handled by the mod that has the original vehicle, you just make the skin!

This pack currently includes templates for the UNU Parts Pack, UNU Civilian Pack, with the original model textures I use to make different paint schemes and interiors! (which is why the textures are so funky)

How to set up your own Immersive Vehicles skin pack (video coming soon):

1. Decide on a packid, make sure it’s unique, all lowercase, and does not have any spaces.
2. Open the .jar (you can rename the .jar to a .zip, or extract it) and open the assets folder.
3. Rename the ‘unutemplate’ folder to your packid, then open this folder.
4. Open the packdefinition.json and fill it out (I suggest just changing packid and pack name)
5. Now you can make skins!

Making skins:

1. Figure out what vehicles you want to make skins for, and what pack it is from (for example, an UNU Rabbit from the UNU Civil Pack).
2. In your <packid> folder, you will see a folder called jsondefs, this is where your skin .json files are. These are the files that ‘code’ your skins.
3. There are also other folders in assets that correspond to UNU packs, like unuparts and unucivil. this is where your skin.png files will go.
4. If you open the jsondefs, then skins folder, you will see folders for each UNU pack. These are further organized just as they are in the various packs.
5. Find the skin jsons you want, and delete everything else (you can always get them later by redownloading this pack).
6. Do the same with all the template textures in the various other folders mentioned in step 3
7. Open the skin json file for the vehicle you want to make a skin for, you will see fields like “name” “subName” etc. The “name” is what you want the vehicle to be called in-game. The “subName” is the file name for your skin, like “_orange” or “_army”. This determines the suffix for your itemname and the filename of your skin. For example, if we made an orange skin for the UNU Rabbit, since the vehicle’s base name is “unucivil_vehicle_unu_rabbit_coupe”, and our skin name is “_orange”, the skin texture file will be named “unucivil_vehicle_unu_rabbit_coupe_orange.png”. I highly reccomend using a subName that is unique, or it may conflict with other skin packs!
8. The extraMaterials section defines crafting materials to make the skin (in addition to the base materials). I suggest making a skin of the paint can and defining your own paint.
9. The partTones define what color the parts will be (specifically, the definition’s subName). The first one is the wheels, the second is the seats, and the third is the licenseplate. Change them to “” to use the default.
10. You can repeat this one definition section to have multiple skins, so you could have two definitions, one for “_orange” and one for “_army”. I suggest opening an official pack to see how this is done since the dfinitions section is right at the top.
11. Once you have defined all your skins, use the template skins to easily make the skin files for your pack! In general, the purple is paint, yellow is carpet, pink is headliner, green/orange is secondary colors, and blue is interior. But make sure to check what colors align with the vehicle in-game!
12. Test it out (make sure you have the base pack or the vehicle won’t load), and upload it! You just made a skin pack without stealing anyone’s model! Make sure to mark whatever pack you used as a dependancy on Curse to make sure it gets downloaded!