为 Minecraft 的区块网格构建提供独立的、可调节的线程池——使区块加载不再与世界生成及其他后台任务争夺 CPU 核心。
问题所在
原版游戏在一个共享线程池中构建区块渲染网格,该池同时用于世界生成、结构搜索和其他杂项后台工作。此池的大小自动设置为 CPU 核心数 − 1,但这些线程中的每一个也随时可能被世界生成占用——因此区块构建始终与其他任务竞争相同的内核,在快速飞行或探索新地形时尤为明显。
模组功能
Multicore Magic 将区块网格构建重定向到一个单独的专用池,其他任何任务都不会使用它,从而不再与世界生成或 I/O 争抢资源。该池完全可配置,并且可以在游戏中实时调整大小,无需重启。
关于范围的说明: 此模组不会、也无法让整个世界游戏“多核化”。Minecraft 的核心 tick 循环故意采用单线程设计,无法安全地整体并行化。本模组针对的是一个特定的真实瓶颈(区块网格构建),其方式类似于 Lithium 或 Starlight 针对特定子系统的工作方式,而非承诺对整个引擎进行通用的多线程处理。
尚不支持 NeoForge!!!!
本模组通过 Launchpad 发布元数据以在 NeoForge 上运行,但 Launchpad 本身目前仅有 Minecraft 26.1.2 的构建版本——上游尚无 26.2 的发行版。由于本模组面向 26.2 版本,无论您安装什么,它目前都无法实际在 NeoForge 上加载。这不是本模组的 bug;它在等待 Launchpad 添加对 26.2 的支持。
一旦 Launchpad 发布了 26.2 构建版本,NeoForge 用户需要:
Launchpad(直接加载此 Fabric jar 包,无需单独构建)
用 Forgedified Fabric API 替代普通的 Fabric API
Mod Menu 配置界面在 NeoForge 上仍将不可用(Mod Menu 仅限 Fabric),但所有 /multicoremagic 命令均可正常使用。尝试前请查看 Launchpad 的发布页面以获取当前状态。
功能特性
- 专用的区块构建线程池,完全解耦于原版的共享后台执行器
- 支持实时调整大小——在游戏中途更改线程数即可立即生效
- 集成 Mod Menu + Cloth Config 界面,附带工具提示
- 内置状态命令,可查看活动/排队任务数量
- 合理的默认值,可调至核心数的 2 倍以供实验
命令
/multicoremagic status — 显示启用状态、线程数、活动/排队任务
/multicoremagic threads <n> — 实时调整池大小,无需重启
/multicoremagic on — 启用专用池
/multicoremagic off — 禁用专用池,回退至原版的共享池
on / off 在下一次加入世界或重载资源(F3+A)时生效;threads 立即生效。
默认线程数与原版的公式一致(CPU 核心数 − 1)。滑块最高可调至核心数的 2 倍用于实验,但如果将其设得过高,加之原版自身的世界生成池,可能导致过载(两个池子争抢相同的核心),特别是在穿越新地形等高负载场景下——如果发现提高数值后出现卡顿,请适当调低。
要求
- Minecraft 26.2
- Fabric Loader 0.18.4 或更高版本
- Fabric API
- Java 25
许可证
MIT —— 源码托管于 GitHub。
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.
评论 0
登录后参与评分
还没有评论,来抢沙发吧