vanilla-wow-addons – Blame information for rev 1

Subversion Repositories:
Rev:
Rev Author Line No. Line
1 office 1 ---------------------------------------------------------------------
2 # v3.7.0
3  
4 Features:
5 * Quest items contained in objects now display more accurate tooltip
6 information.
7 * Changed logic for available quests to follow blizzard's available
8 quest icon logic.
9 * Min-level filter uses recommended level, Max-level filter uses
10 required level. Default to 4 and 7 respectively.
11 * Added silver exclamation mark icon for quests with a minimum level
12 above the player's level.
13 * Added ability to zoom in and out of map even when clicking icons.
14 * Added ability to click any questie icon on the map to add an arrow
15 pointing to it.
16 * Added basic rounding "clustering" for objectives on the world map.
17 * Updated game, minimap icon and worldmap icon tooltips to show more
18 information.
19 * Made Questie compatible with Shagu Quest Chat Hyperlinks – Questie
20 users can send and view Chat Hyperlinks sent by either add-on but
21 Questie users will always see the details of the clicked quest even if
22 they aren't on that quest. Shagu users who click on Chat Hyperlinks
23 sent by Questie users will see quest details based on its own
24 implementation. (If a user is on the quest they will see the full
25 details of that quest or a message saying they aren't on the quest).
26 * Added WIM support for Chat Hyperlinks and Quest Progress features.
27 * QuestieTracker can now be "locked" in any of the four corners of a
28 player’s screen and resize according to the trackerList direction.
29 * Improved the Default Blizzard Questlog while being used with
30 Questie. You are no longer limited to tracking 5 quests and you can
31 track anything you'd like. We've also tied the "Auto Track Quest"
32 setting in the Blizzard Options panel to a "real" auto tracking
33 enabled setting. When enabled new quests will appear automatically in
34 the Quest Tracker.
35  
36 Data updates:
37 * Added startedBy for The Collector
38 * Fixed data for Zapped Giants quest.
39 * Updated data for Raene's Cleansing quest chain.
40 * Fixed position of syndicate documents.
41 * Fixed Henrig Lonebrow's Journal.
42 * Fixed Guarding Secrets quest available.
43 * Tweaked positions of a couple of mobs in Stockades so that
44 objectives properly stack on the icon outside the instance.
45 * Fixed drops and related locations of Red Wool Bandanas.
46 * Improved data for a bunch of quests in Elwynn Forest
47 * Fixed Westbrook Garrison Needs Help quest requirement.
48 * Fixed locations of Captain Sander's Treasure Map.
49 * Removed Darkspear Defense.
50 * Fixed quest started by Head of Nefarian.
51 * Fixed position of Nefarian.
52 * Added Beached Sea Creature/Turtle objects for quests available.
53 * Fixed "Allegiance to the Old Gods" available quest icon.
54 * Added Started by: tooltip line for quests that start from item
55 drops.
56 * Added Wanted Murkdeep object.
57 * Fixed Faction of "Grim Message" and "Theldurin the Lost".
58  
59 Misc:
60 * Fixed invalid locations such as Outland showing up.
61 * Fixed quest difficulty color for tagged quests.
62 * Fixed issues that would cause the player to abandon a quest other
63 than what they selected.
64 * Removed the ability to shift-click an objective map node.
65 * Stopped invalid locations showing up.
66 * Fixed frame level issues with completed quest markers.
67 * When multiple quests are available, moved the "Manually complete"
68 tip to the bottom of the tooltip.
69 * Fixed an issue with Questie users sharing quests.
70 * Fixed numerous issues with adding, removing, updating quest markers
71 and some of the hide/show user options.
72 * Fixed a stack overflow issue with quest abandonment.
73 * Fixed and improved the Questie Events system. All functions related
74 to Quest/Objective pickups, updates, and completions have been fixed
75 and are now firing in the proper order. All redundant checks have been
76 removed and overall memory foot print has improved.
77 * Due to the new events system, We've been able to remove some of the
78 required ReloadUI when changing certain options.
79 * Cleaned up the Help Menu and added a "feature" tag to each option to
80 help identify which component of Questie it's actually changing.
81 * More memory improvements for the QuestArrow - instead of updating
82 based on a player’s frame rate (60FPS = 60 arrow updates per second!)
83 We've throttled it down to one update every .04 seconds.
84 ---------------------------------------------------------------------
85 # v3.69
86  
87 [Hotfix]
88 * The auto resize code was adding extra height to the QuestTracker
89 when adding more than one quest at the same time or at odd times.
90 Added a new refresh kicker to force it back into the correct width.
91 * The hidden place holder button for the Minimize Tracker feature was
92 still present while the QuestieTracker header was disabled. You could
93 still minimize the tracker by accident. Added a check to only enabled
94 the hidden place holder button when the header is enabled.
95 * Aero and I added a check for level one characters that was causing
96 some confusion. This check was intended to resolve a potential issue
97 with players wanting to recycle an old character name they had
98 previously deleted. A level one character with a level 30ish data base
99 filled with completed quests could lead to some frustration. This has
100 been corrected. If you're level one and have more than 3 quests in
101 your DB, it will execute the check. Most level one characters get to
102 level two during or shortly after completing their first quest. Once
103 you get to level 2, you'll never see this check.
104 * Fixed an issue with "faded tooltips". When visiting a vendor to sell
105 off items, occasionally you'd notice that your Money Tool Tip
106 containing the items sell value was "ghosted". This was caused from a
107 Tooltip being set in too low of a FrameStrata. A reset was added a
108 long time ago to fix this but apparently, it wasn't working in certain
109 edge cases. Changed the reset to a higher FrameLevel and I'm not able
110 to reproduce this issue anymore.
111 ---------------------------------------------------------------------
112 * I found a small bug with the QuestieTrackedQuests functions. Some of
113 the DB entries were being left behind. Added an additional logic check
114 to make sure both DB's stay clean and trim.
115 * More performance tweaks! I think I tracked down two of the biggest
116 performance offenders and throttled them to make sure they only fire
117 when absolutely needed. Tons of other functions were traced and
118 duplicate, unnecessary calls to the same functions have been removed
119 or significantly reduced in frequency. I'm hoping the performance nuts
120 will be impressed.
121 * With the performance tweaks came an idea on how to re-implement an
122 old feature that everyone seemed to love. As you know I re-added the
123 QuestieTracker background and gave you all the ability to adjust is
124 transparency level. It came back with the "fixed width". Now this
125 width is dynamically adjusted based on the widest quest that is being
126 tracked. The update is tied into QuestLog updates so it only fires
127 when it's absolutely needed. So, memory impact is extremely low.
128 * A few minor bug fixes here and there. I discovered a few nil errors
129 after moving some of the functions around. Mostly triggered by a fresh
130 character or a fresh install of Questie. Hopefully I got them all.
131 Please report any bugs you find. My evening test run was cut short by
132 the server maintenance. I didn't want to wait until tomorrow to push
133 out this release.
134 ---------------------------------------------------------------------
135 # v3.68
136  
137 * Fixed an issue with CorpseArrow. Thank you for the help Muehe!
138 Occasionally your CorpseArrow would not show correct distance or
139 direction after dying in an instance and appearing at a grave yard.
140 * Fixed an issue with CorpseArrow not being hidden correctly in
141 BattleGrounds. I missed a logic check that in some cases would cause
142 the arrow to appear.
143 * The QuestTracker now has a "Minimize" feature. You can either use
144 the slash command ( /questie mintracker ) **OR** you can click on the
145 "QuestLog Status..." header I.E. 'QuestieTracker Header' AKA: the (
146 /questie header ) slash toggle to Minimize or Maximize the Tracker.
147 This ONLY works when the optional QuestieTracker Header is enabled.
148 * While questing on some of my toons I still noticed some stale
149 entries in both QuestieTrackedQuests and QuestieSeenQuests DB's. I
150 spent some time going back through the Quest pick up and finisher
151 functions and made some tweaks that I'm hoping will keep things
152 trimmed and organized.
153 ---------------------------------------------------------------------
154 # v3.67
155  
156 * Fixed the following quests:
157 - Syndicate Documents
158 - Strange Fruited Plant
159 - Tooga's Quest
160 - Suspicious Hoofprints
161 - The Black Shield
162 - Lieutenant Paval Reethe
163 - WANTED: Andre Firebeard
164 - WANTED: Caliph Scorpidsting
165 - Caught!
166 - Jonespyre's Request
167 - Jonespyre's Request
168 - Caught!
169 - It's a Secret to Everybody
170 - The Missing Shipment
171  
172 * Added a check to NUKE Questie user settings if a user deletes a
173 character and uses the same name for a new character to avoid issues
174 with Quests being displayed.
175 * Added a BG check: If a player is in a BG then CorpseArrow won't
176 appear
177 * You can now toggle the Corpse Arrow on and off. Use ( /questie
178 corpsearrow )
179 ---------------------------------------------------------------------
180 # v3.66
181  
182 * Merged a user suggested change to tooltip hooking that seems to work
183 better after some testing. Thank you rasberryrabbit!
184 * Fixed an issue with quests disappearing from the QuestTracker upon
185 entering a dungeon. In Vanilla WoW, there is no way to get player
186 coordinates and thus Questie can't run it's checks without knowing
187 where Quest Objectives are located so they are automatically removed.
188 While in an instance coordinates returned are always 0,0 so I re-added
189 a check that was inadvertently removed when I rewrote some of
190 Astrolabes functions. Sorry about that guys. Thank you for reporting
191 it!
192 * I submitted some Quest Database fixes for several Quests obtained
193 via wanted posters and fixed a quest that a couple users reported.
194 This Hotfix contains last night’s commit and a fix for another one
195 that I found today.
196 ---------------------------------------------------------------------
197 # v3.65
198  
199 * Added a new feature that allows you to turn off the Questie tool
200 tips. Use ( /questie tooltips ) to toggle them on and off. They are on
201 by default.
202 * Fixed some issues with tool tips causing all kinds of weird issues,
203 everything from duplicate tool tips to nil errors.
204 * Fixed the minlevel and maxlevel functions. One of the new variables
205 wasn't set correctly when the new Required Level field was added to
206 the quest database. These filters are now keyed off of the Required
207 Level instead of Quest Level so don't be surprised if you see a level
208 60 quest appearing on your map. Chances are it's one of those quests
209 that can be done at level 5. Like some of the holiday quests.
210 * I've also added a new line to the Questie MapNotes tooltips. In
211 addition to [QuestLevel][QuestTitle] followed by [QuestStarter} etc.
212 I've inserted [Min Level] info, or what was once referred to as
213 Suggested Level in Vanilla. By default, the minlevel filters hides
214 quests 3 levels BELOW your current level based on the Minimum Level of
215 the Quest. For example, if a quests Level is 40 and its Min Level is
216 35 and your character’s level is 39 then this quest will be hidden if
217 minlevel is on. You can change the number of levels it filters higher
218 or lower. Default is 3. Same example, with maxlevel this quest WON'T
219 show until your character reaches a level of 30. Default maxlevel
220 filter is 5 which means quests won't show until you are within 5
221 levels of the quests Min Level.
222 ---------------------------------------------------------------------
223 # v3.64
224  
225 * If you were actively tracking a quest on the QuestArrow then died,
226 the CorpseArrow wouldn't always appear and display the distance and
227 direction to your corpse.
228 ---------------------------------------------------------------------
229 # v3.63
230  
231 * I introduced a bug where I was clearing the QuestieArrow whenever
232 the player was NOT a Ghost causing the QuestieArrow to never appear
233 for Quest Objectives. Clearing the QuestieArrow is now an event based
234 clear after you resurrect. Sorry guys!
235 ---------------------------------------------------------------------
236 # v3.62
237  
238 * I think I may have traced the issue. In Vanilla WoW the only way to
239 obtain a player’s true position is via the Worldmap. When you open the
240 map, and start browsing other zones, your Avatars position coordinates
241 change accordingly. Questie relies heavily on Astrolabe to determine
242 players position and distances to quest objectives. This can cause
243 weird issues with the QuestArrow, QuestTracker, and the MapNotes that
244 are drawn on the Minimap and Worldmap. I've added some basic logic
245 code to determine which zone the player is physically in and if the
246 world map is open, all distance calculations are halted under certain
247 circumstances.
248 * The code that draws the map icons has also been streamlined, sped up
249 and tweaked in such a way that they now refresh much quicker and ONLY
250 when absolutely needed. This should solve the "flickering" issue that
251 some users have reported.
252 * Since I was in Astrolabe and updating it anyway, I've added a small
253 feature. This feature not being present has been bugging me for quite
254 a while and when someone mentioned TomTom the other day, it reminded
255 me that it's a feature that I've always wanted. If you die, Questie
256 will paint an arrow to your Corpse automatically. When you resurrect,
257 it'll disappear.
258 ---------------------------------------------------------------------
259 # v3.61
260  
261 * Fixed an issue with the [ Shift+Click ] manual quest complete
262 Dewdrop menu popup appearing off screen when a player’s Worldmap is in
263 "Full Screen" mode.
264 * Re-added the Questie QuestTracker background and added the ability
265 to set its alpha level. This is NOT enabled by default. Pay attention!
266 - Step 1: Enable the back ground by running ( /questie background )
267 – default level is 4. If you're happy with that then you're done. If
268 you want it lighter or darker then proceed to step 2.
269 - Step 2: Run the set alpha command ( /questie backgroundalpha # )
270 Enter a number between 1 and 9. 1 is super light almost non-existent
271 and 9 is the darkest you can go. So, for example: ( /questie
272 backgroundalpha 9 ) Your UI will automatically reload after step 1
273 or when you change the setting in step 2. Can't get around the
274 ReloadUI.
275 * The Questie QuestTracker background is a fixed width. I did not
276 re-enable the code to auto resize the width. It's set to 200px wide
277 which can accommodate some fairly wide quest descriptions and
278 objectives without it looking too ugly.
279 * Minor improvement in completed quest markers not disappearing right
280 away after completing a quest.
281 ---------------------------------------------------------------------
282 # v3.6
283  
284 * Fixed an issue with Tooltips - flickering/refresh rate was sometimes
285 visible while hovering over quest items.
286 * Quest items tool tip info wouldn't show up if the Zone/Section in
287 the QuestLog was collapsed/minimized.
288 * Quest update code has been updated. Some of the previous refresh
289 issues with quests updating drop counts has been fixed.
290 * Added the ability to resize the Quest Tracker. There are now three
291 size options available. Small (default) | Medium | Large. Slash
292 command usage: ( /questie qtscale small *or* medium *or* large ) -
293 upon hitting enter to set the size, a ReloadUI will occur to redraw
294 the QuestTracker.
295 NOTE: This option only works on the Questie QuestTracker, NOT the
296 Default WoW QuestTracker.
297 ---------------------------------------------------------------------
298 # v3.5
299  
300 * Hotfix: Corrected issues with ToolTip mods causing certain ToolTip
301 elements to become stuck in a visible state.
302 * Hotfix: Corrected issues with new ToolTip cache system doubling up
303 on displayed info. Re-enabled new features and fixes that were
304 disabled in the previous (v3.4 --> v3.3) rollback.
305 * Moved "Toggle Questie" button to a proper location (not on top of
306 the zone dropdowns)
307 * Fixed available quest maxlevel filter bug
308 * Fixed "icons not showing until map has been opened" bug
309 * Added an option to hide all objectives and only show available
310 quests ( /questie hideobjectives )
311 * Added an option to hide minimap icons ( /questie hideminimap )
312 ---------------------------------------------------------------------
313 # v3.4
314  
315 * Fixed conflict with tinytip that caused questie to add objective
316 text to tooltips multiple times
317 * Moved "Toggle Questie" button to a proper location (not on top of
318 the zone dropdowns)
319 * Fixed available quest maxlevel filter bug
320 * Fixed "icons not showing until map has been opened" bug
321 * Added an option to hide all objectives and only show available
322 quests ( /questie hideobjectives )
323 * Added an option to hide minimap icons ( /questie hideminimap )
324 ---------------------------------------------------------------------
325 # v3.3
326  
327 * Improved mouseover tooltip performance by using caching (this can be
328 improved more in the future)
329 * Fixed "tooltip only showing once" bug
330 * Fixed version number in-game
331 ---------------------------------------------------------------------
332 # v3.2
333  
334 * Fixes to minimap and world coordinates
335 * EQL3 fixes
336 * Before, quests in the same location would overwrite each other on
337 the map. Now you can see all the available quests.
338  
339 ---------------------------------------------------------------------
340 # v3.1
341  
342 * Hotfix: The previous hotfix was incorrect in the assumption that the
343 updated data was incorrect. The city of Darnassis was spelled
344 incorrectly. Someone reported issues with Ogrimmar today and I found
345 that it too was miss-spelled. I've gone through and checked the reset
346 of the cities to make sure they were all correct. I've also reverted
347 the city of Darnassis dimensions back to the submitted values.
348 * Hotfix: About a month ago, someone submitted more accurate zone size
349 data for Astrolabe. The fix was merged with Questie but unfortunately
350 it broke the city of Darnassus and caused all the Minimap icons to
351 appear over the player arrow indicator on the Minimap. The quest NPC's
352 and objectives were no longer stationary in relation to where they
353 were supposed to be positioned. This also broke the QuestieArrow. The
354 old values were imported from the old Astrolabe file and the issue has
355 been resolved.
356 * All previous hotfixes have been merged with this version.
357 * For those not running EQL3 or some other QuestLog mod. If you prefer
358 the default wow QuestLog and Tracker that's fine but it's very
359 limited. For example, if a quest doesn't have any objectives to
360 "track" then it won't appear in the quest tracker and no Quest Arrow
361 will be available for it. Additionally, quests will not automatically
362 be tracked by the default WoW quest tracker. The way that it works is
363 that if you have the option enabled in the games Interface Options -->
364 "Automatic Quest Tracking" then yes, it will auto track a quest with
365 an objective once you OBTAIN the first item. Then it will appear
366 automatically in the list unless you manually [ Shift+Click ] the
367 quest in the QuestLog but again, only if there is a "trackable"
368 objective. Unlike EQL3 or other QuestLog/QuestTracker mods where
369 pretty much anything is trackable, these quests will appear in the
370 Questie QuestTracker. If the quest appears then map coordinates are
371 cached and this allows the QuestieArrow to hook into the position and
372 give you an arrow.
373 * Tons of nil error checks added which were exposed by the global to
374 local code rewrite. Thank you everyone for reporting them!
375 * All "double" tooltip issues have been fixed. Unless you have EQL3's
376 "Show Relevant Quest in Item Tooltip" and "Show Relevant Quest in Mob
377 Tooltip" options enabled. I've added code in Questie to disable these
378 options automatically but I'm willing to bet someone's mod setup will
379 cause it to not work so please check those options before reporting
380 issues.
381 * Added additional support for EQL3, ShaguQuest, and the default WoW
382 client. They all work with and without the QuestieTracker enabled. You
383 can now choose which tracker you want to use however, there is a small
384 caveat. You can only use the quest tracker that is currently enabled
385 unless that quest tracker is capable of being disabled as well. For
386 example, you can't use Questie's arrow features if you have the
387 tracker disabled. Also, if you're running EQL3 and want to use the
388 default wow tracker you can't. In order to use the default wow tracker
389 with Questie you can't run EQL3 or ShaguQuest because their trackers
390 can't be disabled like Questie's can. Their quest trackers override
391 the wow default quest tracker.
392 * Added ShaguQuest mod support to handle their custom EQL3 version.
393 When I moved Questie from the global to the local space, the EQL3
394 function calls in ShaguQuest quit working. This has been corrected.
395 * After rewriting Questie and moving everything from global to local,
396 I neglected to realize that some of the EQL3 calls were checking for
397 the presence of EQL3 SavedVariable keys and of course were failing.
398 I've since replaced them with Blizzard API calls and it's now
399 detecting the presence of EQL3 correctly again.
400 * Fixed an issue with Worldmap code for users that aren't using a map
401 mod. Added a couple of new nil checks that were popping up for some
402 users who recently installed Questie and don't have any Saved
403 Variables file at all. I thought I had thoroughly checked this code
404 but that was before the global to local conversion and code rewrite.
405 Sorry guys!
406 * Fixed an issue with one of the quest management functions. I had to
407 add some additional nil checks to make sure a quest is actually
408 present in the database before setting the saved variables data keys
409 in the db. If a quest isn't present, then it will now silently ignore
410 the nil error but the quest can't be tracked. Questie's quest database
411 as parsed from a well-known and trusted source based on quest data
412 obtained from the live retail realms in the very early days of BC.
413 Some of the Vanilla quest data might be missing or slightly
414 inaccurate. We're in the process of creating a new database for both
415 the Vanilla and TBC clients of Questie and all sources will be scraped
416 and checked for duplicate entries from both the current database and
417 either the most recent mangos distro or some other well respected
418 project.
419 ---------------------------------------------------------------------
420 # v3.0
421  
422 * Code clean up and finalized code rewrite.
423 * Fixed a tooltip issue where some quest objectives were appearing
424 twice.
425 * Added a version check VAR in players SavedVariables file. If a
426 version check fails it will perform a "QuestieClearConfig"
427 automatically. This should help significantly reduce the number of
428 complaints due to nil errors because certain QuestConfig keys aren't
429 yet present. Blame it on players not reading the release notes!
430 * Added some custom VARS for EQL3 to turn off a couple of features
431 that was conflicting with Questie. For example, the quest objective
432 Tooltips. Having both add-ons showing quest objectives in the tooltips
433 is redundant.
434 ---------------------------------------------------------------------
435 # v2.67
436  
437 * On certain servers EQL3 would inject the quest [%level%] tag into
438 the Quest Title. When a player hands in a quest they get a nil error
439 on servers that block this behavior or if the player is using a
440 version that doesn't add the quest level. Or possibly the player has
441 this feature turned off. This check handles all scenarios.
442 * Muehe has contributed the following changes. Thank you Muehe!
443 * This fixes a small deviation in note display on the continent and
444 world maps due to the old data being for TBC.
445 * Removed offset related hack fix loop.
446 * Disabled the error output when mapData gets zeroed. After the
447 removal of the TBC zones the line was throwing an error instead of
448 posting a chat message.
449 * Continent offsets and worldmap size are still everyone’s best guess
450 but zone data is correct.
451 ---------------------------------------------------------------------
452 # v2.66
453  
454 * I have fully converted Questie to cache all quest data for active
455 quests. This means that Questie will no longer run as many function
456 calls as it used to each time you track and untrack a quest. In order
457 to properly cache quest data, it has to be tracked at least once I.E.
458 appear in the tracker list before untracking it. Once the quest data
459 is cached, it will update its data while you're doing the quest. You
460 can toggle Questie on and off using the Worldmap button to hide all
461 the icons and objectives, hunt for herbs with ease and still continue
462 to track quests on your QuestTracker or you can untrack everything and
463 it will still update its local cache and will be correct when you add
464 it back to your QuestTracker. This should also significantly reduce
465 the memory usage when you have a large number of active quests on the
466 QuestTracker.
467 * Fixed a number of nil errors while trying to turn in quests.
468 * Relocated the Questie Toggle button to a more noticeable location.
469 * Added some more nil error checks to all quest management functions
470 as well as more logic to handle new and existing user databases to
471 help users in upgrade scenarios and to resolve database issues for
472 certain types of quests. I've run into several quests that aren't
473 quite right or contain wrong or missing entries. This can lead to
474 stale cached quest data for long quest chains that use the same name.
475 * I've added a "cleanup" routine each time a user turns in a quest. If
476 a Pre-requisite quest exists, the function responsible for marking the
477 quest as complete in the database will crawl back through all the
478 quests before it and make sure they are also marked as complete.
479 ---------------------------------------------------------------------
480 # v2.65
481  
482 * I have thoroughly reviewed all the functions that handle obtaining,
483 abandoning, and tracking quests. Many of the functions have been
484 tweaked or redesigned. During this long review, I found several new
485 bugs and discovered many new and more efficient ways to manage quests
486 with a lower memory footprint. There were several bugs specific to
487 using Enhanced Questlog that have been resolved. Too many little bugs
488 and tweaks to list. The overall look and feel of Questie hasn't
489 changed nor have I added any new features. All the improvements in
490 this release are "under the hood."
491 * In order to do proper testing I created three new characters in each
492 of the three Alliance starting areas (Dwarf, Human, Elf) and leveled
493 them to level 10. I discovered a few quests that had erroneous entries
494 which were corrected.
495 * During the repeated process of NUKEING my quest database to test
496 certain functions I realized that the [ Shift+CTRL+Click ] to manually
497 complete was annoying as F***. I ran into several quests that just
498 wouldn't disappear. I finally grew tired of it and rewrote the whole
499 feature. You no longer have to rely on selecting a step in a quest
500 chain. Just click it. If it's in your quest log, the cleanup loop will
501 re-add it to your database. If you're on the quest, it won't show you
502 on the map the later quests in the chain so there is no risk of you
503 accidently clicking on a quest that you still need to complete. I've
504 also dropped one of the key modifiers. You only need [ Shift+Click ].
505 Here is the best part... I figured out a way to handle the duplicate
506 quest entries in the database. It will complete it no matter what.
507 Just click the icon until it's gone.
508 * In the process of fixing the manual complete feature, I also changed
509 the tooltips. They are cleaner, easier to read and they all contain
510 just the right amount of information - including the Quest
511 Description! If for some reason, you encounter a quest you need to
512 file a bug about, hold down your ALT key while hovering over a quest
513 or an objective and it will show you the Quest Hash Number that I will
514 need to troubleshoot with.
515 * I also fixed the 'NUKE' command (yes, it's intentionally in all CAPS
516 which you have to type in order to get the command to work). I also
517 improved the 'clearconfig' command. For those that weren't paying
518 attention to a hotfix I recently released, I added a 'cleartracker'
519 command. The 'clearconfig' command will clear your Questie settings
520 and clean up your database without clearing your completed quests. The
521 'cleartracker' command just simply resets the location of your tracker
522 to the center of the screen in case it gets stuck behind some UI
523 element. The NUKE command is what it is... it nukes everything back to
524 default.
525 * I also improved the look of the command menu. Type ( /questie ) in
526 game to check it out! I colored some of the text to make it a LOT
527 easier to read and understand. I hope.
528 * Just a small change to the WorldMap feature I added a few releases
529 back. If you don't run Cartographer, MetaMap or some other map mod
530 then you have a couple of options. First option which is the default,
531 is the Blizzard Fullscreen Worldmap with no customizations done by
532 Questie. There is a new special command only visible to those not
533 running a map mod. It's called 'resizemap' and you can find it in the
534 ( /questie ) command menu. If you run the command it will resize the
535 Worldmap down to 80% and make it movable. For those running a map mod
536 like Cartographer or MetaMap the code doesn't even execute and the (
537 /questie ) command doesn't appear in the list. The CVAR does appear in
538 the ( /questie settings ) menu and should be 'false' unless you're
539 actively using it. As long as it's 'false' then the map code doesn't
540 execute and won't interfere with your map mod.
541 * I also rewrote some of the descriptions for some of the commands in
542 the ( /questie ) menu. Hopefully they are easier to understand.
543 * I added a few new EVENT handlers to enhance the quest updates. There
544 is one minor annoyance I can't seem to resolve. If you have a quest
545 that needs X number of items, it sometimes won't register the first
546 item but will update properly once you pick up the second item.
547 *scratches head* Yeah, I'm still thinking about that one...
548 * Tons of code cleanup
549 ---------------------------------------------------------------------
550 # v2.64
551  
552 * Since there are some new options in the SavedVariables - there
553 needed to be better error checking for missing entries.
554 * Cartographer's settings weren't being applied after a ReloadUI or a
555 Re-Log - Questie was overriding the settings because it was no longer
556 detecting the component. I can only assume that MetaMap users would
557 run into the same issue so I made both Cartographer and MetaMap
558 optional dependencies.
559 * QuestArrow was trying to hook quests that weren't being tracked in
560 the QuestTracker. Added an additional check to make sure it only fires
561 for quests that are being tracked. This is by design.
562 * Fixed an issue with the QuestTracker. In one of the options I forgot
563 to apply the new button (Quest objectives in the list) width settings.
564 Its width was (1) causing some players some issues with dragging the
565 QuestTracker.
566 * I forgot to include some header code in the QuestTracker to allow it
567 to be toggled "on" while using the default color set.
568 * Inserted a "block" function to prevent RuWoW and ruRU from
569 translating quest objectives into Russian. This caused the "Sword"
570 icons from appearing on the Minimap and Worldmaps.
571 * Fixed an issue with QuestTracker re-appearing after a quest update,
572 zone change, obtaining or turning in quests etc. I've reviewed all the
573 areas that triggers update functions in the QuestTracker module.
574 Hopefully I caught them all and added a QuestTracker toggle check.
575 ---------------------------------------------------------------------
576 # v2.63
577  
578 * Added a new command line option - ( /questie NUKE ). This wipes out
579 all your settings and the quest database. USE WITH CAUTION. There is a
580 confirmation popup.
581 * Fixed an issue with the MapMod for users using Cartographer or
582 nothing. Cleaned up the code and added an additional check to cover
583 all of Cartographers sub-modules. Zooming in and out on the Worldmap
584 now works as it should. It opens for the player’s current zone.
585 Full-screen mode in Cartographer no longer error's out.
586 * Tweaked some QuestTracker code in the hopes to resolve some FPS
587 issues that some players have reported. I added another "Table Dump"
588 on the end of a function to keep the tables smaller and not allow the
589 entries to build over time. I also had to remove the QuestTracker back
590 ground. The auto resize feature was nice in theory but too expensive
591 and contributed immensely to the lag that some players reported. I
592 guess I never noticed it on my computer.
593 * Added the ability to Left Mouse Click on an objective and flip on
594 the QuestArrow without having to go through the QuestTracker. If a
595 clicked item is able to be tracked via the QuestArrow, it will appear
596 but it doesn't track distance to the actual object selected. It only
597 tracks whatever the quest is tracking which is usually the closest
598 objective for that quest. If it's not trackable, for example, an
599 available quest, then it will silently fail and the arrow will not
600 appear. This works for items on both the Worldmap or the Minimap. This
601 only works in areas where you can get Map Coordinates. Outdoors only
602 since instances / dungeons, Map Coordinates weren't available until
603 Burning Crusade (WoW 2.0+).
604 * Added the ability to remove the QuestArrow off your screen without
605 having to open your QuestTracker or the Worldmap. Simply Right Mouse
606 Click on the arrow frame and the QuestArrow will disappear.
607 * I'm still working on "Quest Caching" - it's development has been a
608 HUGE headache and it's taking FAR longer than I anticipated. So, I've
609 boxed up the current changes and bug fixes and am releasing this
610 version now so you guys don't have to wait so long for the next
611 release.
612 * I've also done some exhaustive testing with the "hover over this NPC
613 or object and am getting lag or an FPS drop" issue. This is not
614 related to Questie in anyway. Due to the way that Questie WAS auto
615 resizing the QuestTracker, it only exasperated the underlying root
616 cause of the issue. The issue is in the WoW client and has popped up
617 from time to time for the past 15 years. Occasionally Blizzard would
618 implement some new feature that taxes the tooltip system too much and
619 people complain about it. You can check out all the posts over the
620 years. The issue also happens in Diablo. I personally disabled Questie
621 and if you stand some place with tons of people and move your mouse
622 pointer over different people, your FPS will drop. I continued to
623 disable mods one at a time and repeated this process. TinyTip was an
624 even bigger impact than Questie. I used a Dev tool to monitor CPU Time
625 and Memory consumption while profiling/troubleshooting this issue.
626 TitanPanel was the second biggest offender. Questie actually came in
627 3rd. I even went through each video setting and couldn't get the issue
628 to go away entirely. Even with the default interface on a clean
629 install the issue was present. My FPS at one point dropped from 120FPS
630 to 20FPS... with all my mods turned on I got as low as 16FPS.
631 * More code clean-up. I tweaked several iteration loops and slowed
632 them down to lessen the impact of the tooltip issue without
633 compromising function. I believe I was fairly successful in reducing
634 lag. I flew around between several flight points with 20 quests all in
635 the tracker to test distance sorting and overall performance.
636 ---------------------------------------------------------------------
637 # v2.62
638  
639 * The Questie Toggle Button has been returned - added bonus: if you
640 turn off Questie using the Toggle then all Questie related objects
641 will be hidden accept the quest tracker. You'll have to untrack all
642 your quests to make the tracker disappear or use the command line
643 option to disable your tracker. However, the bonus is that Quests that
644 are available will re-appear after the next OnUpdate allowing you to
645 see them whereas previously they might have been covered up by an “?”
646 icon or a quest objective. Don't let this mislead you - Questie is
647 still disabled so don't forget to hit the Toggle button again to turn
648 it back on.
649 * Added a toggle to "always show quest objectives" regardless of
650 tracked status (default) - I.E. quest objectives will always show up
651 on the Minimap (for the current zone only) and Worldmap no matter
652 which zone you're in unless you use the toggle to turn it off. In the
653 'off' state, Questie will only display the quest objective if you're
654 tracking it in the QuestTracker.
655 * Added a toggle to turn on/off the QuestTracker. In the off state,
656 you'll be able to use whatever tracker is enabled. If you're running
657 EQL3 then you'll use its tracker. If you don't have another MOD, then
658 it'll revert to the Blizzard default tracker.
659 * Improved the QuestTracker to auto resize itself based on the number
660 of quests listed as well as it's width. If no quests are being
661 tracked, it's size will shrink to 1x1 pixels and should resolve some
662 reported issues where players weren't able to click on objects located
663 around or near where the tracker was previously placed. The old size
664 was 200x200 pixels so it's understandable that players were having
665 some issues.
666 * I also added a header that will show you your QuestLog status. I.E.
667 how many quests you have in your log out of the max number you can
668 have (20). This option is disabled by default and can be enabled via
669 the command line using ( /questie trackerheader ).
670 * Added a 'Clear Config' option to the ( /Questie ) menu - this will
671 clear ALL settings for the currently logged in character. This will
672 NOT reset your Quest Database but it will clean up stale entries. The
673 purpose of this is to help users resolve issues upon upgrading to a
674 newer version of Questie.
675 NOTE: This will automatically reload your UI. This should also help
676 resolve issues with the QuestTracker in case you somehow move it
677 somewhere off screen.
678 * I've fixed the Worldmap for users that aren't using Cartographer or
679 Metamap. It's been scaled down from 100% to 80% and I've fixed the Esc
680 button issue. The WoW client has a built-in feature that if no key is
681 bound to the System/Game Menu then you can still close the Worldmap
682 with your Esc key. I've added this bit of code into Questie even if
683 you're using Metamap or Chartographer. This should resolve issues for
684 players that have reported not being able to close the Worldmap with
685 their Esc key no matter what Map mod you're running or no matter what
686 you have your Key binds set to.
687 * Fixed a bug with the Manual Complete functions. If you manually
688 complete a Quest with more than one step using either the command line
689 or by map click, then it will flag ALL quests in that Chain as
690 complete even if you have one of the steps in your Quest log. This can
691 cause the quest to be permanently tracked until it's completed and
692 leave entries in the database that aren't needed. This bug has been
693 present since before I started making changes and wasn't noticed until
694 now. *ducks* Sorry! This might be contributing to some reported issues
695 players have been having with quests not properly being flagged or
696 showing up or disappearing after accepting a quest.
697 * Discovered a memory leak that caused some in game 'stutter' when
698 tracking quests in the QuestTracker. Turns out that the new code I
699 added to resize the QuestTracker was the cause. Too many senseless
700 iterations over custom tables due to Questies inefficient way of
701 building the Tracker buttons that go into the QuestTracker list. I've
702 streamlined the code and added some cleanup routines to keep the
703 tables MUCH smaller. I left it running with 20 quests tracked for over
704 an hour with no stuttering. Previously, if I had half of those tracked
705 and standing still the issue would show up after a few minutes. My
706 test case was overkill but I wanted to make sure the issue was gone!
707 I've also slowed down the build QuestTracker List so it's function
708 runs only once per second rather than at FULL SPEED which has reduced
709 some memory usage.
710 * This next feature was extremely complicated to implement. You can
711 now choose which direction to have your quests listed in the
712 QuestTracker! Top --> Bottom (Default) or Bottom --> Top. It doesn't
713 change the sort order which is by default: closest quest at the top
714 --> to the furthest quest away from your current position. By swapping
715 the grow order it also changes the anchor point. By default, the
716 anchor point is in the upper left hand corner thus your quests are
717 listed Top --> Bottom. If you flip the order then, your anchor point
718 changes to the lower left hand corner thus growing your list Bottom
719 --> Top. I hope that is explained clearly enough. You can access this
720 setting by the command menu ( /questie trackerlist ). When Using this
721 command please pay attention to the messages that popup. It will
722 automatically reload your UI but depending on which direction you're
723 going there is an extra step. This is critical because the anchor
724 points are flipped. Otherwise your QuestTracker will crawl all over
725 the screen.
726 * I have added a new command menu option ( /questie settings ). This
727 will display the current status of all your flags and settings. In
728 case you forget what is toggled or what isn't. It's also helpful for
729 me to know which state you're in when reporting a bug. So please,
730 provide the appropriate setting and Questie version when you're
731 reporting an issue.
732 * I've reordered the Questie command menu alphabetically as well as
733 the settings output. Should make it easier to find the command and or
734 the setting you're looking for.
735 * TONS of code clean up!
736 ---------------------------------------------------------------------
737 # v2.61
738  
739 * Found a nil error at the last minute while getting a quest. At first
740 I thought I had forgotten to remove some debug code but it was a line
741 I inserted to keep from flagging event type quests as Complete until
742 after the event was complete such as: "Go to this cave and explore
743 it." I ran into a quest that isn't an event and has no objectives and
744 it was causing a nil error - fixed. Inserted one more check to make
745 sure the table entry exists before going on to check a second entry
746 within the first.
747 ---------------------------------------------------------------------
748 # v2.6
749  
750 * Fixed a bug with the QuestTracker - in certain situations upon
751 getting a new quest, the quest would show up as complete when there
752 were still objectives to accomplish. Untracking and Re-adding the
753 quest to the QuestTracker forced the quest to display properly. This
754 has been fixed and quests are now properly displaying upon accepting a
755 new quest.
756 * Fixed a bug with quests that were previously abandoned. If obtained
757 again and if they are untracked from the QuestTracker, the NPC would
758 show an available quest even though it's already been accepted and in
759 your QuestLog. This was also flagging new quests improperly causing
760 some really strange behavior with quest objectives.
761 * I apologize for all the recent fixes and bugs. This project has code
762 all over the place and some of it is necessary and some of it is
763 spider webbed throughout various features. While most of it is
764 redundant in nature, it's been causing some headaches tracking down
765 root causes and implementing new features. Seems when I fix one issue,
766 another crops up someplace else. I spent most of the day unraveling
767 how quests are added to the QuestTracker database, how they are
768 assigned flags and how they are handled when certain events occur. I
769 believe I've reached a point where I have almost every situation
770 accounted for and properly handled. This code review uncovered a small
771 bug with the data base. When a quest is completed the old code left
772 behind a disabled database entry in the QuestieTrackedQuests array.
773 Over time when a player levels, completes quests, and if the database
774 has never been cleared then eventually their SavedVariables would be
775 unnecessarily bloated with useless data. I've built in a routine to
776 clean this entry as quests are completed.
777 * More code clean-up work.
778 ---------------------------------------------------------------------
779 # v2.5
780  
781 * Moved all Questie settings to a "per-character" setup so each
782 character will have their own settings. This was necessary since most
783 of the new options are more or less a Per-Character preference rather
784 than a global one. This also allows Questie to hook and save
785 QuestTracker data between characters and sessions. This also reduces
786 installation/reinstallation issues since you'll only have to clear
787 character saved data rather than remembering to clear both character
788 and global data.
789 * Fixed a crashing issue while dragging the QuestTracker with new
790 installs, reinstalls and new characters. Upon first login, there is no
791 SavedVariables file. I've inserted a temporary config that will be
792 loaded into memory to hold all the initial settings so Questie will
793 have someplace to store the screen coordinates when a user moves the
794 QuestTracker to their preferred position. Once you have logged out or
795 reload your UI these settings and your Saved Variables file is created
796 in your characters SavedVariables folder. This should also resolve
797 some issues with folks not able to move the QuestTracker. Please
798 remember that you must move your mouse pointer over the QuestTracker
799 before you hold down the [ Ctrl+Shift ] keys, then push and hold down
800 your left mouse button while you drag the QuestTracker to the desired
801 location on your screen.
802 * Fixed an issue with the Worldmap for those not running Cartographer
803 or Metamap. The Worldmap was assigned a FrameStrata that was too low
804 so some of the Default UI elements were appearing on top of the
805 Worldmap. I've moved the FrameStrata to a higher level and it now
806 appears above all elements. Please let me know if you're still seeing
807 issues in v2.5 and I'll bump it another layer.
808 * Fixed an issue with the QuestTracker disappearing in an instance. I
809 tracked down the root cause in Astrolabe and added an additional map
810 check. Basically, it wasn't finding map coordinates while the map
811 frame was closed. Everything appeared normal as long as the map was
812 open. Well, that's not very practical when running an instance! So, I
813 forced the check to assume it's always in an instance unless it can
814 get a set of coordinates other than 0,0. This bug was exposed while
815 working on a new feature/improvement for Questie - below.
816 * Quests that are untracked from the QuestTracker will also remove the
817 objective notes from the Minimap and Worldmaps! I'm not entirely sure
818 if this was an issue before but at one point while working on this new
819 feature, every available quest your character could get appeared on
820 the Minimap. Unless, you're in the zone it won't show on your Minimap
821 anymore. This is also true for objectives. However, available quests
822 and objectives will continue to show on your Worldmap no matter which
823 zone you’re in. This should help reduce the clutter in the Minimap
824 that was driving me nuts!
825 * Last but not least... COLORS! Yes, there is a new set of
826 QuestTracker colors you can choose from. Use ( /questie boldcolor ) to
827 flip the color scheme. The idea was requested by a user on GitHub.
828 They wanted to make the QuestTracker resemble MonkeyQuest's color
829 scheme. Well now it does. Quest levels are based on your level - as
830 always and quest titles are now White. Objectives begin Red then fade
831 to Yellow then finally to Green. The QuestArrow has also been changed
832 to match. By default, the old color scheme is enabled.
833 * More code clean-up.
834 ---------------------------------------------------------------------
835 # v2.4
836  
837 * Added an "Elite" tag to the QuestTracker - Elite quests will now
838 properly carry the [+] along with the quest level tag.
839 * Added a minlevel/maxlevel filter along with an on/off toggle. These
840 toggles/filters are independent of each other. Either one can be
841 enabled or disabled in any combination.
842 - ( /questie minlevel ) - toggles the filter on or off
843 - ( /questie maxlevel ) - toggles the filter on or off
844 - ( /questie setminlevel ) <%number%> - accepts a number argument
845 this will filter/notshow quests <x> levels BELOW your current level.
846 - Default=6
847 - ( /questie setmaxlevel ) <%number%> - accepts a number argument
848 this will filter/notshow quests until <x> levels ABOVE your current
849 level. - Default=3
850  
851 * Modified the QuestTracker/QuestArrow dragging Key Modifiers from [
852 Shift+Click ] to [ CTRL+Shift+Click ] - there are too many key combos
853 in WoW that use the [ Shift ] key so I thought it safer to include an
854 additional key combo. Might resolve a crashing issue someone reported.
855 * I fixed the abandon quest bug where the icon was not showing back up
856 on the world/minimaps.
857 * Due to the number of improvements that Questie has undergone these
858 past several weeks, the Toggle Questie button on the Worldmap is no
859 longer needed. If you need to toggle the icons use ( /questie mapaids
860 ).
861 * Code clean up
862 ---------------------------------------------------------------------
863 # v2.3
864  
865 * Added a [ Shift ] key modifier to the QuestTracker and QuestArrow –
866 unless the [ Shift ] key is down, you can't drag it.
867 * Wardz's commit fixing/preventing the QuestTracker from being dragged
868 off screen was also applied to the QuestArrow.
869 * Added Enable/Disable toggles for
870 - Worldmap/Minimap icons ( /questie mapaids )
871 - QuestArrow ( /questie arrow )
872 * Added Bronze Feather to the Winfury Matriarch drop table for the
873 quest Preparation for Ceremony reported by PierrickGT.
874 * Added a small Worldmap modifier for those not running a Map-mod like
875 Cartographer or MetaMap. This allows the user to see the chat output
876 and allows the Popup dialog to appear so they can select a quest step
877 to manually complete.
878 * I discovered a typo in the code pertaining to EQL3. This fix now
879 allows the user to untrack a quest from their QuestTracker with or
880 without EQL3.
881 ---------------------------------------------------------------------
882 # v2.2
883  
884 * A bug was reported on the Nostalrius forums - there was some frame
885 code that was creating double popups preventing new ones from
886 appearing properly. Fixed.
887 * During my debug, I found another bug in the "refresh code" that
888 caused Questie to disable itself in certain situations. Fixed.
889 * I added a 10-sec timeout to the popup dialog in case it doesn't
890 appear on a user’s screen to handle poorly coded evil add-on's that
891 might prevent it from being displayed properly. Grrrrrr.... - A
892 failsafe of sorts.
893 * Updated TOC to reflect new version
894 ---------------------------------------------------------------------
895 # v2.1
896  
897 * Improved the WorldMap Quest tool tips by adding Quest Level, Quest
898 Started by, Quest Finished by and an OnClick usage note for manually
899 finishing quests.
900 * Added an OnClick function to manually finish quests via the WorldMap
901 along with an Auto-Toggle routine that refreshes the map and makes the
902 icon instantly disappear upon manual completion.
903 * For quest chains with more than one step I added a Popup Dialog that
904 accepts user input so they can select which step to complete. Quest
905 chain steps are still reported via the chat window since the popup
906 only accepts two button inputs or an edit box.
907 ---------------------------------------------------------------------
908 eof