Alder is eleven. His father Tomas, keeper of the great bell, went to mend it last autumn and never came home. On the morning of the lantern festival, the bell sounds its first warning, and the village falls quiet.
Take up a practice sword and your father’s reed flute. Follow the pale paths out of Alder Village into the Whisperwood, up Cinderpeak, and down to the Larkwater Coast. Solve each sanctuary’s trial, break its guardian seal, and face the warden at its heart. When three relics rest in the altar, the Bell of Ages offers a crossing that costs seven years of your life.
The Bell of Ages is an original adventure inspired by classic 3D action-adventure games. Its world, characters, story, models, and music are original to the project, and it runs in a browser.
Sword, shield, and the golden ring
Chain a diagonal cut, a return cut, and a heavier thrust. Damage comes from the blade itself: each swing traces the sword’s real path against enemy hit volumes, so a miss is really a miss, and a blade that hits a wall glances off in sparks. The sword leaves a warm arc that fades toward the hilt, and hits land with amber sparks and a brief hit-stop. Guardians telegraph every attack with a pulsing golden ring, outlined in dark so it reads on sand and snow, and an arrow on the screen’s edge points to one winding up out of view. Guard a blow and the attacker staggers. Lock-on keeps a single foe in focus.
Guardians come in three kinds: the stone guardian, the horned skirmisher that lunges down a short marked lane, and the tall warder that lobs a stone at a circle marked where you stand. Each sanctuary ends with a warden, and every warden has signature attacks with their own warnings on the ground: a charge down a marked lane, a shockwave that rolls outward from a ring, and a volley of three circles that erupt around you.




Seven sanctuaries each run from a puzzle chamber to a sealed guardian hall to a warden’s arena, and each asks something different: touch memory stones in the order the roots remember, push a stone onto a seal, echo a melody on the three-note reed flute, turn star mirrors toward the north, balance light and shadow across three flames, or ring bells in the order an inscription names. Each hall and arena has its own layout of cover, and every hall hides a cracked wall that breaks open onto an alcove and a carving for your journal.
The kingdom map remembers the chests and wandering lights you’ve passed, lets you set your own marker, and the compass always names where the journey goes next. Treasure chests, Mira’s three wandering lights, and a star-forged blade wait off the beaten path.
A kingdom in two ages
Before the crossing, you make your oldest friend Mira a promise: “I’ll find my way home” or “I’ll remember us as we are.” The choice changes your reunion, the memories in your journal, and the ending. As an adult you’re taller and stronger and carry the keeper’s longsword. The kingdom’s light has changed, and new sanctuaries wake in its far corners.


The campaign spans ten regions on one continuous overworld, seven sanctuaries and wardens, sixteen story scenes, one meaningful choice, and optional chests, wandering lights, hidden carvings, and a sword upgrade. Up to three journeys share a browser, and a journey can be exported as a file and imported in another.



Graphics fidelity, input and comfort
One Graphics fidelity slider has four steps and applies at once. Low is for weak graphics, with no post-processing. Medium, the default, adds contact shadows and FXAA and lowers its 3D resolution under load. High adds a soft bloom, a gentle colour grade and fuller grass. Ultra adds supersampling, SMAA, 4096 shadows redrawn every frame, stronger bloom, denser sparks, and depth of field behind the title and story scenes; its extra effects download only when it’s first chosen. On the integrated Radeon it was measured on, Low to High took about 2 to 7 ms a frame and Ultra about 15 ms at 1280×800.
The whole campaign plays with keyboard and mouse, a keyboard alone, a standard gamepad, or touch, and prompts follow whichever you used last, with PlayStation, Nintendo or Xbox button names. Keys and buttons can be remapped. Settings include reduced motion, larger interface text, off-screen attack warnings, a toggle shield, captured mouse look, a camera that trails behind you on a gamepad or touch, a left-handed touch layout with larger buttons, and full screen. Every menu works with the keyboard alone, and buttons light on hover, dip when pressed and share one gold focus ring. Scene changes fade through a dark veil instead of cutting.
What it’s built with
The game is TypeScript on Three.js r186, built with Vite into plain static files. A few engineering choices do most of the work:
- One height function. Terrain rendering, character grounding, and camera clearance all sample the same deterministic function, so nothing floats or sinks.
- Swept collision. Movement and dodge rolls are swept circles against rotated boxes and tree trunks in a spatial hash, so fast rolls can’t tunnel through fences, and you slide along walls instead of sticking.
- Blade-accurate combat. The sword’s base-to-tip segment is sampled at 120 Hz across each swing and tested against enemy capsules, so hits that fall between frames still count.
- A camera that respects walls. The follow camera casts against obstacle heights, retracts immediately, eases back out, and fades Alder when a wall pushes it close.
- Rendering on a budget. Static scenery is batched by material and spatial cell, vegetation is instanced, wind-animated in the shader, and swapped to lighter versions at a distance.
There are no audio files. Every sound, from flute notes to sword swings, is synthesized with the Web Audio API.
How it was made
All the models, including cottages, the sanctuary, a dungeon kit, props, trees, characters, and the wardens, come from one deterministic Blender Python script, along with their procedural texture atlas. glTF Transform then compresses the export with Meshopt and WebP into a small runtime pack. Two painted textures were made with an AI image-generation tool, with prompts recorded in the repository.
The game was developed with AI coding assistants following OpenAI’s guide to building games with Astra. After launch it went through twelve rounds of improvements, each run by a fresh AI session and pushed only after its logs were checked. Those rounds found that two of the six treasure chests could never be opened, because a rock and a cliff blocked them, and that the compass led to the back of three sanctuary doors. They added gamepad and touch play, remapping, three journeys, the hearts’ low-health warning, the guardian kinds, the wardens’ signature attacks, hidden alcoves and the fidelity slider. The tests now include 155 Vitest unit tests and scripted browser checks, including the opening played from the title with real input, and a scripted fighter that measures every hall and arena.
The trailer and screenshots are reproducible. A Playwright harness runs the game under a fake clock, so every frame advances the simulation by exactly 1/30 second, captures each frame in full at Ultra, and records the game’s own Web Audio output through an offline audio context.
On phones and tablets
The Bell of Ages already had touch controls, and a phone pass tightened them. They used to show whenever the screen reported a coarse pointer, and a key press didn’t hide them; now they show only on touch-first devices or after a real touch, and hide for any key, mouse movement or gamepad. The pause button was 40 pixels and menu choices 27 to 42; every control and menu choice is now at least 44 points, and the HUD, controls, title and menus all keep clear of the notch and home indicator. Scrolling, zooming, text selection and long-press menus are off, sound starts on the first tap, and the minimap opens the kingdom map.
Phones now start on Low graphics, and Medium is capped at 1.25 times the resolution on phones and tablets. WebGL memory fell from 111 MB to 65 MB on the iPhone profile and from 119 MB to 66 MB on an Android one. If a visit ends without the page closing, as when iOS kills a tab, the next one starts a step lower and says why.
It has only been played in headless test browsers with iPhone, iPad and Android phone profiles so far. A real phone still has to confirm iOS’s memory limit, sound, frame rate, and how the controls feel under a thumb.
Play it
Play it in your browser at nearbycoder.github.io/Ocarina, on a desktop or on a phone or tablet. It’s the current game, about 8 MB in all, needing a browser with WebGL 2; journeys are saved in the browser, and Export and Import journey file move one between browsers.
The Bell of Ages is a playable prototype with a complete story from opening to epilogue. The v0.1.0 web build is the October 4 launch build, without any of the improvements above. The README is upfront about its limits: all seven sanctuaries share one three-chamber spine, every enemy uses one reshaped model, combat is forgiving, and gamepad and touch have only been tested with synthetic input.
Browse the source on GitHub. GitHub records the repository’s creation on October 4, 2026.