The ethics of cheating in single-player games — a defence of the god-mode button

There is a specific kind of guilt that comes with typing iddqd into Doom for the first time. You know that nothing is at stake. You know that no other player is losing because you gained. And yet, for a moment, you feel like you have done something dishonest.

That reflex is worth taking seriously. It is also, I want to argue, mostly wrong.

Who is the injured party?

The ordinary case against cheating rests on a comparison: one player benefits, another player is worse off. In competitive multiplayer that logic is airtight. Every aimbot ruins someone else's Saturday afternoon.

In single-player games, the comparison collapses. The developers shipped a product. You paid for it. The only remaining relationship is between you and the software. Turning on infinite health in Hades to see the ending you spent forty hours failing to reach does not deprive anyone of anything.

The most common counter-argument — "you're cheating yourself" — is oddly paternal. It assumes that the developer's intended experience is the only valuable one and that you, the player, cannot be trusted to know when to stray from it. But games are not exams. They do not have a single correct answer to be preserved from your grubby fingerprints.

The accessibility case

The strongest positive argument for cheats in single-player games is accessibility, and it has quietly won the mainstream debate over the last ten years. When Celeste shipped its "Assist Mode" in 2018 — infinite stamina, dash resets, invulnerability, all disclosed openly in the menu — the reaction was almost uniformly positive. The team framed it as: we made a hard game, we are proud of the hard game, and we would rather you finish an easier version than never finish at all.

That framing is doing real ethical work. It says two things at once:

• The default experience is valuable and worth protecting for players who want it.
• The player's time is also valuable, and forcing them to give up on the story because their reflexes have slowed at 40 is not a moral victory.

Every cheat code in the CheatBook database can be read the same way. The default game is there. The cheats are there for people whose bodies, schedules, or patience have moved past the challenge phase.

The "I cheated once and it ruined the game" problem

There is a real phenomenon here that pro-cheat writing sometimes glosses over. Turning on infinite ammo in a survival horror game does strip out most of what makes it a survival horror game. Players who reach for a cheat before they have engaged with the intended systems often report that the game felt hollow afterwards.

The honest answer is: yes, this is a risk you carry. The pleasure of a game like Resident Evil 4 is inseparable from the moment you realise you have three shotgun shells and four zombies. Removing that constraint removes the pleasure. If you use cheats to skip past the tension, you also skip past the payoff.

The lesson is not "never cheat". The lesson is: cheat after the honest attempt, not instead of it. Almost every experienced player I know follows the same rough rule — first playthrough clean, subsequent runs whatever they like.

Achievements are a separate contract

The one place where the "no injured party" argument breaks down is achievement systems. When Sony, Microsoft, Steam, or Xbox display a trophy on your profile, they are making a claim about you: that you have done this thing. If you unlocked it via a cheat, the claim is false.

This is why every major platform silently disables achievements when cheats are on, and why any game that fails to do so is considered buggy rather than generous. It is also why every entry on CheatBook that touches achievement status carries a warning at the top of the page: the site's position is that the game itself is yours to modify, but your public profile is a shared record and modifying it dishonestly harms other people.

What the developers themselves think

If the ethics of cheating were as fraught as internet commenters sometimes claim, developers would have removed the ability entirely a long time ago. They have not. Bethesda, Rockstar, id Software, Valve, Larian and dozens of others still ship games with console commands or built-in cheat menus. Larian in particular has been unusually open: Baldur's Gate 3's writers have said in interviews that they expect players to break the systems, and that this is fine.

The only major exceptions are competitive-first developers (Riot, Epic on Fortnite, Blizzard) whose games are multiplayer at the core. On the single-player side, there is a broad and quiet consensus among the people who actually build these games: cheats are a feature.

A working rule of thumb

Here is the rule I have settled on after two decades of writing about games:

• If it is single-player and offline, use whatever cheats you want, once you have honestly tried the intended experience or decided it is not for you.
• If it is multiplayer, matchmade, or ranked, never use anything the developer has not sanctioned. The other players are the injured party.
• If it is single-player but achievement-attached, either accept the achievement lock-out gracefully or turn off cheats before the milestone.

That is not a complicated moral system. It is basically the golden rule with a save file attached, and it is why CheatBook exists in the shape it does.

Further reading

• How to use cheats safely — the four-question checklist we run every submission through.
• Editorial policy — the standards we hold every entry on the site to.
• Browse the database — every game we currently document.