[BUG 1.43] Fireproof Rubber Trees

Quote from IcyPioneer

Hello there! Couldn't help but notice the Rubber Trees appear to be fireproof?

noticed the same recently when setting up a test world (burn all every tree!) and totally forgot to post it.

When I try to light IC2 rubber tree leafs on fire with a flint and steel I get this client side:

And a simple disconnection server side:

Let's try some other combinations...

Yeah, got this error from a fire block burning next to an IC2 rubber tree stump.

Quote from MJEvans

When I try to light IC2 rubber tree leafs on fire with a flint and steel I get this client side:

Display Spoiler

java.lang.NoSuchMethodError: wj.c(Lkq;III)Z
at acr.f(RenderBlocks.java:1374)
at acr.b(RenderBlocks.java:168)
at ge.updateRenderer(WorldRenderer.java:215)
at ge.a(WorldRenderer.java:91)
at afv.a(RenderGlobal.java:1452)
at adt.a(EntityRenderer.java:1050)
at adt.b(EntityRenderer.java:851)
at EntityRendererProxy.b(EntityRendererProxy.java:15)
at net.minecraft.client.Minecraft.x(SourceFile:738)
at net.minecraft.client.Minecraft.run(SourceFile:658)
at java.lang.Thread.run(Thread.java:722)
Stopping!
Exception in thread "Minecraft main thread" org.lwjgl.LWJGLException: X Error - disp: 0xe88040 serial: 39964 error: BadWindow (invalid Window parameter) request_code: 2 minor_code: 0
at org.lwjgl.opengl.LinuxDisplay.globalErrorHandler(LinuxDisplay.java:268)
at org.lwjgl.opengl.LinuxKeyboard.nSetDetectableKeyRepeat(Native Method)
at org.lwjgl.opengl.LinuxKeyboard.setDetectableKeyRepeat(LinuxKeyboard.java:152)
at org.lwjgl.opengl.LinuxKeyboard.destroy(LinuxKeyboard.java:163)
at org.lwjgl.opengl.LinuxDisplay.destroyKeyboard(LinuxDisplay.java:1015)
at org.lwjgl.input.Keyboard.destroy(Keyboard.java:349)
at net.minecraft.client.Minecraft.d(SourceFile:512)
at net.minecraft.client.Minecraft.run(SourceFile:675)
at java.lang.Thread.run(Thread.java:722)

And a simple disconnection server side:

Display Spoiler

java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:150)
at java.net.SocketInputStream.read(SocketInputStream.java:121)
at java.net.SocketInputStream.read(SocketInputStream.java:203)
at java.io.FilterInputStream.read(FilterInputStream.java:83)
at kf.a(SourceFile:136)
at oo.h(SourceFile:190)
at oo.c(SourceFile:10)
at wu.run(SourceFile:77)

Let's try some other combinations...

Yeah, got this error from a fire block burning next to an IC2 rubber tree stump.

Display Spoiler

Exception in thread "UpdateThread" java.lang.NoSuchMethodError: wj.c(Lkq;III)Z
at acr.f(RenderBlocks.java:1374)
at acr.b(RenderBlocks.java:168)
at ge.updateRenderer(WorldRenderer.java:215)
at UpdateThread.run(UpdateThread.java:115)

Display More

screwy, they just burned forever for me. Course I was setting this test world up in single player.

wj.c seems to be optifine. Optifine conflicts with Forge at this point. I heard there is a patch for this, but I don't know if you use it or if you use optifine at all.

Quote from Bluehorazon

wj.c seems to be optifine. Optifine conflicts with Forge at this point. I heard there is a patch for this, but I don't know if you use it or if you use optifine at all.

I checked the commit history for MinecraftForge. It looks like there was a fix for Optifine compatibility in the latest version, 1.24.

I do use optifine, but wasn't aware of an updated version. I wonder if that's also what allowed a creeper to glitch through my CF walls and then blow up. (of course I've seen them bouncing through stone as well, so /maybe/ it's not the CF but single-thickness; just that in the case of stone they get snapped back.)

Ahh it's a -Forge- 1.2.4 update:

Quote

Authored by lexmanos 2011-12-24
Tree
Parent(s): [r195]
Child(ren): [r197]
Changed Block.setBurnRate to public and Block.setBurnProperties
Re-added bounce functions to BlockFire for non-forge mods.
Should fix Optifine compatibility.

change /trunk/forge/patches/minecraft/net/minecraft/src/Block.java.patch (diff)
change /trunk/forge/patches/minecraft/net/minecraft/src/BlockFire.java.patch (diff)
change /trunk/forge/patches/minecraft_server/net/minecraft/src/Block.java.patch (diff)
change /trunk/forge/patches/minecraft_server/net/minecraft/src/BlockFire.java.patch (diff)

Display More

After updating to Forge 1.2.4 the game no longer crashes on trying to burn IC2 rubber trees, they simply refuse to catch fire. Very much like RP2 rubber-trees now.

well, you guys realise that if you use too many items, you cannot find the sprite for the rubber tree sapling and that the IC2-EE addon simply fails to load because of not finding rubbertree sapling thingy?

That's not TMI, that's a problem in the EE add-on. He put two p's in "sapling".

forge 1.2.4 modified how things burn (found out the hard way because it was incompatible with mods that say change the fire behavior back to the old infinite way)

I have had my rubber trees burn down, leaves and all, but I of course wasn't trying to cause it.
A lightning strike took out the wool roof on a nearby building and the fire spread to the nearby rubber trees.

I believe I still had 1.2.4 installed , but it was around the time I noticed the issue with it and nature overhaul, and so I reverted to 1.2.2

It is possible the roof started burning when I had 1.2.4 and the trees only when I reverted since I was in my workshop during the storm, I started having crashing issues and the logs showed issues with "can burn" repeatedly. So by the time I got the files fixed and popped my head out to see what the hell was burning everything was on fire.