What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Honorbuddy 2.5.6850.537

Status
Not open for further replies.
Got the same issue too, with the reputation. I post this in the support section.

I don?t think, that Blizz has changed the Reputation System as well. Tried to make Dailies, with the Profiles postet here. Yesterday everything works fine and the author says, that this must be an hb issue.

Just sit an wait, until the devs fix ist.
 
Just FYI for devs, dungeonbuddy does seem to be working as far as queueing/pathing, however upon entering combat druids are non-responsive with singular. Tried to check if the issue was isolated to singular by running CLU but still had issues with druid tank positioning and attacking. Tried fresh installs of both this release and most recent beta build to no avail.
 
We are trying our best to push a release quality product right after a big patch (a lot changed in the binary itself).

Considering we pushed a release in the patch day, it is normal that we missed stuff. If you are not happy with the bot's current state, wait a day or so before using it, instead of flaming and raging.

Meanwhile, we fixed the combat bug and working on other issues before doing a release.

Will keep you guys informed.

I think the "flaming and raging" might have to do with us not being able to understand why you released this. to waste our time, to beta test it? then call it a beta test.

This release literally does nothing other than attach to wow. nothing works. Assuming ANY of you devs turned it on for more than 3 sec before bundling it in the zip file, you would know this. from the giant logs filled with "System.AccessViolationException: Could not read bytes from FFFFFFFF [299]!", and you know, the part where the bot just stands around doing nothing.
 
having the same problem with my bot just going back to pick up the quest still excited though and not complaining. just trying to help by acknowledging the problem
 
Hey folks, I had those crashing issues.

Personal fix: Disable AutoEquip.

It worked for me, give it a go
 
Questing Bot Error

Using Kick's profiles, moves to quests, when it combat, just sits there.

Also, the bot tends to lock up and when you try to alt tab between the game window and the bot window, it doesn't allow you to go back to the bot window for a while. I have had to end task/process several times to kill the bot and restart.
 

Attachments

That was very fast, thanks Devs!

EDIT: Yes, the singular isn't working but thanks for publishing the new version fast, atleast it's starting and Gatherbuddy seems to be working just fine aside from the singular-problem. :)
 
Last edited:
singular is not working at all for all of us, just keep waitting here !:)
 
Every time i start up HB, it attaches to the game, but then i get a WoW error and the whole thing crashes. Any clue as to what is going wrong?
 
We are pushing a new hotfix release. We are working on the other known issues overnight. Just wanted to get *most* of the bot running with combat and pet fixes.


Known Issues
------------------
* Quest States not being recognized properly
* AutoEquip2 causes crashes
* Weapon enhancements not recognized properly and causes infinite loops on applying poison/imbues.


Hotfix
-------------------
* HB should properly fight back now.
* Pets should be properly detected now.
 
I just updated it but i still get the same problem.. It attempts to apply flametongue over and over..

[Singular] Imbuing main hand weapon with Flametongue
[Singular] Imbuing main hand weapon with Flametongue
[Singular] Imbuing main hand weapon with Flametongue
[Singular] Imbuing main hand weapon with Flametongue
 
We are trying our best to push a release quality product right after a big patch (a lot changed in the binary itself).

Considering we pushed a release in the patch day, it is normal that we missed stuff. If you are not happy with the bot's current state, wait a day or so before using it, instead of flaming and raging.

Meanwhile, we fixed the combat bug and working on other issues before doing a release.

Will keep you guys informed.


Weeeell....patch day for EU maybe, US has been patched for a day already though i hear ya ;)
Take yer time man :)
 
Still problem in new instance:

Currently Using BotBase : Combat Bot
Tilemap is null!
Bot Stopped! Reason: Tilemap is null!
 
Im not bitching or anything.. everyone seems to have it working even somehow but mine says "Bot stopped: Tilemap is null!"
 
Status
Not open for further replies.
Back
Top