Line #18 VideoGame/MissileCommand


1	[[quoteright:256:https://static.tvtropes.org/pmwiki/pub/images/mcommand.png]]
2	[[caption-width-right:256:This can [[ItsAWonderfulFailure end]] [[EndlessGame only]] [[EarthShatteringKaboom one way]]...[[note]][[MoodWhiplash unless you make the high score list.]][[/note]]]]
3
4	->''"What's the bluntest point made by this game? [[UnwinnableTrainingSimulation That you can't win.]] No matter how many stages you survive, or how much time you spend playing, you can't beat Missile Command. Nuclear war has no winners. Your job is futile, but you do it anyway because you can buy people a few more minutes of hope."''
5	-->-- '''Daniel Floyd''', ''WebAnimation/ExtraCredits'', [[https://www.youtube.com/watch?v=JQJA5YjvHDU "Narrative Mechanics"]]
6
7	''Missile Command'' (1980) was, at the time of its release, the most violent video game of all time -- at least until ''VideoGame/{{DEFCON}}'' came along.
8
9	''Missile Command'' portrayed a stark view of nuclear war at the height of UsefulNotes/ColdWar paranoia. The player was given command of three anti-ballistic missile bases, with which six otherwise defenseless cities had to be defended against wave after wave of [=ICBMs=], nuclear bombers, and orbital battle stations. The game featured simple yet realistic animations of mushroom clouds wiping out entire cities whenever the player failed to intercept an incoming warhead, and a nightmarish explosion effect when the player [[EndlessGame (inevitably)]] finally lost the game.
10
11	GCC created an enhancement kit called ''Super Missile Attack'' for ''Missile Command'' machines. Atari was not amused and sued GCC. They settled on GCC producing three games for Atari (''Food Fight'', ''Quantum'', and a never-finished game).
12
13	Just a year later (1982), a sequel for two players competing to destroy each other was prototyped and tested, but ultimately never released. [[http://www.gamesetwatch.com/2011/07/missile_command_2_to_debut_at_.php It later resurfaced]] and was shown to the public in 2012, for the first time in 30 years.
14
15	In 1995, as a part of Atari Corp.'s 2000 series, an updated game called ''Missile Command 3D''. It follows a similar premise, only its now about a group of space colonists settling on a new planet, being attacked by an alien race.
16
17	A remastered version, ''[[https://store.steampowered.com/app/1292010/Missile_Command_Recharged/ Missile Command: Recharged]]'', was released on mobile, then later ported to PC and consoles.
18	----
19	!!''Missile Command'' has examples of:
20	* AdaptedOut: The bombers and killsats do not appear in the Atari 2600 version due to memory limitations.
21	* AtomicHate: The game is all about nuclear missiles, more specifically shooting them out of the sky to prevent Armageddon.
22	* BadassPacifist: In the first game, at least, you can only fire back in self-defense; you can't actually attack whichever country is firing missiles at you.
23	* {{Bowdlerization}}:
24	** The Atari 2600 port changes the story so that you're no longer defending Earth cities from nuclear armageddon at the hands of (presumably) the Russians, you're on the planet Zardon defending alien cities from the Krylons. The 5200 goes even further and explicitly says that Krylon wants to ''conquer'' Zardon for its resources, not destroy it (though the Zardon civilization is still being destroyed).
25	** In what was probably not intentional (but instead due to memory and CPU limitations), the 2600 version also removes the "THE END" text from the end of the game, just having the sky flash brightly a few times, which makes it look a lot like the ''victory'' screens of games like ''VideoGame/{{Adventure}}'' or ''VideoGame/HauntedHouse''.
26	* CosmeticAward: If you make the high score screen, you'll bypass the usual Game Over screen. However, this was only in the arcade version.
27	* DestructibleProjectiles: The whole point of the gameplay.
28	* EarthShatteringKaboom: In the context of a nuclear war, the famous "TheEnd" explosion is implied to be this.
29	* TheEighties: Because let's be honest, a game that focuses on preventing Nuclear Armageddon would never have been as popular if it had been released in [[TheNineties the post-Cold War period]].
30	* EndlessGame: Because in a war fought with nuclear missiles, [[UnwinnableByDesign nobody really wins]].
31	* FailureIsTheOnlyOption: No matter how many you destroy, [[UnwinnableByDesign the missiles will just keep coming until you lose]].
32	* ItsAWonderfulFailure: The GameOver screen is a loud explosion which reveals the words "'''{{THE END}}'''", implying not just the end of the game, but ''the end of civilization itself''.
33	* HopelessWar: [[UnwinnableByDesign There is no hope for victory against the enemy]]; all you can do is intercept nukes until civilization is destroyed.
34	* MacrossMissileMassacre: Taken to its LogicalExtreme, especially considering the times.
35	* PaletteSwap: To shake things up every few levels.
36	* PragmaticAdaptation: The Atari 2600, 5200, and 8-bit computer versions were modified to have missiles fired from one single base instead of three. The Atari 2600 version also included variations for choosing the speed of your missile target tracker, since there wasn't an optional trackball controller to use with the game like the arcade original until a few years later. The Game Boy version by Accolade modified it to have two missile bases.
37	* ProtectionMission: You must protect your cities from a nuclear attack. [[EndlessGame Forever.]]
38	* RecursiveAmmo: MIRV missiles will split into multiple smaller missiles which rain down on your cities if you don't blast them.
39	* ScoreMultiplier: Point values for objects increase by x times its normal value every two waves, up to wave 11, where it remains at 6 times its normal value.
40	* UnwinnableByDesign: No matter how good you are, and no matter how long you manage to hold out, eventually you will lose. There is no way to win the game.
41	* VideoGameCaringPotential: It's pretty standard practice for players to name the six cities after cities and towns they're familiar with. ([[http://www.polygon.com/features/2013/8/15/4528228/missile-command-dave-theurer According to Dave Theurer, the developer, this was an intentional design decision.]])
42	* VideoGameCrueltyPotential: Defied. According to developer David Theurer, "Realizing that the bombs would kill all of the people in the targeted city, I did not want to put the player in the position of being a genocidal maniac,"
43	----

Context VideoGame / MissileCommand