Skip to content

CoFH Core

BonsUnleashed edited this page Oct 7, 2026 · 3 revisions

CoFH Core

Minecraft 1.20.1 / Forge: this page documents that build and its measurements. For the separate 170-control Minecraft 1.21.1 port, see Minecraft 1.21.1 NeoForge.

One control for CoFH Core 11.0.2 (mod id cofh_core), client-side: the translucent render pass asks only the entity types that have a translucent renderer. The switch checks the code it would change against the tested build; another build is left untouched with one WARN line (see How the patches are applied).

Key Target Side Since Kind
cofh_translucent_renderer_memo CoFH Core 11.0.2 CLIENT 1.0.28 opt

cofh_translucent_renderer_memo

Since: 1.0.28 · Target: CoFH Core 11.0.2 · Side: CLIENT · Kind: opt

Mixins: DispatcherRenderersAccessor, TranslucentRendererLookupMixin

CoFH translucent pass looks up only translucent types. After the particles of every frame CoFH Core asks the renderer of every client entity, only to keep the few whose renderer is one of CoFH's translucent ones. The entity types with such a renderer (and whether any player renderer is one) are now worked out once per set of renderers, and only entities of those types are asked; the rest are answered "not translucent", as their renderer would. This holds only while the game's renderer lookup is unchanged, so the switch checks after all mods are loaded that no other mod changed it, and otherwise leaves the pass alone (this pack: BadOptimizations, Friends and Foes and Vivecraft change it, so here the switch stays out of the way).

Measured: 7.2-12.5 -> 3.7-7.9 ns per entity per frame on real classes (2,000 entities: about 7-9 us per frame); 15,407 checks identical.

Bons and Furious

Minecraft 1.20.1 / Forge 1.0.34

Compatibility

Controls by mod

Links

Clone this wiki locally