Optifabric and Optifine + Fabric API = Crash

[hiihavenolife]

I've researched the problem extensively, and it appears that the root cause lies within OptiFabric rather than Optifine or Fabric API. This situation is rather disheartening, given that it's puzzling to fathom why a mod would be developed without compatibility with Fabric API, an essential component utilized by nearly every Fabric mod. Presently, I'm utilizing the most up-to-date versions of Optifine, OptiFabric, and Fabric API.

I'm interested to ascertain whether the mod's creator is already aware of this issue. It's noteworthy that instances of this problem have been documented as far back as 2021, yet a resolution hasn't been implemented thus far.

[brimdaddy69]

same its so annoying bro

[TheUnknownCod3r]

Duplicate of #1123 and a fix is in the works in #1179

use 0.85.0

[XXMA16]

@hiihavenolife Using pompous language doesn't mean much when you don't know shit about what you're talking about...

I've researched the problem extensively

It takes 30 seconds to look that there are like 23 issues open regarding the same bug, yet you did not bother to check. On top of that, I created a pull request (see #1179) to fix this issue and you can find the build artifacts here.

it appears that the root cause lies within OptiFabric rather than Optifine or Fabric API

Optifine breaks shit, who would have thought? To be clear, Optifabric's job is to load Optifine (replace vanilla classes with whatever Optifine does to them) and to fix the inevitable issues that arise from Optifine's fuckery, which is hard because Optifine is close-sourced.

it's puzzling to fathom why a mod would be developed without compatibility with Fabric API, an essential component utilized by nearly every Fabric mod

It's pretty damn easy to figure out that Optifabric can't predict what will break in the next Fabric API update, but alas you choose to ignore the obvious and blame the developer for not predicting the future.

It's noteworthy that instances of this problem have been documented as far back as 2021, yet a resolution hasn't been implemented thus far.

Every single update has the potential (and most likely will) break when Optifine is involved, thus the issue needs to be reported (preferably not 23 times, one report suffices, but reading is hard) in order to be fixed. If you want something that doesn't break when you look the wrong way at it, try Sodium if you just want the performance benefits or Fabulously Optimized if almost all of Optifine's features. Do note however, that there are systems, although not many, which run better with Optifine than with Sodium, but within the Fabric community it's almost universally accepted that Optifine shouldn't really be used because of the plethora of hard to fix compatibility issues.