← All Specials

Gamelovr Special 001

God Mode The Secret History of Cheat Codes

Cheat codes did not disappear. From Manic Miner and the Konami Code to Game Genie, DOOM, assist modes and modern anti-cheat, this documentary follows how changing the rules became part of play.

Published
6 August 2026
Runtime
10:20
Chronology
1983–2024
Presenters
Zoe + Adam
Artwork for God Mode: The Secret History of Cheat Codes10:20 · Original Gamelovr film

The film · 10:20

Watch the complete special.

The film moves chronologically, with every game, document and archive page appearing when its part of the story begins.

Prefer the YouTube player? Open the film on YouTube

The code trail · 12 chapters

From a hidden sequence to a visible choice.

The chronology follows what changed: who controlled the rules, how the knowledge travelled and who else had to live with the result.

The title screen of Manic Miner on the ZX Spectrum
1983 · In at 00:00

Zoe · 1983

Manic Miner

An early documented sequence escaped into public play, but the hunt for one definitive first cheat code is a dead end.

Read this chapter's transcript

Zoe · 00:00

Manic Miner is where this history can begin without pretending we have found a single first. The ZX Spectrum game arrived in 1983, in a home-computer culture where playing and programming sat close together. On the Spectrum, players could enter POKE instructions that changed values in memory. A magazine could print an address and a replacement number, and a limited resource might stop running out. Manic Miner's own hidden sequence was different: enter six-zero-three-one-seven-six-nine and the player could teleport between caverns. A specialist disassembly records Matthew Smith's explanation that the digits came from his driving licence, altered and rearranged. It is tempting to call this the first cheat code, but arcade service switches, development builds and memory edits make that claim impossible to prove cleanly. What Manic Miner gives us is something more useful: an early, documented moment when a private sequence escaped into public play.

The Gradius title treatment from Arcade Classics Anniversary Collection
Mid-1980s · In at 00:54

Adam · Mid-1980s

Gradius

Kazuhisa Hashimoto's test shortcut shows cheat codes as production tools before they became player folklore.

Read this chapter's transcript

Adam · 00:54

Gradius moves the story from player tinkering to developer convenience. Building a difficult game means repeatedly reaching the same late level, boss, weapon state or collision problem. Kazuhisa Hashimoto faced exactly that problem while working on the Nintendo Entertainment System version of Gradius. In a translated interview, he explained that the coin-operated original was extremely difficult and that he could not reliably beat it. He needed a way to reach and test the game without replaying the whole journey. The solution was a controller sequence: up, up, down, down, left, right, left, right, B, A. In Gradius, it supplied power-ups. The important point is not that a developer wanted an easier game. He wanted a faster route to a test state. A practical production tool had now become an authored secret inside the finished software, waiting for players to discover it.

Contra gameplay beside the words Super Contra
Late 1980s · In at 01:45

Zoe · Late 1980s

Contra

The Konami Code became a physical ritual that friends, magazines and players could carry between games.

Read this chapter's transcript

Zoe · 01:45

Contra is where that controller sequence became folklore. In the home-console version, entering the Konami Code before play granted thirty lives. That was a far more dramatic promise than a hidden test convenience: it gave ordinary players enough room to survive a notoriously punishing game. Contra also made the code easy to demonstrate. A friend could recite it, another player could perform it, and the result appeared immediately on screen. The sequence was short, rhythmic and physical. You did not merely know a fact about Contra; your thumbs knew a little ritual. From there, the code travelled beyond one cartridge. Players tried it in other Konami games, designers quoted it as a joke, and magazines printed it for readers who had never met the original source. Gradius explains why the sequence existed. Contra explains why millions of people remembered it.

The cover of Tips & Tricks, Volume 1, Number 4
Late 1980s and 1990s · In at 02:34

Adam · Late 1980s and 1990s

Cheat media

Tips & Tricks and other publications turned secret inputs into a durable media category and a form of player status.

Read this chapter's transcript

Adam · 02:34

Tips and Tricks represents the next stage: cheat knowledge became media. Before a search box could answer every question, a code had to move through playgrounds, notebooks, tip lines and magazines. The Video Game History Foundation describes Tips and Tricks as a long-running publication devoted to strategies and cheat codes, with dedicated codebooks continuing after the main magazine ended. A code such as Contra's thirty-lives sequence gained value from that friction. Somebody had to find it, verify it, remember it and pass it on. A printed page did more than list buttons; it certified the rumour. The same information could confer status even when using it removed difficulty. This distribution network is part of the history because cheat codes were never only software features. They were also small pieces of culture, carried from one player to another until a private input became common knowledge.

A Game Genie device for the Nintendo Entertainment System
Early 1990s · In at 03:26

Zoe · Early 1990s

Game Genie

A cartridge adapter moved rule-changing outside the game and into a court fight over what players could do with software they owned.

Read this chapter's transcript

Zoe · 03:26

Game Genie turned rule-changing into a product. The hardware sat between a Nintendo cartridge and the console, so it could intercept data on the way to the machine. According to the 1992 United States appeals decision, it could block one byte and substitute another, temporarily changing features such as lives, speed or the ability to float. This was not a secret placed in the game by its developer. It was a consumer device built to make purchased software answer differently. Nintendo tried to stop its sale. The court affirmed judgment for Galoob and rejected the claim that these temporary changes created an infringing derivative work. The legal ruling was specific, but the cultural question was larger: after buying a game, could a player renegotiate its rules at home? Game Genie made that argument visible in plastic, plugged directly between the author and the player.

A red-lit combat scene from DOOM
1993 · In at 04:16

Adam · 1993

DOOM

IDDQD and IDKFA made development commands feel like incantations, while the released source preserves how they worked.

Read this chapter's transcript

Adam · 04:16

DOOM is the next stop because the personal-computer keyboard turned cheats into memorable words. Because id Software released the game's source code, its famous examples can be checked directly rather than reconstructed from folklore. The status-bar code contains I D D Q D for god mode and I D K F A for weapons, ammunition and keys, beside checks for no-clipping and level changes. Typed during play, those strings felt halfway between commands and incantations. They also matched the culture of the platform. The keyboard was already present, and the boundary between player, tinkerer, modder and developer was unusually porous. The result was not only easier play. DOOM could become a laboratory: the player could test weapons, inspect spaces, ignore collision and walk through the wall. The same functions that helped build games had become part of how players explored them.

First-person Minecraft gameplay beside a lake
2011 onward · In at 05:07

Zoe · 2011 onward

Minecraft

Commands became visible permissions, with the game stating the trade-off between world control and achievements.

Read this chapter's transcript

Zoe · 05:07

Minecraft shows what happened when the old secret interface became a visible permission. Its menus use the phrase Allow Cheats, and its command line openly lists the powers available to the player. Slash commands can teleport someone, give items, locate structures, change the weather or alter the time of day. In Bedrock Edition, enabling cheats permanently disables achievements for that world. The trade-off is not hidden. Minecraft tells the player what kind of session they are creating and preserves the meaning of achievements elsewhere. The old secret has become an explicit tool for a persistent, shareable sandbox. That design acknowledges two valid desires at once: freedom to manipulate the world, and a comparable record of accomplishments when the world remains unaltered. Minecraft did not kill the cheat code. It moved the code into an interface where permission and consequence sit beside the command.

A character in The Sims 4 looking at a tablet
2014 · In at 05:59

Adam · 2014

The Sims 4

Motherlode shifts the player from contestant to director, using a money cheat to change the kind of play rather than skip it.

Read this chapter's transcript

Adam · 05:59

The Sims 4 keeps literal typed cheats alive, but changes what cheating is for. Electronic Arts still documents rosebud and kaching for one thousand Simoleons, while motherlode grants fifty thousand. Those commands remove scarcity, yet scarcity is not the only purpose of The Sims. A player may want to build an impossible house, stage a story, test an idea or recover from a lost save. In that context, the money code does not simply erase the game. It changes authorship. The player becomes less a contestant and more a director, choosing which constraints make the desired story possible. That is why the word cheating can be misleading in a single-player sandbox. The relevant question is not whether the rules changed. It is what kind of play the change enables. In The Sims 4, the code often moves the fun rather than skipping it.

A snowy platforming scene from Celeste
2018 · In at 06:49

Zoe · 2018

Celeste

Assist, Variant and Cheat modes separate accessibility, experimentation and progression instead of flattening them into one category.

Read this chapter's transcript

Zoe · 06:49

Celeste makes the evolution explicit by separating different kinds of rule change. Its vocabulary distinguishes Assist Mode, Variant Mode and Cheat Mode instead of treating them as one moral category. Assist Mode exists so a player can adjust the experience and continue. Variant Mode changes rules for experimentation and replay. Cheat Mode opens progression more directly. The labels matter because they tell the player why the system exists. Nothing is concealed from another participant, and nobody has to pretend that every route through the game proves the same thing. Celeste turns an old hidden power into a visible design conversation between player and developer. The fantasy remains familiar: alter speed, resilience or access until the game becomes playable in the way you need. What changes is the framing. The adjustment is authored, named and offered with consent.

Zagreus confronting an enemy in Hades
2020 · In at 07:39

Adam · 2020

Hades

God Mode returns as adaptive resilience, keeping the journey intact while changing whether the player can participate.

Read this chapter's transcript

Adam · 07:39

Hades is here for one precise reason: its God Mode shows how the name of an old cheat can be repurposed as an accessibility tool. Supergiant describes the setting as added resilience that becomes a little stronger after each death. It does not ask for a secret password, and it does not remove the whole journey. The player still fights, learns and advances; the game gradually adjusts until progress becomes possible. That makes Hades different from DOOM's instant invulnerability, even though both use the fantasy of godlike protection. One is a compact command that changes state immediately. The other is a visible, adaptive agreement between designer and player. Hades belongs in the history because it shows that the desire behind god mode survived while the purpose changed—from domination or testing toward participation.

A first-person view down a corridor in Counter-Strike 2
2023 · In at 08:27

Zoe · 2023

Counter-Strike 2

A private rule change becomes competitive cheating when a concealed advantage changes the result for everyone else.

Read this chapter's transcript

Zoe · 08:27

Counter-Strike 2 marks the boundary where changing a game stops being private experimentation. In a secured multiplayer match, an unauthorized aim tool or wall hack gives one player a concealed advantage over everyone else. Valve's VAC policy treats that as cheating because the shared contest depends on agreed rules. The contrast with The Sims, Celeste or Hades is not technical cleverness. It is consent and consequence. A private save can be altered without taking anything from another player. A ranked Counter-Strike 2 match cannot absorb a hidden advantage without changing the result for every participant. Modern anti-cheat systems therefore belong to the same history as cheat codes, but on the opposite side of the line. The old question was, what can the player change? Counter-Strike 2 forces the newer question: who else has to live with that change?

A monumental temple scene from Age of Mythology: Retold
2024 onward · In at 09:17

Adam · 2024 onward

Age of Mythology: Retold

DEVASD shows literal cheat codes still survive when spectacle and toy-box play are the point.

Read this chapter's transcript

Adam · 09:17

Age of Mythology: Retold brings the chronology back to literal cheat codes. Its official support page still documents returning favourites and newer additions. Enter D E V A S D and the game showers the player with resources, speed, population capacity, repeated god powers and even UFOs. The effect is extravagant because spectacle is the point. This is not a hidden competitive advantage and it is not an adaptive assist setting. It is an authored invitation to turn the strategy game into a toy box. That final example explains why cheat codes never truly disappeared. Their functions separated. Developers kept debug commands. Sandboxes exposed console tools. Games such as Celeste and Hades turned adjustment into an explicit option. Competitive games built systems to reject unauthorized advantages. And Age of Mythology: Retold still lets a typed phrase unleash absurd power. The code changed form, but the pleasure of discovering that rules can move survived. For Gamelovr, I'm Adam.

Research and credits

Follow the evidence.

Every factual claim in the film was checked against the reporting, source code, court record or official documentation listed here.

  1. 01

    Reporting and research

    The Entire History of Video Game Cheat Codes Popular Mechanics
  2. 02

    Reporting and research

    The Early Micro User DiGRA
  3. 03

    Reporting and research

    Manic Miner Facts SkoolKit
  4. 04

    Reporting and research

    The Origins of the Konami Code Revealed Nintendo Life
  5. 05

    Primary source

    Tips & Tricks Collection Video Game History Foundation
  6. 06

    Primary source

    Lewis Galoob Toys v. Nintendo, 964 F.2d 965 United States Court of Appeals
  7. 07

    Primary source

    DOOM Open Source Release id Software
  8. 08

    Primary source

    DOOM Status-Bar Source id Software
  9. 09

    Primary source

    The Sims 4 Cheats Electronic Arts
  10. 10

    Reporting and research

    The Rise and Fall of Cheat Codes Game Dev Stories
  11. 11
  12. 12

    Primary source

    Hades FAQ Supergiant Games
  13. 13

    Primary source

    Celeste Changelog Extremely OK Games
  14. 14

    Primary source

    Cheats for Age of Mythology: Retold World's Edge and Microsoft
  15. 15

    Primary source

    I've Been VAC Banned Valve

Licensed and archival media

Selected visual credits

Gamelovr Specials

The archive starts here.

Return to the Specials archive for every long-form Gamelovr film, complete transcript and source trail.

Browse all Specials