The Roadmap to Chalice 0.1


I’ve been building the engine and the world at the same time, which is fun but really easy to lose motivation on. So I sat down and wrote a roadmap that works backward from what I want the first playable build to be, then lets that decide what the engine actually needs.

Where things stand

RFEngine is a custom Rust engine running on wgpu for graphics and Rapier3D for physics. Here’s what’s working right now:

  • Streaming terrain with a low detail macro mesh underneath high detail chunks, plus rivers carved into the map
  • Water with alpha blending, a dynamic sky, and instanced foliage
  • A GLB importer that pulls out multiple submeshes, UVs, and embedded textures
  • Terrain colliders built on worker threads, with tree and rock colliders managed per chunk as they stream in
  • An egui dashboard for profiling, memory, VRAM, and world generation settings
  • hecs for entities, including the settlements and their faction data

So it’s a world you can walk around in. It’s not a game yet, and that’s the gap this roadmap is for.

Chalice 0.1: The Barley Run

The first playable build is one complete loop instead of a thin version of everything. I’m calling it The Barley Run version because it touches a lot of the systems I care about in one go.

You spawn in a generated Chalice region and can travel on foot between Harrow’s Cross, one village, and the wilds. You farm barley, brew beer, and sell it. Who you sell to affects your reputation. The roads aren’t safe, so there’s one enemy type (bandits) and the combat uses per-limb damage. You can explore one thread of the Ledger’s corruption secret, and you can find one Verdant Circle item that has a mundane explanation plus one detail that doesn’t quite fit. Then you can save and load.

Under the hood, the big lore piece is a history sim that runs before the world spawns. It seeds faction standing and gives some NPCs a few remembered grudges that show up in dialogue, so the world already feels lived in when you arrive.

What’s not in 0.1, on purpose: deep blacksmithing, full skill trees, player housing, the full crime system (I’ll keep theft with witnesses), alchemy beyond a single recipe, and Stonewake and Hollowmere as full towns. Those two will exist as landmarks you can see but not really live in yet. The feature list is huge and I’d rather ship one loop that works than ten that almost do.

Engine 0.1.90

This is the version where I can build most of Chalice without writing code for every little thing. A decent editor, content as data files, and the systems a game needs. Here’s how I’m splitting it up.

0.1.1x: Harden the base. Wind sway in the forest (base stays anchored, tops move), fixing the seam where high detail terrain meets the macro mesh, proper terrain texturing, and Tracy profiling so I’m not guessing about performance.

0.1.2x: World rules. Distinct biome zones, foliage density driven by moisture, roads between settlements, and actual settlement layouts with streets and building lots. Also the save system scaffolding, where the world regenerates from its seed and only the changes get saved.

0.1.3x: Gameplay foundations. A real character controller on Rapier, interaction raycasts, trigger volumes, an event system, input mapping, basic audio, and first person arms.

0.1.4x: Content pipeline. Items, recipes, factions, and skills defined in data files instead of Rust code, hot reloading, prefabs, skinned meshes and animation, and a proper material system.

0.1.5x: Editor v1. Docked egui layout with a hierarchy and inspector, gizmos, an asset browser, prefab editing, undo and redo, debug overlays for colliders and chunks, and a play in editor toggle.

0.1.6x: Systems layer. NPC navigation and daily schedules, with full simulation near the player and a cheaper version far away. An in game UI toolkit for inventory, dialogue, and trading. Per-limb hitboxes.

0.1.90: The finish line. Adding a new item, recipe, NPC, or building shouldn’t need a recompile, and the Barley Run slice runs on top of all of it.

Side note: I skipped 0.1.70 and 0.1.80 because of how I started the initial version naming system.

How the two tracks line up

Chalice milestone Engine needs to be at
Walk a region that looks right 0.1.2x
A town with buildings and NPCs 0.1.4x to 0.1.6x
The Barley Run loop 0.1.4x for data, 0.1.3x for interaction
Combat and saves 0.1.6x

Things I’m being careful about

The editor goes after the data formats. It’s tempting to build the editor early, but if the data formats and prefabs come first, the editor is just a UI on top of things that already work instead of a moving target I keep rewriting.

The history sim stays standalone. It doesn’t need rendering at all, so I can build and test it on its own while engine work keeps moving, then wire it into world generation when both are ready.

Scope. Every system on the feature list is a rabbit hole. The Barley Run is my guardrail. If something doesn’t serve that loop, it waits.

What’s next

Wind sway in the prop shader, the terrain seam fix, and texturing. After that it’s biomes and roads. I’ll keep posting progress here and in the Discord. If you’ve got opinions on the plan, or you think something should be in 0.1 that isn’t, I want to hear it.