Sounds like a Mekanism problem, but its an interesting issue:

If you have both UniDict-1.10.2-1.5 and industrialcraft-2-2.6.37-ex110 in your modpack, Dirty Iron Dust will not process in the Enrichment Chamber. Other dusts seem to work fine, tested gold, osmium, lead, copper,and tin all work fine.

With just IC2, no UniDict, no issues.
With just UniDict, no IC2, no issues.

Using the default configuration file for all mods.
Its the combination of both of these that seems to cause an issue, leaning towards UniDict because of the way that it changes the dusts.

Mekanism issue for referance

sorry for the late reply.
this is really weird, UniDict don't does anything with the Dirty dusts.

no worries, I can send you a testing instance if you would like, it's an odd issue surely. But my guess is that it has something to do with the interaction between the two mods.

thanks, but there is no need.
I think that after UniDict sort the entries, Mekanism is not recognizing the new entry and is not registering his own dirty dust, lol.

heh... I can code in JAVA, but I have little to no experience (alright, no) in how the minecraft ore dictionary works. Who needs to look at this? You or @aidancbrady?

Same issue. I had an issue logged with Mekanism but Aidan closed it out as crossmod problem. Glad to hear someone figured out WHAT is causing it but yes, curious who the fix request needs to go to as well.

Thanks

It may be UniDict fault, I'm going to do some rewrites in the next few days, may solve this issue, and sorry for how long took to I do something.

could you guys try with this? UniDict-1.10.2-1.8c.

1.7.10 release is coming soon.
edit: UniDict-1.7.10-2.9.1

Seems to be working for me now. Thanks for the quick support!

not so quick actually XD

Thanks for looking into it! :)

On Sep 6, 2016, at 10:48 AM, WanionCane [email protected] wrote:

It may be UniDict fault, I'm going to do some rewrites in the next few days, may solve this issue, and sorry for how long took to I do something.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

after some rewrites, was indeed UniDict fault, I'm really sorry...

No worries. Thank you for fixing it!! :)

On Sep 6, 2016, at 11:40 AM, WanionCane [email protected] wrote:

after some rewrites, was indeed UniDict fault, I'm really sorry...

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Nice, hope to see the new build soon. I am having the same issue and like to keep using unidict.