Load a big modpack, pregen a server, or sprint out past your explored map and you hit the same wall: chunk generation crawls while most of your CPU sits idle. Minecraft builds its world with barely any use of your extra cores, and no amount of RAM fixes that. C2ME, short for Concurrent Chunk Management Engine, goes straight at the problem by spreading chunk generation, loading, and disk I/O across every core you can give it. Around 41 million downloads later, it has become one of the standard answers for slow world loading.

How C2ME Parallelizes Chunk Generation

The mod targets the server side of the pipeline, meaning chunk preparation, generation, and the disk I/O behind saving and loading. Where the vanilla pipeline barely scales with extra cores, C2ME throws the whole processor at the queue. The team's latest benchmark round, run with demanding worldgen datapacks loaded, shows what that means in practice. On a 48-core test machine, throughput climbed almost linearly to around 45 threads at roughly 1,200 chunks per second, then kept rising to about 1,400 chunks per second at 96 threads. That lands up to about 34 times faster than vanilla and more than eight times faster than Paper on the same hardware.

2-80 thread benchmark showing C2ME up to ~32x faster than vanilla and ~5.4x faster than Paper on 40 cores

One honest caveat. Those headline numbers came from a tuned stack, with the benchmark running C2ME alongside Lithium, ScalableLux, VMP, and Chunky for pregeneration, so treat the peaks as ceilings rather than promises. The low-end numbers are more relatable. On a single thread, C2ME came in roughly 120 percent faster than vanilla, and at 16 threads it hit 458 chunks per second where Paper managed 142. Even a normal desktop CPU sees a real difference.

Benchmark chart: C2ME vs Paper vs vanilla chunk generation from 1 to 16 threads (1.21.10, Terralith)

Vanilla Parity and Datapack Support

Speed means nothing if the world comes out different. C2ME does not sacrifice vanilla functionality or behavior, and it does not alter vanilla world generation in the name of raw speed by default. One quirk to know about. Vanilla world generation is itself non-deterministic, a quirk Mojang tracks in its own bug tracker, so worlds vary noticeably from run to run even with the same seed. That happens on unmodded worlds too, and the team is clear that it is not something their mod introduces.

Compatibility with content is in good shape as well. World generation datapacks that run on vanilla are fully supported, so heavy biome and structure packs are not a problem. Custom world generators written by other mods usually run well, though some can break when their design assumptions clash with the parallel pipeline, and the team actively helps mod authors fix that. C2ME even ships undefined behavior sanitization, including CheckedThreadLocalRandom for world random (also available standalone as UWRAD), which catches mods misusing game internals before they cause undebuggable crashes. Those detections almost never fire by mistake, so take one seriously and report it to the mod that triggered it.

Config Settings and Companion Mods

Everything lives in config/c2me.toml, generated on first run. Do not worry when you see the word default as a value. It means the mod picks its own sensible default for that setting, not that something failed to load. The most interesting option is globalExecutorParallelism, which overrides the thread count of the global executor. By default the mod computes parallelism from your CPU availability, maximum heap size, and environment, and it prints a Global Executor Parallelism line in the startup log so you can see what it chose. More threads is not always better, since logical core count alone is not the whole formula. If you change anything, stop the server, edit the file, and start it again.

For the best results the developers recommend running C2ME with Lithium and ScalableLux. Krypton slots into the same stack nicely, cutting server lag and tick times from the network side while C2ME handles the chunk side.

1.21.3 2-80 thread benchmark: up to 17x performance over vanilla and 5.1x over Paper on 40 cores

1.21.3 benchmark, 1-10 threads: C2ME ~20% faster than vanilla and ~30% faster than Paper per thread count

How to Install C2ME on a Server

Back up your worlds first. The project page says it in bold, and anyone running a server should treat that as step zero for every mod.
Install Fabric Loader on your server if it is not already there. Our Fabric guide walks you through the whole setup.
Download the C2ME jar from the official project page. The download table on this page lists the current files.
Drop the jar into your server's mods folder.
Start the server once. C2ME generates its config file and logs the parallelism it picked for your hardware.
Optionally set globalExecutorParallelism to match your thread count, then restart the server.

A note on where the mod goes. Client support is optional, so you can run it on your own client for singleplayer worlds, but the server is where it matters. Installing it only on your client will not speed up a separate server, because chunk generation happens on the machine running the world. New to modding in general? Our full mod install guide covers the basics for every loader.

C2ME FAQ

Does C2ME work on the client or only on servers? The server side is required and the client side is optional. On singleplayer it speeds up the integrated server that runs your world. For multiplayer, install it on the server. A client-only install cannot accelerate a remote server.

Can I use C2ME with other performance mods? Yes. The developers recommend pairing it with Lithium and ScalableLux, and their benchmark stack included several other optimization mods. Built-in sanitization checks flag mods that misuse game internals, which keeps mixed setups debuggable.

Does C2ME change how worlds generate? Not by default. It does not alter vanilla world generation or behavior for speed. Worldgen datapacks that work on vanilla are fully supported. Worlds can still differ between runs on the same seed, but that comes from vanilla generation itself, not the mod.

Is C2ME still being updated? Yes. The project was updated in November 2026 and sits at around 41 million downloads. Full support targets the latest release and latest snapshot, older releases receive critical fixes through long-term support, and older snapshots are not supported. Recent builds ship as alpha, so keep those backups current.

Once C2ME is handling chunks on the server, pair it with Sodium on the client for the rendering half of the equation. And if you want smoother loading while traveling through already-generated land, our Better Chunk Loading write-up covers that side of things.