[BUG] sodium 0.8.7 breaks xray (easy fix)

[DiepCustom2025]

Pre-submission checklist

• I have searched through existing issues and confirmed this bug has not been reported yet.
• I have reproduced this on the latest development build.

LiquidBounce Branch

Nextgen

LiquidBounce Build/Version

likely all of them?

Operating System

Windows 11

Minecraft Version

1.21.11

Describe the bug

SodiumBlockOcclusionCacheMixin is applying a sodium class called BlockOcclusionCache which was removed and replaced with AbstractBlockRenderContext causing the mixin to not inject correctly This can be fixed quite easily however I personally don't think I can do it so I'll post it on here hoping someone else can. Meteor has made a commit fixing this but I don't think I can apply it to LiquidBounce as easily: MeteorDevelopment/meteor-client@1c7927f

Steps to reproduce

• Run any(?) version of LiquidBounce with Sodium 0.8.7
• Enable xray.
• See that blocks remain visible.

Client Log

Not necessary.

Screenshots

[DiepCustom2025]

MixinSodiumBlockOcclusionCache* not SodiumBlockOcclusionCacheMixin, I accidentally used the Meteor mixin in the initial report.

[localpthebest]

8.2 is the recommended version and it downloads that version if u use the launcher, should be easy to fix (but would prolly need izuna to move the default sodium version to latest). in the meanwhile u can just use an older version of sodium

[DiepCustom2025]

understood i just think there should atleast be a toggle within the mod to enable whatever the fix/workaround is for people who prefer newer versions of sodium, as I've noticed 0.8.7 gives me a much needed performance boost.

[localpthebest]

understood i just think there should atleast be a toggle within the mod to enable whatever the fix/workaround is for people who prefer newer versions of sodium, as I've noticed 0.8.7 gives me a much needed performance boost.

i think the correct way would be to detect the loaded sodium version but i have no clue how (or if its even possible) to do that