I am trying to do RAF with honorbuddy. I am controlling one account and want honorbuddy to follow the account and help me attack, kill, and heal. But when I start honorbuddy it says following leader and does not move. Does anyone know what's wrong with the bot? Thanks .
Here is the log. View attachment HBdebug.txt Also I will paste in part of what it is saying. [10:57:13 AM:387] Activity: Moving to leader [10:57:13 AM:405] System.NullReferenceException: Object reference not set to an instance of an object. at Tripper.Navigation.MeshProviders.FileMeshProvider.TileExists(Int32 tileX, Int32 tileY) at cm.TileExists(Int32 tileX, Int32 tileY) at Tripper.Navigation.Navigator.a(TileIdentifier A_0, LoadedTileFlags A_1, Boolean A_2) at Tripper.Navigation.Navigator.GeneratePath(Vector3 start, Vector3 end, QueryFilter filter, Int32 maxLength, StraightPathFlags[]& pathFlags, PolygonReference[]& straightPolys) at Tripper.Navigation.PathFollowing.TripperNav.MoveTowards(Vector3 point) at Styx.Logic.Pathing.Navigator.MoveTo(WoWPoint destination) at Bots.CombatAssist.CombatAssist.g() at Bots.CombatAssist.CombatAssist.o(Object A_0) at TreeSharp.Action.RunAction(Object context) at TreeSharp.Action.a.a() at TreeSharp.Composite.Tick(Object context) at TreeSharp.Sequence.a.b() at TreeSharp.Composite.Tick(Object context) at TreeSharp.Decorator.a.a() at TreeSharp.Composite.Tick(Object context) at TreeSharp.PrioritySelector.a.b() at TreeSharp.Composite.Tick(Object context) at TreeSharp.PrioritySelector.a.b() at TreeSharp.Composite.Tick(Object context) at Styx.Logic.BehaviorTree.TreeRoot.b() [10:57:13 AM:405] Cleared POI [10:57:13 AM:570] System.Threading.ThreadAbortException: Thread was being aborted. at Styx.Logic.Targeting.Pulse() [10:57:13 AM:572] Stop Button pressed. User has stopped the bot.
[10:56:38 AM:256] Honorbuddy executable: C:\Users\Owner\Desktop\Honorbuddy 2.003176\Honorbuddy.exe install the newest HB which is 3182 - Kick
Alright, the bot is working now but I still have a problem. It is extremely slow. For example, when I move my party leader the other account will wait up to 10 seconds until it follows me. It also takes a while for it to get the same target that my character is looking at.
Latency is around 250ms on both screens. Framerate is about 60 fps on both. Here is a log. I moved a few times (took the bot around 10 seconds to start to follow) and i targeted a scorpian (took about 5-10 seconds to attack it) and then I moved again and the bot didn't respond to that... View attachment 11-20-2010_11_50 AM Log.txt
its a CC issue, use Isis and report back http://www.thebuddyforum.com/honorb...iest-cc-pve-pvp-raf-healbot-7.html#post159845 <-- click that
I tried using that first and it did the same thing. I switched to the normal CC that came with the bot after to see if it was a problem with Isis CC.
Here is the log when I use Isis. For Isis my botted character does not attack anything I target. It also does not follow me. View attachment 11-20-2010_12_32 PM Log.txt
Okay, I downloaded the new version of Isis and now it will attack and it targets whatever I target. It still takes about 10 seconds to start following me if I move though. Any ideas about why? Does it have something to do with my mesh folder maybe?
I deleted my mesh and tried almost everything... The bot still takes 10+ seconds to follow my main character and targeting usually takes around 5 seconds.
When HB/WoW is running whats your CPU usage at? I had a similar problem and i fixed it be stopping some processes i had going. I had around 70+ and dropped it down to ~60 and now it runs fine but i'm not even sure that's what fixed it.
That is an excellent point -- I was going to check his log to see what the log was thinking (or lagging). sometimes its errors that are making it slow, too its best to set all bot accounts at ~25 fps and use GameBooster (free download) to lower computer usage as well.
Here is a log. I play on lowest specs and my computer is a quad core and has 8gb of RAM. I don't think memory usage is a problem. Here is a log anyways. View attachment 11-21-2010_11_09 PM Log.txt