How developer consoles work in Unreal, Unity and Creation Engine

Ninety percent of the "cheat codes" people type into a PC game today are not cheat codes at all — they are commands into a debug console the engine ships with. The console is a tool for the developers, kept in the release build because turning it off entirely is more effort than leaving it alone. If you know which engine a game uses, you can guess a lot about how its console will behave.

Unreal Engine

Unreal has had a console since Unreal Tournament. You open it with the tilde key by default, and it accepts three kinds of things: engine commands built into the runtime, cvars (console variables) exposed by the game code, and cheats registered in a special cheat manager that only exists when the game runs with the -cheats launch flag or is built as a development configuration.

Retail builds of Unreal games usually strip the cheat manager and leave only the engine commands and safe cvars. That is why god and fly work in Fortnite Creative but not in ranked matches — Epic disables the cheat manager on live servers. Games that ship with cheats enabled (a lot of single-player Unreal titles do) will accept the whole set: god, fly, ghost, slomo 0.5, summon <ClassName>, teleport.

Cvars are the interesting part. r.ScreenPercentage 200 doubles the internal render resolution. t.MaxFPS 30 caps the framerate. stat unit shows the frame breakdown. These are not cheats, but they are the same interface, and they explain why so many "hidden features" people find in Unreal games are just cvar tweaks.

Unity

Unity does not ship a built-in developer console. That is why cheat codes in Unity games are inconsistent — every studio implements their own. Some ship a full console (Cities: Skylines, Rimworld, Subnautica with mods) and some ship nothing.

When a Unity game does have a console, it is almost always a MonoBehaviour that captures keystrokes and runs a small parser. Because Unity does not standardize this, the commands are game-specific and change between patches. There is no god command that works across Unity titles the way it does across Unreal titles.

For cheating in Unity games without a console, mod loaders like BepInEx and MelonLoader are the standard tools. They inject C# code into the running game and give you a way to patch methods at runtime. That is the technical foundation under most Unity trainers.

Creation Engine (Bethesda)

The console in Skyrim, Fallout 4 and Starfield is different from the other two because it is documented and beloved. Bethesda knows people use it, keeps it in retail builds, and ships games that assume it will be there.

The command set is enormous. tgm turns on god mode. tcl toggles collision. player.additem <ID> <count> gives you anything in the game if you know its 8-character hex ID. setav speedmult 200 doubles your movement speed. psb gives you every spell in the game. The wiki pages for these commands are longer than the strategy guides.

The console is also the standard way modders debug and QA testers verify. That is why Bethesda has left it in every game since Morrowind — removing it would break the tool chain their entire modding community relies on. Achievements disable when the console is used, but nothing else does.

Why the pattern matters

If you can identify a game's engine, you can predict its cheat surface without any research. Unreal games will usually have god, fly, slomo and a set of cvars. Unity games might have anything, but probably a bespoke parser or nothing at all. Creation Engine games will have the full Bethesda command set with the game's own IDs.

This is also why cheats do not port between games even on the same engine. god works in most Unreal titles, but summon FortAthenaChest only works in Fortnite because that class only exists there. The engine defines the interface; the game defines the specific commands available through it.