Open 2.4.2: 2.5.0 : Crash in the Nether

[ExDomino]

Version:
2.4.2

What is the bug:
On my server, we somtime crash in the nether. It's always at the same coordonate, and do a /back will cause a new crash after few moment. The crash is client-side only, the server doesn't crash.

advsolar.common.blocks.BlockAdvSolarPanel.func_149673_e(BlockAdvSolarPanel.java:144)

PS : You should add "2.5.0" in the "Version" field.

Mod & Version:
MC 1.7.10 - Infinity 2.5.0 Normal

Paste.feed-the-beast.com log:
http://paste.feed-the-beast.com/view/74ca6760

Can it be repeated:
Each time you go to the same coordonate in the nether, you'll crash again!

Known Fix:
Unknown.

 

[Booker The Geek]

Remove fast craft.

Report the bug to fastcraft.

 

[ExDomino]

We're still crashing without Fastcraft, same error.

 

[Robijnvogel]

That this is caused by Advanced Solars is clear to see.
Sadly, I can not find that mod's source code, so I can't see what exactly goes wrong at "line 144".

There are other people with the same problem though.

EDIT: More other people.

 

[Booker The Geek]

@ExDomino please upload the crash report without fast craft in it.

 

[Robijnvogel]

Something that seemed completely unrelated, but at some point produced an AOoBE in Advanced Solars as well.

 

[Booker The Geek]

Interesting. Would still like to see the next crash without fast craft but most likely is as you say...

That being said might be a simple fix.

 

[Robijnvogel]

@ExDomino, is there an advanced solars item or block, that has 13 different metadata states?
For example item ID 1:0 up to 1:12 ?

Just fishing for an explanation here.

Edit, actually yes. I have just confirmed this myself. All non-helmet Advanced Solars items share one id. Sunnarium (meta 0) through quantum core (meta 13).

Then "java.lang.ArrayIndexOutOfBoundsException: 13" should not occur though, since meta 13 does exist...

I'm in a bind here. It looks too much like the other issue I just referenced, to not be connected, but it just doesn't fit exactly the same pattern.