Devlog

Designing ORBIT.IO's Difficulty Curve

September 29, 2026

ORBIT.IO has one control: tap to reverse. All of its difficulty comes from what it throws at you and when. This post walks through how a run escalates, and the rules that keep it fair.

A run in progress.
ORBIT.IO game over screen
The game-over screen.

ORBIT.IO, recorded from the browser game.

The unlock schedule

A run starts with a single threat type and adds a new one at fixed times:

Inbounds stay the most common threat for the whole run. They're three times as likely to be picked as any other type. New threats add variety; they don't replace the basics.

Each new threat asks a new question

The order isn't arbitrary. Each addition changes what a reversal means.

Inbounds teach you to read angles. Mines make part of the track off-limits, so your usable orbit gets shorter. Chasers punish careless reversing, because tapping turns you straight into them. Pulse Rings flip the logic: sometimes the right move is not to tap at all, because the gap in the ring is already coming to you. Reversers come from the front, so now both directions can be dangerous at once. Shrinkers change the geometry, making everything arrive sooner.

By the time all six are in play, a single tap has to account for what's ahead, what's behind, what's on the track and what's coming in from outside.

Fairness rules

A hard game only works if deaths feel earned. ORBIT.IO has several rules built in to make sure a threat never comes out of nowhere:

Rewarding risk

The last piece is the shield. Every five near misses earns one. That means the safest-looking strategy, staying as far from everything as possible, is actually the weaker one. Players who let threats skim past bank shields for the brutal final stretch. After two minutes your score also doubles per second, so surviving deep into a run pays off twice.

The full threat breakdown, with tips for each, is in the ORBIT.IO guide.

More from the Devlog