BTW+Optifine=Ladders don't work

[LordHumungus]

I don't know whether this should really your problem or the creator of Optifine's, but when I install both BTW and Optifine ladders no longer work, although they work just fine if I only install one of the mods.

[sargunv]

Moved to tech support.

[kaos78414]

The problem was with optifine. I had this problem when moving to 1.2.4 as well. Just use mcpatcher for now. Also, you might want to report this on the optifine topic at minecraftforums.net.

[destineternel]

I also encountered this. I posted on the optifine thread about it. Hope it gets a solution for now I'll stay with 1.23/3.57. :(

the output log shows something about 'pb.isLadder'

Spoiler

Show

OptiFine_1.2.4_HD_A
Thu Mar 29 10:04:49 PDT 2012
OS: Windows 7 (x86) version 6.1
Java: 1.7.0_03, Oracle Corporation
VM: Java HotSpot(TM) Client VM (mixed mode), Oracle Corporation
LWJGL: 2.8.3
OpenGL: AMD Radeon HD 6310 Graphics version 4.2.11566 Compatibility Profile Context, ATI Technologies Inc.
OpenGL Version: 4.0
OpenGL Fancy fog: Not available (GL_NV_fog_distance)
TextureFX registered: bv@1e304c4, texId: 11, index: 237
TextureFX registered: qa@dda258, texId: 11, index: 205
TextureFX registered: zp@cd7637, texId: 11, index: 14
TextureFX registered: tu@dbf94f, texId: 12, index: 54
TextureFX registered: ht@62ba82, texId: 12, index: 70
TextureFX registered: ael@1c2c498, texId: 11, index: 206
TextureFX registered: gf@1f9021e, texId: 11, index: 238
TextureFX registered: nh@fa0bdd, texId: 11, index: 31
TextureFX registered: nh@2109db, texId: 11, index: 47
TextureFX removed: bv@1e304c4, texId: 11, index: 237
TextureFX registered: TextureHDLavaFX@13b2835, texId: 11, index: 237
TextureFX removed: qa@dda258, texId: 11, index: 205
TextureFX registered: TextureHDWaterFX@cccdf4, texId: 11, index: 205
TextureFX removed: zp@cd7637, texId: 11, index: 14
TextureFX registered: TextureHDPortalFX@1e56319, texId: 11, index: 14
TextureFX removed: ael@1c2c498, texId: 11, index: 206
TextureFX registered: TextureHDWaterFlowFX@cd0da4, texId: 11, index: 206
TextureFX removed: gf@1f9021e, texId: 11, index: 238
TextureFX registered: TextureHDLavaFlowFX@3aaa32, texId: 11, index: 238
TextureFX removed: nh@fa0bdd, texId: 11, index: 31
TextureFX registered: TextureHDFlamesFX@17bbcd6, texId: 11, index: 31
TextureFX removed: nh@2109db, texId: 11, index: 47
TextureFX registered: TextureHDFlamesFX@aaa836, texId: 11, index: 47
TextureFX removed: tu@dbf94f, texId: 12, index: 54
TextureFX registered: TextureHDCompassFX@14471a3, texId: 12, index: 54
TextureFX removed: ht@62ba82, texId: 12, index: 70
TextureFX registered: TextureHDWatchFX@37fd8a, texId: 12, index: 70
Loading custom colors: /misc/grasscolor.png
Loading custom colors: /misc/foliagecolor.png
Class not present: LightCache
Method not found: forge.ForgeHooksClient.onBlockHighlight
Method not found: pb.isLadder

[Itamarcu]

Yeah, I noticed that a few days ago, actually, but this is probably due to the fact Optifine 1.2.4 is NOT OUT YET. Prereleases are not releases.

[destineternel]

so a user by the name of SevenEdges on the optifine thread on the MCF posted something interesting.

"Millenaire requires either Forge or its own 'lite' version of Forge (Sprite Extender, or simply the stuff in the 'place in minecraft.jar if forge absent' folder) to run. Now Optifine has native support for Forge, not the Sprite Extender, so If you drop Optifine on the latter, you will get the exact issues you're describing. Millenaire itself isn't the problem, just the API it uses."

[Gilberreke]

so a user by the name of SevenEdges on the optifine thread on the MCF posted something interesting.

"Millenaire requires either Forge or its own 'lite' version of Forge (Sprite Extender, or simply the stuff in the 'place in minecraft.jar if forge absent' folder) to run. Now Optifine has native support for Forge, not the Sprite Extender, so If you drop Optifine on the latter, you will get the exact issues you're describing. Millenaire itself isn't the problem, just the API it uses."

BTW uses the same API. The thing here is, is Optifine willing to abandon support for two of the major mods? They broke it, not Millenaire. Millenaire and BTW have been using the lite API for a few releases now and it's only the latest Optifine release that broke it.

[destineternel]

So optifine for 1.2.4/1.2.5 has been released. Ladders and vines are now climbable, BTW ropes are not. I would suspect that it is the forge compatibility support optifine has introduced in this version that breaks them. I'm not a coder so honestly that would just be speculation on my part. I've yet to use ropes to climb with but updating this thread for people.

[Stormweaver]

Guys, keep in mind that the infinite sprites that BTW and millenaire use were updated versions of the 1.2.3 forge, as opposed to being based off a 1.2.4 version (IIRC) so something like this is kinda to be expected.

Have to admit, I'm much happier having rope unclimbable than ladders though.

[MrMakrelli]

So optifine for 1.2.4/1.2.5 has been released. Ladders and vines are now climbable, BTW ropes are not. I would suspect that it is the forge compatibility support optifine has introduced in this version that breaks them. I'm not a coder so honestly that would just be speculation on my part. I've yet to use ropes to climb with but updating this thread for people.

They have some of the same class files though. I'm not sure how you got them to work at all. Which class files should I install last then? Sorry if this sounds like a noobish question, I'm quite new to this all, but it seems like if there were two mods with the same class files, some errors would occur when the one didn't exist. Please help.

[destineternel]

I always install optifine last as a general rule.

[MrMakrelli]

Cool, thanks. Managed to get it to work, though it seems to be running worse with Optifine for some reason. I'll figure out how to reduce this lag eventually. I'm not concerned for the graphics at this point, just want my few mods and as little lag as my laptop will allow.