ArmorMaterial identifier is not mod dependent
See original GitHub issueI just noticed that when registering new armor materials, their name is not an Identifier
.
This leads to the strange situation that when implementing own armor sets Minecraft will always search minecraft:textures/models/armor
for their 3d texture.
Shouldn’t Fabric API have an interface for this or at least gain the correct namespace by the item’s id?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
CustomTextures | Thunderstore - The Valheim Mod Database
This mod allows you to replace instances of game textures with custom png files. This mod should allow you to replace the following:...
Read more >Modding By Kaupenjoe: Fabric Modding for Minecraft 1-18-1
This course will teach you how to make your own Minecraft Mod! Not only learn the programming language Java but also how to...
Read more >[1.7.10] Rendering Techne item model. Texture not loading.
I have been making a small mod and I am trying to use a custom model ... public static ArmorMaterial Nature1 = EnumHelper....
Read more >Evaluation of silicon carbide as a divertor armor ... - OSTI.gov
Abstract. Silicon carbide (SiC) represents a promising but largely untested plasma-facing material (PFM) for next-step fusion devices.
Read more >Mod Monday : r/MB2Bannerlord - Reddit
FireReshadePreset (most important) not version dependent as it is an other program ... ChangeClanName usage no contains second identifier.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
See #963
This is still an issue in 1.19. While originally resolved in #963 with the armor texture API, it was never included in the 1.17 branch for some reason. Instead, it got replaced with a new armor rendering registry (#1607) that only lets you do fully custom rendering instead of just providing mod-dependent texture paths.