When you run out of lives in Skyfall, the game-over screen offers one more option before it shows your final score: watch a short rewarded ad to keep going. It's easy to assume that button is just cosmetic, or that it quietly reruns the same logic as pressing restart. It doesn't. The revive is a distinct code path with its own rules, and most of those rules exist to stop the feature from being confusing or exploitable rather than to squeeze more ad views out of a bad run.
A successful revive sets you back to exactly one life and fifteen seconds on the clock — not a full reset to three lives and sixty seconds. Your combo streak also drops to zero, the same as any other life lost. The intent isn't to hand you a second full run for the price of one ad view; it's to buy you a genuine last stand. Fifteen seconds with one life is enough time to meaningfully add to your score if you're playing well, but it's not a way to launder a rough start into a fresh sixty-second round.
Your score itself is never touched. Whatever you'd earned before dying carries straight through the revive, which is why the feature is framed as "continue," not "retry."
The revive can only be used once per run. The moment you tap the watch-ad button, it disables itself and its label changes to a loading state before the ad has even confirmed it will play — so there's no way to double-tap your way into a second revive attempt, and no ambiguity about whether the offer is still on the table once you've taken it.
If the ad provider can't serve a rewarded ad — no fill, a network hiccup, anything — the button doesn't just spin forever. It re-enables itself, resets its label back to "Watch ad to revive," and shows a plain note that no ad is available right now. Nothing about your run is charged against that failed attempt; from the game's perspective, an ad that never played never happened, and a life is never deducted for trying.
Reviving isn't just "unpause and keep looping." Ending a round tears down the active game state, so bringing a player back means re-arming the loop cleanly: lives and time are set explicitly, the sound engine is re-unlocked (mobile browsers can suspend audio contexts when a screen goes away), a short confirmation beep plays, and only then does the game re-request an animation frame and resume. Skipping any one of those steps tends to produce the class of bug where the game "revives" visually but stops responding to input, or the audio comes back silent — so the revive path deliberately re-does a few setup steps that a normal round only does once.