Questie

Questie

116M Downloads

Quesite problem with EQL3

Lainiel opened this issue ยท 9 comments

commented

When handing in the quest, it automaticaly skips the continue button right to the complete button. You can't read what the NPC says before you click continue like this.

If I disable either EQL3 or Questie it starts working again and doesn't skip the continue button.

EQL version 3.6.1
Questie version 3.1

commented

I have confirmed this is also happening to myself with EQL3 + Questie 3.1

commented

Fix:

diff --git a/!Questie/Questie.lua b/!Questie/Questie.lua
index e10288c..30945fb 100644
--- a/!Questie/Questie.lua
+++ b/!Questie/Questie.lua
@@ -418,7 +418,6 @@ function Questie:OnEvent(this, event, arg1, arg2, arg3, arg4, arg5, arg6, arg7,
                                        end
                                        QuestieTrackedQuests[hash] = nil;
                                end
-                               CompleteQuest();
                                Questie:AddEvent("CHECKLOG", 0.135);
                        end
                end

@Schaka Do you want me to PR this or can you upload yourself? P.S. Did no regression testing at all. Think none is needed due to the similar code fragment in Modules/QuestieQuest.lua (which is not only redundant but also unused if I am not mistaken).

commented

Thanks @Muehe I'll give this a shot.

commented

@jimbishop if this does the trick for you, I'll mege Muehe's code.
@Muehe I'd like a PR actually. One, because I want to give credit to you, two because I don't actually have any local code and would prefer not breaking any formatting with the web interface.

commented

@jimbishop @Muehe The patch works to me! Thank very much \o/

commented

Closed by 71e871a

commented

Confirmed. Using ShaguQuest. This didn't happen with 3.0, so it should happen somewhere in Questies EQL3 specific code.

commented

I'm have to downgrade to v2.67 to fix this problem :(

commented

Having the same issue using questie and eql3 together
Edit: Just confirmed. Ran eql3 alone then questie alone, no issues. Only happens when both are running together, so It must be in the questie code meant to interact with eql3.