Witcher 3 Complete Quest Console Command Patched -

Use script extenders / mods that provide safer quest fixes

Use save-game editors that modify quest flags properly

Console workaround: run underlying script/command

Revert to an earlier patch or mod roll-back (advanced)

Since the Next-Gen update (Patch 4.0+), users report specific issues when using commands.

Note: These commands are for the PC version. Console players (PS/Xbox) cannot access the developer console.

While there is no single "Complete All Quests" button, you can still use specific console commands to force quest completion or bypass bugs in The Witcher 3

. Despite various updates, the core method remains using the command to set a quest’s state to finished. How to Use the Completion Commands

To complete a specific quest, you must first enable the debug console and then input a command tailored to that quest's unique ID. Enabling the Console The Witcher 3/bin/config/base general.ini . Add the line DBGConsoleOn=true at the bottom and save. Completing a Quest : Use the command addfact(QuestID_completed) . For example, to finish "Blood Gold," you would enter addfact(lw_gr39_treasure_opened) Finding IDs

: You often need to dig through community resources or game files (like ) to find the exact ID for your specific quest. Why "Patched" is Often Mentioned

The term "patched" usually refers to CD Projekt Red fixing common quest-breaking bugs, which reduces the for these commands, rather than them being removed. Witcher Wiki Unlocking Console Commands and Cheats in The Witcher 3 witcher 3 complete quest console command patched

To complete quests via the console in The Witcher 3 , you generally use the addfact() command to trigger specific "quest phases" or completion flags. While some players believe quest commands were "patched" out, they are actually just more complex than a simple "complete quest" button because the game tracks story progress through hundreds of individual flags called "facts". How to Use Quest Console Commands Enable the Console:

Navigate to your game folder: The Witcher 3 Wild Hunt\bin\config\base. Open general.ini with Notepad. Add the line DBGConsoleOn=true at the bottom and save. In-game, press the ~ (tilde) key to open the interface. Use the addfact() Command:

There is no universal "complete current quest" command. Instead, you must enter the specific ID for that quest's completion phase. Syntax: addfact('quest_id_here').

Example: To complete the "Blood Gold" treasure hunt, you would enter addfact(lw_gr39_treasure_opened). Find Quest IDs:

Because quest IDs are hidden, you often need to look them up in community resources like the TW3 Facts GitHub or use mods like the Debug Console Extensions to view active quest flags.

Common troubleshooting commands for "stuck" quests also include removefact('flag_name') to reset a bugged trigger. Essential "Next-Gen" Console Commands

If you are using the Next-Gen (4.0+) update, these basic commands still work and are often more reliable than quest manipulation for progressing through a difficult area:

To complete bugged quests in The Witcher 3: Wild Hunt on the latest patches (including Next-Gen), there is no single "finish quest" button. Instead, players must use the addfact command to manually trigger quest completion states. Enabling the Console Before using commands, you must enable the debug console:

Navigate to your game folder: ...The Witcher 3 Wild Hunt\bin\config\base. Open general.ini with a text editor.

Add the line DBGConsoleOn=true under the [Config] section and save. In-game, press the ~ (tilde) key to open the console. How to Force Quest Completion

Quests in The Witcher 3 progress through "facts" or internal flags. If a quest is stuck, you can force it to the next stage or end it entirely by adding the completion fact: Standard Syntax: addfact(quest_id_completed). Use script extenders / mods that provide safer quest fixes

Example: To force-complete the "Blood Gold" treasure hunt, you would enter addfact(lw_gr39_treasure_opened).

Finding IDs: Specific quest and fact IDs are often found in community-maintained databases or by using the Witcher 3 REDkit Quest Debugger. Critical Tips for Quest Fixing Guide :: The Witcher 3 Console Commands: Ultimate Edition

For players of The Witcher 3: Wild Hunt, few things are as frustrating as a quest that refuses to progress due to a bug or a missing NPC. While many old workarounds and mods have been patched or rendered obsolete by the Next-Gen update (v4.0+), you can still use the built-in debug console to force-complete or bypass problematic quest stages. How to Enable the Console in the Current Version

You no longer need external mods like the "Debug Console Enabler" from Nexus Mods, as many of these are now outdated. Instead, you can activate the native console by editing a single game file:

Locate your game folder: On Steam, right-click The Witcher 3 in your library, select Manage, then Browse Local Files.

Find the configuration file: Navigate to \bin\config\base and open the file named general.ini with a text editor like Notepad++.

Add the command: At the bottom of the text, add a new line: DBGConsoleOn=true.

Save and Start: Save the file and launch the game. Press the ~ (tilde) key or F2 to open the console overlay. The "Complete Quest" Command (The "Fact" Method)

Unlike games like Skyrim, The Witcher 3 doesn't have a single universal "CompleteQuest" command. Instead, the game tracks progress through "Facts"—tiny flags that tell the game you've reached a specific milestone.

If a quest is stuck, you must use the addfact command to tell the game you've finished it. The basic syntax is: Mods and The Witcher 3 next-gen update - Cyberpunk | Forums

To complete a quest using console commands in The Witcher 3 (including the Next-Gen Patch 4.04 ), you must use the Use save-game editors that modify quest flags properly

command. There is no single "finish quest" button; instead, you must manually trigger the "completed" state of the quest's ID. 1. Enable the Debug Console

If you haven't already, you must enable the console in your game files: Navigate to your game folder: The Witcher 3 Wild Hunt\bin\config\base general.ini with Notepad. Add the line DBGConsoleOn=true at the bottom of the ConfigVersion=5

is present in the file for the Next-Gen version to recognize changes. In-game, press the tilde key ( to open the console. 2. Find the Quest ID

Every quest has a unique internal "Fact ID" that marks it as finished. Guide :: The Witcher 3 Console Commands: Ultimate Edition

As of my latest update (mid-2025), the ability to auto-complete quests in The Witcher 3 using simple console commands like completequest or finishquest has been patched out by CD Projekt Red in the next-gen updates (Version 4.0+).

However, there is still a workaround using the console if you know the quest stages.

Here’s the accurate, up-to-date content on this topic.

Mods like "Console Commands Reborn" attempted to bypass the legitimacy checks by injecting dummy facts before completion. The author abandoned it after patch 4.04, stating: "CDPR hardcoded 47 main quests to ignore external completion signals. A mod cannot override this without breaking the EULA."

Attempting to use outdated versions results in an immediate CTD (Crash to Desktop) when opening the quest journal.

This method uses the game's built-in console.

Look for the file config_base inside the bin folder (not the x64 folder). If you don't have it there, look in \bin\config\base.

Open config_base with Notepad.

Find the line DBGConsoleOn=false.

Change it to DBGConsoleOn=true.

Save the file.

In-game, press the Tilde (~) or F2 key to open the console.

If a recent update or mod appears to have patched or broken the in-game console command completequest (used to finish quests instantly), this post explains how to detect the change, safe alternatives, and practical workarounds to restore progress without corrupting saves.

Since the "magic button" is gone, players must use more specific methods to bypass broken quest stages.