Quest Unstick
[size=5]Quest Unstick[/size] [i]Debug-console commands to force a stuck journal quest to a finished state.[/i] [size=4]What it does[/size] Adds console commands that set a quest's journal entry [b]and
[size=5]Quest Unstick[/size]
[i]Debug-console commands to force a stuck journal quest to a finished state.[/i]
[size=4]What it does[/size]
Adds console commands that set a quest's journal entry [b]and its whole subtree[/b] (objectives, descriptions, map pins) to [b]Completed[/b], [b]Failed[/b], or back to [b]Active[/b], using the game's own journal manager.
Use it when:
[list]
[*]a quest is functionally done in the world but won't leave your active quest list, or[/*]
[*]an objective ticked in the world but never updated in the log.[/*]
[/list]
[size=4]What it does NOT do[/size]
[color=#e05a3f][b]It does not run the quest.[/b][/color] Facts, rewards, items, scenes and world state that finishing the quest would normally set are [b]not[/b] applied. This fixes the [b]journal[/b], not the underlying progression.
[list]
[*]It is [b]not[/b] a "skip this quest" button. Skipping content you haven't played will desync the main questline.[/*]
[*]It [b]cannot[/b] fix a hard freeze where a scene never fires or the game locks up. That needs REDkit's live quest debugger.[/*]
[/list]
[b]Back up[/b] [font=Courier New]Documents\The Witcher 3\gamesaves[/font] before using.
[size=4]Requirements[/size]
A working debug console. Any community console-enabler works:
[list]
[*][b]Next-Gen (v4.0+):[/b] "Mod Console Enabler for NG" / "Debug Console Enabler NG"[/*]
[*][b]Classic (v1.32):[/b] "Debug Console Enabler"[/*]
[/list]Install one first and confirm [font=Courier New]~[/font] opens the console in-game.
[size=4]Installation[/size]
[list=1]
[*]Back up your gamesaves folder.[/*]
[*]Extract so you have: [font=Courier New]The Witcher 3\Mods\modQuestUnstick\content\scripts\local\questunstick.ws[/font][/*]
[*]Launch the game once (scripts recompile on launch).[/*]
[/list]Uninstall: delete the [font=Courier New]modQuestUnstick[/font] folder. No save cleanup needed.
[size=4]Usage[/size]
Open the console with [font=Courier New]~[/font] (or [font=Courier New]F2[/font] on some layouts).
[color=#e0a53f]Every command needs the parentheses, and the name in double quotes.[/color] Typing a command bare (e.g. [font=Courier New]qunstick_undo[/font]) does nothing.
[code]
qunstick_list()
List every active quest: index, display name, baseName, title id.
qunstick("sesame")
Case-insensitive substring match against display name AND baseName.
Sets the match to COMPLETED.
Ambiguous match = does nothing, prints the candidates.
qunstick_fail("some quest")
Same, but sets the match to FAILED.
qunstick_undo("some quest")
Same, but sets the match back to ACTIVE.
Works even after the quest has been completed.
qunstick_id(1104514)
Match by exact title string id (from qunstick_list) instead of name.
Sets it to COMPLETED.[/code]
Command output appears in the debug message area (top-left). If your console setup doesn't render those messages, the commands still work — just check your journal.
[size=4]Compatibility & safety[/size]
[list]
[*]New script file, no core-script edits; Script Merger won't flag it.
