How do i convert my models from 1.17 to 1.19

[wary meteor]

Hi, i made an entire model pack in the version 1.17 and they're supposed to be one of those items where when you rename it, they change to a different model.

I had to update it to 1.19 because everyone in my server that uses it really wants to update the game version, but they also want to keep the models. I changed the pack.mcmeta from 7 to 9 and expected for things to just convert fine but then i started to use the cits and uh

[severe goblet]

which 1.19 version are you using? 1.19.3 or a different one?

Actually, seeing how it's an error cube and not just the texture it seems to be more than just the texture location changes of 1.19.3 🤔

Does your output log throw any errors perhaps?

!faq output-log

[lavish silo]

The output log will show you errors related to resource packs in Minecraft: Java Edition. Here is how you can enable it: https://i.imgur.com/WbQZa6k.png
(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!)

[wary meteor]

ohh slr i just woke up

i'm using 1.19.3

[wary meteor]

i'm not using the official minecraft launcher so i dont know if i can see that

[severe goblet]

then use the official minecraft launcher for debugging purposes now and then once it's fixed you can use your special client again

[wary meteor]

okok wait lemme try that

[wary meteor]

i'm using the output log right now and i don't know what to do now though

[severe goblet]

do any errors or warnings pop up when you (re)load your resource pack?

[wary meteor]

wait a minute

there's something that's confusing aswell

so like i changed the pack.mcmeta to 9 yesterday and then it got converted fine and didnt show the resourcepack as an old outdated version

but now it's back to being outdated even though it's still 9

[wary meteor]

here's the output log

what on earth

i tried to rename it so that it'd change into the custom item but now it wont even show

[severe goblet]

your pack doesn't need to be a .zip btw.

[wary meteor]

oh it isnt

[severe goblet]

so you have a .zip somewhere then 🤔 ?

[wary meteor]

what

[severe goblet]

do you have Optifine installed?

[wary meteor]

wait whatt ahaha im so confused hold on

[wary meteor]

oh wait i'm using normal java minecraft

let me do that

oh wait but before i fix the cit stuff i also found a problem last night

this doesn't really need a cit but i fixed the textures in the .json

and it still won't work

[severe goblet]

well, also just found out (according to this person) that CIT is broken atm

[wary meteor]

ohh

aw i see

[severe goblet]

that's (most likely) because of atlas related changes in 1.19.3:

!faq java-1.19.3-textures

[lavish silo]

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>

[wary meteor]

ohh so do i make a folder called atlases and then put all the custom textures in there?

[severe goblet]

no

[wary meteor]

and also i think i'll just wait it out until optifine cit gets fixed

[severe goblet]

In the atlases folder you create one blocks.json that defines from where the game can load textures (besides textures/item and textures/block).
Those places still have to be within the textures folder ofc.

[wary meteor]

oo ic

so they have to be in the item or block folder if i don't wanna make a custom directory

[severe goblet]

(so the example in the bot message would allow the game to load textures from within textures/custom/...)

if you don't wanna make an atlases file, yes

[wary meteor]

do i still have to make an atlases file if it's within the block or item folder?

[severe goblet]

you can have custom folders within item and block without worries btw. (as long as the texture path in your model points there)

[wary meteor]

ooo i see

thank youu and i think i'll just wait until cit gets fixed