About: Heads I Win, Tails You Lose   Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : associated with source dataset(s)

In a video game's story, how do you portray a battle in which the main player character is supposed to lose? Well, one option is to pull a Hopeless Boss Fight, where the player must fail the battle in order to progress the plot. But there's one problem with that: it doesn't require any skill! The solution? Heads I Win Tails You Lose! If you die, you get a Game Over. No surprise there, right? Note: This trope is not Hopeless Boss Fight. Please only add examples if defeat results in a Game Over (or whatever normally happens when you die).

  • Heads I Win, Tails You Lose
  • In a video game's story, how do you portray a battle in which the main player character is supposed to lose? Well, one option is to pull a Hopeless Boss Fight, where the player must fail the battle in order to progress the plot. But there's one problem with that: it doesn't require any skill! The solution? Heads I Win Tails You Lose! If you die, you get a Game Over. No surprise there, right? Note: This trope is not Hopeless Boss Fight. Please only add examples if defeat results in a Game Over (or whatever normally happens when you die).
  • In a video game's story, how do you portray a battle in which the main player character is supposed to lose? Well, one option is to pull a Hopeless Boss Fight, where the player must fail the battle in order to progress the plot. But there's one problem with that: it doesn't require any skill! The solution? Heads I Win Tails You Lose! If you die, you get a Game Over. No surprise there, right? If you win, the boss reveals that he's not left-handed and proceeds to hand you your ass anyway during the following cutscene. So it is a plot point and a legitimate boss battle at the same time! Genius! But so annoying! A type of Story Overwrite and subtrope of The Battle Didn't Count. May overlap with Cutscene Incompetence. Item #35 in the The Grand List of Console RPG Cliches. Also may be considered a subtrope of Fission Mailed. Compare Morton's Fork. Note: This trope is not Hopeless Boss Fight. Please only add examples if defeat results in a Game Over (or whatever normally happens when you die). Examples of Heads I Win, Tails You Lose include: * Call of Duty: Modern Warfare has this in part one and two. In part one after rescuing a downed helicopter pilot, the entire city you're in is struck by a nuclear blast, killing both you and presumably the pilot you rescued. In part two it happens multiple times. * Metal Gear Solid, you beat Sniper Wolf after much backtracking to one of the earliest areas in the game, the 2nd floor basement of the tank hangar. Immediately afterwards you are captured and hauled back to the first floor basement of the hangar, one floor above, for a torture session. * And in the first sequel, it doesn't matter how quickly Raiden shoots Vamp during the sniper section. Emma still gets fatally stabbed by him after the fight ends, even though if she dies during the actual boss fight it's game over. * Kingdom Hearts: * The first game of the series has the battle against Leon in Traverse Town. If you win, you still receive that "Exhausted Sora" cutscene, but if you lose, well, then you just simply lose in the cutscene as well. Lose/lose situation, in other words. You get an extra reward later if you beat Leon, so it isn't that bad. * The same applies for Cloud later in the Olympus Colosseum. * In Kingdom Hearts: 358 Days Over 2, due to being Doomed by Canon, Roxas may win the boss fight against Riku, but will immediately lose in the cutscene that follows, closing the gap between 358 and KH2. * Batman: Arkham Asylum has Batman trying to save Dr. Young from Zsasz. You have to take Zsasz down stealthily; if you wait too long or rush into the room, he will slit her throat. Immediately after you rescue her, Dr. Young gets killed in the following cutscene. Well damn. * Mother 3 has "Master Eddie," an unavoidable boss battle at the end of the ocean. Losing to him results in a standard Game Over. Do enough damage, and he will release a massive attack which will cause you to "lose" and wash up on a certain island. * The first battle with Malak in Knights of the Old Republic. * The second game has fight against Atris, though in here, win or lose doesn't matter, she will beat Handmaiden anyway. * Knights of the Old Republic II also has the Exile's first fight against Darth Sion on Korriban. If you are killed, you're dead, but after Darth Sion heals himself a few times Kreia tells you to run, and run you do. This is extremely frustrating since you can do the planets in any order, therefore it's entirely probable that by then you're rather powerful and Darth Sion can't hit you, let alone do enough damage that you can't simply heal yourself easily with the Force. * Persona 3 has this as, of all things, the expected Final Boss battle. (The true Final Boss battle, however, is thankfully a scripted Foregone Victory instead.) Somewhat justified in that they've been hammering into your head that you cannot win against this, the only thing you're doing is dying with dignity. * Persona 4 gives us Shadow Rise. If you die against her, it's a Game Over, if you lower her health enough she will perform an Enemy Scan on your party and you will no longer be able to hit her at all. And it is still Game Over if she kills you after this happens, you must hold off against her until the cutscene three rounds later. * Rogue Galaxy has the masked guy. You fight him quite a few times, and in every single fight but the last, after a certain time elapses, you're treated to a cutscene with your characters saying "This guy's too strong!" and "We can't beat him!". This is especially annoying since he's not really that tough--you can end the fight early by dropping his HP to a certain amount, and if you figure out the right strategy, you can get him to that amount in under a minute. * Happens annoyingly often in Klonoa Heroes: Legendary Star Medal. You fight through a swarm of giant mooks, you get overwhelmed by a bigger swarm. You beat Boxmaren, it regenerates and multiplies endlessly until Pango shows up and destroys the computer controlling it. Defeat Joka, he goes One-Winged Angel and whomps you so badly you don't even get a cutscene of him actually doing it, just a bit of dialogue stating you lost. * Final Fantasy VIII pulls this one several times. The first occurs inside the first sequence involving Lunatic Pandora, where after fighting waves of enemy Mooks, the last one brings two party members down to 1HP immediately if they are not already KO'd to facilitate a plot point. Another occurs when you fight against Edea in Disc 1, which, depending on how much magic you've stocked up, is either a fair challenge to stay alive or a pushover. However, the fight against Edea ends with her using what later turns out to be her Limit Break, so it actually makes sense that she could oneshot Squall with it. * Final Fantasy IX pulls a non-cutscene variant several times: all the battles against Beatrix (early in the game) and Kuja (later on) play out as normal boss fights until you defeat them, at which point they automatically pull out an attack which reduces your entire party to 1 HP apiece, forcing them to surrender so that the plot can continue. * Kuja's case is actually him using an attack that just automatically kills the entire party. * Vergil in Devil May Cry 3 after the first boss fight with him. Doesn't matter if you were hardcore enough to No Damage Run over him - he still stomps on Dante afterward. It's not quite as annoying as it might be, though, because you saw part of the fight in the opening cutscene and thus see it coming. Dante is like this in Devil May Cry 4 for the last battle against him. * The story-important Arena battles in .hack//G.U. are played exactly like this for no other reason than Haseo needs to be backed into a corner to unleash his Super-Powered Evil Side. * The first fight with Alkaid has her team automatically activate their Beast Awakening when Alkaid herself is dropped to 50%. To say nothing of the fights where you're winning so easily you may as well be smacking around unarmed small children with the flat side of your BFS, only to have a cutscene activate with Haseo on his knees, panting from the exertion. * In Eternal Sonata, the characters, having just beaten the massively-large Tuba who started a fight with them "for fun", allow themselves to be arrested by the guards. * Then, after you beat Tuba a second time, he knocks the entire party off a bridge. * This happened WAY too many times to be acceptable in Dragon Ball Z Budokai Tenkaichi 2. You could be pingponging the bad guy around the map, blasting him with the strongest attacks in your arsenal and have all your health remaining... and yet the cutscene showed your character in their "weary" pose, having supposedly been badly beaten. Yes, SUPPOSEDLY. There's not even a cutscene where the bad guys suddenly pound them, the goodies win... and then are shown all tired out, complaining that the enemy is "Too strong", while the bad guy is standing with nary a scratch. This got FUCKING RIDICULOUS after a while. Many people were NOT amused with this. * Averted in BT 3. When a battle called for the bad guy to win, this time around you played as the bad guy instead. And when there were fights that could lead to this, beating the bad guy shows your triumphant good guy celebrating their victory. Sure the next episode didn't change, but it was much more nice. * Guild Wars Factions has the Big Bad kill the party in a cutscene after the Vizunah square mission. Fortunately, everyone got better, thanks to some envoys. * Similarly used in the Naruto Clash of Ninja games' story mode. Even in fights where the "heroic" character gets soundly thrashed, you still have to win... and are rewarded with a cutscene where you get stomped. * Inverted in Jade Empire, when you use Sun Kim to fight Death's Hand, win or lose does not matter, since Death's Hand will lose anyway. If you do win, though, you can gain some extra reward or bind Death's Hand as your follower. * Dispute this, too. Sun Kim wanted to finally die. The only way this trope happens is if you bind Sun Kim. * Epically averted in Dragon Age near the end of the game. While exiting the Arl of Denerim's estate after breaking Anora out, you are faced by Ser Cauthrien (who has more hit points than any boss besides the High Dragon) and a brigade of soldiers. If you manage to win (probably through overuse of Cone of Cold), you get to skip the Prison Break in Fort Drakon, and you don't have to fight her again while entering the Landsmeet building. * There are several bouts in the WWE Day of Reckoning games where, when you're just about to win (i.e. the ref's hand is about to hit the three, or your opponent is just about to tap out), you are suddenly jumped from behind by another wrestler. * WWE games have this a lot, the storylines are seemingly not at all dependent on what you do in the ring. * Somewhat acceptable, as the storylines are scripted in the actual WWE as well. And interference by a third wrestler is commonplace. * Not quite as acceptable in some of the WWE titles, though, where these scripted losses actually will negatively affect your records and stats. * Mega Man Maverick Hunter X features this as the Final Boss battle if you play as Vile. Beat X and Zero, and the following cutscene shows them seriously damaged. Then they pull themselves together, stomp you with one shot, and leave you to die. Great reward. * When you play as X, the intro-stage battle with Vile has been changed from a Hopeless Boss Fight to one of these. You have to do a certain amount of damage, but then Vile will simply waste you; Zero's entrance then proceeds on schedule. * In X5, no matter how badly the player wastes Zero (as X) or X (as Zero), Zero's Sōgenmu or X's Soul Body attack from the previous game will be pulled out of nowhere to turn the fight into a draw. * Aladdin Capcom has this for the final boss (Jafar in Scaled Up form): after you see a cool death animation for him, he comes back and kicks Aladdin's ass. You still won, but if it weren't for this, the ending of the game and the ending of the movie wouldn't be the same. (Aladdin Virgin Games finished after killing Cobra Jafar, possibly to avoid this kind of thing.) * Severely overused in Baten Kaitos Origins. This happens so often that it actually drives the main character into a Heroic BSOD over his constant losses when anything other than his own life is actually at stake. The fights usually end with an unavoidable attack from the boss, then a villain coming out of nowhere to blast the boss into pieces and gloat at you. (Especially egregious in the Lava Caves; how the hell did Valara get that mecha in there without anyone noticing?!) Just to make it more infuriating, some of those bosses are tough. * It's done in the first game as well, although not quite as much. It still gets irritating when you're beating a boss into the ground, and then the next minute your characters are flipping out about 'how tough this thing is'. * Mega Man Battle Network does this a lot. Almost every time you beat a WWW or Nebula boss, he'll pull himself together and escape with whatever Plot Coupon you were trying to keep out of his hands. Sometimes the boss even has a doomsday attack in reserve -- cue Chaud and ProtoMan to save you from it, then insult you for being unprepared. * The second battle with Stella and Loretta in Castlevania: Portrait of Ruin is a variant of this mixed with Puzzle Boss elements. Lose the battle, and you get the standard death screen. Win, and you get the bad ending. The only way to progress is to follow some clues from earlier and successfully cast the Sanctuary spell, which cures them of their vampire status. * * The case above doesn't really fit the trope since it doesn't just depict you as losing what happens if Brauner shows and makes Villain Exit Stage Left with Stella and Loretta and destroys Castlevania in hopes you'll leave them alone, and your heroes plan to chase after them after escaping. * In Castlevania: Curse of Darkness, the first fight with Trevor Belmont is like this. It's a little less irritating than usual, since you don't actually have to beat Trevor to get the "you still lose" cutscene, just whittle away a small fraction of his health bar. * In The Incredibles video game you must defeat the second OmniDroid (which Mr. Incredible never really managed to fight in the film), but immediately afterwards you are treated by a clip from the film showing Syndrome arriving and chasing Incredible down a waterfall. * Done very subtly in Paper Mario the Thousand Year Door. When the boss Doopliss copies Mario, he also switches places with him and reverts the real Mario to a shadow. You must defeat the shadowy Mario in order to continue the game, which might make sense at the time, but not so much in retrospect. * In Super Mario RPG, your first fight is to save Toadstool from Bowser. When you beat him, a giant sword crashes into the castle and sends each character flying in different directions. * Quake IV: In the first encounter with the Makron, after he sustains a certain amount of damage, he will whip out his Dark Matter Gun, drain your health, and haul you off to be Stroggified. * The fight with Sephiroth in Crisis Core: Final Fantasy VII. * Also, Zack's final battle. Which is the reason to why many don't want to finish the game. * In the last mission of the Hierarchy campaign of Universe At War your mission is to defeat a single boss unit. No matter what force you have at the end of the battle the cutscene shows your army defeated by the enemy forces and the boss killing you. * Same with the Novus campaign; you're tasked to defend a portal that overloads and explodes in the end when you win. * The battle against Kagekiyo Taira in Genji in the first chapter. You can get your revenge in the second chapter after your training in the Golden Temple. * At least two skill checks in the Billy vs. SNAKEMAN storyline quests are not to succeed in what your character is attempting, but just to lose "in an awesome and non-fatal way". * Harry's battle with the dementors after leaving in the Whomping Willow in the video game version of Harry Potter. * Same goes for the video game version of Harry Potter and the Order of the Phoenix with the battle between Harry/Sirius and Lucius/Bellatrix. I know the plot demands it but it is still rather frustrating. * After you defeat Rictus in Anachronox, he will suddenly recover for no reason and curbstomp the party in a cutscene. Justified, however, since Rictus is a literal comic book villain and pulling cheap moves is par for his course. Boots will even lampshade it, moments before it happens, by recalling a similar fight for the comics. * Happens with most of the final bosses in Odin Sphere if you don't defeat them with the character that is mentioned in the prophecies. * If you defeat King Gallon with anybody besides Oswald, he immediately recovers from his wounds and then kills your character and goes back to destroying the world. Only Oswald can defeat him because his power comes from the Queen of the Dead who was the only person who can destroy Gallon * If you defeat Onyx with anybody besides Mercedes, he will be completely unharmed after the fight is over. For most characters, he will gloat about this, but if you fight him with Gwendolyn, he will mourn her death. The game doesn't exactly explain why only Mercedes can kill him, but the prophecy says that he will be defeated by Yggdrasil, the World Tree. It turns out that Yggdrasil is her "true name" and a huge tree grows in the spot where she dies. * If you defeat Leventhan with anybody besides Gwendolyn, he doesn't die and continues destroying the world. Presumably this is because Gwendolyn's people passed down a legend about the dragon explaining where its weak point is. Of course, to reduce Leventhan's HP to 0 with the other characters, you have to attack the same weak point so it doesn't make a lot of sense. * Actually, after you deal the last hit, Leventhan quite clearly dies. The only problem with using anybody but Gwendolyn during that fight is because She has the ring Titrel, so if she fights anyone else, she's either at the Ruins of Ringford forest or Titania, miles away from the cauldron, or the Cauldron got destroyed, meaning Velvet can't do a damn thing to save what's left of Erion. * The other two bosses don't follow this trope, but the world is still doomed if you use the wrong characters. Ingway is knocked out of his Darkova form regardless of who fights him. The only problem with using the wrong character for this fight is that the character won't be available for the boss he/she is supposed to fight. The Cauldron is also destroyed regardless of who fights it, but if somebody besides Velvet destroys it, they damage it too much meaning it can't be used to restore the world after all the bosses are killed. * Well, there IS the fact that the Cauldron (sans Velvet) is "destroyed" by BLOWING UP IN A HUGE FRIGGIN' FIREBALL, killing the character in the process. * The real reason why you get the bad ending for making a single mistake is because basically everyone has to do exactly the right thing to reverse the Cauldron and save Erion. Don't have Corny fight Darkova? Ingway doesn't get to suggest to Velvet that she reverse the Cauldron. Use Velvet elsewhere? She can't reverse the Cauldron, because she's dead, and the Cauldron gets destroyed. Use Oswald against the wrong person? He dies, Gwendolyn goes splat, Velvet can't reverse the cauldron, Rocks Fall, Everyone Dies. * Baroque's plot is practically built on this. Dying is a key way to advance the plot. Not to mention, once you actually win, It has the same effects as dying. Whee! * While it doesn't come with a curb stomp after the fight, winning against Mukai in The King of Fighters 2003 results in him standing up, back in his standard battle pose, with your characters remarking (more or less) how you barely scratched him (and sometimes how he even seems unfazed). He leaves afterward, with only a hint of the trouble that's to come. * Happens in Starcraft: * The Human mission 9 involves defeating Protoss outpost, without harming the Zerg base. After eliminating the threat, the Zerg overrun your base, facilitating Kerrigan's Face Heel Turn. * Theoretically. Rather foolishly, they didn't make that powerful a force. As such, it's quite easy to destroy it with a few well placed bunkers, battleships, and siege tank emplacements, that you spend much time building to chase down the old enemy. Doesn't change the cutscenes, though. * This mission is a prime example of Gameplay and Story Segregation. Whether or not you constructed a large enough force to take out both the Protoss and the Zerg bases is moot considering you more than likely built a couple of transports to complete the mission and there should be nothing stopping you from loading Kerrigan onto one and flying back to the fleet in orbit around the planet. * In Protoss mission 7, You have to protect Tassadar from the Conclave. Once you destroy part of it Tassadar surrenders. But you win and can rescue him in next mission. * In the Terran Campaign of Starcraft 2 you have to make a hopeless Last Stand against endless hordes of enemies in the vision of Bad Future. Eventually all your forces will be eliminated, but you are still obliged to kill a certain number of enemies to... make the ancestors proud, I guess. * Used aggravatingly often in the Cataclysm expansion of World of Warcraft. Many is the quest where the second you complete the required objectives, you get captured or cornered by mobs who, by all rights, shouldn't even stand a chance against you, and you can do nothing about it. This is most blatant by far in Vash'ir and Uldum. * In the first of the RedAlert series one Soviet mission was to capture a Chronosphere. If you approach it before destroying radars (as warned), it explodes and you lose. If after, it still explodes, but you win the mission. The generals in the briefing room shift blame from you to the intelligence, and your last chance for victory is a full assault on London. * The online Flash game Red Moon has a particularly Egregious example of this: after spending the game watching the heroine get bossed around and outright abused by her walking tutorial boyfriend, you reach the Emperor and beat him... only to see a cutscene where not only does the Emperor win easily, but he defeats your character first, leaving the NPC to do most of the fighting before running away. Then, to add insult to injury, she aplogises to him for not being strong enough. And did I mention that's the end of the game? What the hell!? * The creator of that game loves this trope. Red Moon is a prequel to the Armed With Wings series, and in Armed With Wings 2, you play as the villain. At the end of the game, you face The Hero. Die against him, you lose, beat him, and a cutscene follows where he pulls a One-Winged Angel, reveals he is the avatar of God himself, resurrects all the people you've killed over the course of the story and seals your Villain Protagonist in a white room for all eternity. Justified, however, because this Villain Protagonist is vital to the plot of the next game and as such must be sealed, not killed. * The following game, Armed With Wings 3, also has one of those as the first boss which you defeat (pretty easily, as he's the first boss), only to have him get up and jump your protagonist, who is taken by surprize from behind and totally defenseless, saved only by his mother. Same game has a Hopeless Boss Fight, too. * Not necessarily a hopeless boss fight, but if it becomes apparent that the player is actually capable of winning despite being overpowered, then the game just jumps to the cutscene. * In a series notorious for it, the concept is completely turned around in Culmination, an interquel taking place during the lategame story of Armed with Wings 3, a Foregone Conclusion setting explaining how and when the old hero died. You play him for most of the game and then you face off against the Final Boss...only to realize that you're controlling HIM in this battle now! Cue the player using the Emperor's Purposefully Overpowered arsenal to utterly destroy his earlier player character. * The Force Unleashed has this in the Light Side ending of the final boss battle. Once you've defeated the Emperor, the final cutscene shows that Starkiller is killed anyway while distracting the completely unharmed Emperor from some escaping senators. * The Dark Side ending plays with this a little. For the final boss, you kill Vader but then in the cutscene afterwards, Starkiller turns on the Emperor, who (probably) effortlessly defeats him. You don't die in this ending but you just become a replacement for Vader. It still counts though. * The squeal also has this in the Dark Side ending. You defeat Vader and prepare to kill him when suddenly, a perfect clone of Starkiller comes out of nowhere and kills not only you but Kota and everyone else who's a threat to Vader. * Of course since Starkiller is Doomed by Canon the first example, which is canon was obviously going to happen anyways. The other two examples aren't canon. * MegaMan Star Force 3 has a mini-game style battle where Geo and Omega-Xis have to fight off a wave of Omega-Xis copies and keep them from invading WAZA headquarters. In the first wave, if you lose, it's game over of course, but if you win, the copies proceed to break in effortlessly via cut scene. * Made all the more Egregious in that you're explicitly stated to be stalling for time so Dr. Goodall can get the anti-clone gun working. She gets it working, wiping them all out, which immediately depletes the battery to zip. Then Queentia/Queen Tia summons even more of them, leading to them breaking in. * In many Super Robot Wars games, there would be moments where you take on boss units who in-game can be fairly easy or somewhat difficult to deal with depending on the unit. Then once the units are defeated, mostly to coincide with the units' respective storyline, they would immediately target one of the protagonists with it's strongest attack (usually it's respective series arch rival), completely obliterating it even if you have full health and special skills up. * Sonic Riders, of all games, does this with a particularly irritating race in Story. * The fangame Sonic Before the Sequel is about Sonic trying to stop the launch of the Death Egg before Sonic 2. Therefore, even in the good ending, once Sonic defeats the final boss he just gets blasted out of the sky anyway and falls on Emerald Hill. * The boss at the end of the tutorial in Demons Souls is nearly impossible to beat -- its attacks are fairly easy to dodge, but if you get hit once you die immediately, and given the amount of damage it can soak, you're pretty likely to mess up... but if you do manage to beat it, you end up being killed by another monster in a cutscene, because the plot requires you to die at this point for it to continue. If you do manage this impressive feat, you may obtain his Gray Demon's Soul well before you normally would, so it's not all bad. * No matter how much Sentinel ass Forge kicks in X-Men Next Dimension, he'll still just get himself tied up and captured. * An inverted variation happens in Ultima VII Part II: Serpent Isle. After one of your friends is put on trial in Fawn for blasphemy, you're supposed to sneak into the temple, locate the controls for the oracle, and set her to say the truth (as opposed to being forced by the priestess to condemn the accused). If you don't bother to do so, the next day the oracle will, as expected, condemn your friend... and then the resistance (who gave you the key to the temple earlier) bursts in, reveals the whole plot, and arranges for your friend to be freed. Either way, you can't fail this. (A rare case of averting Holding Out for a Hero, too.) * The Toy Story video game has a boss fight against the Claw where you, as Woody, have to toss LGMs up at the Claw to knock Buzz down until Sid runs out of quarters. Of course, since the movie has Sid capture Buzz and Woody anyway, the cutscene following this fight naturally has that happen. * So, so often in Blaz Blue. Usually thanks to Nu, Rachel, or Terumi * Happens all the time Suikoden III. Most of the plot boss battles (as opposed to the optional treasure bosses) are this. It...gets a bit tiresome. * Naruto Shippuden Ultimate Ninja Storm 2 has a nifty variation that's a combination of this trope and Hopeless Boss Fight. It's the fight between Jiraya and Pain. You have to legitimately win the match, and drain Pain's health meter to zero, then in the middle of the fight, Jiraya gets nailed by a sneak attack by one of the heretofore unseen Pain paths, which then leads to an heavily injured, barely playable Jiraya trying to stave off all six Pains. You will lose, but then in the ensuing quick time event, you have Jiraya get back up, and through sheer will, blow one of the Pains completely away with a move that launches his own dying body into the ocean. Heads I Win Tails you Lose has rarely been this cool. * In the Rise of A Ninja and The Broken Bond games the player is also forced to follow the storyline of the anime regardless of their actual performance in the game which leads to losses you can't avoid. It can be annoying to get trash-talked by your opponent in an animated cutscene after stomping them into the ground (Kiba for this editor) and this can cause some plot holes like Sasuke's fight with the Sound Four as they try to tempt him with power by calling him weak... even if you don't resort to using the Cursed Seal (Rage Mode) to beat them. To be fair there is no way Naruto or the other Konoha genin could win against opponents like Itachi or Orochimaru in Part 1 and in some fights in The Broken Bond your real objective is not to win but to survive or use a specific move to beat your opponent. * An example from a miniboss, is Void, from Grand Chase. Basically, you have to avoid his projectiles, which deal decent damage, and more quickly, while dealing a massive 1 damage per hit. After a certain number of hits, he'll warp to the other side of the rather large arena, and start again. After enough hits have been done, a cutscene will happen, where he just steals what he's after, and warps off. If he takes out all your lives, you fail the dungeon. Not so hard in a party, but with slower characters in a solo run, you'll be hard pressed to not lose at least one life. * Possibly in Cave Story after the Core. The Doctor and Misery arrive, teleport the dying Core out, and leave player and Curly Brace behind. Then, the room floods and player seemingly drowns, until Curly sacrifices herself to save him. (unless, of course, you have a certain item) * In the final battle of Ring of Red, one of your goals is to keep the Prototype mechs used by Weizegger and Ryoko from falling into the hands of the Soviet commander pursuing you. At the end of the mission, Weizegger and Ryoko both stay behind to hold off the Soviet forces in order to let their teammates escape. * In Super Star Wars: The Empire Strikes Back, once you "defeat" Vader, he chops off Luke's hand, just like in the film. * In Ace Combat Zero, Mission 12, you have to shoot down a squadron of Belkan BM-335 bombers supposedly carrying nuclear payloads. If one gets away, it's mission failure. If you shoot them all down, you are exposed to a plot-central nuclear explosion that you just tried to prevent. * In Airforce Delta Strike, Ruth Valentine takes on a solo mission (without orders) to save a stranded hospital ship. No matter how many enemy aircraft you shoot down or the health of the ship, at the end of the Mission Timer, the ship is destroyed by enemy missiles and you suffer a mission failure. * In The Witcher 2 Assassins of Kings, the first battle with Letho, the eponymous Kingslayer ends with him and Geralt getting into a Beam-O-War which Letho wins and knocks Geralt off his feet. Letho however chooses to spare his life since Geralt saved his a long time ago. * In Destrega, if you play on story mode, this happens a number of times when your character is supposed to lose. If you just suck and lose early, you have to do the battle again; if you get your opponent's health low enough, you'll lose control of you character, who will run around like a schmuck until he or she is defeated. * Several times in the Sengoku Basara series. For a concrete example, look no further than fighting Mitsunari in Oichi's blue path in Samurai Heroes. Once you defeat him, he effortlessly defeats you in the ensuing cutscene. * Luminous Arc 2 does this over and over and over, since it likes to use its boss enemies on several maps in a row. It's even a plot point with Bharva, who can only be permanently defeated on his own home plane of existence. * The penultimate battle against Bowletta in Mario and Luigi Superstar Saga: If you lose, it's game over. What happens if you win? A timed bob-omb appears near the brothers and explodes, killing them instantly. Then Bowletta sucks them both up, lunging the brothers with only 1 HP each into the final battle with the spirit of Cackletta inside of him/her. * In Pokémon Mystery Dungeon: Explorers of Time/Darkness/Sky, you can defeat Grovyle at Crystal Lake, but the following cutscene shows him beating you and your partner up to the point that you can't stop him from trying to steal the Time Gear. * Notably averted in Deus Ex. After you defect from your corrupt organization, you run away from them for some, but in the end run into a Hopeless Boss Fight and have to surrender. If, at any moment during that time you're "killed", you're instead captured and transferred to the next level anyway. * Many, many missions in Free Space 2 require you to not only survive, but to keep some other vessel intact—until it gets blown up by overwhelming force at a particular point in the plot. Sometimes ships even mysteriously explode even if you've killed (or cheated away) every credible threat to those ships; other times the plot will simply hang if the ship in question fails to die. It can get a bit frustrating. * The downloadable Resident Evil 5 bonus chapter, Lost In Nightmares, is essentially a playable version of a flashback cutscene from the main storyline, so naturally its outcome is a Foregone Conclusion, including the playable boss fight against the Big Bad. The bare minimum you need to do to "win" is to simply survive for a certain length of time, although you can also "beat" him in the fight and finish the battle earlier. Of course, winning in this case just means you successfully trigger the canonical Curb Stomp Battle cutscene, and you get to watch you and your partner get smacked around for a while. * The first fight against Kai Leng in Mass Effect 3. Lose and its game over. Win and he has a gunship destroy the temple you're fighting in, steals the data both of you are after and escapes while you're busy trying to avoid falling to your death. * One Scooby Doo episode has this exact quote said by Shaggy to decide who enters a scary place, Scooby doesn't like it and changes it to... Heads you Win, Tails I lose. * Also used in the same way on Square One TV, during one of the Cabot and Marshmallow sketches. * In Ranma One Half, Tatewaki Kuno applies this trope to himself regularly as part of his never-ending quest for a date from Akane Tendo and/or Ranma Saotome. He routinely attacks either girl, proclaiming that if he defeats them then they must allow him to go on a date with them, but whenever they fight back, he also states that if they defeat him, then he will allow them to go on a date with him. That they do not want a date with him is something his absurdly inflated ego prevents him from realising. * In Friends, TOW Rachel's Going Away Party, this is used pretty much to the letter in a coin toss between Rachel and Joey. * This is Inverted Trope in an episode of the Super Mario Bros Super Show - Toad is cornered by Snifits while trying to climb a wall into Bowser's fortress, so he pulls out a coin and says, "Heads I keep climbing, Tails you let me go!" He then throws the coin in the air, and while the Snifits are looking at it he jumps to a cannon and says, "Guess what? You lose!" before firing and scattering the Snifits. * In the Community episode Remedial Chaos Theory Jeff does a variation of this. In order to determine who has to go get the pizza, he rolls a six sided die with the person to his right having to go if a 1 is rolled and then going around the table for the rest of the numbers. Since there are actually seven people at the table Jeff always wins no matter what number is rolled. * Real Life Trope Namer. It's a common tactic used by adults on children or older siblings against younger siblings, concerning actual coin flips. The point is to trick the younger individual into not paying attention to the fact that they can't win. It's a surprisingly effective tactic. * Beetle Bailey: Beetle does his best to invoke this when he loses to Sarge in the last game of a ping-pong tournament. The loser has to inform the press, so he does -- resulting in a news story about how Beetle lost, with his picture on the page and only his name mentioned in the headline.
Alternative Linked Data Views: ODE     Raw Data in: CXML | CSV | RDF ( N-Triples N3/Turtle JSON XML ) | OData ( Atom JSON ) | Microdata ( JSON HTML) | JSON-LD    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software