Questie

Questie

124M Downloads

Questie not loading properly. Error during initialization!

THERUSSIANDANE opened this issue ยท 11 comments

commented

Bug description

questie not loading properly

Screenshots

Capture

Questie version

Questie-v6.5.0-tbc

commented

Restart your client after updating should be enough to fix this.

Not, it does not.

Clean install, clean reboot of computer and of course client reset.

commented

I am experiencing the same issue since updating to 6.5.0

commented

Restart your client after updating should be enough to fix this.
If that doesn't help. Delete Questie folder and install/update. It's loading old files.

commented

Try to reinitialize Questie with this command ingame:
/run QuestieLoader:ImportModule("QuestieOptions").tabs.advanced:Initialize().args.questieReset.func()

commented

Try to reinitialize Questie with this command ingame:
/run QuestieLoader:ImportModule("QuestieOptions").tabs.advanced:Initialize().args.questieReset.func()

Same result with same message as OP stated.

commented

I was able to resolve this issue by deleting the Questie folder in interface/addons and re-installing the addon.

Presumably the issue is caused by latent files that are no longer needed, but would remain if the new version was extracted on top of an existing installation.

commented

You should try /run Questie.db.global.dbIsCompiled = false and then do a /reload.

It really is important to close WoW before updating your addons or restart it right away. This does not only affect Questie but can screw up any addon.

commented

I fixed this by doing the following

/run Questie.db.global.dbIsCompiled = false
/reload

closed down client completely, deleted the existing questie addon folder and unpacked the latest questie again into the addons folder

commented

Got the same error, fixed by deleting Questie folder and re extract.

But now i have another error "Questie: [ERROR] Missing objective data for quest 11886 and objective Twilight Correspondence"

commented

Hey @Bagiraa could you open up a separate issue for this? Your second issue has nothing to do with the initial issue of this post.

commented

Assuming this is fixed.