Posted July 3, 20196 yr Two of my texture files, item/hammer_iron.png and item/hammer_diamond.png are not found by Forge although they do exist at the specified paths: [Server-Worker-4/ERROR] [minecraft/AtlasTexture]: Using missing texture, unable to load deathcraft:textures/item/hammer_iron.png : java.io.FileNotFoundException: deathcraft:textures/item/hammer_iron.png [Server-Worker-5/ERROR] [minecraft/AtlasTexture]: Using missing texture, unable to load deathcraft:textures/block/worktable_side.png : java.io.FileNotFoundException: deathcraft:textures/block/worktable_side.png [Server-Worker-4/ERROR] [minecraft/AtlasTexture]: Using missing texture, unable to load deathcraft:textures/block/worktable_bottom.png : java.io.FileNotFoundException: deathcraft:textures/block/worktable_bottom.png [Server-Worker-2/ERROR] [minecraft/AtlasTexture]: Using missing texture, unable to load deathcraft:textures/item/hammer_diamond.png : java.io.FileNotFoundException: deathcraft:textures/item/hammer_diamond.png [Server-Worker-4/ERROR] [minecraft/AtlasTexture]: Using missing texture, unable to load deathcraft:textures/block/worktable_top.png : java.io.FileNotFoundException: deathcraft:textures/block/worktable_top.png (the block/worktable_ textures don't exist yet, so it's normal that they don't get found) Textures are placed in the src/main/resources/assets/deathcraft/textures/item folder, as they should according to the documentation. Also, none of my 4 recipes (including 2 of a custom type) seem to work within the game: no error messages related to them in the console, but nothing appears in the output slot when I attempt to replicate the patterns in a crafting table. All of my JSON files (models and recipes) are valid according to the several tests I did using a Node.js REPL — You'll find them attached if you want to take a look. hammer_iron.json hammer_diamond.json worktable_iron.json worktable_diamond.json hammer_iron.json hammer_diamond.json
July 3, 20196 yr Show a screenshot of your textures directory including full path. Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable. If you think this is the case, JUST REPORT ME. Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice. Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked. DO NOT PM ME WITH PROBLEMS. No help will be given.
July 4, 20196 yr Author Somehow, fixing the path to the recipe files (from assets/deathcraft/recipes to data/deathcraft/recipes) fixed the texture problem, but not the recipe one. So now the textures do appear, but the recipes still don't work.
July 4, 20196 yr I'm not 100% sure, but i think your problem is you are using the ore dictionary in your recipes. The new way to go about that is through tags. Some basic information can be found here https://mcforge.readthedocs.io/en/1.13.x/utilities/tags/#migration-from-oredictionary Hope it helps Edited July 4, 20196 yr by Cyborgmas
July 4, 20196 yr 13 hours ago, Algorythmis said: Somehow, fixing the path to the recipe files (from assets/deathcraft/recipes to data/deathcraft/recipes) fixed the texture problem, but not the recipe one. So now the textures do appear, but the recipes still don't work. That sort-of makes sense. Minecraft now expects server-side "assets" to be in a data pack, not a resource pack, and so recipes go in "data", not "assets". Possibly the model or blockstate loader was being confused by the recipe jsons with the same name as blockstates or items? That would be an interesting bug to suss out. 2 hours ago, Cyborgmas said: I'm not 100% sure, but i think your problem is you are using the ore dictionary in your recipes. The new way to go about that is through tags. Some basic information can be found here https://mcforge.readthedocs.io/en/1.13.x/utilities/tags/#migration-from-oredictionary Hope it helps What he said. You are using no-longer-supported ore dict entries with minecraft:shaped recipes, which never supported oredict recipes in the first place. All recipes are now "minecraft:something" and use tags to support what we used the old ore dictionary for. Just remember to add forge: domain tags for new ores and ingots if you add any. Stuff I maintain: https://minecraft.curseforge.com/members/sinhika/projects Repositories: https://github.com/Sinhika?tab=repositories
July 5, 20196 yr Author Yup. Forgot to post it here, but everything got fixed by switching to tags. Thanks to both of you.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.