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!

Honorbuddy for MoP 5.0.5.16057

Status
Not open for further replies.
Questing bot is working fine for me on three accounts. Main issue though is the behaviors and profiles needing some new tuning with all the game changes.
 
After restart and new update, kicks 1-58 profile isnt starting anymore.
Checks the spells of the toon, then happens nothing.

\Profiles\kick\1-85 Questing Profile Pack\Classic\[A - Quest] 1-58 [Kick]\[A - Quest] 1-12 [Kick]\..\[A - Quest] EK 12-58 [Kick].xml'
[LoadProfile-v241(info) @line 3727]: Loading profile '..\[A - Quest] EK 12-58 [Kick].xml'
Changed tilemap to Azeroth, Tiled: True
Changing current profile to [A - Quest] EK 12-58 [Kick]
System.NullReferenceException: Object reference not set to an instance of an object.
at Bots.Quest.Actions.ForcedBehaviorExecutor..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector..()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.CommonBot.TreeRoot.()
Cleared POI - Reason Exception in Root.Tick()
Cleared POI
[QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[Profile Message]: Compiling Redridge Quests
[QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedIf.
Compiling expression '(!IsQuestCompleted(26640))' @ line 4129
[QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedIf.
[QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedIf.
Compiling expression '((HasQuest(26636)) && (!IsQuestCompleted(26636)))' @ line 4339
[QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedIf.
[QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedIf.
Compiling expression '((HasQuest(26638)) && (!IsQuestCompleted(26638)))' @ line 4343
[QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedIf.
[QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedIf.
Compiling expression '((HasQuest(26636)) && (IsQuestCompleted(26636)))' @ line 4346
[QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedIf.
[QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedIf.
Compiling expression '((HasQuest(26638)) && (IsQuestCompleted(26638)))' @ line 4349
[QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedIf.
[QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedIf.
Compiling expression '((HasQuest(26640)) && (IsQuestCompleted(26640)))' @ line 4352
[QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedIf.
[QDBG] Starting behavior [ForcedSingleton].
[QDBG] Done with forced behavior [ForcedSingleton].
[QDBG] Starting behavior [ForcedGrindTo Level: 21].
Goal: Grinding to level 21
Activity: Moving to hotspot
Activity: Loading Tile/s
Loading Azeroth_34_51
Activity: Loading Tile/s
Loading Azeroth_35_50
Loading Azeroth_34_52
Loading Azeroth_35_51
Loading Azeroth_34_50
Loading Azeroth_34_49
Loading Azeroth_35_49
Activity: Moving to hotspot
Unloading tiles!
Activity: Loading Tile/s
Loading Azeroth_34_51
Loading Azeroth_34_52
Loading Azeroth_33_51
Loading Azeroth_33_52
Activity: Moving to hotspot

Oh I just should add: toon is just standing there, though the log says its moving..
 
Last edited:
After restart and new update, kicks 1-58 profile isnt starting anymore.
Checks the spells of the toon, then happens nothing.



Oh I just should add: toon is just standing there, though the log says its moving..

I have had this happen multiple times, I have to stop and start the bot a few times and even sometimes shut down the bot and re open it and restart and then it works.
 
Can Any of the developer crew give some realistic timescale as to when this bot will be functional again its 3 weeks into expansion now and its still running like a 3 legged pregnant cow, surely there must be some light on the horizon by now or are we going to be continually told to be patient? At least release the updates once a week to give us a chance to use the bloody thing without having to trawl through hundreds of pages of posts in the hope of finding a profile or bot update to get the bloody thing working again.

This ^
 
Ok, the restart, relogg, quit wow and buddy procecedure. I?ll try that -

Posted this to the wether others are experiencing the same.

Edit: Didnt help, but Update .461 helped.
 
Last edited:
Archbuddy is not working properly... when it gets near the digsite it just stands in the air doing nothing then moves abit and stops again.
Tried to do mixed mode with archbuddy + BGbuddy but BGbuddy when enters the BG it says this

[Singular] Context changed. New context: Battlegrounds. Rebuilding behaviors.
[Singular] Singular currently does not support Combat for this class/spec combination, in this context! [None, None, Battlegrounds]
 
I'm getting same issue as Reffih. Bot does nothing but load tiles in questing ( yes i know this isn't supported fully yet) but I just wanted to report the issue as well. Thanks
 
Ever since the last update, I am unable to even use my bot... I launch wow(Tried Dx9 & Dx11), then open HB, & then I enter my key, it attaches, then I get this stupid error message. It does this EVERYTIME & still happens even if I delete my copy of HB & re download it.

I would really like to use my bot again, so a little assistance would be great. :D

http://puu.sh/17fBp
http://puu.sh/17fBp
http://puu.sh/17fBp
 
Can Any of the developer crew give some realistic timescale as to when this bot will be functional again its 3 weeks into expansion now and its still running like a 3 legged pregnant cow, surely there must be some light on the horizon by now or are we going to be continually told to be patient? At least release the updates once a week to give us a chance to use the bloody thing without having to trawl through hundreds of pages of posts in the hope of finding a profile or bot update to get the bloody thing working again.


Come on people give them time, "it's all ready been 3 weeks" really....... I give them props for the bot working as it is in such a short time, ITS A NEW EXPANSION they are pretty much having to rebuild most of the bot all over again of course its going to take a while, not to mention every server restart wow does has a mini patch with it meaning some code in the bot needs to be rewritten just for it to start, I guarantee most if not all the people complaining have never wrote any code in there life, if you think it is so easy go make one yourself. they have already said most if not all of your time you paid for will be giving back to you.

So with that said MUCH LOVE AND MAJOR PROPS TO EVERYONE WORKING ON THIS PROJECT!!!
 
Status
Not open for further replies.
Back
Top