What it is

Cloud9 Arcade is three small browser games built for a physical esports booth. Each one takes under ninety seconds, needs no install, and is playable on a tablet someone is holding in one hand while a queue forms behind them.

They are not strategy simulators. They are about the parts of competing that happen in your hands and your memory.

1. Coach's Calm - sixty seconds on the headset

You are a coach at match point. A line drifts across the screen. Hold the mouse to breathe out and bring it down; release and it climbs. Keep it inside the moving band.

Meanwhile the screen keeps throwing noise at you. Amber bubbles are bait - touch one and you flinch, the line jolts, and your steady time resets. Grey bubbles are harmless intel.

It is not a game about calling the perfect play. It is a game about keeping your hands steady while three people shout in your ear.

2. Draft Sprint - sixty seconds of ban/pick against a clock

Standard BP structure: a shared pool of fourteen archetypes, six hard bans, eight remaining, six picks, two benched. Every ban removes the archetype from the pool for good - this is not a soft ban. Each action has an eight-second limit; miss it and the game picks for you.

Your lineup is scored on coverage, balance, redundancy, and how it lines up against the opponent's three. The scoring formula is printed on the start screen, so you can see it is not a random number.

3. One Glance - six rounds of map awareness

Enemy signals flash on an abstract surface for a moment, then vanish. Reproduce their positions from memory. Each round adds targets and shaves the exposure time: two targets at 1.8 seconds down to six targets at 0.9 seconds.

What inspired it

Booth games at esports events are usually either trivia or a reflex test. We wanted something that modelled the actual texture of competitive play - the discipline of not reacting, the memory of where things were, the decision made under a clock.

The three games map onto three real coach skills: composure, drafting, recall.

How we built it

Every game is a single self-contained HTML file. No frameworks, no bundler, no dependencies, no network calls at runtime. Every pixel is drawn at runtime on a canvas; every sound is synthesised with WebAudio.

That constraint was deliberate. A booth game has to survive a tablet with no internet, a browser that has not been updated, and a queue of people who will not read instructions.

We built and inspected the project with IntelliJ IDEA 2026.3. Its headless inspection flagged 1,177 issues across the three projects - mostly ES6 var-to-let migrations and unused CSS symbols. The raw reports are committed in the repository, along with a file documenting exactly which findings we chose not to fix and why.

Challenges

The hardest part was not the games. It was getting the submission itself to a state where a judge could click one link and play. We went through six hosting approaches before one worked, and the account verification chain for the video platform alone required a physical phone.

We also had to resist the obvious trap: a ban/pick game is easy to get subtly wrong in front of judges who know the real rules. Our first build used a soft ban - banned archetypes stayed selectable at reduced stats. That is not how BP works, so we rebuilt it around a shared pool with hard bans.

What we learned

A ninety-second game is much harder to design than a five-minute one. There is no room for a tutorial, so the start screen has to teach the mechanic in three lines.

And: writing down what you did not do turns out to be more convincing than a feature list.

Built With

Share this project:

Updates

Submission history