done

[loud mango]

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.

[solid lagoon]

asuming you are in 1.19.3 or newere:

!faq java-1.19.3-textures

[loud mango]

FAQ

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>

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>

[solid lagoon]

in your case you'd replace the two instances of the word custom with zephyr_texture

[solid lagoon]

does your game's output log throw any errors/warnings?

!faq output-log

[loud mango]

FAQ

Java: Output Log

The output log will show you errors related to resource packs in Minecraft: Java Edition. Here is how you can enable it.
(PS: Optifine likes to hide vanilla errors/warnings for some weird reason, so always load the game up without it if you don't need it for your pack to work!)
If you don't understand the errors/warnings feel free to show and ask about them (in a help channel).

[next snow]

No nothing

[solid lagoon]

it can't throw nothing but still show an error texture though

[next snow]

i think its because Im doing this process for my server

using a texture pack plugin (itemsadder)

[solid lagoon]

resource packs are still client side

even if it's a plugin that compiles the stuff into a pack

[next snow]

Shall I try it without optifine?

[solid lagoon]

yup

[next snow]

alr

here it is @solid lagoon

sec

[solid lagoon]

your texture is called asa.png but your model is looking for anan2.png?

also, could you enable normal messages too? sometimes there is important information in those too

[next snow]

02:20:57.703
ftn
Worker-Main-3
Missing sprite: minecraft:textures/asa.png

I can send the asa.json and its texture if you want

[solid lagoon]

I can't even remember seeing the term "missing sprite" in a warning before 🤔 (at least not for block/item moedls)

[next snow]

[solid lagoon]

actually, your problem is that those numbers aren't the same

change that to a "1" up there and it should work

and maybe also update the particle texture so the warning gets removed
(set it to the same thing as the "1" line)

[next snow]

oh

[next snow]

done

[solid lagoon]

@next snow you can keep the thread title as it was (makes it easier for others with similar problems to look it up)
to close a post use /close (as described in the very first bot messages of every thread)