How to Play Underwater Arcade Games
Start here. What every game on this site shares: how to start, what the HUD means, and the three control schemes you will meet.
Written walkthroughs and technique notes for the games on this site. Each guide is built from actual play, not from a specification sheet — the numbers quoted are the numbers in the code.
This category holds written material rather than games. The guides are organised by what you are trying to do — survive a canyon, manage an air supply, raise a score, play comfortably on a phone — rather than by which game you happen to have open.
Every guide is written after playing the game it covers, and the figures quoted come from the game code: the actual spawn intervals, the actual multiplier caps, the actual oxygen cost of a hazard. That is only possible because all eight games on this site were written for this site. Advice about technique transfers to similar games elsewhere; the specific numbers will not.
This category covers:
Written from play, with the numbers taken from the game code.
Start here. What every game on this site shares: how to start, what the HUD means, and the three control schemes you will meet.
A first-hour plan. Which game to open first, what to practise in it, and the three habits worth building before you chase a score.
The complete control reference for all eight games: keyboard, mouse-drag, touch and the on-screen D-pad, with what each is best for.
The centre-line technique, why you should read the far edge of the screen, and how to survive each speed tier change.
A simple rule for the turn-back point, the maths behind it, and the three situations where the rule should be broken.
Four search patterns, when each one is right, and why holding the centre beats sweeping the edges in almost every open-water game.
Scoring systems game by game, which ones reward risk, and the four habits that move a score more than raw skill does.
Which games actually work one-handed, when to rotate, and the settings that stop a phone throttling mid-run.
Water drag, spawn tables, collision circles and a render loop. What is actually happening behind an underwater arcade game, explained without jargon.
Six transferable skills that raise your score in every game in the genre, and the practice routine that builds them fastest.
The practical side of the genre — what a browser game needs from your device, where your scores live, and how to tell a good one from a landing page.
No installer, no account, no launcher. What 'no download' really means for a browser game, and what to look for.
Vector shapes, one canvas, no asset downloads. The specific reasons a good browser game runs where a heavier one stutters.
Touch wins more often than you would expect in this genre — but not everywhere. A game-type-by-game-type comparison.
Research for a guide on this site means two things: playing the game for considerably longer than is necessary to describe it, and reading the code that drives it.
The second part is what makes the numbers trustworthy. When a guide says the combo multiplier caps at x8, or that an air pocket restores 26%, or that the canyon's minimum gap has a floor at 26% of the stage height, those are values read from the source rather than estimated from play. A guide that has to guess at the numbers usually guesses wrong, and the advice built on the guess is wrong with it.
Where a guide makes a claim about something outside the games — human reaction times, ocean depths, how browser storage behaves — that claim is sourced and linked. The fact-checking policy explains the standard.
Written guides rather than games: control references, submarine navigation technique, diving air management, exploration strategy, high-score breakdowns and mobile play advice. There are 8 guides in total.
Yes, entirely, with no account and no email required. Every guide is a normal web page.
The techniques do — momentum control, route planning, protecting a multiplier. The specific figures do not, because they are read from the code of the games published here.
Each guide shows a published date and a last-updated date, and the updated date only changes when the text actually changes. Cosmetic edits do not reset it.