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

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[Release] Honorbuddy 2.0.0.5588 - Christmas Edition #2

Status
Not open for further replies.
Warden doesn't "detect" the bot if you minimize the window he's just talking shit
It doesn't work when minimized because wow goes into "sleep" mode alot of plugins like Auctioneer etc. doesn't work either. altho the main reason as to why it doesn't work is because you can't call Click To Move and a few other functions.
I can't let MadDog take the fall on that one.
I was the one who told him this, as this is what I was lead to believe by another user (back in the day, don't remember who)
So my b.


Anyways sweet updates guys.
Haven't seen HB release threads popping up this often since... well never :)
 
Hmm, ever since I've upgraded to lastest version I'm getting very unusual problem: theres a spot in Vashjr in Silver Tide Trench where for some reason the wow screen turns black and the only thing left to do is to restart WoW. Oh and when you try and move your character when the screen is black, it throws 132 error (however you can open WoW map and such). I've already tried repairing WoW and removing cache folder, did not work. Also, it did not happen before the upgrade. Next time it happens I will try and capture a screenshot.
 
Having issues with some nodes now..
wupRR.jpg

It kept trying to land right on the ledge and would slide down the side of the thing. This action is more bot like then the old behavior. I suggest that if it fails to land next to the node, that the second attempt it will try and land directly on top of the node.
 
Having issues with some nodes now..
wupRR.jpg

It kept trying to land right on the ledge and would slide down the side of the thing. This action is more bot like then the old behavior. I suggest that if it fails to land next to the node, that the second attempt it will try and land directly on top of the
node.

i know that place hehe sometimes you fell of the cliff if he mines i had that also but not anymore
 
In a cave in Northen Barrens

Toon just starts to spin round and round and round with a followed disconnect.

Making 1-70 questing with Azenius impossible to accomplish.

Drop all other projects with HB and fix navigation !!!!!!!
 
[3:17:14 a.m.:944] System.TypeInitializationException: The type initializer for 'Styx.Helpers.UISettings' threw an exception. ---> System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
at System.Xml.XmlTextReaderImpl.Throw(Int32 pos, String res, String[] args)
at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Int32 pos, Char invChar)
at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlReader.MoveToContent()
at System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options)
at System.Xml.Linq.XElement.Load(String uri, LoadOptions options)
at System.Xml.Linq.XElement.Load(String uri)
at Styx.Helpers.Settings..ctor(String settingsPath)
at Styx.Helpers.UISettings..ctor()
at Styx.Helpers.UISettings..cctor()
--- End of inner exception stack trace ---
at Honorbuddy.MainWindow..ctor()

strange issue when I start up HB everything is greyed out and nothing loads
I was botting then just decided to turn off my PC to play Xbox must've been about 10 minutes then I decided to bot again only to discover this error
 
Hmm, ever since I've upgraded to lastest version I'm getting very unusual problem: theres a spot in Vashjr in Silver Tide Trench where for some reason the wow screen turns black and the only thing left to do is to restart WoW. Oh and when you try and move your character when the screen is black, it throws 132 error (however you can open WoW map and such). I've already tried repairing WoW and removing cache folder, did not work. Also, it did not happen before the upgrade. Next time it happens I will try and capture a screenshot.
Same here!
Except i've had it in twilight highlands and deepholm.
Will grab a log when it happens next time!
 
i know that place hehe sometimes you fell of the cliff if he mines i had that also but not anymore

Have had it on other spots as well, posted this problem few posts back. Would be nice to have a fix :)
 
Last edited:
ok so, landing on the premium nodes does not work, and often the bot just flies away after 2secs. ....
 
Right now having a char questing in Zul'Drak. It is completly fukked. Gets stucked at nearly every wall... and there are lots there. Please fix this, seems to ignore unstuck routines?!
 
Same here!
Except i've had it in twilight highlands and deepholm.
Will grab a log when it happens next time!

I'm glad I'm not the only one with this problem, lets see what devs will come up with :)
 
Ravage! (When you have stampede) doesn't currently work in feral druid; its two different spells and i think that spell manager is missing it. It does work using the legacy with cast by id however.
 
altho the main reason as to why it doesn't work is because you can't call Click To Move and a few other functions.


I can't speak about these "other functions", but you are 100% wrong about CTM not working with wow being minimized. Anyone that came from Pirox can tell you this.
 
Meh...druids...bot keeps swapping back and forth between ground mount and aquatic form when swimming. Keeps swapping between aquatic form and cat form when in combat in water.
 
I can't speak about these "other functions", but you are 100% wrong about CTM not working with wow being minimized. Anyone that came from Pirox can tell you this.

It depends on how you use it
 
after lot of testing questbot it figures out for me that it's not really a navigation/unstuck issue. It seems to be an issue with running forward endlessly. Thats why the bot runs into walls etc. After pressing the "W"-key manually, HB works again as it should, until it falls again in a run-forward-endlessly-bug.
 

Attachments

Last edited:
after lot of testing questbot it figures out for me that it's not really a navigation/unstuck issue. It seems to be an issue with running forward endlessly. Thats why the bot runs into walls etc. After pressing the "W"-key manually, HB works again as it should, until it falls again in a run-forward-endlessly-bug.

ok, after some testing it seems it's a problem with the cc. didn't have these probs with shamWoW, had it only on my hunters driven by FPSWare Hunter. Hunting with Singular works fine so far. Looks like FPSWares cc's going to get outdated :eek:
 
Status
Not open for further replies.
Back
Top