A Boat Ride Through a Browser World
A playable 3D canal ride uses fluid camera movement and repeated day-to-rainy-night shifts to show off a detailed browser environment.
Starter prompt / by Refs
The creator shared no short prompt. This is ours for making a film like it with Claude.
Set a relaxing boat-steering game on a canal through an old Japanese town, built in the browser with three.js. Line the water with wooden townhouses, paper lanterns, red parasols and an arched vermilion bridge, with misty green mountains behind. Give the water clear turquoise depth, reflections, a foamy wake and gentle swell, let other boats drift past, and add throttle, reverse and steering keys with a speed readout. Capture a 60-second ride at 1920×1080 with headless Chrome and ffmpeg.
Field notes / why it works
The first frame starts mid-ride with a boat, responsive water, and a red bridge as a clear destination; the first confirmed cut waits until 0:15.5 because the moving camera and world carry attention. Daylight at 0:11.6 gives way to rainy, lamp-lit night by 0:16.1 and returns by 0:24.8, letting one route reveal several visual states. Persistent controls and a speed readout make the 3D scene feel playable rather than merely rendered.
Plate 01 / The format in one breath
A screen recording of a playable 3D world starts already in motion. A small game objective and persistent controls make the footage legible as a real interaction; the camera follows a boat through a richly detailed route while daylight and rainy night reveal different versions of the same environment. The post supplies the claim that it runs in a browser; the video supplies the visual proof.
Why it works
- At 0:00 the moving boat, turquoise water, street, and distant red bridge create a destination without an intro card. The first 3 seconds have no cuts.
- The route shows the same canal at different times and weather: day at 0:11.6, rainy night by 0:16.1, day again by 0:24.8. The scene itself provides the pattern interrupts.
- Tiny but persistent controls and a live speed readout (10.2 knots on the cover frame) make this look navigable instead of a pre-rendered flythrough.
Plate 02 / Format card
| Platform · aspect · length | X · 569:360 (near 16:10) · 70.7 s · 1138 × 720 at 60 fps |
| Pace | 9 measured shots, 8 cuts; 6.8–11.0 possible cuts/min including uncertain changes; mean 7.85 s, median 6.15 s; first confirmed cut 0:15.5 |
| Script | No reliable spoken script. The 3-word machine transcript is low confidence and appears to be game/noise recognition. |
| Voice | No discernible presenter or narrator in the supplied evidence |
| On screen | Essentially 100% third-person game capture; no face, studio footage, or inserted graphic card |
| Captions | None. Game HUD only: objective upper left, navigation/target near center, controls bottom center, speed lower right |
| Sound | Measured −26.3 LUFS integrated, −9.3 dBFS true peak; no clear cut accents; musical tempo estimate has low confidence |
| Structure | Immediate ride → approach bridge → night/rain variation → return to daylight → repeat environmental variation → daylight exit; no on-video CTA |
Pro / 13 plates + recipe
The first plates are open. The full dissection is Pro.
Get the timed shots, type and sound specs, and the runnable recipe.
Open the full blueprint- Plate 03 / The hook, frame by frame (first 3 seconds)Pro
- Plate 04 / Structure (beat sheet)Pro
- Plate 05 / Shot grammarPro
- Plate 06 / Visual style guidePro
- Plate 07 / Voice and deliveryPro
- Plate 08 / Sound designPro
- Plate 09 / PackagingPro
- Plate 10 / Script templatePro
- Plate 11 / Production planPro
- Plate 12 / PromptsPro
- Plate 13 / Edit recipePro
- Plate 14 / QA checklistPro
- Plate 15 / Make it yoursPro
- Recipe / runnable promptPro