Multicore Magic
Gives Minecraft's chunk mesh building its own dedicated, tunable thread pool — so chunk loading doesn't compete with worldgen and other background tasks for CPU cores.
Список изменений
NeoForge compatibility via Launchpad + port to Minecraft 26.1.2
The same mod now ships as two Fabric jars, one per supported Minecraft version:
- multicore-magic-fabric-26.2-1.0.1.jar - Minecraft 26.2
- multicore-magic-fabric-26.1-1.0.1.jar - Minecraft 26.1.2
Both opt in to Launchpad (https://github.com/Sinytra/Launchpad) via "launchpad:compatible": true in fabric.mod.json, letting them load unmodified on NeoForge - no code changes, no separate build. Each also ships a NeoForge placeholder (META-INF/neoforge.mods.toml) so installing the jar on NeoForge without Launchpad gives a clear "missing dependency: launchpad" message instead of "invalid mod".
NeoForge status:
- 26.1.2: works today. Launchpad has 26.1.2 builds - install Launchpad + Forgified Fabric API (https://github.com/Sinytra/ForgifiedFabricAPI) alongside the fabric-26.1 jar.
- 26.2: not yet. Launchpad has no 26.2 release upstream yet. The fabric-26.2 jar is ready the moment that changes, but can't be loaded on NeoForge 26.2 today.
The Mod Menu config screen remains Fabric-only either way; /multicoremagic commands work identically on both loaders.
Why two jars were needed
Mojang renamed the method this mod hooks into between the two Minecraft versions - allChanged() on 26.1.2 vs invalidateCompiledGeometry(...) on 26.2 - confirmed by decompiling both real client jars, not assumed. Both redirect the same Util.backgroundExecutor() call site inside that method, so only a small per-version mixin differs; everything else (config, thread pool, commands, Mod Menu screen, metadata) is fully shared source.
Verified: both modules build cleanly, and a runClient smoke test on the 26.1.2 build confirms the renamed-method mixin actually applies at runtime with no Mixin errors.
Requirements per jar: matching Minecraft version, Fabric Loader >= 0.18.4, Fabric API, Java 25.