What is a self-evolving arcade?

A self-evolving arcade is an arcade whose games keep changing after they are released. Instead of shipping a game once and leaving it fixed, the arcade watches how the games are actually played and revises them — difficulty curves, pacing, controls, scoring — as a continuous part of running the place.

Void Arcade is the first arcade built this way. This page explains exactly what that means here: what changes, what it is measured against, and where the line between automation and human judgement sits.

What actually evolves

Not everything. A game's identity — its core action, its look, the thing that makes it itself — stays fixed. What changes is the tuning around it:

Difficulty curves. How fast a run escalates, and when.
Pacing. Spawn rates, wave composition, how long a phase lasts before the next one starts.
Controls and input handling. Especially on touch, where the difference between a good and a bad game is often a few pixels of hitbox.
Scoring and economy. What a run is worth, and which kinds of play the score actually rewards.

A change that would make a game a different game does not ship. A change that makes the same game read more clearly does.

What the arcade measures

Every run writes a telemetry record: which game, how long it lasted, the score reached, how it ended, and which of the game's own events fired along the way — a wave cleared, a power-up used, an extra life spent. Runs from signed-in players and guests are both counted; guests are identified by a per-browser session id, not by anything personal.

That record is what a proposed change is argued against. The useful signals are mostly shapes rather than totals — where in a run players stop, which phase produces a cliff in survival time, whether a control scheme performs differently on phones than on desktops.

On what this is not. The arcade does not change a game while you are playing it, and it does not tune difficulty per player. A change is made to the game, shipped to everyone, and visible in that game's evolution log.

How a change gets decided

The loop is deliberately slow and deliberately human:

Something shows up in the data. A phase where runs end far more often than the ones around it, a control that performs worse on one class of device, a scoring rule that rewards a degenerate strategy.
It gets diagnosed. The telemetry says where; it does not say why. Working out why means playing the game at that point and reading the code.
A change is written and tested. Games are generated from a template and a per-game source, and every build runs an automated contract audit across eight viewports — phone, tablet and desktop, portrait and landscape — before it can ship.
It ships, and it is logged. The change appears in that game's evolution log on its own page.

A person decides every one of these. The automation catches regressions; it does not choose what a game should feel like.

Where AI is and is not involved

Void Arcade is candid about this because the phrase invites the wrong assumption. AI is used as a development tool — helping write and revise game code, and helping read aggregated telemetry. There is no model running inside a game, no model deciding at play time how hard your run should be, and no automated pipeline that ships a gameplay change without a person approving it.

The "self-evolving" claim is about the arcade's operating model: games here are treated as live products that keep being revised, not as finished cartridges. It is not a claim that the games rewrite themselves.

How often games change

Irregularly, and honestly so. A game with a real problem gets attention quickly; a game that is working can go months untouched. Void Arcade used to ship a new game every Sunday and has since moved to releasing when a game is ready instead of when the calendar says so — the same principle applied to releases.

Every substantive change is recorded in the evolution log on the game's own page. The logs with entries so far are Pulse Lock, Data Hopper, Cascade, Snap Stack, Void Gate, Cash Out, Singularity, Star Racer. A game with an empty log has genuinely not changed since release — the logs are not padded.

How this differs from a static online arcade

Most browser arcades are catalogues: a game is licensed or built, uploaded, and left alone. The catalogue grows; the individual games do not change. That model is fine, and it is not this one.

Here the catalogue is small on purpose — 17 games, all original, all built in-house — because every one of them is something that has to keep being maintained. A game that shipped in January is not the same game today, and the differences are written down.

Play something

The clearest way to see what this means is to play a game and then read its evolution log. Pulse Lock and Data Hopper both have real entries. Or start from the full catalogue.