Sodium mod and 3d textures

[trail peak]

Is it possible to create 3D textures on Sodium Mod? Does anyone know how or have a guide?

[broken crater]

Welcome to the help forum!

Please make sure to read #1029373817119838218 as it may answer your question!

Once your question has been resolved, please mark the post as closed by using the </close:1163944441741049897> command.

[silent pumice]

Define "3D textures"

[trail peak]

where

[silent pumice]

Explain what you mean by "3D textures"

[trail peak]

3d texture for item

mean stick

[silent pumice]

So a 3D model?
Or just an extruded texture like the default stick?

[trail peak]

I would like to make a magic rod for my npc. Something like this

But not optifine, but sodium

[silent pumice]

If you just wanna remodel an item you don't need any mods. You can do all that with a normal resource pack.

!faq export-vanilla-java-model

[broken crater]

FAQ

Java: Export Vanilla Models

IMPORTANT:
-Any missing folders need to be created if they aren't there yet!
-Do the steps in this exact order!

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

-Setting up your pack:
Create a folder inside Minecraft's resource pack folder (aka "YourPack" for the rest of this guide). 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 YourPack.
Optionally: Edit it in a text editor and adjust the value of "pack_format" (see https://minecraft.fandom.com/wiki/Pack_format). This only affects whether your pack is shown as "outdated" ingame or not.

Step 1: Saving Textures
Save all your textures first.
To do that either:
-Ctrl+S, or
-click 💾 next to the texture(s), or
-rightclick the texture(s) and click "Save As"
Save them directly within YourPack/assets/minecraft/textures/block/... or /item/....
Reason: If you don't do that or move/rename the files later your model won't find the textures anymore.
(For custom subfolders check !faq java-1.19.3-textures)

Don't use capital letters nor spaces in file/folder names. The model will be invalid ingame!.

Step 2: Exporting the Model
After saving the textures use File > Export > Block/Item export it to YourPack/assets/minecraft/models/item (or /block, but only for placed down blocks.).
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)

[trail peak]

!faq java-1.19.3-textures

[broken crater]

FAQ

Java: Java 1.19.3 Textures

General Information:
The game creates a "texture atlas" (combination of all textures into one file) for block/item models.
For performance reasons as of Java 1.19.3 the game by default only loads textures from within textures/item and textures/block (and any folders within those two folders) into that atlas instead of reading through every model for the relevant textures.

_________________________

Making the game load from custom directories
If you want the game to add textures from other directories (that are still somewhere within the "textures" folder) to that atlas you will need to create a blocks.json file in YourPack/assets/minecraft/atlases:

Example blocks.json

{
    "sources": [
        {
            "type": "directory",
            "source": "custom",
            "prefix": "custom/"
        }
    ]
}```
This example would make the game add _all_ textures that are within `textures/custom` to the atlas. This **even** applies to images that are not used by your models, so keep your pack clean for better performance and smaller size!.

**_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**Additional/more specific information**:
If you have several custom directories you can add several json objects in the "sources" list/array.
blocks.json's of different packs combine btw, so you don't need to worry that one pack will stop another pack from loading their textures.

Here is also an example pack from a Minecraft dev (boq) with some more specific examples (like only using the face part of the default pig texture instead of loading all entity textures or the whole pig texture): <https://cdn.discordapp.com/attachments/593812273164976166/1042452631743901756/sprites.zip?ex=65f1be2b&is=65df492b&hm=6b862c5f31049afecaa6c4a58c119b12e62d9c345dcb6482c77847a05ee30f30&>

The official blog post with the changes (you will have to scroll down quite a bit for the relevant information): <https://www.minecraft.net/en-us/article/minecraft-snapshot-22w46a>

[trail peak]

!faq default-pack