-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Brick Furnace config doesn't let you exclude raw iron and raw gold as things to smelt. #30
Comments
Hey, thanks for your report! minecraft:iron_ingot If you added some recipes with Crafttweaker, you need to blacklist them, too. |
I'll copy and paste what my blacklist looks like. |
Oh yeah, it can still smelt the galosphere ingot, so maybe its something with non-food items...? |
And you are testing with a brick furnace, not with a brick blast furnace? The brick blast furnace recepies must be also blacklisted to be excluded there. please see the wiki: https://github.com/cech12/BrickFurnace/wiki#recipeblacklist-since-150 |
For the alexcaves mod, here is a list of all recipes: https://github.com/AlexModGuy/AlexsCaves/tree/main/src%2Fmain%2Fresources%2Fdata%2Falexscaves%2Frecipes To blacklist one, it should look like this: alexscaves:furnace/cooked_radgill_furnace |
Yes, only the base brick furnace. Does this mean that I cannot only make it to where the brick blast furnace can smelt iron and gold? It has to be blacklisted for both? |
thanks |
Hey, sorry the vanilla recipes changed in 1.20 The correct names for iron are: And for gold: |
Thank you so much! |
Minecraft Version
1.20.1
Forge Version
47.1.46
Mod Version
2.1.1.0
Modpack or other Mod
No response
Describe the Issue
Brick Furnaces cannot be made to exclude iron and gold from their recipes. I'm not sure if this is just the config being wonky or if it's a clash with craft tweaker, but I don't think it's the latter since I'm able to exclude all raw food items from being cooked.
Logs
No response
Do you use any performance-enhancing mods (e.g. OptiFine)?
No response
The text was updated successfully, but these errors were encountered: