To complete quests in The Witcher 3: Wild Hunt using console commands, you must first enable the debug console and then use specific fact-based commands rather than a single "finish quest" button. 1. Enable the Debug Console
You can enable the console by modifying game files or using a mod. Manual Method:
Navigate to your game directory: \The Witcher 3 Wild Hunt\bin\config\base. Open general.ini with a text editor like Notepad. Add the line DBGConsoleOn=true at the very end and save.
Activation: Once in-game, press the ~ (tilde) key to toggle the console window. 2. Primary Quest Completion Commands
Because quest states are tracked via "facts," you must tell the game that a specific stage or the entire quest has happened using the addfact command. addfact(ID_Name)
Marks a specific quest stage or world state as true/completed. removefact(ID_Name)
Removes a quest fact, which can sometimes "un-stick" a bugged quest. 3. Common Quest and Story IDs witcher 3 complete quest console command
To use these commands, you need the internal Fact ID. Here are some common examples of IDs used for quest progression and story outcomes: General Quest Completion:
q206_completed: Helps resolve issues around the massacre in Kaer Trolde.
q105_evil_spirit_destroyed: Resolves the "The Whispering Hillock" quest by marking the spirit as destroyed. Character and Ending Outcomes: q206_hjalmar_king: Sets Hjalmar as King of Skellige.
mq3035_fdb_radovid_dead: Marks Radovid as assassinated for "Reason of State". q109_keira_to_km: Sends Keira Metz to Kaer Morhen. q302_whoreson_dead: Marks Whoreson Junior as dead. 4. How to Find Specific Quest IDs
Since there is no universal list for every minor objective, you may need to dig for specific IDs if a quest is bugged:
To complete quests in The Witcher 3: Wild Hunt using the debug console, you must use the addfact command. Unlike some RPGs with a single "finish quest" button, this game tracks progress through "facts" that represent specific narrative milestones. 1. Enabling the Debug Console To complete quests in The Witcher 3: Wild
The console is disabled by default. You can enable it by modifying your game files or using a Nexus Mods enabler.
Navigate to your game directory: .../The Witcher 3 Wild Hunt/bin/config/base/. Open general.ini with a text editor like Notepad. Add the line DBGConsoleOn=true at the bottom and save. In-game, press the ~ (Tilde) key to open the console. 2. The Command Structure
To "complete" a quest, you typically need to add the fact that triggers its finished state. Command: addfact(quest_id_completed)
Example: To finish the quest "Blood Gold," you would use addfact(lw_gr39_treasure_opened).
Case Sensitivity: Commands and IDs are strictly case-sensitive. 3. Essential Quest Fact IDs
The game uses internal codes (IDs) rather than the visible quest titles. Common IDs used for completing or fixing major quests include: Forcing a main story branch If you want
Place to find out quest names by ID number? | Page 2 | Forums
Here’s a detailed, practical piece on using the complete quest console command in The Witcher 3: Wild Hunt.
If you want to test the endgame without playing 80 hours, complete main quests in sequence:
completequest('q101_lilac') → completequest('q201_velen') → completequest('q302_novigrad') → completequest('q401_skellige') etc.
⚠️ Warning: Completing main quests out of order can break your save beyond repair. Always keep a manual backup.
You want to start New Game+ with a specific set of gear unlocked by a late-game quest. You can quickly complete the prerequisite quests on a test save, craft the gear, then start NG+.
gameplay/quests/questlist.ws in the game filesxdbskipfact Command (Fixing Buggy Stages)If a quest is bugged and won't progress to the next stage (e.g., a door won't open, an NPC is missing), use this to force the current objective to complete and move to the next one.
The Command:
xdbskipfact
addfact because it only advances the quest one step at a time, preventing you from accidentally skipping dialogue or cutscenes you wanted to see.