Wo. W Add. Ons - . Curse. Forge. Quest. Helper. Change log. Version 0. 5. 0 0. Memory leak should now be fixed. Let's have it for regular updates again! Before, only the most probable location was considered. It's either there or it isn't. The button will be invisible unless the cursor is over the quest tracker, and transparent when the quest tracker is minimized. The tracker will be re- anchored to the button depending on where on the screen it is placed so that when it changes size, it will grow away from the edges of the screen. You can use the builtin quest log, beql, or Double. Wide to manage quest watches. Other addons might also work if they hook Blizzard's original quest watch functions properly. I also tried to make this work properly with Uber. Quest, but your milage may vary. It's probably only temporary and isn't translated. This will probably still work if you're using an English client, otherwise your best best would be to make sure Cartographer is up to date. The initial beta data for World of Warcraft Legion is available! We'll be updating this post frequently with any information we find. Had this issue, Went into WoW folder and changed the settings of the WoW.exe file so that it would run as administrator and I ceased to have any troubles. Hope this helps guys! If your pfSense box is managing a wireless connection (generally through an internal or USB wireless device), you may find configuring and connecting your Chromecast is failing. I recently switched to this type of setup and. If I ever get motivated enough to rewrite Quest. Helper, it will use these values. Cross your fingers and hope this still works. Quest. Helper has a dummy route linking the existing world to it, but this is just to keep it from breaking, you shouldn't try to follow it. The pathing data got calculated before the player's level was set, and thus the route was set to take 2. Quest. Helper from directing low level players from wandering into Out. Lands. It should now be back to reasonably accurate guessing. This mostly applies to non- English users, where Quest. Helper hasn't learned them already. Although it won't show up for times that were guessed from taking a known path and reversing it, I didn't bother checking for that case. If you're already flying, it doesn't apply to the current flight. Will probably be inaccurate until all the data I deleted is recollected. I suspect it caused some people some grief. Now why on Earth might I have done that? Or compounded it further. Should prevent weights in the generated data from getting biased. Reduced the RAM used by static. KB, by removing duplicate tables, and having everything reference the first instance. All that searching also increased the generation time by a few hundred fold, but all well. It's a one time thing for code most people aren't going to run. At least I think I fixed it, can't really test it. I can't fix the problem right now, but I can try to hide the symptoms. All the positions were wrong. This is probably the kind wierdness that happens when you give yourself a deadline. If I actually supported multiple locales, this might have been a useful change. Happened a lot with objective sharing, when a party member joined and then quickly left. You can see your effective level with /qh level. Sure, there's a non- zero chance I removed something important, but that's what you get for complaining about the memory footprint. Can turn filters on or off with /qh filter. It will probably be replaced by some kind of priority system later. Astrolabe would declare you to be in the zone you were looking at. Too many special cases I don't want to deal with. They're now all hardcoded into pathfinding. In most cases, anyway. Now the big problem with them is their size isn't getting calculated correctly. Probably something obvious that I'm too tired to see. I'll customize the images for different objective types later. If an objective wasn't in the route because it was being moved to another position, it would lose its pathing data, and bad stuff would happen. Because somebody is bound to try running it anyway, even with the version mismatch. There seems to be some horrible bug related to recycling them, but I can't figure it out and I'm not going to worry about it for now. You can drag them around by their title or right click on their title to close them. If new nodes were created, pathing would break when it tried to do math on a value that didn't exist. When the player landed, it would think you were still where you took off from, think that was where you flew to, and crash and burn when it discovered that that wasn't one of the possible flight routes you could have taken. Should prevent performance from degrading with lots of objectives. If you don't say what you want, it'll search everything it knows of. Locations can be prefixed with a zone name, to add the location in that zone instead of your current one. All text is compared using Levenshtein distance, so it should be able to handle typos and partial matches. It also makes it slow as hell. At the moment, you can't remove objectives or force them to be first, so this is almost useless. No more telling you to kill the people you talk to, just because they were on your route and killing them is faster than walking to the vendor. Actually, that's a lie, my herustic isn't working properly, so until I fix it, it's technically Dijkstra's algorithm. But the point is, it should be able make more intelligent decisions now. So it might, for example, direct you towards a flight master. Of course, the reverse is equally true. So, cross your fingers. Routing is still using straight line distance between objectives though, as I haven't programmed a proper heuristic for it yet, and I'm worried about performance. Note that for a flight point to get considered in pathing, you need to talk to the flight master there. Naturally, that doesn't include the time required for killing monsters and collecting items, or using mounts, swimming through water, obstacle avoidance, or anything else that'll affect your speed. Incomplete quests were hiding the imported quest data, so Quest. Helper didn't know where to hand them in. Now that it's fixed, it can now tell you where to hand quests in.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |