Live demos · docs · copy-paste code
Game building blocks,
made once, properly.
Grass, water, ink outlines, soil and post-processing for three.js. Each one is measured, tested headlessly and documented. Drop it in instead of rebuilding it.
Nothing matches.
Try another word, or .
Catalogued elsewhere
How an asset earns its place
01Built inside a game
Made for something a real game needed, in its own module that takes THREE as an argument, so any game's three.js works.
02Moved here
A folder with asset.json, the module, a README.md and a live demo: looks, sliders, diagrams and a "Use it" snippet.
03Proved headlessly
Shaders compiled the way three builds them, every JS↔GLSL twin pinned on a real GL context, and real renders checked by number.
04Reused
Copy the files into a game and pass in its THREE. No build step, no second copy of three, no dependencies.