This isn't Three.js. Wallhammer Web has its own WebGL2 renderer, and everything in this village comes from code. No imported models. No texture files.
Houses, cobblestones, trees, villagers and flowing water, generated in the browser. Watch the sunlight fade and the windows and lanterns come on:
Graphics made with code
The world is a set of generators. A roof, a tree and a villager are geometry produced by TypeScript. Change the recipe and the world changes. A seed controls repeatable variation.
Wallhammer Web brings the renderer, cameras, environment, world streaming and simulation into one engine. The sun, sky and time of day work together, so the village can move from afternoon into evening as one scene.
Agent-first, from the start
An AI agent can work directly on the world because the world is code. It can build a scene, inspect the result and revise the generators.
The workflow pairs planning and review with implementation. Architecture checks enforce module boundaries. Generator checks, screenshots and performance tools help verify what the agent built. The rendered scene matters as much as the code.
That's what I mean by an agent-first engine: the tools to create a world and check it belong in the same workflow.
The village is one example
The same core also powers a planet with a continuous surface-to-orbit flight, a solar system, building destruction and endlessly streamed terrain. There is a character controller for exploring the world on foot, too.
Simulation runs at a fixed step and can run in Node without a browser or GPU. Rendering stays separate from world logic.
This video is the latest fantasy village running in Wallhammer Web. Graphics made with code. Worlds built by agents.
Top comments (0)