While there is no single "Finish All Quests" button, recent updates to The Witcher 3: Wild Hunt
have changed how players interact with the debug console to fix or bypass bugged missions. Fixing "Patched" Quest Commands in 2026
If you find that older console commands for quest completion aren't working, it is likely due to the "Next Gen" and subsequent 2025/2026 updates which changed internal quest flags. Instead of a generic "complete" command, the current reliable method involves using the addfact function to trigger specific quest phases. How to Enable the Console
Before you can enter commands, you must enable the debug mode in your game files:
Navigate to your game folder: \The Witcher 3 Wild Hunt\bin\config\base. Open the general.ini file with Notepad. Add a new line at the bottom: DBGConsoleOn=true.
Save the file and restart your game. Press the tilde (~) key in-game to open the console. The Quest Completion Workaround: addfact
Most "complete quest" commands were never official; they were "facts" that the game checked to see if a stage was done. Use the following syntax: Command: addfact(quest_id_completed) witcher 3 complete quest console command patched
Example: To force-complete the "Blood Gold" treasure hunt if it gets stuck, you would enter: addfact(lw_gr39_treasure_opened). Finding Quest IDs
Because thousands of quest IDs exist, you often need to look up specific "Fact IDs" from community repositories like GitHub's Witcher 3 Booster or search for your specific quest on Reddit's Witcher 3 community. Useful Alternative Commands
If a quest is stuck because of a missing item or a dead NPC, it is often safer to spawn the missing element than to force-complete the quest, which can break future story triggers.
While there is no single "one-click" console command to complete a quest in The Witcher 3, you can use the debug console to manually force quest progression or bypass bugs by manipulating the game's internal flags, known as Facts.
The original method for quest debugging remains active in the next-gen update (v4.04), though it requires manually identifying quest-specific IDs. Enabling the Debug Console
Before attempting to fix a quest, you must enable the console in the game's configuration files: While there is no single "Finish All Quests"
Navigate to your game's installation folder (e.g., Steam\steamapps\common\The Witcher 3 Wild Hunt\bin\config\base). Open the general.ini file using a text editor like Notepad.
Add the line DBGConsoleOn=true under the [General] section and save.
Launch the game and press the ~ (tilde) or F2 key to open the console. How to Force Quest Completion
Because quests are complex world-state triggers, simply "finishing" one often requires setting specific progress markers.
Is there a console command to finish a bugged quest? | Forums
goto to bypass obstacles.spawn to get quest items.setlevel to overcome difficulty walls.| Command | Intended Effect | Current Status (Patch 4.04) |
|--------|----------------|-------------------------------|
| addfact(q###_completed) | Marks quest stage as finished | Unreliable – facts vary by quest ID |
| completequest('questname') | Completes main objective | Never officially existed (common myth) |
| abort() | Cancels current quest | Works, but may break later triggers |
| witcherQuest('q001') | Internal test command | Patched out post-1.31 | Use goto to bypass obstacles
You cannot type the quest name (e.g., "Bloody Baron"). You must use the specific code. This is usually formatted as qXXX_name.
How to find the code: There are two ways.
findquest [keyword]
findquest baron will return q003_barons and other related IDs.To see what's really broken:
getfact active_quests
Then to clean orphaned quest flags (safe to run anytime):
clearorphanedfacts
Instead of completequest, you must advance the quest stage by stage using:
addfact(some_fact_string)
or use the debug console enabler + abort or finish via quest stage IDs.