Mineforgian
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.
- Загрузки
- 392
- Подписчики
- 3
- Обновлён
- 8 июля 2026 г.
- Лицензия
- MIT
Опубликован 4 июля 2026 г.
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.
The problem
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.
What this mod does
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.
Does NOT work on NeoForge yet.!!!!
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.
Features
- Dedicated chunk-builder thread pool, fully decoupled from vanilla's shared background executor
- Live-resizable — change the thread count mid-game and see the effect immediately
- Mod Menu + Cloth Config screen with tooltips
- In-game status command for active/queued task counts
- Sensible default, tunable up to 2x your core count for experimentation
Commands
/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 pool
on / 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.
Requirements
- Minecraft 26.2
- Fabric Loader 0.18.4 or newer
- Fabric API
- Java 25
License
MIT — source on GitHub.
Ченджлог
1.0.2Релиз26.1, 26.1.1, 26.1.2 · 8 июля 2026 г.
fixes version misorder
1.0.2Релиз26.2 · 8 июля 2026 г.
fixes version misorder
1.0.1Релиз26.1, 26.1.1, 26.1.2 · 5 июля 2026 г.
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.
1.0.1Релиз26.2 · 5 июля 2026 г.
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.
1.0.0Релиз26.2 · 4 июля 2026 г.
Initial release.
Gives chunk mesh building its own dedicated, live-resizable thread pool instead of sharing vanilla's background pool with worldgen and IO.
- /multicoremagic status|threads |on|off
- Mod Menu + Cloth Config screen
- Default thread count matches vanilla's own formula (CPU cores - 1)
Requirements: Minecraft 26.2, Fabric Loader >= 0.18.4, Fabric API, Java 25.
Комментарии
Загружаем…