What's new
By:
  • 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.
Gathering , i deleted cache wtf addon problem still presist , also done reinstall all drivers still same problem . And i see others have this problem so it must be bot related :/
 
raphus said:
You sure you watched how this release gathers ?

It will fly to node and right-click directly without dismounting. It will however dismount manually if it's not automatically dismounted in 2 seconds.
Click to expand...

Ever since the update to GB2 so that it doesn't land directly on top of nodes, the bot is now unable to farm nodes that are on top of a steep cliff. These types of nodes are very common in Twilight Highlands. Using the default node blacklisting time of 20 seconds, it is now extremely easy to spot a botter. Any chance at this change being reverted, making it optional, or fixing the node approach logic?

Great updates otherwise.

- Ben
 
benkoren said:
Ever since the update to GB2 so that it doesn't land directly on top of nodes, the bot is now unable to farm nodes that are on top of a steep cliff. These types of nodes are very common in Twilight Highlands. Using the default node blacklisting time of 20 seconds, it is now extremely easy to spot a botter. Any chance at this change being reverted, making it optional, or fixing the node approach logic?

Great updates otherwise.

- Ben
Click to expand...

Yes, not ontop makes a few in Uldum impossible too, after falling of a cliff 5 times you look silly :)

G
 
look like black screen of death showing up then bot has some unstuck problemm or can't find the way to the next hotspot ( deleting meshes doesn't help ) only moving tonn far away sometimes helps for a short period of time
 
Got the same black screen issue in Vash'jir with christmas edtion#2, log doesn't show anything either.
 
got the prob with wow crashing.

But only with 1 of 6 WoW runing GB2 :

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal exception!

Program: F:\MCWoW_3.3.3lma\Wow.exe
ProcessID: 6424
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:0016DB06

The instruction at "0x0016DB06" referenced memory at "0x00000080".
The memory could not be "read".


Clean HB copie and clean WoW no addons Fresh Chage and Wtf

only the 1 bot of all the 6 is crashing after 5-30 min

need halp pls

( no plugins activ)
 
Isn't it possible to get another way of getting combat distance on a boss?
Like people are reporting issues with last 4 bosses in Dragon Soul, it's told to be a CC issue - but everybody seems to be using the same code

I saw WoWnerds saying they found a way of doing a check so that the range would fit, isn't it possible to do something like that aswell?
 
benkoren said:
Ever since the update to GB2 so that it doesn't land directly on top of nodes, the bot is now unable to farm nodes that are on top of a steep cliff. These types of nodes are very common in Twilight Highlands. Using the default node blacklisting time of 20 seconds, it is now extremely easy to spot a botter. Any chance at this change being reverted, making it optional, or fixing the node approach logic?
Click to expand...

Bump. Is this something the HB devs plan on fixing? Is there an issue tracker I should be posting to instead? With this behavior, we can't realistically use GB2 in its current state without getting reported within a short amount of time.

- Ben
 
so all of a sudden it take like 3 min to log into my session ... my wow client has been acting wierd and HB wasnt closing so I forced shut down my PC ... eversine there has been a huge delay in logging on to HB. Any thoughts?
 
Kickazz006 said:
well your video card still renders it, it just doesn't render it on your monitor ;)
Click to expand...
yawp, exactly my point. it fixes the issue of not being able to minimize wow lol. idc about it being open, i am just usually doing many things while playing, so it keeps wow out of my way by dragging it off screen :p
 
Ehm i dunno if this is wrong section but whats wrong in this line... cant get anythin up in the log on honorbuddy.

The Debug part says this:


[17:52:51:992] 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()
 
I always forget to mention it...

It'd be great if we ever saw a fix to whatever is causing looting to SOMETIMES (I'd say 40% of the time) to take 30 seconds (almost like clockwork).
It doesn't happen always, but it's quite botish. Just picture yourself killing a bunch of mobs and then stopping for 30 seconds before you move again >.<
 
Ralphus,

Thanks for your hard work!!

Is there any way to fix the targeting issues in dragon soul? Fall of deathwing is the worse but other places are bad as well for casters. You basically have to stand on the claws to target them? And it sometimes targets friendlies? Now if this is the cc's fine but I have not found 1 cc that will work there not even shamwow so that leads me to believe it is HB and not the cc's. I have 20+ 85's and a lot of time so I raid with them all so anything you need to fix this please let me know. I would be glad to provide whatever I can to get targeting fixed once and for all.
 
Excuse me but can anyone help me with " Then you need to do this:
Open your Options->Advanced->Graphics API make sure it's set to DirectX 9 if it isn't change it and restart wow then restart and login on the bot again."?
Im new to honorbuddy and can find "options" in the folder.

By the way thanks for your hard work!
 
specctruz said:
Excuse me but can anyone help me with " Then you need to do this:
Open your Options->Advanced->Graphics API make sure it's set to DirectX 9 if it isn't change it and restart wow then restart and login on the bot again."?
Im new to honorbuddy and can find "options" in the folder.

By the way thanks for your hard work!
Click to expand...

The options of World of Warcraft.
 
Arpo said:
Ehm i dunno if this is wrong section but whats wrong in this line... cant get anythin up in the log on honorbuddy.

The Debug part says this:


[17:52:51:992] 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()
Click to expand...

clear your settings folder and try again
 
Suggesting modifying the gather function to attempt landing around the node once, or two times.
If failed, fly up, and land directly on.

Thanks.
 
no1knowsy said:
Suggesting modifying the gather function to attempt landing around the node once, or two times.
If failed, fly up, and land directly on.

Thanks.
Click to expand...

I think that sounds like a good idea... it would be REALLY nice if our toons were able to log "discovered mesh errors" - it attempts to land where it thinks it can stand, discovers it can't because the slope is too steep - logs that location in a file and then attempts a 2nd location... if that fails, then it logs that location, flies up and lands directly on the mine.

THEN... once every couple of days, we hit the "Upload Mesh Errors" button and HB uploads those discoved Mesh errors to the server and the server modifies the mesh automagically. No having to record the location manually and reporting it... our toon found the spot, recorded the location and then we uploaded the update.

Every single day the mesh would be improved simply by us playing it and uploading what our toon discovered.
 
Status
Not open for further replies.
Back
Top