No. Its not Fixed. Outdated APIs
jztech101 opened this issue ยท 11 comments
http://pastebin.com/raw.php?i=VGhZsxzv - So further discussion with other mod devs has resulted in the conclusion that Mekanism appears to be using outdated COFH and BC APIs. @unpairedbracket
Oops. I was assuming we were up to date because we were about 3 days ago. I'll take a look at it
I can confirm that Mekanism 52 and EnderIO 136 work fine together. Still investigating...
And Mekanism 52, EIO 136 and EU1.1.0c are all working together no problem for me...
AE2 appears to do the same as we do to avoid shipping APIs of other mods. It has a soft dependency on Mekanism which changes the load order so that Mekanism gets loaded before EnderIO or ExtraUtilities. I think that it's because EnderIO and ExtraUtilities actually ship the BuildCraft and CoFH APIs that this is happening.
I've just discovered from the load order information that our BuildCraft dependency is a little off. I'll try and fix it now.
No, that didn't work. I'll try adding a (soft) dependency on EUtils and EnderIO to see if that fixes it. If that's the issue, it's really annoying...