Witcher 3 Complete Quest Console Command Top !!better!! -

This guide provides the essential console commands for managing quests in The Witcher 3: Wild Hunt. Whether you’re stuck due to a bug, want to bypass a tedious objective, or are experimenting with different story outcomes, these commands are your primary tools. How to Enable the Console Before using commands, you must enable the debug console:

Navigate to your Witcher 3 installation folder (usually bin\config\base). Open general.ini with Notepad.

Add the line ConfigVersion=2 (if not present) and DBGConsoleOn=true at the bottom.

Save the file. In-game, press the tilde key (~) to open the console. Top Quest Console Commands 1. Complete Current Quest Objective

If a specific quest marker is bugged or an NPC won't talk to you, use this to jump to the next step. Command: addfact(quest_fact_name)

How it works: Quests in The Witcher 3 progress based on "facts." To find the specific fact name for your quest, you often need to reference community spreadsheets or the Witcher Wiki, as every objective has a unique internal ID (e.g., q103_finished). 2. Start a Specific Quest

If you missed a side quest or want to force a quest to begin. Command: addquest(quest_ID)

Example: addquest(sq302) starts the "A Towerful of Mice" quest. 3. Instantly Succeed a Quest Command: successquest(quest_ID)

Note: Use this with caution. Completing a main story quest this way can occasionally break the script logic for the following mission. 4. Fail a Quest

Useful if you want to see specific dialogue or world states that only occur upon a quest's failure. Command: failquest(quest_ID) Important Quest IDs for Major Story Beats

When using the commands above, you’ll need the internal IDs. Here are the most common: Quest Name Lilac and Gooseberries q001_white_orchard The Bloody Baron q103_baron_intro Ladies of the Wood q104_swamp_witches Pyres of Novigrad q301_triss_intro The Isle of Mists q210_isle_of_mists Essential Utility Commands for Questing

Often, "completing" a quest isn't just about the objective, but having the right items or levels to handle the outcome.

cleardevelop: Resets Geralt to level 1 and clears your inventory. Useful if a quest reward bugged out your stats.

setlevel(X): Instantly sets your level to X. Perfect if you are under-leveled for a quest you just forced to start.

additem('Item_Name'): If a quest requires a specific item (like the 'Potestaquisitor'), you can spawn it directly. A Word of Caution

The Witcher 3 uses a complex web of "flags." Forcing a quest to complete using addfact or successquest does not always trigger the cinematic or world changes associated with that quest. Always save your game before attempting quest manipulation to avoid "breaking" your save file's logic.

1. addexp(amount)

While not strictly a "quest" command, this is often used in conjunction with quest skipping. If you manually complete a quest via console, you may not receive the intended Experience Points (XP). Use this to compensate.

Prerequisites: Enabling the Console

Before you can input any commands, you must unlock the developer console.

  1. Locate the Configuration File: Navigate to your game installation folder. typically found at: C:\Documents\The Witcher 3\
  2. Edit the File: Open user.settings with a text editor (like Notepad).
  3. Change the Setting: Search for the line DBGConsoleOn=false. Change it to DBGConsoleOn=true.
  4. Save and Launch: Save the file and start the game.
  5. Activate: Press the tilde key (~) or F1 (depending on your keyboard layout) to open the console command overlay in-game.

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.

The Witcher 3: The Ultimate Guide to Complete Quest Console Commands (Top Commands & How to Use Them)

Few games in the history of open-world RPGs have achieved the legendary status of CD Projekt Red’s The Witcher 3: Wild Hunt. With its sprawling narrative, morally grey choices, and dozens of hours of side content, the game is a masterpiece. However, even masterpieces can have flaws. Maybe you’ve encountered a game-breaking bug that prevents a quest from triggering. Perhaps you’re on your fifth New Game+ playthrough and just want to skip the Velen slog to get to the Blood and Wine expansion. Or, you might simply want to experience a specific quest ending without replaying 20 hours of content.

Enter the Console Command. For PC players, the console is the ultimate tool of control. And when it comes to quests, one command reigns supreme: the addfact and removefact commands (often misnamed as the "complete quest" command).

In this article, we will break down the top Witcher 3 complete quest console commands, explain exactly how they work, provide a safe usage guide, and list the most sought-after Quest IDs.

Verdict

Use sparingly – excellent for bypassing game-breaking bugs or skipping a single failed side quest, but disastrous for completionist runs or narrative immersion. For “complete every quest,” mods like Quest Objectives Plus or Friendly HUD are safer.

To manage quests in The Witcher 3: Wild Hunt, players on PC can utilize the developer console to manually complete, reset, or bypass objectives. Unlike Skyrim, there isn't a single, universal "complete quest" button; instead, you often have to manipulate "facts"—internal flags that track your progress. Direct Console Commands for Quests

addfact(fact_id): Manually sets a quest flag to "completed" or "true." witcher 3 complete quest console command top

removefact(fact_id): Removes a flag, effectively un-completing an objective.

resetquest(quest_id): Attempts to restart the quest from the beginning.

stopquest(quest_id): Forces a quest to stop, though this can sometimes leave it in a "failed" state. How to Enable the Console

Navigate to your game folder: The Witcher 3\bin\config\base. Open general.ini with Notepad. Add the line DBGConsoleOn=true under the [General] section. Save and launch the game. Press the ~ (tilde) key to open the menu in-game. 💡 Essential Quest Manipulation Tips

The difficulty with quest commands is finding the correct ID.

The Quest ID: These are internal names like q302_the_last_wish.

The "Fact" Method: If a quest is stuck (e.g., "The Last Wish"), you can often force the outcome by adding specific relationship facts, such as addfact(sq202_yen_lover).

Safety First: Quest commands can break the game's logic. Always create a backup save before using them, as some changes are irreversible and can cause NPCs not to spawn later.

No Achievements: Using the console is considered cheating and may disable your ability to earn Steam or GOG achievements for that session. Most Useful General Commands god Toggle immortality. levelup Increases Geralt's level by 1. addmoney(X) Replaces X with the amount of Crowns you want. killall Instantly kills all enemies in combat. settime(H, M) Sets the game time (e.g., settime(12, 0) for noon). additem('Item Name') Adds a specific item to your inventory.

Which specific quest or objective are you trying to complete? If you provide the name, I can help you find the exact Fact ID or command string needed to fix it. The Witcher 3 - Console Achievement Guide - Steam Community

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

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

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.

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

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 This guide provides the essential console commands for

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).

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

The developer console in The Witcher 3: Wild Hunt is a powerful tool for players looking to bypass bugs, skip tedious travel, or fix broken quest progression. While most commands are straightforward, managing quests requires precision to avoid breaking the game’s logic. Enabling the Console

To use these commands, you must first enable the console. On PC, navigate to your game folder: The Witcher 3\bin\config\base general.ini and add the line DBGConsoleOn=true section. Once in-game, press the key to open the interface. Top Quest-Related Commands The most effective way to handle quests is by using Quest Facts or direct completion triggers. addfact(fact_id)

This is the most "surgical" command. Instead of forcing a whole quest to end, it tells the game a specific event happened. For example, if a door won't open because a guard didn't give you a key, adding the "fact" that you spoke to the guard can fix the trigger. removefact(fact_id)

Essential for reversing mistakes. If you accidentally triggered a "fail" state for a side quest, removing that fact can sometimes reset the quest's logic. setprogress(quest_name, phase, objective)

This is the "teleport" of quest commands. It moves your current quest to a specific stage. It is highly technical, as it requires knowing the exact internal strings (names) used by the developers. Ciri commands (e.g.,

While not strictly quest commands, many main story quests soft-lock because the game fails to swap characters. Using these commands to manually switch between Ciri and Geralt can often force a quest to resume. The Risks of Quest Manipulation

Unlike spawning items or changing the weather, quest commands can cause "sequence breaking." If you force-complete a quest that involves a major character, the game may not know where to place that character in the next scene, leading to empty rooms or infinite loading screens. save your game manually

before attempting to move quest phases. The console is a great "Plan B," but it works best when used to nudge a stuck objective rather than skipping entire chapters of the story. Should I look up the specific IDs for a quest you're currently stuck on?

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 force-complete quests in The Witcher 3: Wild Hunt , players primarily use the addfact command within the developer console. While there is no universal "complete quest" button, manipulating "facts"—the game's internal flags—is the most effective way to bypass bugged objectives or skip tedious tasks. Essential Quest Completion Commands The most critical commands for quest manipulation are: Example: addexp(1000)

addfact(fact_id): Sets a specific quest objective or state as "true" (complete).

removefact(fact_id): Reverses a choice or clears a completed flag.

addgwintcards: Instantly completes card-collecting objectives by adding every Gwent card to your deck. Top Quest-Specific IDs

Completing a quest typically requires the specific "completed" ID. For example:

Keira Metz's Storyline: addfact(q104_completed) marks the "Hunting a Witch" quest as finished.

Triss Merigold's Romance: addfact(q309_completed) completes "Now or Never".

Specific Ending Triggers: You can force specific world states, such as addfact(q110_visited_emhyr) for the Empress ending or addfact(q310_ciri_faced_lodge) for a "good" choice outcome. How to Find Quest IDs

Since every quest has a unique internal ID (like q104 or mq4003), you may need to look up specific codes:

To complete quests using console commands in The Witcher 3 , you must first enable the debug console. Unlike some other RPGs, there isn't a single universal "finish quest" command; instead, you must use "facts" to force the game into a completed state for a specific quest. 1. Enabling the Console

Before entering commands, you must enable the debug console through the game's files:

Locate the File: Go to your game's installation folder, usually The Witcher 3 Wild Hunt\bin\config\base. Edit general.ini: Open this file with Notepad.

Add Activation Line: At the very end of the file, insert the line DBGConsoleOn=true and save.

Access in Game: Start the game and press the ~ (tilde) or F2 key to open the console. 2. Primary Quest Commands

Quests are completed or skipped by adding "facts" that represent specific outcomes or stages. Command Syntax Complete Quest addfact(QuestID_completed) Marks the specified quest as finished. Fail Quest removefact(QuestID) Removes progress or resets certain facts. Add Specific Outcome addfact(FactID)

Forces a specific choice or world-state (e.g., romancing a character). 3. Example Quest IDs & Outcomes You must use exact, case-sensitive IDs for these to work. Now or Never: addfact(q309_completed)

Romance Triss: addfact(q309_triss_lover) and addfact(q309_triss_stayed) Romance Yennefer: addfact(sq202_yen_girlfriend) King of Skellige: addfact(q206_hjalmar_king) Radovid Dead: addfact(mq3035_fdb_radovid_dead) 4. Tips for Finding IDs If you need an ID for a quest not listed above:

External Repositories: Use community-maintained lists like those on GitHub or Steam Community.

Quest Stages: For bugged quests, you may need to advance to a specific stage instead of just "completed." These often follow the format QuestID_phase_#.

Caution: Forcing quest completion can break world-state triggers or skip important rewards and experience points. Always save your game before using these commands.

Part 3: Finding the Correct Quest ID (The "Top" Cheat Sheet)

The most frustrating part of using console commands is finding the exact name. Below are the top requested quests with their exact console IDs and completion facts.

| Quest Name (In-Game) | Internal Quest ID | Complete Quest Fact Command | |----------------------|------------------|-----------------------------| | Family Matters (The Baron) | q104 | addfact(q104_completed) | | The Last Wish (Yennefer) | q302 | addfact(q302_completed) | | A Towerful of Mice | q204 | addfact(q204_completed) | | Now or Never (Triss) | q209 | addfact(q209_completed) | | The Isle of Mists | q310 | addfact(q310_completed) | | Through Time and Space (Avallac’h) | q505 | addfact(q505_completed) | | Reason of State | q206 | addfact(q206_completed) | | Scavenger Hunt: Cat School Gear | q201_cat | addfact(q201_cat_completed) |

Pro Tip: For DLC quests, IDs change. For Hearts of Stone (ep1), use addfact(ep1_qxxx_completed). For Blood and Wine (ep2), use addfact(ep2_qxxx_completed).

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.

4. Force-Starting a Quest

If a quest hasn't triggered yet, you can force the game to start it.

Command: startquest('quest_id')

Command: restartquest('quest_id')