#removed
13 messages · Page 1 of 1 (latest)
Question '1.19.3' not found!
!faq 1.19.3-textures
(Result for "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>
You can move your textures into assets/realms/textures/item/weapons/swords... and it'll work without the atlas json
With the custom namespace, you also shouldn't have to worry about potential issues with other resourcepacks.
Though, I'd recommend a more unique namespace.
realms has a high risk of being used by others too.
Assuming that it's for a server, I wouldn't worry to much about it, but there's always the chance that players have another pack with the namespace.
numbers are fine iirc, a-z, 0-9 and _
generally I'd likely go with the full server name.
The more unqiue the namespace is, the smaller the risk of packs conflicting.
(Unlike the popular approach of just throwing stuff into assets/minecraft/textures/custom/ which you can usually see here once a day)