Llywylln

Pointing out something in an Error log i've read isn't very helpful. My point is that build 230 wasn't crashing on an exception... the save version of mFC that I used with build 230 and is less than a month old will not work with any Forge build after 230. (I've tested it on 241,247,249,251,259) I don't know what v3xzz is doing in that class file, since I don't have a decompiler for Java (if I did I'd fix it myself) but since forge 230 worked with it and later versions don't, I have to ask myself what changed? I'll keep trying new versions until a forge version works or v3xzz fixes the code... -Llywylln

With the latest version of MC (1.3.2) I built my mod stack around Forge universal 4.0.0.230 and I have about 40 mods playing nice at the moment. Recently I nnoticed an odd bug, End Stone had become a second Blaze Powder in the Item ID list, and mining End Stone give you blaze powder. I decided to go back to vanilla and do incremental steps to locate the mod with the issue, turns out it's Forge. So, I thought, maybe I should upgrade to the latest version... So i did that and discovered that it still has the End Stone problem. Alas... Since I had upgraded, I dediced to pack in the rest of my mods, thinking that the new Forge would still work with them. No such luck. Two of them caused fatal errors: Runic Dust (wihich is so new I don't care) and Mo Food and Crops, which is too cool to lose. So ultimately I had to roll back to 230 to get it all working again. Still, I thought I might let folks here in Forge-land know about it so that it could be addressed, sometime. My Forge-client lot: I also noticed that the new Matmos requires Forge 4.0.0.249+ so I am hoping that this gets corrected. (I miss my env sounds) -Llywylln