#How?

4 messages · Page 1 of 1 (latest)

nocturne umbra
#

with resourcepacks? Optifine CEM

#

unless you mean blocks, then that's CIT

slow scroll
#

!faq export-vanilla-java-model

timber roostBOT
# slow scroll !faq export-vanilla-java-model

(Result for "export-vanilla-java-models")
Disclaimers:
-This is a tutorial to get your item/block models into a normal Java Edition resource pack.
-Any folders that are mentioned need to be created if they aren't there yet!
-Do the steps in that exact order!

Step 0: Setup
In Blockbench:
Your project needs to be in the Java Block/Item format. (Check at File > Project... in Blockbench).
If it's not convert it via File > Convert Project. ATTENTION: This will break the model visually due to format specific restrictions! (see !faq java-rotation and !faq java-sizelimit)

-Your Pack:
Create a folder inside Minecraft's resource pack folder (will be referred to as "YourPack" for the rest of this tutorial). It is usually at C:\Users\INSERT_YOUR_PC_USER_HERE\AppData\Roaming\.minecraft\resourcepacks. Put this file https://cdn.discordapp.com/attachments/883449189533638777/899224109869846558/pack.mcmeta in there.

Step 1: Saving Textures
Save all your textures first.
To do that either:
-press Ctrl+S, or
-click on the save icon next to the texture(s), or
-rightclick the texture(s) and click "Save As"
Make sure to save them directly in any subfolder of YourPack/assets/minecraft/textures.
Reason: If you don't do that or move/rename the files later your model won't find the textures anymore.

Do not use any capital letters or spaces in file or folder names or they will be invalid for a vanilla client! (except for the pack's main folder).

Step 2: Exporting the Model
After saving the textures use File > Export > Block/Item and save the json file in YourPack/assets/minecraft/models/item (or /block, depending whether you replace an item in your inventory etc. or a placed block.).
Name the file based on the id of the thing you wanna replace (totem_of_undying for a Totem of Undying for example). Check the default pack if you are not sure what the exact name is (see !faq default-pack for more information)