ItemFix Logo

Witcher 3 Complete Quest Console Command Patched Work ★ Latest & Hot

To complete a quest using console commands in The Witcher 3 (including the Next-Gen Patch 4.04 ), you must use the

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

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. witcher 3 complete quest console command patched

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

3. Completing the Entire Quest (The "Nuke" Option)

This marks the quest as "Completed" in your journal, gives you the XP, and usually teleports you out of the quest area. It marks every stage as done.

Command:

questcomplete("quest_id")

Example: questcomplete("q003_barons")

The Modder's Counter-Attack: Un-patching the Patch

Here is the most important part for PC players: While the command is patched in the vanilla v4.0+ game, it is not dead.

The modding community, specifically creators like wghost81 (famous for the Community Patch - Base), have reverse-engineered the changes. They have released mods that restore the debug console and, in some cases, improve the quest completion logic.

Workaround 2: The force Forked Mod (Discontinued)

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.

Part 5: Deep Dive Example Walkthrough

Scenario: You are playing the "Scavenger Hunt: Griffin School Gear" quest. You found the chest, but the game did not register it, and the quest marker is stuck on an empty chest.

  1. Open Console: Press F1 (or Tilde).
  2. Identify Quest: Type findquest griffin.
    • Result: q001_griffin_armor (Hypothetical ID).
  3. Check Stage: You are currently at the stage where you opened the chest. Let's assume that is stage 50. You need to be at stage 60 (Quest Complete).
  4. Execute Fix: 
    setstage("q001_griffin_armor", 60)
    Result: The quest journal updates, the XP is awarded, and the marker disappears.

Scenario 2: The quest is completely broken, and you just want it gone from your "Failed" or "Active" list. To complete a quest using console commands in

  1. Open Console.
  2. Execute: 
    questcomplete("q001_griffin_armor")
  3. Check Inventory: Did you get the diagram? No? 
    additem("q001_griffin_diagram")

Step-by-step: force-complete a quest (general method)

  1. Backup: Copy your save folder (Documents/The Witcher 3) and the game installation folder if desired.
  2. Enable console:
    • Install a known console enabler mod (e.g., "Debug Console Enabler") compatible with your game version and latest patches.
    • Follow the mod’s install instructions (usually drop files into the game’s mods folder and enable via mod manager or add to mods registry).
  3. Launch the game and load the save where the quest is active.
  4. Open the console (typically ~ or a mod-specified key).
  5. Identify the quest:
    • If you know the quest ID, proceed. If not, use in-console commands (if available) to list active quests (commands vary by enabler; common commands: getQuests, listQuests, or using showQuest).
    • Alternative: look up quest IDs online (quest names → quest IDs) or extract from game files.
  6. Use quest-complete command:
    • Common console syntax (mod-dependent) examples:
      • completeQuest("questId")
      • setQuestStage("questId", stageNumber)
      • finishQuest("questId")
    • If patched, you may need to set the quest to a high stage or directly toggle completion flags:
      • setQuestStage("questId", 100) — many quests treat high stage as completion.
      • completeObjective("questId", objectiveIndex) — completes a specific objective.
  7. Verify rewards/state:
    • After executing, check journal and inventory.
    • If rewards didn’t apply, manually adjust (add XP/gold/items) using console give commands (giveExp, addMoney, addItem("itemId", amount)).
  8. Save and test play:
    • Save to a new slot, quit to desktop, reload the new save, and confirm there are no dangling scripts or NPCs in strange states.

Step 1: Diagnose (View Current Stage)

getfact <quest_name>

Example: getfact q302 (q302 = "Family Matters" - The Bloody Baron)

This returns a number. That's your exact stage.

Step 2: Find the Next Valid Stage (The "Patch" Feature)

Open the game console and type:

listfacts <quest_name>

Example: listfacts q302

This outputs every possible stage fact for that quest. Look for the next logical number above your current getfact result.

What Still Works (Patched but Functional Method)

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. Example: questcomplete("q003_barons")