I have a custom pack I have been tailoring to fit my needs. As I have found Railcraft to be pretty much useless to me (especially with duplicate ores with their own unique IDs), I pulled it before starting a new world. The crash report below is the result when starting up Minecraft. When I re-add Railcraft, no error. Any clue what's going on here? Thanks.

http://pastebin.com/zZ1jyBk5

After further research, it seems that Mekanism actually requires the Buildcraft API to use pipes. Apparently Railcraft has this API built in, probably because CovertJaguar has his hands in it. So Mekanism can run fine without BC installed as long as Railcraft is there.

I installed Mekanism by itself to test this. Game loaded just fine, but as soon as I placed a pipe, I crashed. This should be noted in the wiki and adjacent source pages that it requires the Buildcraft API to be functional.

Kind of disappointed. I guess I will install Buildcraft. If you know of a workaround, I would like to hear it.

Old Mekanism version, please update.

@mcgraj3 You're using a very outdated version of Mekanism. That issue was fixed a long time ago.

EDIT: ninja

I just realized that there are newer versions on the download links on the wiki. I downloaded from the "Recommended downloads" buttons (7.1.1.127), but I neglected to see the newer versions below (my brain must have filtered them out as older versions). Please update those buttons. Thanks guys! :) 👍