# Cubyz: a Zig voxel sandbox with level-of-detail rendering and no world height limit

> Cubyz is a GPL-3.0 voxel sandbox game written in Zig, built around level-of-detail rendering for far view distances and 3D chunks with no height or depth limit. It is a source-build project, not a launcher download.

**PixelGuys/Cubyz** — Voxel sandbox game with a large render distance, procedurally generated content and some cool graphical effects.

- Repository: https://github.com/PixelGuys/Cubyz
- Stars: 3,678 · Forks: 244
- Language: Zig
- License: GPL-3.0
- Published: 2026-09-23 · Updated: 2026-09-23 · Language: en
- Canonical page: https://hysenlabs.com/projects/pixelguys-cubyz

## What Cubyz solves, and who it is actually for

Cubyz is a 3D voxel sandbox game inspired by Minecraft, and the README lists three features it treats as distinctive: level of detail, which it says enables far view distances; 3D chunks, which it says remove any height or depth limit; and procedural crafting, which it describes as giving infinite possibilities for tool crafting. Those three choices define the audience. It is for players who care more about draw distance and vertical freedom than about a finished survival loop, and for Zig developers who want a readable codebase in a language the README calls small with a focus on readability.

It is not a polished consumer product. The repository has no homepage, and the README's own run instructions are framed as compiling a dev version, with precompiled builds pushed to the releases page instead. The project has a history: it was written in Java until a Zig rewrite that the README says started in August 2022, and the Java code still lives in a separate repository with its own launcher. The original authors, zenith391 and ZaUserA, lost interest, and IntegratedQuantum maintains it now. That history matters if you are deciding whether to build on it, because the rewrite means the current game and the older Java game are different codebases with different release channels.

## Level of detail, 3D chunks and procedural crafting as mechanisms

The three headline features are not marketing labels; each one implies a rendering or gameplay constraint. Level of detail means distant terrain is drawn at reduced detail so that view distance can grow without the cost growing linearly. That is the mechanism behind the far view distance claim, and it is also why the README ties the feature to rendering rather than to world generation. 3D chunks mean the world is not a stack of columns with a fixed ceiling and floor, so terrain generation and storage have to work in three dimensions rather than two, and the README states there is no height or depth limit.

Procedural crafting is the vaguest of the three in the README, which says only that it gives infinite possibilities for tool crafting. The repository layout backs the claim that content is data-driven rather than hard-coded: there are top-level assets/ and mods/ directories, and the README points contributors at docs/CONTENT_SUGGESTIONS.md for content additions and docs/GAME_DESIGN_PRINCIPLES.md for gameplay additions. The practical reading is that content lives in those directories and is loaded by the engine, while the engine itself is Zig under src/. Beyond that, the README does not document the crafting algorithm, the mod loading order, or the asset format, so anyone planning to extend Cubyz will be reading source rather than documentation.

## Building Cubyz from source on Windows or Linux

The README offers two paths. The easy way needs no tools: download the source zip, extract it, and run the platform script. The better way uses Git so that updates are a pull rather than a fresh download, and the README notes this avoids repeatedly downloading the compiler on every update. Windows and Linux are supported; the README states Mac is not, because it does not have OpenGL 4.3. That is a hard platform boundary, not a preference.

The easy path is two steps after extraction:

```bash
./run_linux.sh
```

On Windows the equivalent is `run_windows.bat`, double-clicked from the extracted folder. The README says that if you already have a compatible Zig installed you can skip the scripts and call the build directly:

```bash
zig build run
```

The compatibility caveat is real. The README says the installed Zig must be a compatible version, and the repository carries a .zigversion file at the top level, which is where that pinned version should be read from. The Git path is the one the README recommends for anyone who intends to keep playing:

```bash
 git clone https://github.com/pixelguys/Cubyz
cd Cubyz
git pull
```

After the first successful build the game should launch from the script or from `zig build run`. The repository also ships debug_linux.sh and debug_windows.bat alongside the run scripts, so a debug build is a separate entry point rather than a flag you have to guess.

## The first-build hang, the cache and what to do when it fails

The README documents a failure mode that a new user is likely to hit. If the build keeps running for more than 10 minutes without doing anything, the README suggests killing and restarting the process, notes that a few people seem to experience this and that the cause has not been found, and adds that deleting the zig-cache folder might also help. That is an honest limitation rather than a solved problem, and it is the single most useful thing to know before your first run.

If you see an error message in the terminal, the README directs you to the Issues tab or the Discord server. It also says that if you cannot get it compiling on your machine, you can ask on Discord and the maintainers may compile a release for you. That last offer is unusual and worth noting: it means a failed build is not necessarily the end of the road, but it also means support flows through Discord rather than through a documented troubleshooting guide. There is no rollback procedure in the README, and no documented way to pin the game to an older release beyond downloading that release from the releases page.

## Where Cubyz is the wrong tool

Three cases stand out. The first is macOS. The README is explicit that Mac is not supported because it lacks OpenGL 4.3, so no amount of configuration will make a Mac build work through the documented path. The second is anyone who wants a finished game. The README describes the run instructions as being about a dev version, and the release history since 0.1.1 in January 2026 shows three releases reaching 0.3.0 in July 2026. A 0.x version line with a recent engine rewrite is a moving target.

The third case is modding or content authoring without reading source. The repository has mods/ and assets/ directories and three separate contributor documents, but the README does not describe a mod API, a mod manifest format, or a stable content schema. If your plan depends on a documented extension surface, Cubyz does not currently offer one in the README as published. The Java-era codebase in the separate Cubyz-Java repository and its launcher is the alternative for anyone who wants the older implementation, though the README notes that code is from before the rewrite.

## Licence, maintenance and the cost of keeping up

Cubyz is licensed under GPL-3.0. For a game that is the ordinary case: if you distribute a modified binary, the licence's copyleft terms apply to the source you distribute with it, and content you add inside the repository inherits the same terms. This is not legal advice, and anyone planning to ship a fork commercially should read the licence text in the LICENSE file rather than rely on a summary.

The maintenance picture is straightforward. The repository is not archived and the last push was on 2026-09-20, three days before this writing, so it is being worked on. The upgrade cost is dominated by the Zig toolchain rather than by the game. Because the README requires a compatible Zig version and the repository pins one in .zigversion, a Zig upgrade can invalidate your local build, and the README's own recommendation to clone rather than re-download exists precisely so that `git pull` is the update path. The practical cost of following Cubyz is keeping a matching Zig installed and re-pulling rather than re-downloading. There is no documented save-compatibility or world-migration policy, so treat worlds created on one version as disposable until the project says otherwise.

## Conclusion

Cubyz is for players and Zig developers who want to build a voxel game from source and are willing to accept a project with no packaged installer, no macOS support and a documented first-build hang. It is not for anyone who wants a one-click download or a stable, content-complete sandbox. Before adopting it, check the .zigversion file for the required compiler version, confirm your GPU exposes OpenGL 4.3, and read docs/CONTRIBUTING.md and docs/CONTENT_SUGGESTIONS.md if you intend to send changes upstream.

## FAQ

### How do I install Cubyz?

The README offers two paths. The easy way is to download the source zip, extract it and double-click run_linux.sh or run_windows.bat. The better way is to clone the repository with git and run the same script, or use zig build run if you already have a compatible Zig installed.

### Does Cubyz support macOS?

No. The README states that Windows and Linux are supported and that Mac is not, because it does not have OpenGL 4.3.

### What should I do if the Cubyz build hangs for more than ten minutes?

The README suggests killing and restarting the process, and says deleting the zig-cache folder might also help. It notes that a few people experience this and that the cause has not been found.

### What makes Cubyz different from other voxel sandbox games?

The README lists level of detail, which it says enables far view distances, 3D chunks with no height or depth limit, and procedural crafting with infinite possibilities for tool crafting.

### Can I add mods or content to Cubyz?

The repository has top-level mods/ and assets/ directories, and the README points contributors to docs/CONTENT_SUGGESTIONS.md for content additions and docs/GAME_DESIGN_PRINCIPLES.md for gameplay additions. The README does not document a mod manifest format or a stable content schema.

## Sources

- [Issues](https://github.com/PixelGuys/Cubyz/issues)
- [License: GPL-3.0](https://github.com/PixelGuys/Cubyz/blob/master/LICENSE)
- [PixelGuys/Cubyz on GitHub](https://github.com/PixelGuys/Cubyz)
- [README](https://github.com/PixelGuys/Cubyz/blob/master/README.md)
- [Releases](https://github.com/PixelGuys/Cubyz/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/pixelguys-cubyz