Top | Witcher 3 Complete Quest Console Command

Top | Witcher 3 Complete Quest Console Command

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

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) witcher 3 complete quest console command top

: 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

To complete a quest in The Witcher 3 using the console, the standard command is addfact(quest_id_completed) or using a quest-specific success flag. Unlike some other RPGs, there isn't a universal "completequest" command that works reliably for every entry in the journal without potentially breaking scripts. Essential Quest Commands

If you have the Debug Console enabled, these are the primary ways to manipulate quest progress:

addfact(fact_id): This is the most common method. You must replace fact_id with the specific internal name for a quest's completion state (e.g., q101_done). To complete a bugged or tedious quest in

removefact(fact_id): Useful if you accidentally completed a quest or want to reset a specific world state.

setcustomhead(id): While not a quest command, it's often used alongside them to reset Geralt's appearance if a quest script forces a change. How to Find Quest IDs

Because The Witcher 3 commands are case-sensitive and require specific internal names, finding the right ID is the hardest part:

Check Community Lists: Sites like Witcher 3 Wiki or Steam Community Guides host spreadsheets of quest and "fact" IDs.

Quest Debugger: For modders using the REDkit, the Quests Debugger tool allows you to see active quest phases in real-time. Important Warning

Forcing quests to complete can break the main story line. If you skip a quest that sets a vital "fact" (like a character surviving), future quests may fail to trigger or characters might not appear where they should. It is highly recommended to save your game before attempting any quest-related commands.

The Witcher 3 Console Commands: Ultimate Edition - Steam Community

To complete or manipulate quests in The Witcher 3: Wild Hunt using the debug console, players primarily use the addfact() and removefact() commands. These commands allow you to manually trigger "facts"—the internal flags the game uses to track progress, story decisions, and quest states. Essential Quest Control Commands

While there is no single "complete_quest" command that works for every mission, you can use these specific tools to advance or fix bugged objectives:

addfact(FactID): Marks a specific quest stage or world event as completed.

removefact(FactID): Removes a completed flag, often used to restart a failed quest or undo a specific decision. Part 8: The "Top" Alternative – Scripts vs

addkeys: Instantly grants every key required to open doors in the game, which can bypass quests stuck behind locked areas. Common Quest and Romance Fact IDs

The game uses unique strings for every major milestone. Here are some of the most frequently used IDs for the addfact() command: Goal / Quest State Fact ID to use in addfact() Complete "Now or Never" q309_completed Romance Triss Merigold q309_triss_lover and q309_triss_stayed Romance Yennefer sq202_yen_girlfriend Kill Radovid (Assassination) mq3035_fdb_radovid_dead Kill Whoreson Junior q302_whoreson_dead Ciri Snowball Fight (Good Choice) q110_calmed_down_ciri Ciri Empress Ending Requirement q110_visited_emhyr How to Use Quest Commands Guide :: The Witcher 3 Console Commands: Ultimate Edition

Here’s a deep, technically accurate answer for using console commands to complete quests in The Witcher 3, focused on the completequest command and its nuances.

Part 8: The "Top" Alternative – Scripts vs. One-Liners

If you find yourself repeatedly typing addfact(qxxx_completed) for dozens of quests, consider using a console script. Create a .txt file in your \The Witcher 3\bin\ folder named complete_all.txt. Inside, write:

addfact(q104_completed)
addfact(q105_completed)
addfact(q201_completed)
addfact(q302_completed)
// Add all your quest facts here

Then in-game, type: exec complete_all.txt

This will run all commands in sequence. This is the ultimate "top" efficiency method for power players.

How to Enable the Console (Step-by-Step)

Before you can use any top commands, you must enable the console.

  1. Navigate to your The Witcher 3 bin/config/base directory.
  2. Find the file general.ini.
  3. Open it with Notepad.
  4. Add the following line at the bottom: DBGConsoleOn=true
  5. Save the file. If the file doesn't exist, create it.
  6. Launch the game. Press the ~ (Tilde) or F2 key (depending on keyboard layout) to open the console.

Pro-Tip: If you want a visual interface, download the "Community Patch - Base" and "Console Commands" mod from Nexus Mods. It adds autocomplete, which is a lifesaver.

Integration Notes

Command Format

addfact(q302_completed)

Or for quest stages:

addfact(mq0001_stage)

A Warning on Quest IDs

The most difficult part of this process is discovering the correct Quest ID. The internal names are cryptic.