Gives Minecraft's chunk mesh building its own dedicated, tunable thread pool — so chunk loading doesn't compete with world generation and other background tasks for CPU cores.
Vanilla builds chunk render meshes on a thread pool it shares with world generation, structure searches, and other misc background work. The pool is sized automatically to CPU cores − 1, but every one of those threads is also up for grabs by worldgen — so chunk building is constantly competing with everything else for the same cores, especially noticeable when flying or exploring new terrain quickly.
Multicore Magic redirects chunk mesh building to a separate, dedicated pool that nothing else touches, so it no longer contends with worldgen or IO. The pool is fully configurable and can be resized live, in-game, with no restart required.
A note on scope: this mod does not — and cannot — make the entire game "multicore." Minecraft's core tick loop is intentionally single-threaded and can't be safely parallelized wholesale. This mod targets one specific, real bottleneck (chunk mesh building) the same way mods like Lithium or Starlight target specific subsystems, rather than promising generic multithreading of the whole engine.
This mod ships metadata to run on NeoForge via Launchpad, but Launchpad itself currently only has builds for Minecraft 26.1.2 — there is no 26.2 release upstream. Since this mod targets 26.2, it cannot actually be loaded on NeoForge right now, regardless of what you install. This is not a bug in this mod; it's waiting on Launchpad to add 26.2 support.
Once Launchpad releases a 26.2 build, NeoForge users will need:
Launchpad (loads this Fabric jar directly, no separate build) Forgified Fabric API in place of regular Fabric API The Mod Menu config screen will still not be available on NeoForge (Mod Menu is Fabric-only), but all /multicoremagic commands will work the same. Check Launchpad's releases for current status before attempting this.
/multicoremagic status — shows enabled state, thread count, active/queued tasks/multicoremagic threads <n> — resizes the pool live, no restart needed/multicoremagic on — enables the dedicated pool/multicoremagic off — disables it, falling back to vanilla's shared poolon / off take effect on the next world join or resource reload (F3+A); threads applies immediately.
The default thread count matches vanilla's own formula (CPU cores − 1). The slider goes up to cores x 2 for experimentation, but pushing it too high alongside vanilla's own worldgen pool can cause oversubscription (both pools competing for the same cores) under heavy load like flying through new terrain — dial it back if you notice stutter after raising it.
MIT — source on GitHub.
