3.2 patch quest helper

About time, that single paned quest window was annoying. Now it will just be built-in questhelper memory hog instead. I'm not so sure it's an improvement. Post by wigg1es yea, means no more quest helper memory hog and no more quest guru either. I don't think its going to be as deep as Quest Helper or Carbonite though. Think about all the other stuff QH does; the arrow, prioritizing, ant trails, travel times, movable tracking list, area-wide highlights, etc etc. The 3. I can't see that being a huge memory demand.

Post by wigg1es At some point i read that it was removed, because on some type of quests it showed wrong quest places ie, showing the objective in Westfall while it was actually in, say, Borean Tundra Don't know if it was fixed, but not seeing it in the official release notes doesn't sound good Only tomorrow will have last word Oh damn Caveats: 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. 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, individual locations to visit, burns around 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. There may be bugs. That's why this is a beta.

Report away. It is not going to work right now. The option will not do anything. However, once 3. 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.

Magic will occur shortly. I have no idea how that got through my testing. Correct me if I am wrong! I am not wrong. 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! There are probably missing features that I'm not aware of, and there may be bugs. Please report any issues or unfortunate behavior! May not show up on top of your bags anymore. May still work properly. May not! It is an adventure to all. This one's about numbers! You like numbers, right?

Come play with numbers. 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.

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! 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.

At least, breaking it as much. Why did it used to? I do not know. There are nooks of this code that I still do not fully comprehend. WoW should start a little faster, though QH will take a little longer overall to be "ready". There also may be some little framerate hitches during the early load sequence, I'll deal with those later.

This is a good thing. You were there, right? 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. 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.

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. You should play it. Who can say? It is a mystery! 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. Should no longer hugely drop framerate for about a minute after login. Thanks to all who reported it! It displays the next objective in blue, and any objective you mouseover in red.

There's a lot of changes and some of them might be flaky. Please test it and let me know. Added more debugging info, please report any crashes you get with this version. It's more solid now, at least. Fingers crossed! 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. Group allows you to dump group quests and instances regardless of level. It automatically disables when the player is in a group or raid, and defaults to 2-person groups at most.

Why did it take me this long to come up with that fix? It is a very, very simple fix. Bad all around. 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.

That's pretty neat. The old numbers have basically no relevance to the new system. Lemme know what it feels like. Want some way to easily path between all the bonfires? Now you have one!

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. Along with that, it may update the player location very infrequently. It may take several minutes for it to become good. You'll have to do that manually, with "ignore". Enjoy the Fire Festival! With luck, it won't make Cartographer explode badly. With further luck, if it does, nobody will blame it on me. 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.

It's now a lot more efficient. Probably more. Consider this essentially an entire new UI mod, that merely happens to behave identically to QH 0.

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. 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. 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.

While I don't respond to every message, I do read every one. Thank you. Second: I'm still plugging away at 1. I'm hoping to get a beta release out before WoW 3. 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. Bad news, everyone. Questhelper's dead. 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. 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. 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. I've been painfully busy. You have no idea how busy I've been. That said: 1. 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.

It's close. I promise it's really close. I'm not just slacking here. But it'll be a little longer. This release is merely being done for fun. Hey look! Wasn't that fun! Let me know if it breaks again, I may not notice. I'll work on it for 0. No worries, it'll be in fine shape by the time 3. Please submit your files after you've quested a bit with this version, I can really use them. Should reduce memory requirements substantially, after a period of time in which it uses far more memory than it used to.

May also improve load speed. If it doesn't say that, it doesn't have anything left to compress. Do you use a PowerPC Mac? Get in touch with me! I want you to help me debug this! Get those bug reports in if you're having trouble. Possibly make it worse! At this point I'm mostly just maintaining this version while I do work on another branch. You won't see any new features for a while, but rest assured there's a lot being worked on. I do finally have my error collection code working properly, so I'm going to be patching up the most common bugs to make QH rock-solid.

This change may also screw with people's preferences. Go find that picture of Picard covering his face in frustration, that's the expression I'm making right now.

Maybe not. I don't have access to a raiding group, so I honestly can't tell you if it's fixed. I sort of wildly guessed at the problem, and then wildly guessed at a fix, so. Let me know! Still getting false positives on it?

Tell me! Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors. Analytics Analytics. Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.

This cookie is used to track how many times users see a particular advert which helps in measuring the success of the campaign and calculate the revenue generated by the campaign. These cookies can only be read from the domain that it is set on so it will not track any data while browsing through another sites. This cookie is used as a part of ShareThis service. It counts the number of unique users share the content and the page view acquired by this share. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report.

The cookies store information anonymously and assign a randomly generated number to identify unique visitors. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing.

The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form. Advertisement Advertisement. Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns.

These cookies track visitors across websites and collect information to provide customized ads. The cookie is used for targeting and advertising purposes. The cookie is used to collect information about the usage behavior for targeted advertising.

DSID 1 hour This cookie is setup by doubleclick. This cookie is used by Google to make advertising more engaging to users and are stored under doubleclick. It contains an encrypted unique ID. It is used to create a profile of the user's interest and to show relevant ads on their site. This Cookie is set by DoubleClick which is owned by Google. IDE 1 year 24 days Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website.

This is used to present users with ads that are relevant to them according to the user profile. This cookie registers a unique ID used to identify a visitor on their revisit inorder to serve them targeted ads. This cookie is used for serving the user with relevant content and advertisement. The cookie is used to serve relevant ads to the visitor as well as limit the time the visitor sees an and also measure the effectiveness of the campaign. The purpose of the cookie is to determine if the user's browser supports cookies.

The data includes the number of visits, average duration of the visit on the website, pages visited, etc. Others Others. Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.

The domain of this cookie is related with a company called Bombora in USA. The cookie is used by cdn services like CloudFare to identify individual clients behind a shared IP address and apply security settings on a per-client basis. This cookie is set by Google. The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Advertisement".

This cookie is native to PHP applications. The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. This cookie is set by CloudFare. This cookie is set by Addthis. This cookie is used to recognize the visitor upon re-entry. This cookie is set by the provider Addthis. The cookie is set by Addthis which enables the content of the website to be shared across different networking and social sharing websites.

This cookie tracks anonymous information on how visitors use the website. This cookie is set by Google and stored under the name dounleclick. This cookie is provided by Share This. This cookie is installed by Google Analytics.

This domain of this cookie is owned by agkn. The cookie is set by CasaleMedia. This cookie is set by Casalemedia and is used for targeted advertisement purposes.