Witcher 3 Complete Quest Console Command Top May 2026

To complete a bugged or tedious quest in The Witcher 3: Wild Hunt using console commands, you must first enable the debug console and then use specific "fact" IDs to force a quest into its finished state. How to Enable the Debug Console

Before entering commands, you must unlock the console in your game files:

Locate Game Files: Navigate to your installation folder (e.g., Steam\steamapps\common\The Witcher 3 Wild Hunt\bin\config\base). Edit Config: Open the general.ini file with Notepad.

Add Activation Line: At the very end of the file, add DBGConsoleOn=true.

Launch Game: Open the game and press the ~ (tilde) key or F2 to open the command line. The Command to Complete Quests

Unlike games like Skyrim that use a simple "completequest" command, The Witcher 3 uses a "fact" system to track progress. To complete a quest, use: addfact(FactID_completed)

Replace FactID with the specific internal name for your quest. For example, to force the completion of the "Blood Gold" quest, you would enter addfact(lw_gr39_treasure_opened). Common Quest Fact IDs Quest / Objective Cerys/Hjalmar Choice addfact(q206_completed) Radovid Assassinated addfact(mq3035_fdb_radovid_dead) Whoreson Junior Dead addfact(q302_whoreson_dead) Sent Keira to Kaer Morhen addfact(q109_keira_to_km)

Note: Commands are case-sensitive. Ensure you type them exactly as they appear in internal game files. Finding Specific Quest IDs

If the quest you need isn't listed above, you can find specific IDs through these methods: Guide :: The Witcher 3 Console Commands: Ultimate Edition

In The Witcher 3: Wild Hunt , there is no single "complete quest" command like those found in games like Skyrim. Instead, quests are tracked through a system of "facts" that represent choices, objectives, and world states. Primary Quest Commands

To manipulate quest progress, you must use the addfact command followed by a specific Quest ID.

addfact(quest_id_completed): Marks a specific quest or objective as finished.

removefact(quest_id): Removes a recorded choice or objective, which can sometimes be used to "reset" a bugged state. Examples of Quest Fact Commands witcher 3 complete quest console command top

Because IDs are specific to each quest, you must know the exact internal name. Common examples found in community forums include:

addfact(q309_completed): Completes the quest "Now or Never".

addfact(q206_completed): Helps Cerys or Hjalmar after the massacre in Kaer Trolde.

addfact(q309_triss_lover): Sets the world state to show Geralt romanced Triss.

addfact(mq3035_fdb_radovid_dead): Records that Radovid was assassinated in "Reason of State". How to Enable the Console

Before using these commands, you must enable the debug console in your game files: The Witcher 3: Wild Hunt - Complete Edition – Cheats

The primary console command for completing or manipulating quests in The Witcher 3: Wild Hunt addfact(fact_id)

. This command manually triggers quest stages or flags a quest as finished by adding a specific internal "fact" to the game's database.

Because the game lacks a universal "complete current quest" button, players must use specific for each quest or its completion phase. CD Projekt Red 1. Enabling the Console

Before using commands, you must enable the debug console by editing your game files: Navigate to Game Folder The Witcher 3 Wild Hunt\bin\config\base general.ini with Notepad. DBGConsoleOn=true at the end of the file. Open Console : In-game, press the (tilde) or key to open the command prompt. Steam Community 2. Core Quest Commands

There is no single command to instantly finish any quest; instead, you trigger the "completed" state of a specific quest ID. CD Projekt Red

Is there a console command to finish a bugged quest? | Forums To complete a bugged or tedious quest in

To complete quests in The Witcher 3: Wild Hunt using the debug console, you typically use the

command rather than a single "complete quest" button. This command allows you to manually trigger "facts" or milestones that the game uses to track progress. Core Commands for Quest Manipulation Because quests in The Witcher 3

are complex chains of events, completing one often requires triggering specific IDs (facts) associated with that quest's completion state. addfact(fact_id)

: Triggers a specific event or marks a quest objective as finished. For many quests, adding a fact like [quest_id]_completed

will move the quest to the "Completed" section of your journal. removefact(fact_id)

: Use this if you accidentally triggered a milestone or want to "un-complete" an objective to fix a bug. Examples of Common Quest & Outcome Facts

These are used to force specific game states or finish major storylines: addfact(q309_completed) : Marks the quest "Now or Never" as complete. addfact(q110_calmed_down_ciri)

: Simulates a "good" choice for the ending (snowball fight). addfact(q302_whoreson_dead)

: Forces the state where Whoreson Junior is killed during "Get Junior". addfact(q109_keira_to_km)

: Sends Keira Metz to Kaer Morhen, completing her arc favorably. CD Projekt Red How to Enable the Debug Console

Before you can use these commands, you must enable the console in your game files: Console command to complete quest :: The Witcher 3

Part 4: How to Instantly Fail a Quest (The "Alternate" Top Command)

Sometimes, completing a quest isn't your goal. You may want to fail a timed quest to see alternative dialogue or to clear your journal. The command for this is: Part 4: How to Instantly Fail a Quest

removefact(qxxx_xxx_xxx_started)

Example: To fail the quest "The Gangs of Novigrad" (ID: q302), you would type:

removefact(q302_started)

This tells the game you never began the quest, auto-failing it. To force a specific failure state, find the _failed fact:

addfact(qxxx_xxx_xxx_failed)

Part 1: How to Enable the Console (The Prerequisite)

Before any command works, you need to unlock the developer console. CD Projekt Red left it in the game engine but disabled it by default.

Step-by-step activation:

  1. Navigate to your Witcher 3 bin folder (e.g., C:\Program Files (x86)\Steam\steamapps\common\The Witcher 3\bin\config\base).
  2. Find the file named general.ini .
  3. Open it with Notepad or any text editor.
  4. Add the following line at the bottom:
    DBGConsoleOn=true
  5. Save the file and close it.

Alternative (Mod Method): Install the Developer Console Mod from Nexus Mods. It adds visual feedback and command history.

Once enabled, press the ~ (tilde) key (or F2 on some keyboards) to open the console in-game.

3. Complete Quest by ID (Full List)

| Quest | ID | Notes | |-------|----|-------| | Main game ending | q601 (final battle) | Risky — may skip epilogue | | Gwent: Old Pals | q208_gwent_friends | Complete with addfact("q208_gwent_friends_completed") | | Cave of Dreams | q210_cave_of_dreams | Breakable if completed too early | | Reason of State | q302_radovid_treason | Use facts to avoid bugs |

A. addexp(amount)

Adds experience points. Use this if you want to simulate the XP reward of a completed quest.

  • Example: addexp(1000)

4. The Holy Trinity of Quest Manipulation

These are the specific commands used to advance or complete objectives. Use these with extreme caution.

✅ Pros

  • Skip bugs – Unstuck broken quests (e.g., “Return to Crookback Bog”).
  • Quick testing – Jump to endgame or specific loot/mutagens.
  • No need for save editors – Works on the fly.

2. showpins(1) and showpins(0)

This is arguably the "top" command for completionists who don't want to spoil the story but need help finding objectives.

  • Function: showpins(1) reveals every map pin and marker on the current map, including hidden quest objectives, merchants, and undiscovered locations.
  • To disable: Type showpins(0).
Scroll to Top