Honorbuddy v2.5.7496.650

As a RL bizsoft-programmer I can tell yo, it's NEVER EVER a good choice to build up new features on old bugs.
Errors increase exponentially with each new release until a point, where you lose track of the whole construct.
That's not only needlessly complicating your own job, but also annoying your customers.

Do we really need new features?

As for me, I'd rather see the Team to stop implementing new features for a while and take a few weeks to eradicate the old bugs.
We will surely survive that with a much better bot in mind, instead of permanently fumbling around with old/new bugs and errors.

The Team does indeed a great job, but please do yourself a favor and also listen to your customers.

 

I can only agree with taking out bugs being to priority above all new features. It seems like the quest bot is really off track here by the look of the posts. I am getting the impression that it's not at all the skill that is missing from the team, but testing is. I can also understand the annoying bit with getting flamed while working your ass off! But working you ass off is not always the best approach. Working with the most important parts and squashing the really annoying bugs are!

Do you have anyone working as the test lead? Using bugzilla or whatever tool to just keep track is great. The test lead should be responsible for adding bugs. Interpreting and asking for more information. Removing duplicates and closing bugs when people/testers report them fixed.

For questing these are the major issues I have found looking at the posts just briefly.
1. Handin in quests. Works/doesn't work etc.
2. Some quest mobs are not being targetted (yellow mobs, special mobs etc.)
3. Some quests just get completely stuck.

There are several boundary conditions that are not being really tested eg. Dying while on the quest may just fail the quest, the bot just doesn't know how to resume. I have seen many problems with the quests that needs to summon lorewalker cho when you have died doing them. Also getting into the building where you need to use the little companion.

Keep up the good work!

 

Same thing. Stuck at loading tiles forever. Did a clean install, deleted mesh folder. Still just sits there doing a whole lot of nothing.

 

To me personally the biggest issue is pathing - stuck at almost every fence (especially those wooden with sharpened tips), it looks very bad. People report you and account is gone or at least flagged.

I stopped allowing HB to take/deliver quests in hubs or walk in the cities - I rather stop HB, take/deliver Q's and resume HB outside of city/hub. Otherwise its like screaming "I'm bot! I dare Blizzard to ban me!" I had terrible experience with HB being stuck on some fence or doorway and convulsing while 50 players were nearby...

 

All the while Raphus works on native flying that we've lived without for years...
Devs need to get their priorities straight.

Honestly, at this point I think they just want more "features" to advertise the bot with. It doesn't matter if those work or not (like questing) as long as they can be put in a list on the website.

 

Agreed, fix whats broken, we don't need anything else for now. Can't be too hard to figure out the questing bug as it worked perfect once before.

Pathing is terrible (and to be truthful always has), any tower you climb you get stuck for example. I am not sure why my character doesn't run up the middle of staircases or in the middle of paths, always cutting corners and getting stuck everywhere, eliminating this close shave shortest path behavior would probably eliminate 90% of the stucks.

G

 

use the new beta the 27 version seems to be pretty smooth im testing it with a few accounts questing.

 

When i try to install this one i getting this error

[0A68:1B48][2013-08-16T10:08:52]i001: Burn v3.7.1224.0, Windows v6.1 (Build 7601: Service Pack 1), path: C:\Users\johan de jong\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\AA63SBLU\Honorbuddy Installer v2.5.7496.650 (1).exe, cmdline: ''
[0A68:1B48][2013-08-16T10:08:52]i000: Initializing string variable 'InstallFolder' to value '[PersonalFolder]Honorbuddy'
[0A68:1B48][2013-08-16T10:08:52]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\JOHAND~1\AppData\Local\Temp\Honorbuddy_20130816100852.log'
[0A68:1B48][2013-08-16T10:08:52]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\xxx\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\AA63SBLU\Honorbuddy Installer v2.5.7496.650 (1).exe'
[0A68:1B48][2013-08-16T10:08:52]i000: Setting string variable 'WixBundleName' to value 'Honorbuddy'
[0A68:1B48][2013-08-16T10:08:52]i100: Detect begin, 3 packages
[0A68:1B48][2013-08-16T10:08:52]i000: Setting version variable 'MFC100_Version_x86' to value '10.0.40219.325'
[0A68:1B48][2013-08-16T10:08:52]i000: Setting string variable 'NETFRAMEWORK40' to value '1'
[0A68:1B48][2013-08-16T10:08:52]i102: Detected related bundle: {1752ebf7-7805-4846-bab3-2c57f650fc37}, type: Upgrade, scope: PerUser, version: 2.5.7248.625, operation: MajorUpgrade
[0A68:1B48][2013-08-16T10:08:52]i052: Condition 'NETFRAMEWORK40' evaluates to true.
[0A68:1B48][2013-08-16T10:08:52]i103: Detected related package: {6D8FB164-2A7D-43B2-A59E-E16BF568ACB0}, scope: PerUser, version: 2.5.7248.625, language: 1033 operation: MinorUpdate
[0A68:1B48][2013-08-16T10:08:52]i101: Detected package: NetFx40Web, state: Present, cached: None
[0A68:1B48][2013-08-16T10:08:52]i101: Detected package: vcredist_x86, state: Absent, cached: None
[0A68:1B48][2013-08-16T10:08:52]i101: Detected package: Honorbuddy, state: Present, cached: None
[0A68:1B48][2013-08-16T10:08:52]i199: Detect complete, result: 0x0
[0A68:1478][2013-08-16T10:09:04]i000: Setting string variable 'InstallFolder' to value 'C:\Users\xxx\Desktop\honorbuddy Beta'
[0A68:1B48][2013-08-16T10:09:05]i200: Plan begin, 3 packages, action: Install
[0A68:1B48][2013-08-16T10:09:05]w321: Skipping dependency registration on package with no dependency providers: NetFx40Web
[0A68:1B48][2013-08-16T10:09:05]i052: Condition '(NOT MFC100_Version_x86 >= v10.0.40219.1) OR NOT MFC100_Version_x86' evaluates to false.
[0A68:1B48][2013-08-16T10:09:05]w321: Skipping dependency registration on package with no dependency providers: vcredist_x86
[0A68:1B48][2013-08-16T10:09:05]i000: Setting string variable 'WixBundleLog_Honorbuddy' to value 'C:\Users\JOHAND~1\AppData\Local\Temp\Honorbuddy_20130816100852_0_Honorbuddy.log'
[0A68:1B48][2013-08-16T10:09:05]i201: Planned package: NetFx40Web, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[0A68:1B48][2013-08-16T10:09:05]i201: Planned package: vcredist_x86, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[0A68:1B48][2013-08-16T10:09:05]i201: Planned package: Honorbuddy, state: Present, default requested: Present, ba requested: Present, execute: MinorUpgrade, rollback: None, cache: Yes, uncache: No, dependency: Register
[0A68:1B48][2013-08-16T10:09:05]i207: Planned related bundle: {1752ebf7-7805-4846-bab3-2c57f650fc37}, type: Upgrade, default requested: Absent, ba requested: Absent, execute: Uninstall, rollback: Install, dependency: None
[0A68:1B48][2013-08-16T10:09:05]i299: Plan complete, result: 0x0
[0A68:1B48][2013-08-16T10:09:05]i300: Apply begin
[0A68:1B48][2013-08-16T10:09:05]i000: Caching bundle from: 'C:\Users\JOHAND~1\AppData\Local\Temp\{69519df4-3d85-4b10-b09a-a1a7a64ab470}\.be\Honorbuddy Installer v2.5.7496.650.exe' to: 'C:\Users\xxx\AppData\Local\Package Cache\{69519df4-3d85-4b10-b09a-a1a7a64ab470}\Honorbuddy Installer v2.5.7496.650.exe'
[0A68:1B48][2013-08-16T10:09:05]i320: Registering bundle dependency provider: {69519df4-3d85-4b10-b09a-a1a7a64ab470}, version: 2.5.7496.650
[0A68:15DC][2013-08-16T10:09:05]i305: Verified acquired payload: Honorbuddy at path: C:\Users\xxx\AppData\Local\Package Cache\.unverified\Honorbuddy, moving to: C:\Users\xxx\AppData\Local\Package Cache\{6D8FB164-2A7D-43B2-A59E-E16BF568ACB0}v2.5.7496.650\Honorbuddy.msi.
[0A68:1B48][2013-08-16T10:09:05]i323: Registering package dependency provider: {6D8FB164-2A7D-43B2-A59E-E16BF568ACB0}, version: 2.5.7496.650, package: Honorbuddy
[0A68:1B48][2013-08-16T10:09:05]i301: Applying execute package: Honorbuddy, action: MinorUpgrade, path: C:\Users\xxx\AppData\Local\Package Cache\{6D8FB164-2A7D-43B2-A59E-E16BF568ACB0}v2.5.7496.650\Honorbuddy.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" INSTALLLOCATION="C:\Users\xxx\Desktop\honorbuddy Beta"'
[0A68:1B48][2013-08-16T10:09:05]e000: Error 0x80070659: Failed to perform minor upgrade of MSI package.
[0A68:1B48][2013-08-16T10:09:05]e000: Error 0x80070659: Failed to configure per-user MSI package.
[0A68:1B48][2013-08-16T10:09:05]i319: Applied execute package: Honorbuddy, result: 0x80070659, restart: None
[0A68:1B48][2013-08-16T10:09:05]e000: Error 0x80070659: Failed to execute MSI package.
[0A68:1B48][2013-08-16T10:09:05]i329: Removed package dependency provider: {6D8FB164-2A7D-43B2-A59E-E16BF568ACB0}, package: Honorbuddy
[0A68:1B48][2013-08-16T10:09:05]i351: Removing cached package: Honorbuddy, from path: C:\Users\xxx\AppData\Local\Package Cache\{6D8FB164-2A7D-43B2-A59E-E16BF568ACB0}v2.5.7496.650\
[0A68:1B48][2013-08-16T10:09:05]i330: Removed bundle dependency provider: {69519df4-3d85-4b10-b09a-a1a7a64ab470}
[0A68:1B48][2013-08-16T10:09:05]i352: Removing cached bundle: {69519df4-3d85-4b10-b09a-a1a7a64ab470}, from path: C:\Users\xxx\AppData\Local\Package Cache\{69519df4-3d85-4b10-b09a-a1a7a64ab470}\
[0A68:1B48][2013-08-16T10:09:05]i399: Apply complete, result: 0x80070659, restart: None, ba requested restart: No

 

To be fair, I'd love native flying since I'm mostly playing druids, but this shouldnt come at the expense of quality. 3 working features is better than 5 half-working ones.

 

Yeah, this is my point. We can wait a bit longer for native flying (I'd love this as well), but quest bot is kind of a must for the majority of us...

 

The Doodads like campfires, fences etc. have always been an issue. Not sure why since they don't change unless it's a festival like Midsummer or Halloween when they put extra ones in. Which would require extra Blackspots obviously. But after all this time i still don't understand why standard always in the game Doodads don't have blackspot priority when meshing. The getting stuck on corners thing is down to the meshing program deciding that the path *is* the most optimum ways to navigate them. The problem is that where a gnome can go a Tauren can't. Not sure what parameters the Dev team uses but it has been suggested for a few years to use Taurens/Trolls as the litmus test. If they can make it, anyone can. that includes being mounted on the biggest mounts ofc.

Native flying...i am all for it and when Outlands got the option in config i was like "Shit yes!" But that was when the bot was working right. Between then and now the bot doesn't work right I don't think it was the implementation of all over Native flying that broke the bot though. Silly things like not being able to pick up/turn in quests unless you face the QG, which *is* fixed now thank for that , have made the bot less than it was and it took quite some time to fix. Quite some time in relative time as far as programming goes. It only took 2 months or so real time but that's a lifetime in programming.

All i know is this. For the last 5 months or so i cannot trust to leave the bot running Kicks questing profiles while i am work for 12 hours or even when i sleep because of the many small issues the bot has. Not due to Kicks profiles because, and i hate to swell his head even more than it is , they run great....when the bot runs great.

 

I honestly don't know why you're getting so bent out of shape Raphus, it's not like we took a perfectly working and mostly afkable bot, and broke it for months .

I know a little change can create a butterfly effect, but that's why you're supposed to test things before you release them. And when all fails, you roll back changes (like I've seen you do not too long ago).

 

If I remeber correctly, like a year ago the team said that since many bugs were present they would do extra testing before releasing to avoid bugs, I come back after a year... Well i can say that now most features that made it great are broken.

As for the fences and laterns and such, yes this has been a issue from day one which has not been removed as of today.

Don't see why they don't use the road more often or want to hug ledges and fall off because the bot thinks its a short cut. Optimal navigation to me is avoid getting stuck and navigate in such a way that questing, bgs etc get quickly from location a to b.

Today I've seen 5 hordes stuck in a tower using kicks profile all on flying mounts humping a wall, you can guess what happends to those accounts right?

Back in the days you started quest bot and came back and be amazed by the speed and lvls you gained,
Now you come back to see: disconnected/banned.

I'm looking forward to next week as raphus has said above, I'll wait and see if the issues are gone.

 

I think if you included all the fixes you've done on a dedicated page, people would think twice before asking (not just the major ones).

It can just be a simple text only page to save bandwidth and loads fast while providing all the information on changes.

 

http://www.thebuddyforum.com/honorb...mega-profile-packs-1-90-a-25.html#post1244960

CJ told me to post this here. The Logfile i attached there was after a reload! So it does the failure after the reload aswell.

 

Setting the bar high there, be ready for a shedload of complaints if there is anything wrong, good luck with a new release.
5.4 will drop 20th or 27th, so something will need tweaking again for sure to make HB work with WoW again, please don't break anything while fixing it.

G

 

yes, the pathing has always been horrible, and never an attempt made to fix it. I am currently leveling several characters and everytime one gets stuck or runs into a wall I think to my self, that happened on the last character I leveled this way, wonder why it isn't fixed.

I have to watch my questbot now, turn it off when I go for a leak, thats how horrible it is now, lets hope things go back to the way they were.

G

 

The method of taking the shortest route has always confused me, the time saved doesn't get made up for with the time stuck. roads, run down the middle, staircases run up the middle, rock pathways run up the middle. Lost count the number of times my bot will try run up a pathway and is literally a pixel out and will continue to run and run and run when there is 2yd's of perfectly good path it could of run up in the first place.

Flying in outland and upto mop, I have it, my gryphon shouldn't get mounted and run along the ground it should FLY ALL OF THE TIME. As for the interface to pick mounts please strip it back to basics, far too many options that get you in trouble. It just needs a land/air/underwater/onwater box to type the names into, hide all the other stuff, just makes end users frustrated.

G

 

There's a reason there's a public thread to post navigational issues. If you're running into a wall across different characters it's most likely an issue that should be addressed. Reporting it so it can get fixed would be a start, I don't have time to sit and complain about the issues across the 17 zones I'm currently testing, so I just drop the nav error or hotspot where it's at in the thread and let it eventually get dealt with. These things can be remeshed, especially areas with lots of new gameobjects. They can be dumped and used to make the mesh better.

I'm not going to say it's amazing the way it is especially in tight areas, but I'm 98% sure a developer made a much better response to this exact thing, but I'm pretty sure there's a margin of acceptance that can only be tweaked so far. If they ever decide to let the bot know what the "middle" of a staircase is, you can go around and do all of them. The navigable space is just space to the bot and you'd have to re-do the meshing system.

If you don't want your gryphon to run on the ground, manually type in a better mount. Also not too sure how removing the mounting options will help anything. The hazardous native flying setting was removed and was probably the only thing that can really cause frustration. If you want to type in the mounts, type them in, personally I think the automatic setting should shut off once mounts are typed in, but the random setting is an obvious giveaway that it can alter your mounts. The bot barely navigates on water, you'd have better luck making a plugin for a waterwalking mount, which is why I will not envy whoever decides to walk into Vash'jir.

A stepping stone to native flying was just made above, which you guys were griping so hard about. Just open up the deepholm profile and feel the pain of how hard navigation is sometimes, let alone flying. If they told the bot to simply fly all of the time now, you'd be complaining tenfold with how stuck it would get.