There’s no shame in wanting to bend the rules of your Civ playthrough every now and then. Whether you’re stuck in a brutal war against an aggressive AI, testing a new civilization build, or just want to spawn 100 tanks and roll over the map for fun, Civilization 7 console commands open up a huge range of customization options most players never get to use. I’ve spent dozens of hours testing these commands across single-player runs to figure out which ones work reliably, which cause game-breaking bugs, and how to enable them without messing up your save files.
How to Enable Civilization 7 Console Commands Safely
Before you can start entering commands, you’ll need to turn on debug mode for your game installation, a process that only takes a minute if you follow the right steps. First, if you own the game on Steam, open your library, right-click on Civilization 7, select “Properties”, and add -debug to the launch options field under the General tab. If you own the game on another platform, you can edit the config file in your game’s local files to set “DebugMode” to 1, which has the same effect.
Once debug mode is enabled, boot up the game and load any single-player save file. Press the tilde (~) key, usually located below the Escape key on most keyboards, to open the console input box. Always back up your save files before using console commands, because some commands can corrupt saves if used incorrectly, and you won’t be able to recover that progress otherwise. Console commands are disabled in official multiplayer matches to prevent cheating, and attempting to enable them can result in a temporary or permanent ban from online play, so stick to single-player runs only.
Most Useful Console Commands for Casual Play
If you’re not using commands to test builds and just want to fix a frustrating run or mess around for fun, these are the commands I use most often that rarely cause issues. Most of these Civilization 7 console commands work immediately, so you’ll see the change in your resource bar or map right after you hit enter. You don’t need to include brackets when entering commands, just replace the placeholder values with the numbers or IDs you want to use.
- AddGold [number]: Adds the specified amount of gold to your treasury. I usually use this to fix a sudden economic crash after a war, rather than giving myself unlimited gold right at the start of the game to keep things fun but balanced.
- AddFaith [number]: Works exactly like the gold command but for faith, perfect if you’re one turn away from unlocking a great prophet and an AI snatches it out from under you.
- RevealMap: Removes fog of war across the entire map, so you can scout out natural wonders, enemy positions, and resource spots without sending out units. I only use this if I’m playing a very slow, peaceful build and don’t want to waste turns exploring.
- AddUnit [unit ID] [number]: Spawns the specified number of units at your currently selected tile. This is the command I use most for testing new unit balances, or just spawning a fleet of battleships when a surprise AI invasion catches me off guard.
- SkipTurn [number]: Skips the specified number of turns instantly, perfect if you’re waiting for a wonder to build or a tech to research and don’t want to click through turns one by one.
You can find a full list of unit IDs on fan-run Civ databases if you don’t know the exact name of the unit you want to spawn. Also, avoid spawning more than 20 units at a time, as this can cause the game to crash, especially if you’re playing on a larger map with lots of AI civilizations already active. If you want a lot of units, spawn them in batches of 10 and wait a few seconds between each command to let the game process the changes.
Advanced Commands for Testing and Build Creation
If you’re a content creator, modder, or just someone who likes to test out broken civilization builds before you play them normally, these more advanced commands give you full control over almost every aspect of the game. The first one I use all the time is SetCivDifficulty [civ ID] [difficulty level], which lets you adjust the difficulty of individual AI civilizations mid-game. I use this a lot when I’m testing how well a new government build holds up against Deity level AI, without having to play through the first 100 turns every time to get to the late game.
Another useful advanced command is UnlockAllTechs, which instantly gives you every technology in the game. This is great for testing late game unit and building interactions without spending hours working your way through the tech tree, but it will remove most of the challenge from your run if you use it on a normal playthrough. Never use the UnlockAllTechs or UnlockAllCivics commands if you’re planning to earn achievements, as activating either of these will disable achievement progress for that save file permanently, even if you turn off debug mode later.
There’s also a ToggleAI command that stops all AI civilizations from taking their turns, which is perfect if you want to build up your empire for 50 turns without any interference from raiders or enemy invasions. Just remember to toggle it back on when you’re ready to start interacting with the rest of the world again, otherwise you’ll be stuck in an endless waiting loop when you hit the end turn button.
Common Console Command Mistakes to Avoid
I’ve messed up more than a few save files testing these commands, so I know first hand what mistakes you should avoid to keep your runs running smoothly. The first and most common mistake is using commands that change the game state right before an auto save. If you spawn 100 units and the game auto saves 2 seconds later, that save file could get corrupted if the game didn’t have time to process all the new data. To avoid this, I always turn off auto save before I open the console, and save manually only after I’ve closed the console and waited 10-15 seconds for all changes to load.
Another common mistake is using console commands to remove a civilization from the game mid-run. While the RemoveCiv command exists, it almost always causes bugs with trade routes, city state alliances, and world congress votes later in the game, even if you don’t notice the issues right away. If you want to remove an opponent, it’s much safer to use the AddUnit command to spawn enough troops to take them out normally, rather than deleting them entirely.
Don’t use console commands to edit city ownership unless you absolutely have to, as this can cause permanent bugs with production queues and building bonuses that never go away for the rest of the run. I learned this the hard way when I took a city from an AI using a command and it never let me build any specialty districts there, no matter what I did. The last mistake to watch out for is using too many commands at once. If you add gold, add faith, spawn 10 units, and reveal the map all in one go, there’s a much higher chance of the game crashing than if you use one command at a time and wait for it to take effect before using the next one.
At the end of the day, the point of playing Civ is to have fun, and there’s no right or wrong way to play if you’re enjoying yourself. Whether you use Civilization 7 console commands to fix a frustrating run, test new builds, or just mess around and cause chaos, they’re a great tool to make your playthroughs feel even more personal. Just follow the safety tips we covered, back up your saves, and don’t be afraid to experiment to find what works best for your play style.