I can't update from Mekanism 92 to 127 in my modded world.

My modded world was last saved in Mekanism 92. Everyting has been working pretty fine, except by the lag, no crashes. Now I tried to load my world on Mekanism 127, no other mod was updated, I'm getting "Exception in server tick loop" on LogisticalTransporter.

Log: https://gist.github.com/EzerArch/264487d4b28754e3cc0c

On the other hand, creating a new world with the same mods and Mek127 is ok.

This would have to originate due to an issue with the BuildCraft API - it's the only thing that TransporterPipeProxy implements. Do you have BuildCraft installed? If so, it's a conflict issue.

Just pushed something that should hopefully fix the issue, let me know if it does. Should be the latest build

Hi Aidan! It's a nice surprise to see you again.

Meanwhile I made a copy of my world and removed all Logistical Pipes from it (not a big thing) and then I managed to load the world. It crashed again when I attempted to place the Logistical Pipes back.

As to your question: I don't have BC installed in "mods" folder, but in a "_bkp" folder within "mods" folder (i.e.: .minecraft/mods/_bkp), it's where I keep old mods for legacy. Probably Mekanism or something else was trying to load other mods from the folders within "mods". If it is the issue I can remove all BC files, I haven't used them for a 2.5 forevers.

Let's see what happens...

EDIT: Oops, I hadn't seen your 2nd reply. Testing 128 right now.

Tried 128. I'm still getting "Shutting down server" if I try to place a Logistical Pipe, even in a brand new word.

https://gist.github.com/EzerArch/cc8d5d7ca9b9eba351cf

The line 32 says "Caused by: java.lang.NoClassDefFoundError: buildcraft/api/transport/IPipe" but I'm sure I removed all BC-related stuff from .minecraft/*.

Now I'll test Mek128 with no other mod and see what happens.

EDIT:

Removed all mods, MCPatcher and resource packs, and let FML download its libs again. Created a new world on creative and tried to place a Log pipe, and... crashed:

https://gist.github.com/EzerArch/f090a0340d72ae02e407

[turret]Aidan, are you still there?[/turret]

Sorry EzerArch! I fell asleep before I had a chance to read your response. It's great to see you here too.
@unpairedbracket is right, someone a BuildCraft API reference is bleeding through. I'll do a little search too see what I can find.

Edit: Yeah, I can't find any other references. This really is strange.

Just pushed another fix, build 129. Tell me if it works!

Try with BuildCraft (or at least their api) installed. We've not managed to properly isolate the new pipe stuff yet, apparently.

Maybe @Optional doesn't like nested classes?

New log (mek-only): https://gist.github.com/EzerArch/36b146b74c673a91236f

EDIT 14 hours later: tested 130, still crashes.

Nope. Still the same crash.

Yes, installing BC solves the problem.

Could you post your fml-client-latest.log please? I suspect the @Optional system isn't working quite as expected here.

Yeah, looks like FML isn't looking for @Optional on inner classes. I'll move it to its own file.

Worked. Thank you!