-
Notifications
You must be signed in to change notification settings - Fork 302
This FAQ is for Classic (1.13)
--> IMPORTANT: Always make sure you have the latest version of Questie installed!
--> IMPORTANT 2: Try to disable all addons except Questie to see if your issue is really caused by Questie!
Follow the installation guide and make sure to grab the latest release!
Have you restarted the WoW client? If yes, you can try to reset the Questie settings by deleting the following files. This will delete your Journey as well! If you don't care delete the following files with WoW closed:
World of Warcraft\_classic_\WTF\Account\<yourAccount>\SavedVariables\Questie.lua
World of Warcraft\_classic_\WTF\Account\<yourAccount>\SavedVariables\Questie.lua.bak
World of Warcraft\_classic_\WTF\Account\<yourAccount>\<yourServer>\<yourCharacter>\SavedVariables\Questie.lua
World of Warcraft\_classic_\WTF\Account\<yourAccount>\<yourServer>\<yourCharacter>\SavedVariables\Questie.lua.bak
If that doesn't help read the other FAQs and message us in #general on Discord if nothing helps.
This is likely because of a conflict with another addon. Make sure you have the latest version installed. If not try to disable all addons except Questie and see if that works. If you find conflicts let us know in #general on Discord or create an issue.
This is most likely because of some wrong entry in our database. Please open an issue or let us know in #general on Discord!
Same as 4.
You'll find such options in the "General" tab of Questie. If they're turned off make sure to check your other addon. Addons known doing this are: AAP, Leatrix, Quest Codex, SpartanUI.
Have another look at the installation guide. Your folder paths are incorrect.
This is most likely because of a conflict with another addon. If you use GatherMate2 make sure to update to v4.0.16.
This message comes from the AAP addon. Disable it or pickup the quest to fix it.
Are you sure it is the same quest and not another part of a quest chain? If yes make sure you have the latest Questie release installed (v4.0.13+). If you already have that version installed you should open up an issue.
We have yet to think about a way how to include those items on the map. The problem is that the map would be absolutely flooded with icons for most quests.
For the arrow you need to install v4.0.16+ and make sure to install the TomTom addon. Then you can right click a quest or an objective in the tracker to set the TomTom target.
Ctrl + left click
You can always open up the config with: /questie
.
If that doesn't work you most likely didn't restart WoW after an update or have more than 1 Questie version installed. In your addon folder you should have a "Questie" and a "QuestieDev-master" folder. Remove the latter.
Yes, with v4.0.15+ you can use "shift + leftclick" to hide a quest. Unhiding is done by searching the quest in the journey (right click the questie icon). But please make sure to report bugged quests so we can fix them!
Make sure you have only 1 version of Questie installed! In your addon folder you should have a "Questie" and a "QuestieDev-master" folder. Remove the latter.
Those mark repeatable quests.
This is the new DBM HUD feature which helps you to navigate to available quests and quest objectives. You can access the config in the DBM tab of Questie.
This happens if you have more than one Questie version. In your addon folder you should have a Questie
and a QuestieDev-master
folder. Remove the latter.
20. I have an error saying something about Usage: NewAddon([object,] name, [lib, lib, lib, ...]): 'name' - Addon 'Questie' already exists.
Have a look at 16. You have more than one version of Questie installed which results in such an error!
This indicates you are trying to use the Classic (Patch 1.13+) version of Questie on a vanilla (Patch 1.12) server. Have a look at the install guide below and grab v3.7.1 of Questie.
One of your party members updated to Questie v5.1.0 and you didn't. Update to v5.1.0 as well and there won't be an error.
For now you can do this by running the following command:
/run Questie.db.char.hidden = nil
and do a /reload
afterwards.