Why we are writing our own voxel engine
An editable world is not a world with cubes on top. It is a problem of generation, memory and save times. Here is what we chose and why.
Soulslands is a world made of cubes, but it is not a game about cubes. The difference lies in one word: persistence. A world that a hundred thousand people modify for years is not a map with a few holes in it: it is a database with geometry on top.
That is why we wrote our own engine instead of adapting an existing one.
The world comes from data, not from code
Biomes, minerals, trees, structures and spawn points live in a data pack: content files that the generator reads. Adding a new forest does not require recompiling the game, and the same generator can produce different worlds with the same code.
That choice has a cost: every field the generator learns to read changes the fingerprint of the pack, and therefore the worlds already generated. That is why the noise version is an explicit number: when it changes, we know, and we update the reference snapshots in the tests.
About 525 chunks per second, per core
Generating a chunk — terrain, biomes, caves, minerals — costs about 1.9 ms of CPU on an i9-9900K with the world in tmpfs. That is roughly 525 chunks per second per core, linear up to eight threads. With saves on disk the bottleneck moves to I/O, and that is where we worked the most: saving two hundred modified chunks went from a few seconds to a few tens of milliseconds, by writing a journal per epoch instead of an fsync per chunk.
The numbers matter because a large world is not judged by how good it looks standing still: it is judged by how smooth it stays while you walk through it.
The server is the only truth
The client decides nothing. The server simulates the world at 20 Hz, authorises movement, validates interactions, manages inventory. The client predicts just enough to hide latency, then corrects itself.
It is more work. It is also the only way to have a full-loot game where the rules actually apply, instead of being a suggestion.
What is missing
A lot. The world exists, multiplayer is in progress, the public alpha has no date. We prefer to write about what works and what does not, instead of a countdown that slips.
The next step is making the world save as large as the world we are building.