Witcher 3 Console Commands: The Complete Debug Guide
CD Projekt Red built an extraordinarily deep RPG in The Witcher 3: Wild Hunt, but beneath its polished surface lies an even more powerful layer — the developer debug console. Whether you want to skip a frustrating section, test build ideas without grinding, or simply explore what the game's engine is capable of, Witcher 3 console commands put the entire game world at your fingertips. This guide covers everything you need to know to enable and use the debug menu effectively on PC.
How to Enable the Debug Console
The console is not active by default in retail versions of The Witcher 3. To unlock it, you need to install the Debug Console Enabler mod from Nexus Mods — search for it by name and follow the installation instructions, which typically involve placing a single DLL file into your game's bin/x64 folder. Once installed, press the tilde key (~) or F2 (depending on your mod version) during gameplay to open the console overlay. No save file is required and the console works on any existing playthrough.
Note that using console commands can disable achievements in your current session on some versions of the game. If achievements matter to you, keep a separate save file before experimenting.
Essential Witcher 3 Console Commands for Every Player
The most commonly used Witcher 3 console commands cover experience, currency, and basic character management. Here are the commands you'll reach for most often:
setlevel(50) — Set Geralt's level directly
addmoney(9999) — Add crowns to your wallet
healme — Restore Geralt to full health instantly
god — Toggle invincibility on or off
likeaboss — One-hit kill all enemies
AllowFT(1) — Enable fast travel from any location
ShowAllFT(1) — Reveal all fast travel points on the map
These commands are safe to use mid-game and won't corrupt your save. The setlevel command is particularly useful for testing high-level builds without committing dozens of hours to leveling in the witcher series' demanding progression system.
Spawning Items and Equipment
One of the most powerful features of the debug console is item spawning. The command structure is additem('ItemName', quantity). Item names must match the game's internal identifiers exactly — capitalization matters. Some essential examples include:
additem('Bear3') — Add Ursine Witcher Gear (Grandmaster tier)
additem('Cat3') — Add Feline Witcher Gear (Grandmaster tier)
additem('Griffin3') — Add Griffin Witcher Gear
additem('Wolven3') — Add Wolf School Gear
additem('Dimeritium Ore', 20) — Add crafting materials
additem('Ruby', 10) — Add gemstones for selling or crafting
Complete item ID lists are maintained by the Witcher community on wikis and fan sites. The witcher game's internal item database contains thousands of entries covering weapons, armor, alchemy ingredients, quest items, and more.
Managing Skills and Ability Points
Respeccing in The Witcher 3 normally requires a Potion of Clearance, which is expensive and sometimes hard to find. The console makes skill management far more flexible. Use these commands to control your character build:
addabl('sword_s1') — Unlock a specific ability by internal ID
removemutagen('Mutagen_Strong_Red') — Remove a slotted mutagen
setstat('AttackPower', 9999) — Raise a specific stat value
For RPG gaming enthusiasts who want to theory-craft builds, these commands are invaluable. You can test a full Signs build, reset it, and switch to a pure combat build within minutes — something that would take hours through normal play.
World and Weather Control Commands
The debug console also gives you control over the game's environment. These commands are useful for screenshots, exploration, and general experimentation:
WitchersHut — Teleport to a specific location
settime(12,0) — Set the in-game time to noon
setbeard(1) — Toggle Geralt's beard growth stage (1-4)
TM(0.5) — Slow game time to half speed
TM(1) — Return to normal game speed
Quest and Progression Commands
Stuck on a bugged quest or want to skip a section you've already completed on a previous run? The Witcher 3 console commands include quest control functions that let you advance or restart story missions. Use startquest('QuestName') with the internal quest ID to begin any quest, or setquestphase('QuestName', phase_number) to jump to a specific stage. Be cautious — skipping quest phases can occasionally create inconsistencies in journal entries or NPC states, so always save before using these commands.
Tips for Using the Debug Console Responsibly
The debug console is a powerful tool, but it works best when used with intention. A few best practices: always maintain a clean save file before heavy console use; avoid spawning story-critical quest items before their intended trigger points; and use god mode sparingly if you want to preserve any sense of challenge. The witcher series is designed around a specific difficulty curve, and the console is most rewarding when used to enhance your experience rather than bypass it entirely. Use it to fix problems, experiment with builds, or set up the perfect screenshot — and you'll find it an indispensable companion to one of gaming's greatest RPGs.