Witcher 3 Complete Quest Console Command Top Guide

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

Here’s a concise review of using the complete quest console command in The Witcher 3: Wild Hunt (Complete Edition).

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.

Key Features

1. Safe Completion Logic

   • Checks if quest is already in Failed or Completed state → warns and aborts.
   • Verifies prerequisite quests – warns if main story continuity might break.

2. Reward Handling

   • Reads quest_reward entries from game files.
   • Awards: XP (scaled to player level), crowns, unique items (e.g. diagrams, swords).
   • If giveRewards = false, only marks quest complete without granting loot.

3. Journal & Map Cleanup

   • Removes all active objectives from journal.
   • Clears quest-related map markers (qst_marker entries).
   • Updates log entry to “Quest completed via console”.

4. Force Mode Risks

   • Displays red warning text: “Force completion may break later quests. Save first.”
   • Force mode does not advance other quest dependencies automatically (prevents cascade failures).
   • Only bypasses is_stage_locked checks within the same quest.

5. Feedback Output

   • Console prints:

     [SUCCESS] Quest 'q302' completed. Rewards granted: 250 XP, 85 Crowns.
     Journal entry added. Map markers cleared.
     

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

The Master List: Top Quest IDs for Console Commands

Below is a curated table of the most frequently requested quest IDs. Use the pattern addfact(qXXX_completed).

| Quest Name | Quest ID | Command to Complete | | :--- | :--- | :--- | | Lilac and Gooseberries (Prologue) | q001 | addfact(q001_completed) | | The Beast of White Orchard | q002 | addfact(q002_completed) | | The Incident at White Orchard | q003 | addfact(q003_completed) | | Pyres of Novigrad | q105 | addfact(q105_completed) | | Gangs of Novigrad | q206 | addfact(q206_completed) | | The Lord of Undvik | q302 | addfact(q302_completed) | | The King's Gambit | q309 | addfact(q309_completed) | | Through Time and Space | q310 | addfact(q310_completed) | | Battle of Kaer Morhen (Ugly Baby) | q311 | addfact(q311_completed) | | Final Preparations | q601 | addfact(q601_completed) | | Blindingly Obvious | q602 | addfact(q602_completed) | | On Thin Ice (Finale) | q604 | addfact(q604_completed) | | Envoys, Wineboys (BaW Start) | q701 | addfact(q701_completed) | | The Warble of a Smitten Knight | q702 | addfact(q702_completed) | | Tesham Mutna (Dungeon) | q705 | addfact(q705_completed) | | Scenes From a Marriage (HoS) | q603 | addfact(q603_completed) | The primary console command for completing or manipulating

4. Force-Starting a Quest

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

Command: startquest('quest_id')

• Example: startquest('q401_battle')

Command: restartquest('quest_id')

• Use this to completely reset a bugged quest to the very beginning.

4. Safest Completion Method (for Main Quests)

Instead of completequest, use stage facts:

addfact("q302_post_keira_meeting")
addfact("q302_crones_fulfilled")
addfact("q302_main_plot_done")

Then verify with getfact("q302_main_plot_done") (returns 1 if set). Locate the Configuration File: Navigate to your game

The Witcher 3: Mastering Quest Console Commands

Despite being a masterpiece of RPG design, The Witcher 3 is a massive game with thousands of moving parts. Even after the Next-Gen update, players occasionally encounter broken quests, stuck objectives, or simply wish to bypass a frustrating segment on a replay.

Using console commands to manipulate quests is a powerful tool, but it operates like a scalpel rather than a sledgehammer. Understanding the specific commands and how to use them safely is essential to avoid corrupting your save file.