fix(questhelper): auto-accept quest-start prompts and pause re-interaction after dialogue#1749
Conversation
…ction after dialogue - Add Rs2Dialogue.acceptQuestStartDialogue() to click "Yes" on "Would you like to start the <X> quest?" prompts that QuestHelper doesn't pre-highlight, so the script no longer cancels the dialogue by walking away. - Add a 4-7s cooldown after a tracked dialogue ends before QuestScript re-clicks the NPC, to avoid interrupting scripted NPC animations or cutscenes that play out between dialogue exchanges.
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
WalkthroughThese changes add dialogue cooldown handling to quest progression and a utility method for accepting quest start dialogues. A new 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Rs2Dialogue.acceptQuestStartDialogue()to detect "Would you like to start the <X> quest?" prompts (which QuestHelper doesn't pre-highlight) and click "Yes", so the script no longer cancels the dialogue by walking away.QuestScriptafter a tracked dialogue ends before re-clicking the NPC, so scripted animations/cutscenes between dialogue exchanges aren't interrupted into a retry loop.Test plan
[N]-highlighted choice path — confirm the prior behavior still works (no regression inhandleQuestOptionDialogueSelection).