-
Notifications
You must be signed in to change notification settings - Fork 1
Supported Renderers
Chunksmith does not draw anything itself. It builds a store of level-of-detail data (CSLOD) and hands it to whatever LOD renderer you have installed. Two renderer families exist, and Chunksmith supports both.
Have a renderer you would like supported? Open a ticket at mod_support with the mod, where to get it, and the Minecraft version and loader you run it on. Adding one is usually cheap -- see How a new renderer gets added at the bottom.
-
modrinth.com/mod/distanthorizons -- mod id
distanthorizons -
Minimum version:
2.3.0-b. No upper bound. - Fabric, NeoForge, and Forge on 1.20.1. One jar covers client and server.
Chunksmith registers as a Distant Horizons world-generator override and answers straight from the CSLOD store, so pregenerated terrain appears without DH regenerating anything.
This is the renderer with the widest reach: every Minecraft version and loader Chunksmith ships LOD on has a Distant Horizons build. If you are on NeoForge or Forge, it is your only option.
One thing worth knowing: DH has no stable-channel release -- every published version is beta or alpha. "DH stable" is not a thing you can pin to.
-
modrinth.com/mod/voxy -- mod id
voxy, by MCRcortex - Fabric only, client-side only.
- Published for 1.21.11, 26.1 / 26.1.1 / 26.1.2, and 26.2 (and 1.20.4, which Chunksmith does not ship an LOD cell for). There has never been an upstream voxy build for 1.20.1 or 1.21.1.
voxy is fed live while Chunksmith pregenerates, and can also be replayed afterwards with
/cslod inject -- so you can pregenerate today, install voxy next month, and get your LODs without
regenerating anything.
voxy pins an exact Sodium version and will not load without it. This catches people out more than anything else on this page. The pin differs per voxy build, so check the version you downloaded.
voxy has a lively fork scene, mostly people porting it to loaders or Minecraft versions upstream does not cover. Chunksmith supports them through one adapter, not per-fork code -- they are all format-identical to upstream, so anything that reads as voxy is fed the same way.
Detection is by mod id. Every fork below reports itself as voxy (the one exception renamed itself
to neovoxy, which is also detected), so auto-detection picks them up with no configuration.
Tested end to end against Chunksmith:
| Fork | Maintainer | Where |
|---|---|---|
| voxy (upstream, the control) | MCRcortex | 1.21.11, 26.1.2, 26.2 -- Fabric |
| mia-edition | ggonzaDNG | 1.21.11 -- Fabric |
voxy 2622 branch |
NHblock714 | 26.2 -- Fabric |
| voxy 0.2.18 | Paulem79 | 26.2 -- Fabric |
voxy multiversion
|
m3t4f1v3 | 1.21.1 -- Fabric and NeoForge. Wired into Chunksmith 3.2.1; this is the only way to get voxy on NeoForge at all |
Two more were tested and are partially supported, honestly reported:
- Vulkan-Voxy (SpinGiantCRM, 26.1.2) -- Chunksmith detects it and feeds it correctly, but whether it draws could not be confirmed on the test rig, which has no Vulkan-capable GPU. Not a known failure; simply unverified.
- voxy-mseries-support (srjefers, Apple M-series) -- not supported. Chunksmith reads it fine, but the fork's own renderer throws before drawing anything, with or without Chunksmith installed.
A note on the NeoForge and Forge forks. Several exist -- j-shelfwood, realBritakee, meansabine
(neo-voxy), JustinTHChapman, NHblock714 -- and they are all Minecraft 1.21.1. None is published
on Modrinth; all are source-build only. Of these, only m3t4f1v3's is wired into Chunksmith. No voxy
fork exists for any 26.x on NeoForge, which is why NeoForge 26.x is Distant Horizons only.
On downloads and licences. voxy is All Rights Reserved, and its forks are unlicensed derivatives of it -- one has deleted its licence file outright, and one ships binaries against upstream's "do not redistribute". Chunksmith therefore compiles against them and never bundles, mirrors or links a download for any of them. Go to the maintainer's own repository. Distant Horizons is LGPL and is likewise linked against, never vendored.
Gates are per Minecraft version and loader, and reflect what the renderer itself publishes -- not a limitation Chunksmith chose.
| Distant Horizons | voxy | |
|---|---|---|
| Fabric 1.20.1 | yes | no (never published) |
| Forge 1.20.1 | yes | no |
| Fabric 1.21.1 | yes | via m3t4f1v3's fork |
| NeoForge 1.21.1 | yes | via m3t4f1v3's fork |
| Fabric 1.21.11 | yes | yes |
| NeoForge 1.21.11 | yes | no fork exists |
| Fabric 26.x | yes | yes |
| NeoForge 26.x | yes | no fork exists |
/cslod status tells you what your install can actually feed. It distinguishes "voxy: no build for
this loader/MC" from "voxy is not installed", which is usually the question you are really asking.
Chunksmith refuses to load beside three mods, and the loader will say so:
| Mod | Why |
|---|---|
LOD Server Support (lss) |
Streams LOD into your voxy database over its own channel. Same job, same target |
Voxy Server (voxyserver) |
Same -- voxelizes server-side and pushes to connected clients |
LOD-Server (lodserver) |
Chunksmith's own predecessor, superseded and retired |
The reason is the same in all three cases: two writers, one renderer database, no coordination. You get the data downloaded twice, ingested twice, and a real risk of racing voxy's internal id allocation. Pick one.
Distant Horizons is never a conflict -- it is a renderer Chunksmith feeds. One caution though: if you run DH server-side with its own Distant Generation enabled, it will also push LODs to every DH client. That is duplicated effort rather than breakage, but if Chunksmith is doing the distribution there is no reason to run DH server-side as well.
Worth knowing before you open a ticket, because it sets expectations.
Chunksmith writes a neutral format, not any one renderer's private shape. Adding a renderer means writing an adapter that hands it CSLOD data -- it does not mean changing how anything is stored. For anything voxy-derived that is usually no work at all: the forks are format-identical, so the existing adapter already covers them, and the only question is whether the renderer exists for your loader and Minecraft version.
What is useful in the ticket:
- the renderer, and a link to where you actually get it
- your Minecraft version and loader
- its mod id if you know it (auto-detection keys on that)
- whether it is published anywhere, or source-build only
What will slow it down: a renderer that only exists for a loader and MC version Chunksmith has no LOD cell for, or one whose licence makes it impossible to compile against.