"The Russian vehicles and men are constantly yelling out in battle what I can only assume is real Russian dialogue — despite the fact that perhaps 95% of the game's audience may never understand it."
— Metacritic user review, World in Conflict: Soviet Assault, 2009
Russian as Enemy Language
In Western games, Russian is the enemy's language. Soldiers bark untranslated orders as atmospheric noise; the moment a Russian character needs to be understood, the game switches to English or adds subtitles. The assumption runs deep enough that developers have routinely dressed non-Russian characters in Russian dialogue — Czech soldiers, Caucasus separatists — on the reasonable bet that the player won't notice the difference. The nationality was never the point. The sound was.
This article examines the mechanism behind that sound: the consistent pattern by which Russian dialogue in Western games is withheld from comprehension, used as sonic texture for threat and hostility, and denied the ordinary register of human speech. It is a companion piece to the Archive's entries on Random Russian Words, Broken English and the Russian Accent, and Russians Dubbing Russians — but where those entries examine how Russian is performed or corrected, this one asks when Russian is permitted to exist at all, and for whose benefit.
The Untranslated Perimeter
The most consistent pattern across Western military shooters featuring Russian enemies is not inaccurate Russian — it is deliberate Russian opacity. Enemy dialogue is recorded in Russian, or in something approximating it, and then left entirely unsubtitled. The player hears voices closing in, orders being issued, positions being called — and understands none of it. This is a design choice, not a production shortcut. The same games that invest in full subtitle tracks for their English dialogue, sometimes for ambient NPC chatter the player will never seek out, consistently decline to extend that investment to enemy Russian.
The effect is precisely calibrated. Untranslated speech performs threat at a frequency comprehension cannot reach. The player does not hear a soldier; they hear an enclosing sound that signals danger without permitting the cognitive distance of understanding. Russian becomes a sensory alarm rather than a language — something the body responds to before the mind processes it. The tactical information the dialogue might contain (flanking orders, retreat calls, grenade warnings) is withheld not because the developers forgot to translate it but because legibility would humanize it, and the design does not want that.
Call of Duty: The Architecture of Selective Translation
The Call of Duty series is the most structurally complete example of this pattern, and the most instructive, because it is not simply a case of Russian being left untranslated. It is a case of Russian being selectively translated, and the selection is ideologically exact. Throughout the series — Call of Duty 4: Modern Warfare, Modern Warfare 2, Black Ops, and their successors — the rule is consistent: Russian characters speak Russian to each other, unsubtitled, in all combat and ambient contexts. The moment a Russian character needs to deliver narrative information — a villain's monologue, an interrogation, a mission briefing — the game switches to English, or subtitles appear.
This creates a precise language hierarchy. Russian is the language of the perimeter — of enemies advancing, taking positions, calling out the player's location. English is the language of the story. Russian is what the threat sounds like; English is where meaning lives. The architecture teaches the player, without stating it, that Russian speech is not a vehicle for thought but a marker of hostility. When Zakhaev addresses his forces in COD4, he does so in English. When his soldiers die around the player, they die in Russian. The language of consequence is English; the language of cannon fodder is Russian.
Soldier of Fortune II: The Language of the Generic Enemy
Soldier of Fortune II: Double Helix (2002) is a more nakedly revealing case because it makes the substitution explicit. The game's prologue is set in Soviet-era Prague, where John Mullins must extract a defecting Russian scientist. The enemies guarding the city and pursuing Mullins are Czech soldiers — Czechoslovak Army troops operating on their own national territory. They speak Russian.
This was not an oversight the developers were unaware of: a pre-release GameSpot preview quoted the development team explaining that enemies would speak their respective native languages — "when you're in Russia, the bad guys will speak in Russian." Prague is not Russia. The Czech soldiers are not Russian. But in the finished game, they speak Russian regardless, and no one appears to have raised this as a problem worth fixing before release. The logic underlying the decision is the same logic underlying the untranslated perimeter in the Call of Duty games: Russian is the sound of the Eastern Bloc enemy, and Eastern Bloc enemies speak Russian, irrespective of their actual nationality. Czech, Slovak, Polish — these distinctions are invisible to a design process that treats Russian as the generic phonetic signature of the hostile East. The Soldier of Fortune II case is only unusual in that the substitution is documented and verifiable. In most games, the same assumption operates quietly beneath the surface.
World in Conflict: The Sound No One Was Meant to Understand
World in Conflict (2007), Massive Entertainment's Cold War real-time tactics game, offers a different and more complicated case. The game's Soviet forces — the invading army whose occupation of the American Pacific Northwest forms the game's premise — are given fully recorded Russian-language dialogue at the unit level. When the player zooms the camera down from the strategic overhead view to ground level, the Soviet soldiers can be heard speaking Russian to each other in the middle of the battle.
A reviewer on Metacritic noted it precisely at the time of the Soviet Assault expansion's release: the Russian vehicles and men were "constantly yelling out in battle what I can only assume is real Russian dialogue — despite the fact that perhaps 95% of the game's audience may never understand it." The observation is accurate in both directions. The dialogue is there, it is apparently genuine, and it is almost entirely inaccessible to the game's intended audience. It functions as environmental detail — the sound of the enemy made more textured and immersive for a player who cannot and is not expected to parse it. It is, in other words, the most elaborate possible version of the same basic gesture: Russian as atmosphere, Russian as the sound of the opposing force, present not to be understood but to make the world feel inhabited by something real and foreign and hostile.
The irony of World in Conflict is that the care taken — genuine Russian dialogue recorded for soldiers the player will never speak to, will never spare, and whose words the game never translates — is ultimately in service of the same effect as the laziest untranslated barking in a corridor shooter. The craft is real. The function is identical.
Metal Gear Solid V: The Exception That Proves the Rule
Metal Gear Solid V: The Phantom Pain (2015) is the closest the medium has come to breaking this pattern, and its approach is worth examining for exactly that reason. Soviet Army soldiers in Afghanistan speak untranslated Russian; Afghan Mujahideen speak Pashto; the child soldiers of the Diamond Dogs speak Kikongo. In this game, no enemy faction speaks English as a default — the player is the foreigner in every theatre, and the language environment reflects that. Russian is not singled out as the hostile tongue; it is one among several languages that the player cannot understand and must navigate around.
The design implication is significant. When Russian is one language among many that the player cannot understand, it loses its specific coding as the language of the enemy and becomes instead the language of a particular group of soldiers in a particular place. The Soviet troops in Afghanistan are not "Russian" in the shorthand sense the Call of Duty series deploys — they are a specific military force in a specific historical situation, and their language is the language those soldiers would actually speak. This is the only major Western-developed franchise to have arrived at this position, and it arrived there not because of a particular ideological commitment to accuracy but because Hideo Kojima's design methodology required it. The result, almost accidentally, is the most linguistically honest portrayal of Russian soldiers in the genre.
The Absent Register
What Russian is never permitted to be in Western games is ordinary. There is no Russian equivalent of the ambient NPC chatter that populates allied bases, friendly villages, or civilian areas in games set in the West — the soldiers complaining about food, the civilians discussing the weather, the small irrelevant human exchanges that accumulate into the impression that a world is inhabited by people rather than by functions. Russian-speaking characters exist in a register of pure utility: they command, they threaten, they die. The horizontal register of ordinary speech — the conversation that carries no tactical information and serves no narrative purpose and exists simply because people talk — is entirely absent.
This is the deepest structural effect of the trope, and the hardest to see because it operates as absence rather than presence. The untranslated orders are noticeable; the missing small talk is not. But the cumulative result of a medium in which Russian speech exists only as command and threat is a world in which Russian speakers are not, in any meaningful sense, people. They are a sound the game makes when danger is near. The Russian dub is the first context in which those same characters finally speak for an audience that has always known what they were saying — and the register that opens up when that audience receives them is not the language of the enemy. It is just language.
Notable Cases
| Title | Russian Dialogue Function | Notable Detail |
|---|---|---|
| Call of Duty 4: Modern Warfare (2007) and sequels | Enemy combat chatter unsubtitled; villain and plot dialogue delivered in English or subtitled | Most systematic example of selective translation: Russian marks the perimeter, English marks the story |
| Soldier of Fortune II: Double Helix (2002) | Czech soldiers in Prague speak Russian throughout | Developers stated in pre-release materials that enemies would speak their native languages; final game does not apply this to Czech forces |
| World in Conflict (2007) | Full Russian-language unit dialogue recorded at ground level, entirely unsubtitled | Noted by reviewers as genuine Russian inaccessible to virtually the entire target audience; the most elaborate version of Russian as atmosphere |
| Metal Gear Solid V: The Phantom Pain (2015) | Soviet soldiers speak Russian alongside Pashto, Kikongo, and other unsubtitled languages | The only major Western franchise to deprive Russian of its specific enemy-language coding by placing it within a multilingual environment where no faction speaks English as default |
| Freedom Fighters (2003) | Soviet occupiers speak Russian throughout; dialogue frequently mispronounced or garbled | Player community documented incorrect pronunciation and Cyrillic signage as pure nonsense; Russian present as texture, not as language |
Conclusion
Russian as enemy language is not a policy anyone wrote down. It is the accumulated result of a thousand separate decisions made across decades of development, each one locally reasonable — enemies should sound foreign, foreign should sound threatening, threatening should sound like Russian — and collectively producing a system in which an entire language is encoded as hostile by default. The player who has spent hundreds of hours in military shooters has been trained, below the level of conscious thought, to hear Russian as the sound of danger closing in.
The answer, with rare exceptions, is consistent across four decades of the medium. Russian is heard when the enemy is near. It is understood when the plot requires it. And it is never, in any Western game of consequence, the sound of someone saying something that does not matter — which is to say, the sound of a person.
References
| Source | Notes |
|---|---|
| GameSpot. (2001, October 18). Soldier of Fortune II: Double Helix Preview. gamespot.com | Pre-release developer statement that enemies would speak their native languages in each level location |
| GameSpot. (2002, March 14). Soldier of Fortune II: Double Helix Updated Preview. gamespot.com | Confirms Prague flashback setting and Soviet-held city premise; contextualizes the Czech enemy faction |
| IMDB. Soldier of Fortune II: Double Helix — Trivia. imdb.com | Documents that Czechoslovak soldiers in Prague speak Russian in the finished game |
| Soldier of Fortune Wiki. Czechoslovak Army. soldieroffortune.fandom.com | Confirms Czech Army faction identity and their role as enemies in the Prague prologue |
| Metacritic user review. (2009). World in Conflict: Soviet Assault. metacritic.com | Source of the epigraph; documents the presence of unsubtitled Russian unit dialogue accessible only at ground-level camera zoom |
| TV Tropes. Translation Convention — Video Games. tvtropes.org | Documents the Call of Duty series' consistent use of unsubtitled Russian for enemy combat dialogue, with English reserved for plot-relevant speech; also documents MGSV's multilingual approach |
| Steam Community. Soldier of Fortune 2: Prague gameplay discussion. steamcommunity.com | Player community discussion documenting mispronounced and garbled Russian dialogue in Freedom Fighters; includes partial transcription and translation of enemy lines |