Create
Create copied to clipboard
No smelting for crushed silver
Describe the Bug
i can crush (occultism) silver ore using the Create crushing wheels but cannot smelt it
Reproduction Steps
- crush silver ore
- try to smelt it in any way
Expected Result
have the ability to smelt it into ingots with furnace or blast furnace and to be able to use bulk blasting and maybe even washing to get 9 nuggets
Screenshots and Videos
No response
Crash Report or Log
No response
Operating System
Windows 10
Mod Version
0.5.0c
Minecraft Version
1.18.2
Forge Version
40.1.51
Other Mods
No response
Additional Context
No response
Washing the crushed ore also fails, FWIW. I'm using Galosphere, which adds silver.
I've created a couple recipe JSONs for Galosphere. I'll upload them if the dev's (or you) want them.
Can confirm, still a problem in 1.19.2.
I am a bit confused on this. Base create only has Iron, Gold, Zinc, and Copper as crushed ore. What adds the Silver? Ah, occultism. Perhaps they need to adjust something if the others work fine?
The question id say is who added the recipe for the crushed version and recipe of silver since crushed ores in general is a create "thing"? I'm just guessing but I don't believe that occultism is the one responsible for that part.
I tacked on the confirmed label since Create does add compat recipes for crushed ore -> ingot for other mods adding silver.
I assume that compat would work through tags, right? I doubt it would be a regex on the item name.
Tag outputs aren't a thing sadly (crushing into crushed ore is indeed done by tags) (and even more sadly I don't think Mojang will ever add those as they'd have no need for them) so we have a specific recipe per mod that we have ootb support for Example: https://github.com/Creators-of-Create/Create/blob/mc1.20.1/dev/src/generated/resources/data/create/recipes/blasting/silver_ingot_compat_galosphere.json But they do kinda have to come as community submissions; the team can't be expected to scour curseforge/modrinth for any mod adding a compat metal.
Oh... That is quite a chore.
Still an issue in 6.0.6!
Yes we are aware, hence the issue still being open.
Just a bit worried because it happens to lead too, and another similar issue about that was marked closed.
I'll take care of this