Also, I haven't the slightest clue where to put it in if this is indeed where I need to put in EnableQuestDebugger=True. The few places I've tried have made a mess. I need to tombstone Lord K'avar Pt III because akorithi is mute, and the unmutequestnpcs function seems to be failing, as well.
Also, I may recommend making the working function Ctrl-Tab or shift-tab again, just to keep it a bit less likely to be accidentally used - or toggled via the command menu itself - Honestly when I found tdbg didn't pull the quests it was exceedingly frustrating and I've been looking for a solution for this for days, and ended up making an account just for this.
Can't use "Purgequests" because I have warm ashes mod
Code: Select all
"Quest Debugger Input Changes
The quest debugger has a few changes to input settings. These changes are to prevent accidentally opening debugger during normal play, free up the Tab key for other uses, and to make shortcuts easier on non-US keyboards. For example, the square bracket keys [ and ] are not so easy to use on AZERTY keyboards.
If you are not a quest author or don’t care about quest debugger, you can ignore these changes.
Quest debugger is now disabled by default. Must edit EnableQuestDebugger=True in settings.ini to activate it again.<---
Ctrl+Shift+D now cycles through debugger display states off/partial/full
Ctrl+Shift+LeftArrow now opens previous active quest while debugger active
Ctrl+Shift+RightArrow now opens next active quest while debugger active
Ctrl+Shift+UpArrow now teleports to next dungeon quest marker while debugger active inside dungeon
Ctrl+Shift+DownArrow now teleports to previous dungeon quest marker while debugger active inside dungeon
Note: Some inputs might move character, e.g. Ctrl+Shift+D will also move character slightly to right when activating debugger. This is expected and not considered a breaking issue for a debug/development feature that is normally disabled."