Skyfall has two systems running underneath the score counter that most players feel before they ever consciously notice them: the combo multiplier, and the power-up drops. Both went through more revisions than almost anything else in the game, because both are exactly the kind of mechanic that's easy to get slightly wrong — too generous and the game stops feeling skill-based, too stingy and streaks never feel worth chasing.

The combo curve

Every clean hit adds one to your combo counter; a miss, a shot decoy dove, or a lost life resets it to zero. The multiplier itself doesn't climb every hit — it steps up by 0.5 for every three hits in a row, and it hard-caps at x3. So the progression looks like x1 → x1.5 at combo 3 → x2 at combo 6 → x2.5 at combo 9 → x3 at combo 12, and then it just sits there no matter how long the streak runs.

The cap was deliberate. An uncapped multiplier sounds exciting on paper, but in a 60-second round it turns the run into a single binary event: either your streak survives and you win by a landslide, or it breaks early and the round is functionally over. Capping at x3 means a broken streak is a real setback, but not a run-ending one — you can rebuild to x2 or x3 again with 6–9 clean hits, which is very achievable inside a single wave. The step size (every 3 hits, not every hit) exists for the same reason: a per-hit multiplier increase makes the bonus feel automatic, while batching it into groups of three makes each step feel like a small earned milestone, and it lines up with the toast notification — you get a "streak!" callout every 5 hits, which lands just often enough to feel rewarding without spamming the screen.

Point values scale with the multiplier at the moment of the hit, rounded to the nearest whole number, so a golden bird (40pts base) at a x3 streak is worth 120 — enough that a maintained streak against high-value birds is genuinely the highest-scoring play available, on purpose.

Why decoys reset the streak too: the pale "avoid" dove already costs you points if you shoot it. Letting it also break your combo was a deliberate double penalty — it's the one bird on screen you're supposed to actively track and avoid, and a streak-safe mistake would make it too easy to tap through on autopilot.

One power-up on screen, ever

Rapid Fire, Wide Scope, Slow-Mo, and +1 Life float across the screen and get shot like any other target, but only one can ever be in play at a time — the spawn logic simply won't queue another until the current one is gone, whether that's because a player grabbed it or it drifted off-screen unclaimed. That single-instance rule is what lets each power-up be strong. Rapid Fire cuts your shot cooldown by two-thirds for 6 seconds, and Wide Scope nearly doubles your hit radius for the same duration — either one is a noticeably different way to play for a few seconds. Letting both stack at once (or letting a second copy of the same one queue up) would make the strongest moments of a run about power-up luck rather than aim, so the game deliberately throttles supply instead of nerfing the effects themselves.

Slow-Mo runs a beat shorter, at 5 seconds, because it doesn't just help you — it slows every bird on screen, including the ones you haven't reacted to yet, so its value compounds fast in a way Rapid Fire and Wide Scope don't. +1 Life is the odd one out: it has no duration at all, it just resolves instantly on pickup, and it's the only power-up capped by your maximum life count rather than a timer.

Spawn timing follows the same "don't let it become the whole game" philosophy as the combo cap: the first power-up won't appear until 13 seconds into a round, and after that, the gap before the next one lands somewhere between 12 and 18 seconds, chosen at random each time so players can't metronome their way to a predictable pickup. Across a 60-second round that typically works out to two or three power-up windows — enough to matter, not enough to define the run.

More from the blog: read Anatomy of the wave system for how difficulty escalates around these same systems, or head back to the Blog index for the rest of our dev notes.