The developer console remains fully accessible to players who enable it via mods or by editing the game's general.ini configuration file. However, simply typing a universal "complete quest" command no longer works as a magical fix. Why the Command Destroys Save Files
Players do not receive the experience points, crowns, or unique items tied to the natural completion of the quest.
is tricky because, technically, a single universal "complete quest" command like Skyrim's completequest has never officially existed in the base game's debug console. witcher 3 complete quest console command patched
Before attempting any quest manipulation via the developer console, always follow these three rules:
Unless you are truly stuck due to a bug, avoid "complete quest" patches. They are notorious for causing "silent" bugs—where you finish the quest now but find out 20 hours later that a major character like Yennefer or Triss has disappeared from the world entirely. The developer console remains fully accessible to players
abortquest("quest_id")
To complete a specific quest, you must first enable the debug console and then input a command tailored to that quest's unique ID. Enabling the Console The Witcher 3/bin/config/base general.ini . Add the line DBGConsoleOn=true at the bottom and save. Completing a Quest : Use the command addfact(QuestID_completed) . For example, to finish "Blood Gold," you would enter addfact(lw_gr39_treasure_opened) Finding IDs is tricky because, technically, a single universal "complete
Yes. The specific, native, one-word command completequest that worked in v1.31 is in the official Next-Gen version of The Witcher 3 . You cannot activate it without third-party mods.