Recipe conflict for Raw Cinnabar Ore in Crucible

[ALongStringOfNumbers]

Your GTNH Discord Username

alongstringofnumbers

Your Pack Version

Nightly 718

Your Server

private server

Java Version

Java 21

Type of Server

Vanilla Forge

Your Expectation

No warning about recipe conflict

The Reality

When starting a server, the following warning is printed about a recipe conflict

[17:14:04] [Server thread/WARN] [FindCrucibleRecipe]: Recipe CrucibleRecipe{key=PURECINNABAR,catalyst=[1xgt.metaitem.03@5826],output=1xitem.ItemNugget@21,aspects=1xMetallum;1xOrdo} ignored due to collision with CrucibleRecipe{key=PURECINNABAR,catalyst=[1xtile.blockCustomOre@0, 1xgt.blockores@826],output=1xitem.ItemNugget@21,aspects=1xMetallum;1xOrdo} for hash 2098103745

Your Proposal

No conflicting recipe

Final Checklist

• [X] I have searched this issue tracker and there is nothing similar already. Posting on a closed issue saying the bug still exists will prompt us to investigate and reopen it once we confirm your report.
• [X] I can reproduce this problem consistently by follow the exact steps I described above, or this does not need reproducing, e.g. recipe loophole.
• [ ] I have asked other people and they confirm they also have this problem by follow the exact steps I described above, or this does not need reproducing, e.g. recipe loophole.

[chochem]

I dont get anything in the log but yea I do see the recipe conflict

[chochem]

@Ethryan it looks like you added both recipes. so I guess you gotta decide which one you want more :P

[Ethryan]

On it… Tomorrow…

[Ethryan]

Hmm, this is a sign of a much larger error, since the code iterates over every valid GT material in search for metals to make into clusters. So every material even those already added by Thaumcraft, seems to be added here as a completely new cluster.