MineMaarten / PneumaticCraft

PneumaticCraft source
Other
84 stars 50 forks source link

Crash on start-up #820

Closed Sir-Chi closed 8 years ago

Sir-Chi commented 8 years ago

When I load up the game it gets part way through the loading but then seems to crash. Here's the crash report hopefully you can work out what's causing this.

crash-2016-02-15_11.31.28-client.txt

MineMaarten commented 8 years ago

I have absolutely no clue. Stuff would've to be messed up real bad to even recreate this... The only thing I can think of is that the PneumaticCraft jar is tampered and the SemiBlockInitializer class is changed (to an older version perhaps).

It sounds like a really strange inter-mod problem, and because of the high amount of mods you have I really can't reproduce it. I'd suggest trying to reproduce it by first making sure you have a clean jar of PneumaticCraft, seeing if you have the problems still with just PneumaticCraft in the instance, and also by taking mods out of the mod set you had...

I'm really clueless here..

Sir-Chi commented 8 years ago

Okay thanks, i'll see what I can do. I'll be sure to let you know what i find & if I can fix it :) thanks for the reply anyways.

Sir-Chi commented 8 years ago

I managed to find the problem - it was with NHAVE's OmniWrench V3. For some reason the Lib & the mod itself are okay but the problem comes when I add the Integration module. It looks like it messes with the PneumaticCraft jar but I can't be sure. Here is another crash report but with only with NHAVE's mod. crash-2016-02-22_16.01.11-client.txt

Hope this helps. Thanks again S.C.

MineMaarten commented 8 years ago

Hmm, I'd suggest telling the author of that mod (with a link to this issue, possibly, so he can see my view/suspicion on the matter), that would be awesome

Sir-Chi commented 8 years ago

Okay I'll do that. Thanks again :)

nhave commented 8 years ago

With the V3 of my mod, i seperated the mod into a core and an integration module. With that i forgot to create an exeption for the dummy classes i had in my build.gradle. It should be fixed in V1.0.10 of the integration.

Sir-Chi commented 8 years ago

Yup can confirm it's all fixed. No more problems! Thanks guys. :)