The tested badge

Cheat Codes We Have Actually Tested

Every code on this site is labelled either tested or reported working. This page is the whole list of the first kind, with the date each test was done.

8 of the 9,853 codes on this site have been entered by hand on the platform listed and watched to work — 0.1 per cent, across 2 games. Every one carries the date it was tested. The rest are published as reported working and say so.

Verified
Testing progress
Codes published 9,853
Tested by hand 8 (0.1%)
Games covered by a test 2
Testing started 23 August 2026
Most recent test 23 August 2026
That is a small fraction, and it is meant to be visible. Testing a code means owning the game, getting to the point it applies, and entering it on the right platform. The alternative — calling everything tested — is what most cheat sites do, and it is why the word means nothing anywhere else.

The list

23 August 2026

8

Enable cheat mode

Civilization IV: Beyond the Sword — Added under [CONFIG] in CivilizationIV.ini, this enables WorldBuilder and the debug keys.

PC Tested

Open WorldBuilder

Civilization IV: Beyond the Sword — Opens the map editor, which can add units, cities, gold and technologies mid-game.

PC Tested

Reveal the map

Civilization IV: Beyond the Sword — Uncovers the whole world map.

PC Tested

Enable the console

Icewind Dale — Added under [Program Options] in icewind.ini, this enables the console.

PC Tested

Add gold

Icewind Dale — Adds the given amount of gold to the party.

PC Tested

Set experience

Icewind Dale — Sets the selected character's experience total.

PC Tested

Create an item

Icewind Dale — Spawns the item with the given code into inventory.

PC Tested

Reveal the map

Icewind Dale — Uncovers the whole of the current area.

PC Tested

What readers report

Separate from the above, and deliberately so. These are readers pressing a button on a cheat page to say whether a code worked for them. They are useful — a code with a run of failures is worth retesting — but a click is not a test, and none of this changes any badge.

Reader confirmations by code
Code Worked Did not
God mode · Cry of Fear 0 3

How a code gets the badge

  1. It is published as reported working, with its source — the game's own documentation, its console, a manual, or a well-sourced community record.
  2. Someone here buys or already owns the game, gets to the point the code applies at, and enters it on the platform the code is listed under.
  3. If the effect happens, the code is marked tested and the date is recorded. If it does not, the code is corrected or removed.

Nothing automated can set that flag, and nothing does. Not an importer, not a reader vote, not a count of how many other sites list the same code.

Know a code that works and is not here? Send it in — it will be published as reported working, credited, and queued for testing like everything else.

Quick answers

Tested codes

What does "tested" mean on this site?
That a person here entered that exact code, on the platform shown beside it, in that game, and watched the effect happen. Not that it appears in several places online, and not that a reader said it worked. The date is when the test was done.
Why are so few codes tested?
Because testing one properly means owning the game, reaching the point the code applies at, and entering it on the right platform. That is slow. Publishing a code as reported working and labelling it honestly is better than either waiting years or pretending.
What does "reported working" mean, then?
That the code comes from the game's own documentation, its developer console, a manual, or a well-sourced community record — but nobody here has run it. Most codes on most cheat sites are in this state. The difference is that this one says which is which.
Readers say a code works. Does that make it tested?
No. Reader confirmations are shown separately, and counted separately, and they never change a code's badge. If they did, the badge would mean "some people clicked a button", which is not what anyone reading it would take it to mean.
A code stopped working after a patch. What happens?
Tell us and it gets retested. A tested date that predates a patch is exactly the signal this page exists to give you — it tells you how old the check is so you can judge it.