|Quest Helper (v1.1.14) - File Description
| Description: |
What It Does
QuestHelper tells you how to finish your quests in the easiest, fastest manner. It includes a database of quests, monsters, and items, telling you the exact location of that dang Perfect Satyr Horn you can't find. It also computes the fastest path to complete all your quests - and gain experience - as quickly as possible.
If you can't afford to donate (It's okay! I still like you) then I also need your data. QuestHelper records monster positions, questgiver locations, item drops, and all manner of fun information that I use to build QuestHelper's database. There's no personally identifiable information involved - I can't get your username, your character name, your friend's names, or anything of that sort. The file I need is stored in the following location, assuming you're using Windows XP and didn't change the installation path:
Crogram FilesWorld of WarcraftWTFAccountACCOUNT_NAMESavedVariablesQuestHelper.lua
Some have reported that for Vista and Windows 7 their path is one of:
C:UsersUSER_NAMEAppDataLocalVirtualStoreProgram FilesWorld of WarcraftWTFAccountACCOUNT_NAMESavedVariablesQuestHelper.lua
C:UsersPublicGamesWorld of WarcraftWTFAccountACCOUNT_NAMESavedVariablesQuestHelper.lua
I've heard that on OSX, the path is:
/Applications/World of WarCraft/WTF/Account/ACCOUNT_NAME/SavedVariables/QuestHelper.lua
To make things even more difficult, it seems that Windows might try to "help" you by hiding file extensions. This makes 'QuestHelper.lua' appear as "QuestHelper". Warcraft makes backups of all these files, so there is a "QuestHelper.lua.bak" file in there as well, and without its file extension, it appears as "QuestHelper.lua", but it isn't really and it's not actually the file I want.
Be careful not to descend into the realm / character directories, we specifically want the SavedVariables directory. There are QuestHelper.lua files in the other directories as well, but they only store which flight routes your characters know, and aren't actually useful. On a similar note, I also don't want the file named SavedVariables.lua, which contains your UI preferences and is entirely unrelated, or the file named QuestHelper.toc, which is a small part of the QuestHelper code and not anything I need.
When in doubt, look at the file size - if it's less than 100k, it's probably the wrong file.
You can email it to me at:
This address is NOT the proper place to direct inquires about the addon. that should be done in the comments below. NO messages sent to this address are EVER read as it receives more than anyone could hope to read. The only thing that logs into that account is an AUTOMATED script to download all the attachments. Every once in a while I happen to glance at a few messages when deleting attachments, and there are consistently month-old pleas for help. These get deleted and not responded to. Do not email questions to this address. Seriously, stop doing it, I don't know why people keep emailing me here.
Many have asked how often to send in data. My personal preference is basically this: Send stuff in every month or so, or when you remember. Thanks!
Please note that the above has nothing to do with installing this AddOn. You install this AddOn the same way you would install any other AddOn, by unzipping it into the "Interface/AddOns" folder.
And, of course, a huge thanks to everyone that has sent me their data so far. It's very much appreciated.
READ THIS BEFORE POSTING AND ASKING FOR HELP
If you're confused by how to make it work, use the Curse Client. The Curse Client pretty much just works now. It is your friend. If you want to install manually, more power to ya, but if you just want to make it work, consider the client. Seriously. I really mean this.
It doesn't show me any objectives on the map: Type "/qh hidden" and see why they're hidden.
It reduces my framerate too much/uses too much CPU: You could try reducing "/qh perf" (for example, "/qh perf 50%".) Some parts of what Questhelper does just intrinsically use a lot of CPU. There ain't no such thing as a free lunch. This problem should be largely fixed in the current version.
It uses too much RAM: You could try "/qh purge" (please submit your data first!) but, fundamentally, the things Questhelper does also use a lot of RAM. There is not much I can do about this.
Pretty much any issue with it not running: "/qh hardreset" should reset it to "factory install conditions". Try it!
How can I help?
Donations pay my rent and buy me food. I'm very attached to rent and food, I find them good things to have. Even a few bucks will help more than you'd expect - look at the top of this page for more information.
You could also submit your collected data to me, which is free and helps Questhelper's database. Check out the top of the page for that as well.
It doesn't work. What can I do?
Three things. First, if there's a major issue with QuestHelper, you can type "/qh error" and it will show you the first error it ran into. If you post that in the comments here, one of the people who helps regularly may be able to solve your problem. Please post the entire error, not just parts of it. We really, really want the see the whole thing, even if it's long.
If it just doesn't work, "/qh hardreset" will reset all your accumulated data and preferences, hopefully getting rid of weird problems. If you still can't see the quest tracker, "/qh treset" will try to force it into a visible position on your screen, with "/qh treset center" jamming it uncomfortably into the center of your screen. It can be moved from there by dragging the small gray box at the top-right of it. If you're not seeing quests at all, even on your main map, "/qh hidden" will tell you why and let you change it. The combination of these three fixes most problems.
If none of those help, disable your other plugins as a test to find incompatibilities.
My framerate is low. What can I do?
If you have any addons that enabled CPU profiling, turn it off, it greatly increases the amount of work WoW has to do. The command to do that is: /console set scriptProfile 0 /console reloadui
If that doesn't make a difference for you, there's a slash command, /qh perf, that can scale the amount of work QuestHelper does per frame. Example: /qh perf 50%
QuestHelper uses a lot of memory. What can I do to fix this?
QuestHelper intrinsically uses a chunk of RAM. You can currently expect about 15m of usage. There's really not anything anyone can do about this, but that small amount of RAM usage also shouldn't be much of an issue.
Why aren't my quests showing up?
/qh hidden will list everything that isn't being shown, along with the reason for it being hidden.
If I send you my data, should I delete my copy?
You'll save hard drive space and RAM, but lose any preferences you had saved. I don't recommend it, but if you want to, it's fine. You can type "/qh purge" ingame to get roughly the same effect without losing your preferences.
How can I get rid of that arrow over my character's head?
First, try right-clicking it and looking for a "hide" option. Second, try /qh arrow, /qh cartwp, or /qh tomtom, depending on which arrow it is. Try them all - at worst, you'll end up with extra arrows. The same command will disable it again. If you'd rather move it instead, you can drag it around by left clicking . . . unless it's been locked, in which case right click on it and unlock it first.
How do get that 3D arrow pointing where to go?
If you'd prefer integration with Cartographer Waypoints or Tomtom, try /qh cartwp or /qh tomtom respectively. I don't really officially support these options, but they seem to work.
The Icons on my map are huge! How can anyone see anything?
If you find the icons are too big for you, you may enter /qh scale X%, replacing X with some reasonable scale. I'd start with 80%, depending on how that looks you can try bigger or smaller numbers.
ZorbaTHut is the current maintainer of this project. Any bugs are probably either his fault or Blizzard's.
Smariot is the original developer of the package.
Nesher and Vipersniper both made improvements while Smariot was still maintaining it, and are worthy of praise.
Lonadar and Divinewind420 haven't actually written any code, but they've been helping out with customer support for many months now, and their assistance has been invaluable. <3
How to avoid getting your account stolen.
Don't run any programs attached to UI mods. Just decompress them into your addons directory. The major site installers, like the Curse.com installer, are probably safe. Be suspicious of everyone and don't give out your password.
Despite persistent rumors, Questhelper does not contain anything that can steal your password. Such a thing isn't even possible.
For the most part, you just install it and leave it alone. It should hopefully be smart enough to do The Right Thing, and not require you to meddle with it.
The task QuestHelper thinks you should do first is displayed on your minimap, which you can mouse over for a description. If the task isn't in your current zone, then it will point towards where QuestHelper thinks you should go to get there, such as a flight master or the zone border.
All the tasks QuestHelper wants you to do are displayed on the World Map. There are 'marching ants' connecting the objectives, showing you the order QuestHelper thinks you should complete them in.
You can right click on an objective to get a list of options for it.
Using the menus should, hopefully, be obvious. The only catch might be that they don't automatically disappear if you click on something else.
You can right click anywhere on a menu to hide it, or select the Close Menu command from the end of the menu.
|Quest Helper (v1.1.14) - File Download Options
Primary Download Locations:
| || Name: |
| Worldwide Mirror by FileFront |
| || || |
|Quest Helper (v1.1.14) - Readme |
| Readme File: |
Version 1.1.14 8/31/2009
* Increase the standard-flying-mount internal speed to 150%
* Add a special case to not take flight paths, ever, if you have an epic flying mount
* Restrict the Dark Portal warps to only exist at level 58. Unfortunately this means that if you hit 58 during a play session, they won't show up until you reload your UI. I'll fix this later, I don't have full access to my dev environment right now.
* Why not? Because I'm at the Penny Arcade Expo this weekend! If you are also, come say hi! I'll be in Tabletop for most of the event. That is all the hinting I will give you to find me.
Version 1.1.13 8/24/2009
* Add new portals to Blasted Lands from each faction city
* Fix right-click on arrow, add objective submenu to arrow
* Fix crash with the new zone system
* Update a few quests and monsters that changed in 3.2
* Add new option for minimap icon transparency, "/qh miniopacity". My lord do I need to set up a better settings dialog at some point
* Make the error reporting system a little more durable in case of wacky versions
* Fix glitch on login where the blocked filter might miss items
Version 1.1.12 8/18/2009
* Fix bug causing a little debug spam on startup, and possibly some other startup issues
* You should still play the new game.
Version 1.1.11 8/17/2009
* Try to handle installation errors better, part 1/2. Stopping here so I can make sure the current code works - if it does, I'll be doing some more work in the next version.
* Minor performance boost
* Tweak to the tooltip to avoid showing unnecessary clutter
* Update database, all new quests should be working just fine now
* Made another game. You should play it.
Version 1.1.10 8/10/2009
* Fix issue causing error messages to not be displayed properly
* Redisplay tooltip entries that are not actual objectives
* Disable some ancient old code that probably wasn't working but definitely was crashing
* Maybe fix the new batch of fascinating performance issues (or maybe not! Who can say? It is a mystery!)
* Update database, dealing properly with another pile of quests that were changed in 3.2 (let me know if you find more)
* Why can't I catch this last stupid terrorfish
* Oh there it is
Version 1.1.9 8/6/2009
* Fix mouseover tooltip for monsters
* Fix group filter to filter out heroics
* Remove the option to disable Blizzard map icons, as Blizzard got there before I did and made it mandatory (seriously blizzard, what happened? this is not that hard to get right)
* Deal with unknown quest objectives properly, where properly is defined as "not by putting them north of Azuremyst in the ocean"
* Fix some issues with 3.2 building causing Icecrown quests to end up in Sholazar
Known bug: if you're Alliance, doing the Taking Battle To The Enemy quest, it will show your quest monsters in the wrong place. I made a typo and it's a 2-hour rebuild to fix, so I'm pushing now - just live with it until either next week or until I run into another build that requires a thursday or friday push. (I know about this bug because I have the very same quest, so I feel your pain.)
Version 1.1.8 8/4/2009
* Fix error in error handling causing non-serious errors to incorrectly be handled as serious errors, thus causing a serious error to occur, which, itself, was handled incorrectly.
Version 1.1.7 8/4/2009
* Bump TOC so it works on 3.2 without tweaking
* Can't currently test it for obvious reasons, so, crossing fingers, praying, etc
* TWO JORMUNGARS
Version 1.1.6 8/3/2009
* Improve the CPU usage system. Should no longer hugely drop framerate for about a minute after login.
* Add option to disable the Blizzard map points in 3.2
Version 1.1.5 7/28/2009
* Re-introduce the per-player objective progress on the map
* Fix Acherus (again)
* Re-introduce the "quests are hidden" message, since it seems like it's needed
* Small bugfixes
* DB update
Version 1.1.4 7/20/2009
* Hopefully fix an issue with high-FPS systems not providing QH with enough CPU
* Hopefully fix an issue where the blue zone may persist even after its objective is complete
* I sound very confident in this patch don't I
* Back to my own projects for a bit! (for real this time)
Version 1.1.3 7/19/2009
* Add a new reminder to submit data
* Fix a possible conflict with other UI mods where we both did something horribly wrong
* Fix a bug causing menus on the bottomright part of the map to sometimes end up truncated
* Add "/qh zones", currently a toggle to remove the blue zone display on the map
* Add "/qh traveltime", a toggle to add or remove display of the "travel time" counter on tooltips
* Back to my own projects for a bit!
Version 1.1.2-rc 7/17/2009
* Fixed a conflict causing missing QH tooltips with some UI mods installed
* Crop the new zone data to the edge of the map properly
* Update database
* Update translations
Version 1.1.1-beta 7/15/2009
* Found and fixed a bug causing excessive RAM and CPU usage after the map was opened. Thanks to all who reported it!
Version 1.1.0-beta 7/13/2009
* Major new feature: Questhelper will now show graphically on your map where objectives can be accomplished. It displays the next objective in blue, and any objective you mouseover in red.
* Increase the cost of the Dalaran/Violet Stand so it stops recommending it as a precursor to flying (even though it may actually be faster)
* Add some instrumentation to hopefully help debug Northrend flying mount errors
* An attempt at a compromise between CPU and memory. Should result in significantly faster routing on startup and not too much more RAM usage
* Fix issue causing QH to try synchronizing quests with people in battlegrounds
* Possible detection of whatever is causing people's systems to entirely stop CPU processing
There's a reason this is beta. There's a lot of changes and some of them might be flaky. Please test it and let me know.
Version 1.0.29 7/3/2009
* Take 2 with the new rare issue bug
Version 1.0.28 7/2/2009
* Rare issue ain't fixed yet! Added more debugging info, please report any crashes you get with this version.
Version 1.0.27 7/2/2009
* Hopefully rather rare issue with quest objectives and, man, I'm not even sure. Groups? Maybe? It's more solid now, at least. Fingers crossed!
* Preliminary 3.2 support
Version 1.0.26 6/30/2009
* Hopefully fix the issues with uncached quest objectives
Version 1.0.25 6/30/2009
* Defer to Blizzard tooltip hints when available, resort to the database entries when tooltip hints are unavailable
* Fix some bugs related to the minimap right-click menu
* If the user is dead or flying, do routing from the user's corpse or flightpath destination, since that's where they're probably going to be next anyway
* Re-enable quest-sharing-related settings menu options
* New filter: "/qh filter wintergrasp". This filter will automatically filter out Wintergrasp PvP objectives unless you are actually in Wintergrasp. (Though, if you're walking around Wintergrasp staring at your Questhelper arrow, you're doing it wrong anyway.)
* Improve the behavior of the new CPU code again
* Cull some old dead code left over from the 0.x line
Version 1.0.24 6/25/2009
* Add a new filter, "/qh filter group". Group allows you to dump group quests and instances regardless of level. The group cutoff can be changed with "/qh group 3", for example, to allow 3-person group quests but no more. It automatically disables when the player is in a group or raid, and defaults to 2-person groups at most.
* Tweak the new CPU code to reduce CPU usage after being alt-tabbed
* Update translations
Version 1.0.23 6/23/2009
* Possibly fix that old routing paradox error. Why did it take me this long to come up with that fix? It is a very, very simple fix. Sigh.
* Rework QH's CPU usage significantly.
|Quest Helper (v1.1.14) - User Comments
The following comments are owned by the user that posted them. World of Warcraft Files is not responsible for their content.
Total comments: 1 | Last comment: 09-23-2009 at 13:31
Joined: September 23rd, 2009
|i am thinking wow matrix is messes up and will nothing work anymore |
When posting comments, you must follow these rules:
The high interactivity of this site should be considered a luxury, not a right. If you cannot follow these simple rules, you can and will be warned or banned from the comments, site or the entire network for any period of time.
- No "Yay I got First Post!" posts, no exceptions and no matter what other content the post has!
- No Pornographic Material. Any sexually oriented imagery or links to such content will not be tolerated.
- No Warez or Illegal Software. This includes linking to software, posting about it, and suggesting to get it.
- No Cursing or Swear words. We encourage you to use our comment sections as a forum to debate files, news, etc., but please use proper adjectives to express yourself. We will not tolerate abuse upon another member or author.
- No Attacks / Retaliation of any kind against a member, or group of members.
- Please do not advertise for other sites or forums here.
- Maximum of 3 smileys per regular member.
Now enjoy yourself and behave!