versions:
minecraft: 1.12.2
forge: 2703
Rcore: 3.8.3.279
TR: 2.15.9.663

crash report: here

seems to have to do with ingotRuby, perhaps because I have just added projectRed to my pack, and that might have to do with the Ruby issue, but im not entirely sure.

there shouldnt be a ingotRuby, it should be gemRuby. I will look into finding a way to fix this.

Btw removing project red does not fix this, and also in my pack there should actually be an ingotRuby because I added ruby as a base material just for now, so that might have to do with the bug instead.

ok, i found the issue. My pack uses custom items that are added by BASE, and for now I have added a set of materials for every metal in the game, which is clearly a bad idea, but the point is, if you run this script with base, contanttweaker, crafttweaker, and tech reborn, then you will get this same issue. Hopefully that can clarify things about the issue

Im not sure if its an issue with your script or the mod you are using, but the ruby is being registed as an ingot and not a gem.

Ok, im going to close this as I think it is an issue with the script you are using. Try not to add ruby as an ingot because it isnt one.

but what i don't understand is that why does this mod of all mods interact with something like that now? Is there anything in your code that handles oredict "ingotRuby"? because before i totally was able to get away with this for months, and now i don';t understand why it crashes. Was something reimplemented with oredict recently? This scirpt is fine, the item gets registered, but i don't get why your mod should interact with that when it does