Honorbuddy v2.5.8113.696

The new changes to the mesh system or the unstuck is better than I thought since now I know exacltly where I'm going to get stuck unlike before where it was random... now I believe 1-90 is more possible but I've yet to see if the meshes have been updated for Storm Peaks and the 70-80 gap that exists atm (I understand why cava stops at 67 ).

All that needs changing is the fact that the bot needs to detect the stucks and then do an unstuck movement, other than that it's good apart from the mesh issues with some quests which have to be overridden with RunTos

 

Dear raphus, dear bossland.

I am from Germany so if there are any grammatical mistakes please forgive me

As you can see I am quite a long time using honorbuddy (since wotlk).
And was always satisfied with your service.

But since several months the quality of your service decreased for me.
This isn't any flame post, more "positive" critic.

I am also posting some logs about my problem later, but maybe you have some minutes to read my post.
For the "normal" user using Gatherbuddy the last releases may work fine, but I can't use the bot at the current state for my matters.

I use Botanist's RAF Profile which was working quit fine some weeks ago. Sorry don't know the exact build number of honorbuddy but it was a rock solid release [before the unstuck change].

At the current state AFK botting (yes you should never bot afk, but if I can't go away for 30 minutes I also can play by hand) isn't possible for me.

I have several problems (Logs later)

Before you changed the unstuck mechanism, unstuck works quite well. Currently each time I take a look on the monitor the bot stucks during his movement phase and I need to rewrite the profile, which was working fine with the old unstuck mechanism.

For example: The Bot (Taure) sometimes doesn't dismount if he can't get through a small door. He stuck at ingame objects (mailbox, or like at the moment brewfest objects which you can find all around the world at the moment).
The old mechanism detected this and navigate around.

And he completely ignores unstuck mechanism during a CTM move command for me.

Next one: Currently the bot doesn't perform some commands for me.

For example:

[13:12:02.095 D] Goal: NoCombatMoving to <-7571.14, -1324.96, 245.538>
[13:12:02.095 D] Activity: Moving To Location - X: -7571.14 Y: -1324.96 Z: 245.538

He is sitting there and doesn't move (no mesh errors, Log later)
Next one:
With custom routines, he doesn't detect his death and is sitting in the release dialog for hours.

Yes I can switch to Singular, but Superbad preforms much better (sorry). So why should I switch to a ?poorer? product only to get the bot working but the char dies more often (tested).
So if there is anything changed, why can't you fix it or send the cc developer some info to adjust their cc.

Im quite unhappy with your feedback. It has improved much, for example during wow patch phases.
But I posted several times about the slow hotspot moving problem [or other problems in the past] (several releases before the current) and beside the default answer from Tony (no flame) (fresh install, without plugins. And I posted in my thread the problem persists also with fresh install, no problems) wasn't any feedback and after long 3-4 weeks the problem was fixed.
Maybe you don't have the time because you develop new bots.

Maybe you have a small QA Team.

I don't know your team strength but a little more feedback about our bug reports would be nice.
Maybe some list of known problems in the first post.

There was a rock solid release some weeks ago. I don't know why there are currently so "extreme" problems.

Yes Software changes can break other things. But after ?each? big ore often smaller patch the Bot is for some weeks in a unstable state (for me), which is very unhappy ~~

So enough text from me.

I quit botting for a while until there is a far more stable release and maybe there aren't this quality jumps in further releases. I hope so :/

The logs are in the attachment.

Sorry I don't have one for the stuck problems, but for the other.

And yes, also tried this with fresh install and without plugins.

Greetings

 

The DungeonBuddy issue has been resolved by highvoltz. It is waiting on an update from HB Core, which we have heard nothing about from the dev team, not even in a Beta build.

Downloaded latest Beta, v2.5.8173.372 to test.

Navigates and kills the first boss in an LFR raid without issue. After the first boss dies, the character continues as it should. It appears the latest Beta build has fixed the DungeonBuddy bug that was not following the group after the first boss kill. Will continue to test and if the bug occurs again, will post a thread.

 

Nice if you're not from germany...

 

See Tony and Raphus what you guys are failing to understand is these are not support issues people are complaining about, its more or less the "Lack" of attention to detail with the HB development. Bad code, poor testing prior to releasing, and NO I mean absolutely NO communication to your customers the past 4 days on ANYTHING. That is unacceptable and we all knew you where going to clear this thread well because if thats one thing you folks are good at is that.

 

...Or it looks like you're not reading the forums because if you were then you would clearly see what people are saying. Listen you dont need to preach to me as I have donated so much to this community its not even funny. I tell you what show us a post on what was going on with the HB Core Yesterday and the day before I would love to see this, and btw if you placed it anywhere other then bot status updates or Beta then you guys dont even know how to update the community on HB core news. Dont want to argue about this, but the bottom line is HB has not been the same with the past 10 releases and is not even close to what it was when Bossland was the main overseer of the HB back in the day.

 

Whatever checking process once existed, doesn't now. We have come to expect a professional product from the HB team, it is like amateur hour now with every sloppy release. Bossland grow a set, sack some devs, get the end user back on your side. HB was once great, it is now mediocre at best, whatever used to happen needs to happen again.

G

 

I would expect this with a free program from mmowned, but not a product i paid for. Bossland, im not angry, just disappointed.

 

I know that Tony and CG have been posting in people's HB support threads, but personally, why would you expect everyone having an issue to read other's threads when most people, at least logically, check the Releases forum, Beta thread and Bot Updates thread for updates? If I see someone else post a thread with my issue, but either they have not received a reply from you guys, or failed to attach a log, etc., why would I want to clutter the forum with more threads of the same problem? The issue with DungeonBuddy had been happening since 5.4 hit, but it's just now appearing to be fixed in a Beta build, yet NOT ONE word was said to anyone about the latest Beta resolving their DB issue. I know devs are real people and have other obligations, but The Buddy Team needs to have a staff meeting of some kind to discuss ways to improve their communication to their clients. Having to spend hours on the forums searching through dozens of threads to seemingly get nowhere is beyond frustrating.

Please consider this criticism constructive as I really do enjoy your products and find them to be the best on the market; however, many, MANY clients of yours do not feel the communication is on par for what we have come to expect from The Buddy Team.

Looking forward to getting back to DungeonBuddy now that it appears to be fixed in the latest Beta build.

Thanks.

 

y2krazy, may I ask which Raid/Dungeon you tried? Since so many people are posting in the beta thread that DB still doesn't work. So maybe I can avoid the ones not working

 

I have been trying beta's it is still not working try running the seasonal dungeon Direbrew... it just stands there