Questie

Questie

116M Downloads

Client locks up when player accepts quest 6241

Muehe opened this issue ยท 4 comments

commented

[22:09] TommyK: It seems everytime I log in my game freezes right off of login, it all started when I left the cave entering winterspring, I did the full troubleshooting i could find online being, making sure it was questie and all, deleting and downloading the new beta version, but no luck if questie is on my game instantly freezes on load in and it locks up.

...

[22:57] TommyK: Yea, did it, nothing changed
[22:57] Muehe: K, I'll have to look if I can repro this later. I guess the dude in the screenshot is the one you were getting the quest from?
[22:58] TommyK: Oh na, I turned the addon off and ran around a bit, just to check out to see if it was not the addon but after turning all the addon off and doing a check addon by addon it was questie
[23:04] Muehe: Got him.

[23:04] Muehe: The quest he gives indeed freezes my client.
[23:05] Muehe: Although at least I can Al+Tab to close WoW.
[23:05] Muehe: #not-a-wine-bug-but-a-feature
[23:07] Muehe: This is the quest: Winterfall Activity
[23:07] Muehe: If you finish it Questie might start working again ๐Ÿ˜„
[23:08] TommyK: it was 100% that guy too haha

commented

Interesting... I recently did these quests and had zero issues.

Try turning off clustering before entering the zone and repro'ing the bug. I've noticed some slight performance hits when obtaining quests with large numbers of objectives that need to be clustered. However, I'm running a fairly beefy rig so it might not effect my client like it would someone else.

commented

I actually couldn't reproduce this issue with Questie myself, but the version of pfQuest I was using (some point into the 3.0 branch) had the very same issue. I actually thought I had enabled Questie, went to the addon list to disable it, but it already was. So my guess is that there is some weird bug with this quest which is triggered by the WoW questlog/event API.

Edit: Maybe corrupt cache?

commented

Could be corrupt cache... kinda makes sense.

commented

Possibly fixed with the newer versions