You find a cheat code, you type it in, and nothing happens. The obvious conclusion is that the code is wrong. It usually is not. In almost every case the code is fine and something about the copy of the game in front of you is different from the copy it was written for.
There are six of these, and they are worth knowing apart, because the fix is different every time.
1. The game was rebuilt, not re-released
A re-release can mean two very different things. Sometimes it is the same game in a new box — a Game of the Year Edition, a Gold Edition, a Complete Edition. The files are the same, so the cheats are the same.
Other times the game was rebuilt. Doom 3: BFG Edition reads like packaging and is not: it reworked the game. Grand Theft Auto: San Andreas – The Definitive Edition was rebuilt on a different engine entirely, and while most of the classic codes survived, not all of them did.
If a code from 2004 does nothing in a version released in 2021, check which of the two you have before you look for a different code.
2. A patch closed the door the cheat came through
Plenty of consoles are not switched on by default. They are opened by editing a config file or adding a launch flag, and a later patch can quietly change that step.
The clearest example is The Witcher 3. For years you enabled its debug console by adding one line to general.ini. The Next-Gen update in version 4.0 stopped that from working. The console commands themselves did not change at all — the way in did.
So when a guide's commands look right but the console will not open, the guide is probably older than your copy of the game.
3. You are in a mode that switches cheats off
Some games disable the console rather than the codes. Every Paradox grand strategy game does this in Ironman mode: Crusader Kings II, Crusader Kings III, Europa Universalis IV, Stellaris, Hearts of Iron IV. Ironman is the mode that lets you earn achievements, and the trade is that the console is gone. Not restricted — gone.
If the console key does nothing at all in one of those games, look at the save before you look at the key.
4. It is a multiplayer server, and it is not yours
This is the one that gets people banned rather than disappointed.
In every Source and GoldSrc game — Counter-Strike, CS:GO, Team Fortress 2, Left 4 Dead, Day of Defeat — cheats are gated behind sv_cheats 1, and that command belongs to whoever runs the server. On a server you host, it works. On matchmaking or a community server, it does nothing, and repeatedly trying is a good way to collect a VAC ban.
The instruction that matters on those games is not the code. It is: start your own local or listen server first.
5. The code belongs to the engine's other game
Games built on the same engine share a console, which is why god and noclip work across a dozen Source titles. But sharing an engine does not mean sharing everything typed into it.
impulse 101 is the example we run into most. It appears next to god and noclip on every Half-Life page, so it looks like part of the Source engine. It is not. It is a Half-Life command that hands out Half-Life's weapon list, and in a Source game that has no such list it does nothing at all.
An engine's cheat commands travel. Its content commands — item names, map names, weapon lists — do not.
6. It worked, and you did not notice what it cost
Sometimes the code runs perfectly and the disappointment comes later.
Bethesda games disable achievements for a save the moment you open the console. Paradox games do the same. Minecraft on Bedrock Edition turns achievements off permanently for a world once cheats are enabled — Java Edition advancements are unaffected, which is a difference worth checking before you flip the switch.
Nothing is broken here. The game simply decided that a run with cheats in it is not a run it will award anything for.
How to work out which one you have
- Does the console open at all? If not, it is reason 2 or 3 — the enabling step, or Ironman.
- Does the console open but reject the command? Check whether you are on someone else's server (reason 4).
- Does the command run and do nothing visible? It is probably reason 5 — a command from a sibling game.
- Does everything work but achievements stopped? That is reason 6, and it is working as designed.
- Does none of the above fit? Check the edition. Reason 1 hides inside a name that looks like packaging.
Every code on this site is labelled either reported working or tested, with the month we entered it ourselves. That distinction exists because of everything above: a code can be correct and still do nothing on your particular copy, and pretending otherwise helps nobody.
