Witcher 3 Complete Quest Console Command Top [repack] Page
Alternatively, you can add --use-console to your game’s launch arguments within your respective launcher settings, though the general.ini method remains the most reliable. The Top Console Commands for Quests
: Removes a flag, effectively un-completing an objective.
Do you need help finding a variable? Share public link witcher 3 complete quest console command top
completequest(q302, true, false, true)
addfact("q110_graves_hag_destroyed") addfact("q110_graves_hag_freed") addfact("q110_completed") Alternatively, you can add --use-console to your game’s
This is the most powerful and safest command for fixing broken quests. The Witcher 3's engine relies on "facts" (state flags) to track player choices and triggers. If an NPC refuses to talk to you or a door won't open, adding the missing fact usually resolves the block. Example: addfact(q103_completed) 2. removefact( )
To complete a quest in The Witcher 3 using the console, the standard command is 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 Example: addfact(q103_completed) 2
Whether you are doing a new playthrough, testing character builds, or trying to bypass a bugged objective, knowing how to manipulate quests using the Developer Console is incredibly useful. In The Witcher 3 , while there isn’t a single, magical completequest(all) command that works universally without breaking the game's scripts, there are specific, highly effective techniques you can use to force your way past difficult sections or manipulate quest states.
If you have the Debug Console enabled, these are the primary ways to manipulate quest progress:
Quests in The Witcher 3 are hard-coded with specific fact checks (e.g., whether you talked to a villager or found a specific clue). You can restart a broken phase of a quest by removing the "done" fact, forcing the game to re-trigger the event. Part 3: Using "Fact IDs" to Fix Bugged Quests
| 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) |