Witcher 3 Complete Quest Console Command Direct

Before using any commands, you must enable the console:

Better than outright completion: set specific stage to trigger proper endings.

addfact(q302_stage_25)

Stages are numeric (e.g., 5, 10, 15, 20, 25). You can find them in the game’s w3strings files or quest modding guides.

Despite the risks, there are perfect scenarios for using the complete quest console command.

If you want to test the endgame without playing 80 hours, complete main quests in sequence:
completequest('q101_lilac') → completequest('q201_velen') → completequest('q302_novigrad') → completequest('q401_skellige') etc.

⚠️ Warning: Completing main quests out of order can break your save beyond repair. Always keep a manual backup.

If you are using console commands simply because a fight is too hard or you are tired of walking, you might find these quality-of-life commands easier than manipulating quest files:

To complete quests in The Witcher 3: Wild Hunt using console commands, you must first enable the debug console and then use specific fact-based commands rather than a single "finish quest" button. 1. Enable the Debug Console

You can enable the console by modifying game files or using a mod. Manual Method:

Navigate to your game directory: \The Witcher 3 Wild Hunt\bin\config\base. Open general.ini with a text editor like Notepad. Add the line DBGConsoleOn=true at the very end and save.

Activation: Once in-game, press the ~ (tilde) key to toggle the console window. 2. Primary Quest Completion Commands

Because quest states are tracked via "facts," you must tell the game that a specific stage or the entire quest has happened using the addfact command. addfact(ID_Name)

Marks a specific quest stage or world state as true/completed. removefact(ID_Name)

Removes a quest fact, which can sometimes "un-stick" a bugged quest. 3. Common Quest and Story IDs

To use these commands, you need the internal Fact ID. Here are some common examples of IDs used for quest progression and story outcomes: General Quest Completion:

q206_completed: Helps resolve issues around the massacre in Kaer Trolde.

q105_evil_spirit_destroyed: Resolves the "The Whispering Hillock" quest by marking the spirit as destroyed. Character and Ending Outcomes: q206_hjalmar_king: Sets Hjalmar as King of Skellige.

mq3035_fdb_radovid_dead: Marks Radovid as assassinated for "Reason of State". q109_keira_to_km: Sends Keira Metz to Kaer Morhen. q302_whoreson_dead: Marks Whoreson Junior as dead. 4. How to Find Specific Quest IDs

Since there is no universal list for every minor objective, you may need to dig for specific IDs if a quest is bugged: witcher 3 complete quest console command

The Witcher 3 does not have a single "complete quest" command like Bethesda games do . Instead, you must use to manually progress or finish specific quest stages. CD Projekt Red Core Command

To mark a quest or objective as done, use the following syntax in the debug console addfact(fact_name) — Sets a specific quest objective or world state as true. removefact(fact_name) — Resets a fact if a quest is bugged. Common Completion Facts

Because the game uses thousands of internal strings, there isn't one list for every quest, but many major quests follow a pattern: CD Projekt Red Console Command Complete "Now or Never" addfact(q309_completed) Complete "King's Gambit" addfact(q206_completed) Kill Radovid (Reason of State) addfact(mq3035_fdb_radovid_dead) Close "Blood Gold" addfact(lw_gr39_treasure_opened) How to Find Quest IDs

If the quest you need isn't listed above, you have to find the specific "fact" name used by the game's engine:

The Quests Debugger is a useful tool to test your newly created quests.

Here’s a useful, practical guide to completing quests via console commands in The Witcher 3: Wild Hunt.

addfact(qxxx_yyy_completed)

or more commonly:

addfact(qxxx_yyy_finished)

But the most reliable way is to use quest stage facts. Example for Pyres of Novigrad:

addfact(q302_completed)

⚠️ Warning: Completing a quest via console bypasses normal triggers, choices, cutscenes, and rewards. It can break later quests, lock you out of achievements, or leave items/characters in wrong states. Always save first.

The witcher 3 complete quest console command is one of the most potent tools in the PC gamer’s arsenal. It can rescue a broken save, bypass tedious grinding, or let you craft the perfect narrative state. However, like a Witcher’s mutagens, this power must be handled with care.

Recap of best practices:

Now, go forth, Geralt. Whether you’re fixing a bug in “The Greedy God” or jumping straight to the Battle of Kaer Morhen, the console is your silent ally. Just remember: even destiny has stages. Complete them wisely.

Happy hunting on the Path.

While there is no single "win game" or "complete all quests" command for The Witcher 3: Wild Hunt like there is in games like , you can use the Debug Console

to manipulate specific quest states, items, and character attributes. 1. Enabling the Debug Console (PC Only)

To use any commands, you must first enable the console by editing your game files: Steam Community Locate the File : Go to your Witcher 3 installation folder: \bin\config\base\ general.ini : Open the file with Notepad. Add Command : Under the section, add a new line: ConfigDefaultValue=true DBGConsoleOn=true Open In-Game : Once the game is running, press the key to toggle the console. Steam Community 2. Essential "Quest-Fixing" Commands

Since "complete quest" is not a standard command, you typically use these to bypass bugs or force progression: additem('item_name') : Directly adds a missing quest item to your inventory. removeitem('item_name') : Deletes items if they are stuck in your inventory. cleardevelop

: Resets Geralt to level 1 and clears all items. Use this only as a "hard reset" for your character. setlevel(X) Before using any commands, you must enable the console:

: Instantly sets Geralt to level X, which is useful if you are under-leveled for a mandatory quest. 3. Gwent Quest Shortcuts

The "Collect 'Em All" quest is notoriously difficult to complete manually. You can use these specific commands to finish it or win matches instantly: winGwint(true) : Instantly wins the current Gwent match. addgwintcards : Adds every Gwent card in the game to your inventory. 4. Character & World Commands

These can help you move through content faster if you are stuck or want to skip travel: gotoWitcher gotoNovigrad : Teleports you to major hubs. : Swaps your playable character.

: Enables invincibility, allowing you to breeze through difficult boss fights. Note for Console Players

: There are currently no console commands or cheats available for the Xbox or PlayStation versions of the game. Item Codes for a particular mission you're stuck on?

In The Witcher 3: Wild Hunt, completing a quest via console commands isn't as simple as a single "finish" button. Instead, you must use the addfact() command to manually trigger specific quest phases or outcomes. How to Enable the Debug Console

Before using any commands, you must enable the hidden debug console in your game files.

Navigate to your game directory (e.g., Steam\steamapps\common\The Witcher 3 Wild Hunt\bin\config\base). Open general.ini with a text editor like Notepad.

Add the line DBGConsoleOn=true under the [General] section and save the file. In-game, press the ~ (tilde) or F2 key to open the console. The Command: addfact()

To force a quest to complete or progress, use the following syntax:addfact(quest_id_completed)

This command adds a "fact" to the game's internal database, tricking it into believing a specific objective has been met. Common Quest Completion Examples Complete "Now or Never": addfact(q309_completed)

Complete "The Last Wish" (Romance Yen): addfact(sq202_yen_girlfriend)

Complete "Reason of State" (Kill Radovid): addfact(mq3035_fdb_radovid_dead) Complete "Blood Gold": addfact(lw_gr39_treasure_opened) Finding Specific Quest IDs

Because there are hundreds of quests, you often need to find the specific "baseName" or "fact ID" associated with your bugged quest. Guide :: The Witcher 3 Console Commands: Ultimate Edition

To complete a quest via the debug console in The Witcher 3 , you generally use the addfact command followed by the specific internal ID for that quest's completion. Primary Command

The syntax for marking a quest as finished is:addfact([QuestID]_completed)

For example, to complete the quest "Hunting a Witch," you would enter:addfact(q104_completed) Common Quest IDs

Because there is no universal "complete current quest" button, you must know the specific ID. Here are a few notable examples: The Last Wish: q302_the_last_wish_completed Gangs of Novigrad: q302_05_completed The Bloody Baron: Often falls under q105 variations. How to Enable the Console (PC Only) If you haven't enabled the console yet: Better than outright completion: set specific stage to

The Witcher 3: Wild Hunt , there is no single "complete quest" button. Instead, you must use "facts"—internal flags the game uses to track progress—to force a quest or objective to a finished state. 1. Enable the Developer Console

Before entering 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 like Notepad. Add the line DBGConsoleOn=true at the bottom of the file.

Save and restart the game. Press the ~ (tilde) key to open the console in-game. 2. Commands to "Complete" Quests

To manipulate quest states, you use the addfact command. This effectively tells the game that a specific event has occurred. To complete an objective/quest: addfact(fact_id) To remove a failed status: removefact(fact_id)

Note: You must replace fact_id with the specific internal ID for that quest stage. For example, to mark a specific part of the "Bloody Baron" questline as finished, players have used addfact(q105_evil_spirit_done). 3. How to Find Quest IDs

Because there are hundreds of unique IDs, you cannot guess them. You must find the specific string for the quest you are stuck on:

External Databases: Users often reference community-maintained spreadsheets or files like tw3facts and w3journal found on Steam Community guides or Nexus Mods.

Common Prefixes: Most main quests start with q, followed by a number (e.g., q303 for "Count Reuven's Treasure"). ⚠️ Risks of Quest Skipping

Using these commands is considered a "heavy" tweak. Unlike adding money or items, forcing a quest to complete can break world-state updates. If you skip a quest that triggers a character appearing later, that character may never show up, potentially soft-locking your save file. Always create a backup save before experimenting with addfact. Guide :: Console commands for The Witcher 3: Wild Hunt

The Witcher 3: Wild Hunt , there is no single "complete quest" command that works for every mission by name. Instead, you must use the

command to manually trigger the "completed" status of a specific quest phase. 1. Enable the Debug Console

Before entering commands, 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 and save. In-game, press the to open the console. Steam Community 2. Quest Completion Command

To finish a quest or move past a bugged objective, use this syntax: addfact(quest_id_completed) : To complete the "Blood Gold" quest, enter: addfact(lw_gr39_treasure_opened) : Quest IDs often use internal "fact" names (like q104_completed ) rather than the quest's display name. 3. Finding the Correct Quest ID

Because IDs are internal, you usually need to look them up. Common patterns include: Main Quests : Often start with Side Quests : Often start with Fact Lists

: You can find comprehensive lists of IDs on community resources like the Witcher 3 Fact ID Reddit thread Nexus Mods forums 4. Alternative: Removing Failed/Bugged Facts

Here’s a useful console command feature for The Witcher 3: Wild Hunt (with both expansions) to complete quests instantly: