Table of contents
- 1 Version 184.108.40.206r February 13, 2011
- 2 Version 4.0.3a.142r Februrary 13, 2011
- 3 Version 4.0.3a.115r Mark 2 Jan. 30, 2011
- 4 Version 4.0.3a.115r Jan. 29, 2011
- 5 Version 4.0.3a.112r Jan. 29, 2011
- 6 Version 4.0.3a.111r Jan. 28, 2011
- 7 Version 4.0.3a.106b Jan. 27, 2011
- 8 Version 4.0.3a.103b Jan. 24, 2011
- 9 Version 4.0.3a.100b Jan. 23, 2011
- 10 Version 4.0.3a.92b Jan. 22, 2011
- 11 Version 4.0.3a.90b Jan. 21, 2011
- 12 Version 4.0.3a.75r Dec. 16, 2010
- 13 Version 4.0.3a.73r Dec. 15, 2010
- 14 Version 4.0.3a.72r Dec. 14, 2010
- 15 Version 4.0.3a.70r Dec. 12, 2010
- 16 Version 4.0.3a.67r Dec. 11, 2010
- 17 Version 4.0.3a.66r Dec. 11, 2010
- 18 Version 4.0.3a.65r Dec. 9, 2010
- 19 Version 4.0.3a.64r Dec. 8, 2010
- 20 Version 4.0.3a.62r Dec. 4, 2010
- 21 Version 4.0.3a.57b Dec. 1, 2010
- 22 Version 4.0.3a.54b Nov. 27, 2010
- 23 Version 220.127.116.11b Nov. 20, 2010
- 24 Version 1.4.0 5/5/2010
- 25 Version 1.3.11 2/26/2010
- 26 Version 1.3.10 1/26/2010
- 27 Version 1.3.9 1/20/2010
- 28 Version 1.3.8 1/12/2010
- 29 Version 1.3.7 1/4/2010
- 30 Version 1.3.6 12/29/2009
- 31 Version 1.3.5 12/15/2009
- 32 Version 1.3.4 12/8/2009
- 33 Version 1.3.3 12/2/2009
- 34 Version 1.3.2-beta 11/24/2009
- 35 Version 1.3.1-beta 11/18/2009
- 36 Version 1.3.0-beta 11/16/2009
- 37 Version 1.2.7 11/16/2009
- 38 Version 1.2.6 11/10/2009
- 39 Version 1.2.5 11/2/2009
- 40 Version 1.2.4 11/2/2009
- 41 Version 1.2.3 10/28/2009
- 42 Version 1.2.2 10/28/2009
- 43 Version 1.2.1 10/26/2009
- 44 Version 1.1.23 10/18/2009
- 45 Version 1.1.22 10/11/2009
- 46 Version 1.1.21 10/5/2009
- 47 Version 1.1.20 9/29/2009
- 48 Version 1.1.19 9/22/2009
- 49 Version 1.1.18 9/15/2009
- 50 Version 1.1.17 9/14/2009
- 51 Version 1.1.16 9/14/2009
- 52 Version 1.1.15 9/07/2009
- 53 Version 1.1.14 8/31/2009
- 54 Version 1.1.13 8/24/2009
- 55 Version 1.1.12 8/18/2009
- 56 Version 1.1.11 8/17/2009
- 57 Version 1.1.10 8/10/2009
- 58 Version 1.1.9 8/6/2009
- 59 Version 1.1.8 8/4/2009
- 60 Version 1.1.7 8/4/2009
- 61 Version 1.1.6 8/3/2009
- 62 Version 1.1.5 7/28/2009
- 63 Version 1.1.4 7/20/2009
- 64 Version 1.1.3 7/19/2009
- 65 Version 1.1.2-rc 7/17/2009
- 66 Version 1.1.1-beta 7/15/2009
- 67 Version 1.1.0-beta 7/13/2009
- 68 Version 1.0.29 7/3/2009
- 69 Version 1.0.28 7/2/2009
- 70 Version 1.0.27 7/2/2009
- 71 Version 1.0.26 6/30/2009
- 72 Version 1.0.25 6/30/2009
- 73 Version 1.0.24 6/25/2009
- 74 Version 1.0.23 6/23/2009
- 75 Version 1.0.22 6/22/2009
- 76 Version 1.0.21 6/15/2009
- 77 Version 1.0.20 6/10/2009
- 78 Version 1.0.19 6/4/2009
- 79 Version 1.0.18-beta 5/22/2009
- 80 Version 1.0.17 5/21/2009
- 81 Version 1.0.16 5/18/2009
- 82 Version 1.0.15 5/14/2009
- 83 Version 1.0.14 5/14/2009
- 84 Version 1.0.13 5/11/2009
- 85 Version 1.0.12-rc 5/6/2009
- 86 Version 1.0.11-beta 5/6/2009
- 87 Version 1.0.10-beta 5/5/2009
- 88 Version 1.0.9-beta 4/30/2009
- 89 Version 1.0.8-beta 4/29/2009
- 90 Version 0.106 4/27/2009
- 91 Version 1.0.7-alpha 4/22/2009
- 92 Version 0.105 4/22/2009
- 93 Version 0.104 4/22/2009
- 94 Version 0.103 4/16/2009
- 95 Version 0.102 4/15/2009
- 96 Version 0.101 4/14/2009
- 97 Version 0.100 4/14/2009
- 98 Version 0.99 4/13/2009
- 99 Version 0.98 4/7/2009
- 100 Version 0.97 4/5/2009
- 101 Version 0.96 4/2/2009
- 102 Version 0.95 3/20/2009
- 103 Version 0.94 3/17/2009
Version 18.104.22.168r February 13, 2011
Fixes issue 349.
Version 4.0.3a.142r Februrary 13, 2011
Resolves several issues and updates quite a bit of pathing info.
Issues resolved (GoogleCode issue numbers): Issue 50, issue 294, issue 295, issue 315, issue 321 and issue 324. Issue 294 and issue 295 may have been resolved in release 115, but I am not sure.
And yes, this is compatible with the 4.0.6 client. I just forgot to change that part of the version number... next release will see this problem fixed.
Version 4.0.3a.115r Mark 2 Jan. 30, 2011
Reupload of 115r. File was corrupted during upload yesterday. Local checksums are different from what is shown here and on GoogleCode.
Version 4.0.3a.115r Jan. 29, 2011
As far as I can tell, all runnability errors have been dealt with. Implemented some elder waypoint changes.
Version 4.0.3a.112r Jan. 29, 2011
Version 4.0.3a.111r Jan. 28, 2011
This version hopefully fixes the "Coord = 181" error for good. It also finishes a collector for hearthstones, to hopefully allow for the inclusion of hearthing during path calculation.
I have chosen a full release for this version in order to get the new collector in play on as many machines as possible.
Version 4.0.3a.106b Jan. 27, 2011
Added an assertion to help diagnose the persistent "Coord = 181" error. Added a collector for hearthing.
Version 4.0.3a.103b Jan. 24, 2011
Made a few elder coordinates more accurate. Made it so that coordinates would map, regardless of localization. You still need to input in US English, but you should get the "right" points regardless of locale. Made some modifications to collect_loot to better understand what's coming through when we are doing archaeology.
Version 4.0.3a.100b Jan. 23, 2011
Well, this is a milestone of sorts... Version 100.
- Corrected the Durotar Zeppelin location, which is now in Orgrimmar.
- Corrected issue 267.
- Added functionality to route you to the elders. This can be accessed via the slash commands "/qh find elder" or "/qh find elders". If you add an argument, you can find a particular elder or all the elders for a particular achievement. To access achievements, use the last part of the achievement name. For example, for "Elders of the Horde," use "Horde" as the argument. Likewise, if you are looking for a particular elder, drop the "Elder" part of the elder's name and the location part. For example, for "Elder Darkhorn in Orgrimmar," use Darkhorn as the argument. One caveat though is that QH doesn't seem to be ordering the elders in a consistently logical order or reordering when it should be.
Version 4.0.3a.92b Jan. 22, 2011
Fixed a bug.
Made errors contain a list of quests.
Version 4.0.3a.90b Jan. 21, 2011
The culmination of LOTS of changes.
This version has many collection structure changes in hopes to make it easier to build the new database. In the meantime, I have put the old database back in place.
Just beware if it seems to work with EK and Kalimdor... You probably will be directed to the wrong place. You shouldn't have any issues in Outland or Northrend.
There's also a couple bug fixes thrown in there too.
Version 4.0.3a.75r Dec. 16, 2010
Fixed issue with Coord = 209. Made some more changes to the saved variables file structure.
Version 4.0.3a.73r Dec. 15, 2010
Added LostIsles_terrain2. Made some more changes to the saved variables layout.
Version 4.0.3a.72r Dec. 14, 2010
Added flight master check for EK, Kal and Maelstrom. Added LostIsles_terrain1. Set real sizes of new zones.
Version 4.0.3a.70r Dec. 12, 2010
Added check for nil c in float(c) in collect_location.lua. Added 'meta' paths for Maelstrom Continent zones. Added 'meta' sizes for new zones. Converted some of the stored data to output strings, rather than convert numbers to sequences of bytes.
Version 4.0.3a.67r Dec. 11, 2010
Except for Goblin start zone and Maelstrom Continent zones, paths are complete. I also fixed and issue with archaeology, which was caused by fragments not having item links.
Version 4.0.3a.66r Dec. 11, 2010
Fixed issue 140. Added paths for STV sub-zones, did not encounter STV master anywhere. Finished pathing for Worgen starts, up to and including the official path to main world... I just need to go back with another new Worgen to check the start coords for accuracy. Added routes for Ruins of Gilneas and Ruins of Gilneas City (City is its own zone, but isn't triggered reliably or accurately). Adjusted assertion error text for collect_location to be more useful. Made the afflicted function return strings too, since I want as much plain text as possible. It is late, and that seems to be all I can remember.
Version 4.0.3a.65r Dec. 9, 2010
Added paths for Vash, Hyjal and Uldum. Started debugging an error that occurs when flying between Vash and mainland EK. This error also is occurring while browsing maps.
Version 4.0.3a.64r Dec. 8, 2010
Due to database build issues and excessively out of date quest data, I blanked out database files. This means NO DATA FOR ANY QUESTS. I also stopped collected data compression for the time being, in order to keep the underlying data structures visible for building the new database build system. Added support for new spell objective type. Began inserting static routes for zones. Removed Portals from Shatt and Dal. Added virtual zones for Worgen starting areas. Made a couple new error messages that are a bit more verbose. Fixed a syntax error.
Version 4.0.3a.62r Dec. 4, 2010
This update creates some more informative error messages that were needed to fix an issue with German and Russian clients, where Blizzard used the same name for Gilneas and Gilneas City in those languages.
This update implements a work around for said problem.
Version 4.0.3a.57b Dec. 1, 2010
This update re-enables tracking. New zone information has been mostly implemented (still need to determine current sizes, map ids and offsets of old & new zones).
Version 4.0.3a.54b Nov. 27, 2010
This update disables tracking allowing QH to run without noticeable errors and collect quest information. Please collect data for a few days before submitting the saved variables file for QH.
Version 22.214.171.124b Nov. 20, 2010
This update contains a shaky memory of what has been done thus far.
- Updated QH for the 4.x.x clients.
- Made quest sharing work again. You may need to toggle solo mode off and then back on again to start sharing properly.
Version 1.4.0 5/5/2010
- Added a configuration system (okay, the excellent configuration from the UI mod QuestHelperConfig)
- GPL'ed the source
- Included the build tools in the git repo
- Updated the DB for old time's sake
- Everything in the bottom section is still accurate, so go re-read it
Version 1.3.11 2/26/2010
- Database update
- The following enormous wall of words
Okay, clearly it's time for a State of QuestHelper.
Short version: QuestHelper isn't being updated much anymore, for a variety of reasons. I'm going to keep it working, but aside from a few interface improvements that I've been meaning to put in for months, you're probably not going to see many big changes.
QuestHelper's always been kind of an odd project for me. I picked it up because it looked like a challenge, because I wanted it to work better for my own purposes, and because I saw a lot of potential for what it could become. Since then, we've seen a lot of changes in WoW. I started back in the days of 2.4.0, when we were eagerly awaiting Wrath, and today we're largely finished with Wrath and eagerly awaiting Cataclysm.
As WoW has changed, so has my situation.
- I don't quest anymore. I always enjoyed dungeons more, and with the 3.3 LFD changes, pretty much all of my playtime is now spent in dungeons. I imagine I'll level up a Worgen through quests once Cataclysm comes out, just to see the new quests, but that's about it.
- On top of that, I don't really play much anymore. I've got other huge projects on my plate (come visit http://www.mandible.net). I originally picked up WoW to play with friends and to learn from Blizzard's design expertise. All the friends I originally joined with have quit, I started raiding and then stopped again, and, minus the changes coming up in Cataclysm, I feel like I've learned everything I'm going to from Blizzard, and learned quite a few things that Blizzard could stand to learn.
(Hey, Blizzard. Hire me to balance your classes. You want me. Trust me on this. I'll make your game sing.)
- QuestHelper was actively worked on as long as it was, largely thanks to the donations. Without those, I would have had to dump it much earlier - your generous donations literally kept QuestHelper running. With the 3.3 quest map changes, QuestHelper doesn't have nearly as many users, and those who still use it don't donate as much. I simply can't afford to put a lot of time into it anymore.
Note: This isn't an attempt to throw blame on people or anything of that sort, I don't want you to feel guilty for not donating, I'm not trying to make a last snatch of cash off this thing. It's just what happened. Sometimes the economic truths change.
- Along with that, QuestHelper doesn't have as many users as it used to. QH was partially useful as a vehicle for learning how to deal with large userbases (done, mostly) and, I'll admit, for advertising my other projects. Both of those, obviously, aren't as useful anymore.
- Along with *that*, I had a bunch of neat ideas on how to turn QuestHelper into something truly huge and spectacular. Unfortunately, Blizzard's addon development rules, coupled with the 3.3 changes, pretty much killed that project. If I were to do that - and I'd still like to do that - I'd need a level of funding that I simply don't have potentially available anymore. If you're sitting out there with a few million bucks burning a hole in your pocket, lemme know - I might have a good way to spend it - but without that person showing up, my ultra-long-term plans are pretty infeasible, and I already burned a month trying to come up with alternatives. Turns out not all business plans work out :)
- Most importantly, though: QuestHelper is done. It works. It's got a few glitches, it's got a few missing features. Fundamentally, it accomplishes what I wanted it to accomplish. I'm proud of what I've built, but I don't see anything to add that seems worth the time.
I don't yet know what the future of QuestHelper brings. Obviously, there's some question about whether it will continue working in Cataclysm. I really couldn't say - the Cataclysm conversion might be simple, it might be a major redesign of QuestHelper's interface. I'll let you know when I find out. This will happen once I get my hands on a Cataclysm beta code. :)
If someone would like to take it over, they're absolutely welcome to. I don't *really* expect this to happen - QuestHelper is a beast of a UI mod, and I firmly believe it is the most complex UI mod in WoW. But if someone would like to try, take a look at the sourcecode and go add something moderately major.
But beyond that: it's been a good ride, thanks for coming along. I've had a lot of fun working on this thing, and that's largely thanks to the people who donated, the people who encouraged me, and the people who helped out with tech support. You're all awesome.
Go kill Arthas for me.
Version 1.3.10 1/26/2010
- More instrumentation, more DB update. I'm hoping to get some of these bugs squashed but I still need more debug reports, so keep 'em coming.
Let's have it for another game! Mr. McDougal's Marvelous Upside-Down Electrotree took far longer than I'd really expected, but it is here now and so you should play it.
Version 1.3.9 1/20/2010
- More instrumentation for a few more weird bugs I'm seeing. Keep reporting 'em, I'm not quite sure what's going on yet
- Standard DB update
- Been slacking off waaaay too long on updating translations, so I updated 'em. Sorry 'bout that.
Version 1.3.8 1/12/2010
- Fixed a bug caused by slightly odd out-of-order loading
- Add some debug instrumentation for a consistency failure in data collection
- Trying to track down the missing-tooltip glitch
- DB update, I'm just doin' one of these every week now clearly
Version 1.3.7 1/4/2010
- Just a database update today, but with luck this'll include a good chunk of the 3.3 quests
Version 1.3.6 12/29/2009
- Well that was a bit longer of a delay than I'd intended
- Fix a bug involving ignoring quests through the arrow
- Somewhat improve the smoothness of the loading system
- Add some instrumentation so I can, in the future, strip out race-specific and class-specific quests from /qh incomplete
Made another monthly game! Andre Copperman Picture Panic! is now available for free download. Come give it a shot! Destroy my webserver with your downloads.
Version 1.3.5 12/15/2009
- Fix "/qh help" to display all the text instead of its previous behavior, namely, not displaying all the text
- Strip a ton of private server data out - should eliminate some of the crud showing up in "/qh incomplete"
- Database update
Version 1.3.4 12/8/2009
- Bump TOC for official 3.3.0 support
- Fix up the "/qh help" text for "/qh find"
- Tweak the worldobject support code
- Database update
Version 1.3.3 12/2/2009
- Alright, let's make this official. Achievement support out of beta! There may be bugs, please report. You know the drill by now.
- Disable radar if target is dead
- Database update
Version 1.3.2-beta 11/24/2009
- Sorry for the slow bugfixes, life has been incredibly busy. Another pile of bugfixes in this version - once again, please report anything that's problematical.
- Database update, also.
Version 1.3.1-beta 11/18/2009
- Many many small fixes and tweaks. If you had an error in 1.3.0-beta, please try to reproduce it and report on success or failure. Every error report I received had been handled one way or another, but some of them may still be live, as I was unable to reproduce some of them. Also, if you can give solid reliable instructions on how to reproduce any error, it's much appreciated!
- Made the objective menu a little smarter - it will no longer prompt for "ignore this location" if that location is the last one it knows about for that objective
- Added some better error handling for "/qh find"
- Commented out a pile of dead code, will remove it in a future version if it proves to actually be dead and not just staggering along in some horrifying abomination of diseased unlife, moaning for cerebral matter and dripping on your carpet
- I think the carpet is a metaphor for your computer's memory but I sort of lost track somewhere in there
- ALTERNATE PUNCHLINE: that carpet really tied the room together
- I came up with a neat idea and some guys told me it was impossible, so I did it. "/qh radar" attempts to triangulate the position of your current target and shows its likely location on your minimap. It may be buggy and/or have performance problems - at the moment it's largely a proof-of-concept, and it's already proven invaluable at helping me track down a few rare monsters. I may improve it in the future.
- If you want a one-line description of my life, just go up one bullet point from here and read until you hit a period.
Version 1.3.0-beta 11/16/2009
Hey hey time for a major version
Major feature the first: Achievements. QuestHelper will now help you with various achievements directly in the UI, including exploration, monster/critter slaying, and fishing node achievements. Merely go into your existing Achievements pane and look for a little checkbox on the bottom-right of some achievements next to the QuestHelper symbol. Check the box and follow the path!
Want an easier way to find achievements QH can assist you with? Look at the dropdown in the topright of the achievements window, and choose "QuestHelpable". Bizam! Now it only shows QH-compatible achievements.
First, there are some achievements that QH claims it can help with that, in reality, it's pretty much useless for. At the moment this includes just about everything in the PvP category, many things in Raids, and the entire World Events category. Conversely, there are some achievements that QH could help with that it currently doesn't, mostly all the Classic and BC dungeons, but also some of the World Events. (Yes, Bonfires and Candy are . . . uh . . . unsupported, I guess? They should be back before next year, along with Elders.)
Second, if you add a lot of achievements, Questhelper may get somewhat slow and memory-hungry. Adding all the Exploration nodes to a new level 1 character generates approximately 1,400 individual locations to visit, burns around 150 megs of RAM, and takes something like twenty minutes to finish the setup phase. Its path generation may suffer under this kind of load. Luckily, it's reasonably easy to remove and add things, but if you say "I added World Explorer to my level 2 hunter and it got slow, how can I fix this" my answer is going to be "turn off World Explorer".
Third, there's no way QuestHelper can know where rare mobs are at any particular moment, so it just routes you to where they probably are, and if they aren't there, well, ignore the node (right-click the item on your minimap) and come back later. In my testing you've got less than a 2% chance of any particular location containing a spawned rare monster, so, I mean, there's a reason they're called "rare", and it's not because they're so dang easy to find.
There may be bugs. That's why this is a beta. Report away.
Major feature the second: THIS FEATURE WILL ONLY WORK IN WoW 3.3. Seriously. It is not going to work right now. The option will not do anything. However, once 3.3 is released, QuestHelper will now optionally show dots on your map for quests that you haven't done. "/qh incomplete" to activate it, then look at your map.
There may be bugs, including quests shown that shouldn't be shown and quests not-shown that should be shown. It does give the quest name and the quest ID number to help track down info about that quest. Again, go ahead and report bugs, but remember, THIS FEATURE WILL ONLY WORK IN WoW 3.3, if you tell me it doesn't work right now I am just going to laugh at you.
- Various improvements to make it more immediately responsive to new objectives/finished objectives/completed achievements.
Version 1.2.7 11/16/2009
- Database update
- Hey, why are you reading this, go read the 1.3.0 entry instead
Version 1.2.6 11/10/2009
- Fix some bugs involving the Tracker button visibility
- Shrink the Tracker button a bit
- Calling it now: people are going to complain that the tracker button is too small
- Lots of work going on behind the scenes! Magic will occur shortly.
- New database
Version 1.2.5 11/2/2009
- Fix an initialization bug that nobody but Zorba would ever notice nor care about
Version 1.2.4 11/2/2009
- Fix some data collection issues keeping me from adding game object support
- Added a progress indicator for route changes that are taking an uncommonly long time
- Cleaned up some bad behavior with the tooltip
- Fixed a bug causing unnecessary info to be built into the compressed datafiles
Version 1.2.3 10/28/2009
- Well that was a silly bug. I have no idea how that got through my testing. Fixed.
- There is still a new game available to be played. It is about numbers and counting - two things which everyone finds fun. Correct me if I am wrong! (I am not wrong.)
(I wish I could stop releasing new bugfix versions, I'm going to feel pretty silly spamming this six times in one week)
Version 1.2.2 10/28/2009
- Fix visual issue with the modified tooltip
- Fix some irritating consistency issues with the tracker button
- There is still a new game available to be played. It is about numbers and counting - two things which everyone finds fun. Correct me if I am wrong! (I am not wrong.)
Version 1.2.1 10/26/2009
where doing it man where MAKING THIS HAPEN
Reimplemented "/qh find". For example, "/qh find murloc", "/qh find loc 50 50", "/qh find loc stormwind 20 80". It may be slightly faster than it used to be. It may also have issues. Issues with a capital Issues.
First, I currently don't have support for items, only for monsters and locations. Does anyone care about items? Note that it won't include everything - a full database is huge, and QH currently only includes stuff that's useful for quests. So I can track known quest items. Alternatively, I can include a certain set of things (like reagents) into the database explicitly. Are those useful? I really don't know. You tell me!
I'm not releasing this as a beta version, since everything but "/qh find" is stable. "/qh find" itself should be considered beta. There are probably missing features that I'm not aware of, and there may be bugs. Please report any issues or unfortunate behavior!
- New database, obviously :D
- Tweaked the rendering order on the tracker handle. May not show up on top of your bags anymore. May still work properly. May not! It is an adventure to all.
Oh yeah I went and made another game. This one's about numbers! You like numbers, right? Come play with numbers. Come play with numbers.
Version 1.1.23 10/18/2009
- Remember how the last version was supposed to have 3.3 compatibility? Yeah well uh
- 3.3 compatibilty for real this time
- (crosses fingers)
- Fix minor display irritation in tooltips
- QuestHelper now has a logo. You'll notice it in tooltips and in the quest tracker. I've done my best to make it noticable but unobtrusive - I've noticed that a lot of people seem to have a hard time distinguishing the line that separates Questhelper and World of Warcraft, and I'm trying to make this line a little more obvious (both for my sake, and for Blizzard's.) Let me know if you've got suggestions for improving either the logo or its placement, or if you really really really hate it.
- Also let me know if you want it on a T-shirt :D
- Support for Hallow's End candy buckets! "/qh buckets". It behaves just like the old Midsummer Fire Festival bonfires did, since it's based on the same code. Performance may suffer while this option is on, as it's nowhere near optimized, it's just a dirty hack. I don't yet have support for Northrend buckets. (Just like Blizzard! ha ha, burrrrrn)
Version 1.1.22 10/11/2009
- 3.3 compatibility
- Add a new filter "/qh filter raidaccessible". If the filter is on, and you're in a raid, it will filter out quests that you would be unable to make progress in.
- By now you should realize that a significant number of QH features exist because I keep screwing things up, so you can probably guess why that feature exists
- Fix the director_quest.lua crash (I hope)
- Add debug instrumentation for a few more bugs
Version 1.1.21 10/5/2009
- Make Cartographer stop breaking Questhelper. At least, breaking it as much.
- Add support for quest items contained inside containers (alright this mostly exists because I got tired of the Bloated Monsterbelly daily directing me to Dalaran)
- Make Questhelper stop resetting the chat font on startup. Why did it used to? I do not know. There are nooks of this code that I still do not fully comprehend. If this causes your computer to melt into a small puddle of radioactive slag
**, please let me know.
- Fix an issue causing the load progress indicator to be displayed despite the user indicating a clear preference that it should not be
- Initial quest-update will again be reliably included in the progress indicator
- Stop an annoying flicker when tracking/untracking quests
** Questhelper is not responsible for your computer melting into a small puddle of radioactive slag, nor responsible for proper disposal of the aforementioned slag.
Version 1.1.20 9/29/2009
- Fix some glitches in the database build code that may have produced Unexpected Output in 1.1.19, probably including flighpath errors and possibly including dang near any wacky behavior imaginable
- Found and fixed a mistake in data gathering that was causing excessive data to be recorded
- Implemented a quick cleanup to go obliterate everything that was mistakenly recorded (okay most things not everything)
- Moved some initialization from the loading screen to post-load. WoW should start a little faster, though QH will take a little longer overall to be "ready". There may be some obscure bugs if you use /qh commands early in the load sequence, please report these if you run into them. There also may be some little framerate hitches during the early load sequence, I'll deal with those later.
- Possibly fix a minor compatibility glitch with ClearFont4
- Database update again, this time without problems, fingers crossed
- Translation update
- Hey guess what I did! I made another game. Come give it a try and let me know what you think.
Version 1.1.19 9/22/2009
- Database update, hopefully including Brewfest quests
- Translation update
- yeah alright this is a pretty crummy version, sorry, life's been busy
Version 1.1.18 9/15/2009
- Fix the crash when exiting Isle of Conquest
- Update translations
Version 1.1.17 9/14/2009
- Remove some debug output
- Fix a small potential glitch allowing people to accidentally break QH
- This might be my fastest version update ever
Version 1.1.16 9/14/2009
- Fix bug with misnamed flightpath links
- Simplify the description of interzone links
- Add more debug output for a new bug that seems to be related to leaving battlegrounds (please report any "/qh error" crash you encounter when doing so)
- Improve speed of adding new quests and objectives yet further
Version 1.1.15 9/07/2009
- Added the error catching system to /qh purge, which honestly should have been in there for quite some time
- Turn some data gathering off, turn some on
- Further speed improvements. Something like a 50% improvement (or more) to picking up new quests and new objectives. This is a good thing.
- Disable some old 3.1 compatibility code which may be incorrectly triggering in some situations
- PAX was awesome. You were there, right?
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.
Old QH would use a certain amount of CPU time per frame (about 2 milliseconds by default). This meant that on high-FPS systems it could use 20% or more of the system CPU (reducing framerate heavily), and on low-FPS systems it could drop to 1% of the system CPU. Bad all around.
New QH tries to use a roughly constant amount of CPU time (by default, it's 7.5%.) This should result in roughly the same CPU usage on systems that get 40FPS, with increased CPU usage with lower FPS and decreased CPU usage with higher FPS.
On top of that, New QH tries to smooth out your framerate a little. If it notices that the last frame took a very very long time to render, it'll actually halt calculations for that frame, increasing your CPU. Conversely, if the last frame was extremely fast, it'll do more calculations since you probably won't notice. It's possible that WoW with QH installed will actually feel smoother than with it not installed - "/qh perf 500%" not only uses more CPU on my system than it used to, but it feels like only a slightly increased drain on resources.
It turns out that, in many situations, the "use more CPU during higher framerate times" code will account for the majority of QH's CPU usage. That's pretty neat.
As a side note, I reset everyone's "/qh perf" setting. The old numbers have basically no relevance to the new system.
Lemme know what it feels like.
Version 1.0.22 6/22/2009
- Added right-clicking objectives on the minimap
- Remove the annoying "Too Many Stored Objectives" error
- INCREDIBLY EXPERIMENTAL FEATURE -
Enjoying the Fire Festival? Want some way to easily path between all the bonfires? Now you have one! Type "/qh bonfires" and Questhelper will add an objective for each bonfire in the game! It's just that simple, right?
No, it's not that simple.
The bonfires are a thing I hacked in in about an hour. As such, it is a highly unpolished feature. On top of that, it exposes some scaling issues with the Questhelper core (issues that I knew existed, but haven't really been important until now.) On top of *that*, I put basically no effort into making the interface good.
- Questhelper may take several minutes to display the bonfires in your route. Along with that, it may update the player location very infrequently.
- Questhelper's initial route will be quite crummy. It may take several minutes for it to become good.
- Questhelper will use significantly more RAM.
- Questhelper will not detect which bonfires you've already completed, nor automatically remove the bonfire objectives after you complete them. You'll have to do that manually, with "ignore".
- Performance issues will probably remain until you log off.
- There may be other issues. This is a *highly experimental feature* and I provide no support for it - it's sort of a sneak peak into what's coming.
Enjoy the Fire Festival!
Version 1.0.21 6/15/2009
- Tired of Cartographer being broken, hideous ghastly hackjob to make it stop causing problems in instances. With luck, it won't make Cartographer explode badly. With further luck, if it does, nobody will blame it on me.
- Database update
- Next week's update will be similarly small, with luck the one after that will include, you know, useful things
Version 1.0.20 6/10/2009
- Fix compatibility issue with UnicodeFont
- Database update
Version 1.0.19 6/4/2009
- Move event handling around quite a lot to make it possible to debug stutters and performance issues a little better
- Added <tt>/qh metric</tt> to toggle between metres and yards, thanks to smariot
- Various small bugfixes in the quest sharing code
Version 1.0.18-beta 5/22/2009
BACK TO BETA
So, why's it beta? Because I've got an experimental implementation of group quest sharing working. See, normally, when I do big nasty things, I go and test it for a few hours on my own. I bet you can figure out the problem with testing "group quest sharing" on my own!
So I'm posting it here. Want group quest sharing? Try it out, you've got the weekend. Barring bugs, it'll be released as a non-beta on Monday. And if it then turns out to be buggy I shall be very cross indeed.
That's the only change of note in this version.
Version 1.0.17 5/21/2009
- Fix the issue with QH crashing inside Ulduar and Naxxramas (and, in the process, fix some truly stupid decisions I made with the pathfinding. seriously, what was I thinking. can someone invent a time machine so I can go back and kick myself in the shins?)
Version 1.0.16 5/18/2009
- Fix for a series of possibly-related problems - table-too-large errors, ridiculous loading times, and excessive memory use
- Hopefully fix issue with quest items vanishing from the tracker
- Undo the possible optimization in 1.0.14 since I decided it was a bad idea
- Update translations
Version 1.0.15 5/14/2009
- Fix a very silly mistake causing QH to crash on login if the user decompressed over the old version (this does nothing useful if 1.0.14 works for you, but if it doesn't, try this out)
Version 1.0.14 5/14/2009
- Take a shot at a fix for routing in non-enUS locales
- Make the arrow and textsize configuration stick through restarts
- Reimplement the tracker color and level options
- Optimize routing a little bit
Version 1.0.13 5/11/2009
- Lucky number 13 is the official release.
- kmcguire pointed out that a bit of QH was using far more memory than I'd thought, and gave a suggestion for how to improve it. It's now a lot more efficient. Memory usage reduced by 5mb.
- Handle one or two this-should-probably-never-happen errors more cleanly
- Possibly remove some jerkiness issues people were having
Version 1.0.12-rc 5/6/2009
- Attempt to fix the too-many-tables error in several different ways
- Let's call this a release candidate, I either need to do that or push a new version of 0.x and I really don't want to push 0.x (yep that's right, "release candidate" status is based solely on how lazy Zorba is)
Version 1.0.11-beta 5/6/2009
- Fix the obj-null-arrow error that's been plauging a lot of people
- Better-instrument the too-many-tables error. If you've been running into this error, please make it happen again and report it
- Increase performance a bit when using flying mounts
Version 1.0.10-beta 5/5/2009
- "Done" filter was mislabeled as "zone" filter in /qh hidden
- Fixed dumb mistake in the code to clear out ancient collected data
- Add hooks to allow QH to be reset to point at a custom minimap object, thanks to Antiarc
- Maybe fix that recurring crash in the arrow
- Make it slightly more emphatic about rescanning filters when they're likely to change
Version 1.0.9-beta 4/30/2009
- Instrument some errors that people are running into - I haven't fixed them, but this should give me more information on how to fix them properly.
- Fix a bug causing the routing code to essentially stop routing new things when a large number of flightpoints are discovered
- Allow the tracker to grow up again
Version 1.0.8-beta 4/29/2009
- Change how the too-many-objectives-for-this-quest error shows up - hopefully I'll get reports without it breaking people's QH now
- Remove a lot of old 0.x saved variables
- Better support for mods that embed the quest level into the quest name
- Highlight quest-turn-in spots gold
- Many tweaks to handle WoW tooltips properly
- Update the route in realtime as you gain/lose objectives, instead of throwing all the work away and starting semi-fresh
- Store new flightmasters properly
- Fix a minor issue with tracker spacing on quests that have special items
- Add loading progress percentage
- Fix issue with arrow and minimap dodad not unhiding properly
- Add settings menu and button
Version 0.106 4/27/2009
- Provide scaling for the arrow and the arrow text
- Re-insert the map button in a less conflicty place, hopefully
- Add a feature to generate error reports on-demand - "/qh error full" to get a version and addon dump, which may be useful for debugging issues.
- Provide the rotating-arrow-pointing-down thingy, now people are going to leave comments complaining about the existence of it instead of the nonexistence of it, I CAN SEE THE FUTURE AND IT'S FULL OF EMO
Version 1.0.7-alpha 4/22/2009
- Not quite sure where to start here.
- Full rewrite of the routing core, pathing core, filters, quest director, data collector, data compilation, and database systems. Probably more. Consider this essentially an entire new UI mod, that merely happens to behave identically to QH 0.x.
Version 0.105 4/22/2009
- Fix a bug in the Cart-arrow-autodisable, hopefully before too many people have looked at two arrows and said "oh hey I think I'll turn this one off" and picked mine (sigh.)
- Get rid of an old useless error, because, why not
Version 0.104 4/22/2009
- Questhelper now includes a built-in arrow. "/qh arrow" to disable or enable, "/qh arrow reset" to reset its position. I've turned the Cartographer and Tomtom arrows off by default, but you can turn them back on with the old /qh cartwp and /qh tomtom commands.
- Possibly fix a small issue with the "special item" code
- Disable the map button. This is temporary - it's just kind of broken right now and conflicts with the default Blizzard UI. I'll come up with a solution.
Version 0.103 4/16/2009
- Fix up the errors more permanently with a fundamentally better system
- Give up on trying to be clever, brute-force the quest item thing
Version 0.102 4/15/2009
- Take 2 on suppressing that donglestub error
- Fix the textviewer for /qh changes and /qh help and the like
- Improve the behavior of the quest-special-item display so it actually, you know, displays the right item
Version 0.101 4/14/2009
- Fixed an issue causing the tracker to show up in the middle of the screen by default
- Suppressed an error caused by QH's overzealous error detection
- Of course there would be last-minute bugs, what else were you expecting
Version 0.100 4/14/2009
- Bump TOC so it works in 3.1 without having to check the "out of date addons" box
- Awaiting the inevitable complaints that 0.100 doesn't come after 0.99
Version 0.99 4/13/2009
- Add preliminary support for 3.1 dungeon maps
- Replace the minimap arrow for 3.1 compatibility (let me know if it breaks, it's written completely differently now although it should behave identically)
- Update translations
Version 0.98 4/7/2009
- Try another fix for the collect_quest.lua crash
- Make it a little more careful about stripping yellow text out of tooltips
Quick explanation of what's going on: The reason we're running into some new bugs right now is in preparation for 3.1. 3.1 involves a little extra code to deal properly with its built-in tooltips, and while the tooltips don't exist yet, I do have some of the code already rigged up to watch for them. Obviously there's a few bugs in that code, but I'd rather have the bugs showing up now - when you can downgrade to a previous version without issue - than later, when you can't.
Fingers crossed that this polishes everything off.
Version 0.97 4/5/2009
- Fix a bug with uncached quests on logon and with quests that have multiple identical objectives
Version 0.96 4/2/2009
- Support for special quest items in 3.1
- Support for reading from and suppressing Blizzard's 3.1 "questhelper clone" tooltips
First: I want to thank everyone who has donated. I've been getting a lot of donations from people saying that they sympathize, saying that Blizzard's actions suck, I've even gotten a few that explicitly said "don't consider this a requirement to keep working on Questhelper, consider this a thanks for all the work you've put in already."
You guys rock. While I don't respond to every message, I do read every one. Thank you.
Second: I'm still plugging away at 1.0. I'm hoping to get a beta release out before WoW 3.1 is released. There will be a few missing features, but I plan to eventually re-implement everything besides possibly "/qh find", which would either take a lot of memory or be painfully slow. (I guess I could choose the latter, if people want it a lot.)
Third: Does anyone know a reasonably-skilled artist who'd be interested in breaking into games? I'm looking for someone to do non-tilebased 2d art. Don't know if I can pay or not, but I do plan to release stuff frequently, and at least it'd get your name out there. Email me or leave a comment if you're interested.
Yeah that's right, if I can't make a living off this I can at least use it as a blurb space for my other projects :D
Version 0.95 3/20/2009
- Disable donation request.
Bad news, everyone. Questhelper's dead.
Blizzard just posted their new UI Add-On Development Policy at http://www.worldofwarcraft.com/policy/ui.html. The important part is that I'm no longer allowed to ask for donations in-client. I know how much I got before I added the in-client reminder - it doesn't pay a significant fraction of the bills. And, as much as I like you guys, good intentions don't pay for my apartment.
So that's it. I'm going to be finishing up and releasing v1.0, and I'll keep posting incremental database improvements every month or two. I do plan to keep QH functional, at least through the end of Wrath, and probably further. I've got one or two features in mind that I want to do for my own sake - a few achievements, mostly - but besides that (and the v1.0 release) that's pretty much all there's going to be.
I would like to say: thanks to everyone who donated in the past. I enjoyed working on this quite a bit, and I always enjoyed seeing another donation come in - not just because of the money, but because it meant that people wanted to use QH and wanted to keep it going.
Let Blizzard know if you don't like it, and if I can get an exception, I'll start everything right back up again :)
Version 0.94 3/17/2009
- Update database.
HEY ZORBA WHERE'S 1.0 YOU SAID IT WOULD BE OUT BY NOW YOU SUCK AND I HATE YOU
Yeah, I'm sorry. I've been painfully busy. You have no idea how busy I've been. That said: 1.0.0 pre-pre-pre-alpha is sent out to a few good friends of mine to test. I'm hoping to get a pre-pre-alpha out for testing by the end of the week. There's a bunch of problems left, but most of them are reasonably easy to fix, just timeconsuming. Unfortunately, next week is pretty much 100% taken (thanks to
Database is not current... It is the old one, but should work sufficiently for Outland and Northrend.
Elders doesn't seem to be ordering in a consistently logical order or reordering when they should be. Removing elder points as you progress through them is likely to result in an error. Your best bet is to only have a few active at a time.
- Uploaded on
- Feb 13, 2011
- Game version
- 5.7 MiB