BuildCraft|Core

BuildCraft|Core

7M Downloads

This crash happened but makes no sense at all.

Opened this issue · 3 comments

commented

[B#434] Time: 2/19/14 7:42 AM
[B#434] Description: Ticking Particle
[B#434]
[B#434] java.lang.ClassCastException: net.minecraft.block.BlockSandStone cannot be cast to net.minecraftforge.fluids.BlockFluidBase
[B#434] at buildcraft.energy.render.EntityDropParticleFX.func_70071_h_(EntityDropParticleFX.java:100)
[B#434] at net.minecraft.client.particle.EffectRenderer.func_78868_a(EffectRenderer.java:79)
[B#434] at net.minecraft.client.Minecraft.func_71407_l(Minecraft.java:2051)
[B#434] at net.minecraft.client.Minecraft.func_71411_J(Minecraft.java:953)
[B#434] at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:870)
[B#434] at net.minecraft.client.main.Main.main(SourceFile:103)
[B#434] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[B#434] at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
[B#434] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
[B#434] at java.lang.reflect.Method.invoke(Unknown Source)
[B#434] at net.minecraft.launchwrapper.Launch.launch(Launch.java:134)
[B#434] at net.minecraft.launchwrapper.Launch.main(Launch.java:28)

Looking at the code, it doesnt even MAKE that cast, and only does some instanceof checking. There may have been a change making the line be different, but there is no BlockFluidBase in there, just IFluid or whatever. This is on a client with JUST buildcraft, iron chests, and custom npcs and I was just making designs with oil/fuel and water/lava far away from anything else so there is an extremely low chance of conflict. I was also on a server, although that shouldn't effect anything.

Because of the oddness of this issue, I put it under investigate rather then one of the bugs.

commented

please post your crash at http://mod-buildcraft.com/forums/index.php?board=2.0
the issue tracker is for problems that are beïng worked on

commented

Well, that's a dumb system...

commented

I understand that no system is ideal. I hope you won't mind interacting with us on the forum on this. FWIW, this is a 5.0.0 problem reported there already, supposed to be fixed in 5.0.1, which is probably why it looks odd.