Jungle Trail

A browser-based first-person shooter built with Three.js r180 and WebGL2. It uses procedurally generated textures, meshes, animations, and Web Audio synthesis rather than external art or sound files; its systems include a market-street world with enterable interiors, custom physics and character movement, procedural weapons and ballistics, GPU visual effects, navmesh-based enemy AI with perception and cover behavior, and a DOM/CSS HUD. The repository also provides a development and testing harness: headless-Chromium screenshot capture, isolated reproducible shotsets with pixel-diff gating, scripted playtesting, and a gameplay profiler that reports frame-time distributions and attributes hitches to per-frame WebGL program compilation. The project is run with npm and has Three.js as its only runtime dependency.

Kage is an interactive five-chapter night walk through a Kyoto mountain temple, rendered live in Three.js and WebGL. As the page scrolls, a camera moves through procedurally constructed architecture, lantern light, fog, rain, drifting leaves, terrain, a vermilion moon, and a restrained bloom pipeline. Generated scene plates, alpha-preserving WebP foreground artwork, editorial typography, and section-specific fade and blur transitions are layered over the live 3D world. The project is a deliberately small static site contained in one HTML document, using a vendored Three.js r149 build without a package manager or build step. It includes chapter navigation, responsive mobile layout, reduced-motion behavior, and a custom cursor for precise pointer devices; it has no runtime network dependency. No license is granted for reuse or redistribution of the original Kage code or artwork, while the included Three.js runtime retains its MIT license notice.

An interactive skillshot visual-effects sandbox built with Three.js, Vite, and hand-written GLSL. It provides seven abilities and five aiming modes, with keyboard-armed targeting indicators that follow the mouse before the user clicks to fire. The documented abilities use procedural animated effects such as molten ground and burning blades, a ring of tentacles emerging from a rift, an electrical sphere rising from a containment platform, stone formations along a cast line, and constructed gates or rings. The video describes it as a workbench for designing game abilities while they are animated, using procedural geometry, GLSL, and GPU particles with live adjustment against a paused frame.

Sakura Crossing is an explorable Japanese suburban railway-crossing neighbourhood built as a real-time Three.js 3D scene and rendered to resemble a hand-painted, cel-shaded 2D anime background. The spherical town includes a railway, shopping street, shrine, school, library, residential areas, festival ground, hills and a drainage channel; users can walk, ride an e-bike, call a train, interact with vending machines and other objects, and orbit out to view the planet. Signs, lanterns and other facade details are drawn at runtime with Canvas2D rather than loaded as image assets, while the outlines use a screen-space second difference of depth instead of an edge filter. The repository runs with Node 18 or newer, Three.js and Vite, and provides development and production-serving commands.

Snowflow is a real-time procedural snow-rendering demonstration built with WebGPU, Babylon.js, and hand-written WGSL. It generates terrain, snow deformation, procedural characters, inverse-kinematics foot placement, cloth, surf wakes, water spells, atmosphere, and post-processing at load time without textures, meshes, HDRIs, or animation assets. Its terrain uses a nested-ring geometry clipmap whose vertex shader performs world placement, level-of-detail morphing, and displacement. Layered gradient noise produces the underlying heightfield, while a persistent GPU terrain-state buffer handles additive deformation through scrolling, relaxation, and splatting in a ping-ponged full-screen pass. The demo also provides GPU snow shading, cascaded PCSS shadows, procedural character and cloth systems, and in-browser settings, performance, and debug views. It requires a WebGPU-capable desktop browser and a discrete or recent integrated GPU; it intentionally has no WebGL fallback.