TheGameCrateTheGameCrate
Preservation

Type Your Name, Break the Game: GTA1 Cheats and Debug Culture

The first Grand Theft Auto hid its cheat codes in the high-score name field, and one of them opened a door into the developers' toolbox.

September 10, 2026· 3 min read

Cheat codes used to be a folk art form. Before achievements, before online guides, before a game could be patched, they were things passed around playgrounds and magazine columns, and the best of them were never meant to be found by accident. The first Grand Theft Auto has one of the more charming systems from that era: you enter them as your player name.

The mechanism is simple. Where the game asks who you are, you type a special word instead, and the game quietly reads your name as an instruction. On PC, community documentation lists codes such as “itsgallus,” which unlocks all the cities, and a weapons-and-jail-card code that is exactly as subtle as it sounds. The PlayStation version has its own set, entered at the name entry screen, and fan-maintained lists, including Grand Theft Wiki, catalogue entries like “WEYHEY” for a huge points total and “SATANLIVES” for extra lives, alongside codes that remove the police or grant a scoring multiplier. I would treat all of these as community-documented rather than officially published, and it is worth checking a list against a real copy of the version you own.

The most interesting entry is not really a cheat at all. Typing “porkcharsui” as a player name switches on a debug mode. According to the same community documentation, it gives access to developer functions such as camera controls, screen capture and level restarts through specific keyboard inputs. That is a rare thing: a documented door into the working tools of the people who made the game, left ajar in a released product.

This is a big part of what makes early game code so valuable to preservationists. Debug modes, hidden menus and developer shortcuts are a kind of fossil record. They show how the team tested its own levels, what they needed to see while building them, and how they moved around a world before the polish went on. Games from this era were often shipped with these tools still compiled in, sometimes guarded by an obscure code and sometimes not guarded at all. Later, publishers grew more careful about stripping them out, which makes the ones that survived in classic titles all the more useful.

It also says something about the culture of the studio. Naming a debug switch after something as absurd as “porkcharsui” is not the choice of a team building a corporate product. It is a joke that got baked into the executable. For a series that later became a byword for shrugging, provocative humour, that seems fitting.

There is also a lesson here about how we document games. Cheat codes survive because people write them down, and they survive in a format that is inherently fragile: a list on a website, a forum post, a scanned magazine page. If a particular code does not work in your version, that is not necessarily an error in the wiki. Different releases, ports and patches had different behaviours, and knowing which version a code belongs to is a part of the record that is easy to lose. Good preservation work notes the platform, the region and the release each time.

If you have a working copy of the game, enter one of the documented codes just to see the system in action. The tiny thrill of typing a word and watching a game change its rules is one of the purest pleasures the medium ever had, and it is worth keeping alive.