HB ARCHIVES: Processed Issues from Honorbuddy Release threads

Lisa Ann · Apr 2, 2015

I found the issue! It stays stuck in "Logging in..." because you have to use the launcher in honor buddy, Then wait for your WoW to open, log in, and then accept the administrative permission from HB, then it start it up and it should work just fine.

MaxMuster · Apr 3, 2015

"Generate Hotspot" in the Dev Tool includes now Nav="Fly":

<Hotspot Nav="Fly" X="824.2756" Y="-2732.359" Z="99.058" />

Please undo it. Nav="Fly" should not Standard in the Hotspot Output.

//Edit: And the same for "Copy XML" from the Current Target Info:

<Vendor Name="Leerenberührte Seherin" Entry="79827" Type="Repair" Nav="Fly" X="822.4614" Y="-2731.152" Z="99.05758" />

Nav="Fly" should be never standard in a XML Output.

Instead of doing so stupid things, they should better fix HB-1908: Developer Tool fails to generate NPC Names and Ids.

Please wait while we retrieve the data from WoWHead...
<PickUp Nav="Fly" QuestName="Kang Dornstab" QuestId="29874" GiverName="" GiverId="" />
<TurnIn Nav="Fly" QuestName="Kang Dornstab" QuestId="29874" TurnInName="" TurnInId="" />

And i see that here is Nav="Fly" standard too...omg...

Or make a Option Tab in the Dev Tool and there a to Toogle to enable/disable Nav="Fly" Output or not.

cg1203im2 · Apr 4, 2015

MaxMuster said:
...

Or make a Option Tab in the Dev Tool and there a to Toogle to enable/disable Nav="Fly" Output or not.

Thats indeed a graet idea!
a dropdownmenu. output coordinates as:
MyCTM, Hotspot, MoveTo, Flyto.
then checkboxes:
Include Nav=Fly

that would save so much work converting <Hotspot ... to <RunTo

Sorry for highjacking your post, MaxMuster

tomten2 · Apr 4, 2015

Purely curiosity but whats the difference between: Test release and release ? And how does it differ from say a beta release ?
The former 2 are still public releases and are automatically updated.
Why the test prefix ?

Pushing · Apr 4, 2015

I want to report a bug. Basically there is a condition where SpellManager.CanCast("Spell") returns True, while SpellManager.FindSpell("Spell") -> SpellCooldownTimeLeft is greater than 0.. usually something small like 3-25 ms.

I made a couple threads where I work through some of the issue:
https://www.thebuddyforum.com/honor...termining-spell-cooldown-considering-gcd.html
https://www.thebuddyforum.com/honor...ng-true-giving-ability-ready.html#post1913907

If this is working as intended.. a comment to clarify SpellManager.CanCast's purpose would be helpful. Thanks.

tomten2 · Apr 4, 2015

chinajade said:
Fair question. Let's start by disposing of "Beta" immediately...

Makes sense, thanks

DMan · Apr 5, 2015

Since this test release and the LAST full release the Line of Sight issues with Iron Gunnery Sergeant on the Operator Thogar fight have returned. You guys had fixed them before but now it is once again not attacking

I will attach a log, but do notice that any casting done on the Iron Gunnery Sergeant was manual casting.

View attachment 15056 2015-04-04 19.42.txt

tumbum · Apr 5, 2015

Got this Exception while running Brodiemans Apex Garrison Daily. At the moment it seems there is a Problem somewhere in HB Core itself and not his Profile.

Code:

[08:28:51.729 D] Goal: InteractWith-v1997: In Progress (no associated quest)
Interacting with MobId(86992), Unknown, MobId(87017), Pile of Grenades, MobId(87264), MobId(85976), Stolen Goods
    [Ref: "Assault on Mok'Gol Outpost Daily" @line 70]
[08:28:51.763 D] Exception was thrown in BotBase.Root.Tick
[08:28:51.763 D] Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at Bots.Grind.LevelBot.()
   at Buddy.Coroutines.Coroutine..()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Bots.Grind.LevelBot..()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Bots.Grind.LevelBot..()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at Ž...()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at CommonBehaviors.Actions.ActionRunCoroutine....()
   --- End of inner exception stack trace ---
   at Buddy.Coroutines.Coroutine.(Boolean )
   at Buddy.Coroutines.Coroutine.(Boolean )
   at Buddy.Coroutines.Coroutine.Resume()
   at CommonBehaviors.Actions.ActionRunCoroutine.Run(Object context)
   at Styx.TreeSharp.Action.RunAction(Object context)
   at Styx.TreeSharp.Action..()
   at Styx.TreeSharp.Composite.Tick(Object context)
   at Styx.TreeSharp.PrioritySelector..()
   at Styx.TreeSharp.Composite.Tick(Object context)
   at Styx.Common.HookExecutor.Run(Object context)
   at Styx.TreeSharp.Action.RunAction(Object context)
   at Styx.TreeSharp.Action..()
   at Styx.TreeSharp.Composite.Tick(Object context)
   at Styx.CommonBot.Coroutines.CoroutineCompositeExtensions..()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Ž...()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at CommonBehaviors.Actions.ActionRunCoroutine....()
   --- End of inner exception stack trace ---
   at Buddy.Coroutines.Coroutine.(Boolean )
   at Buddy.Coroutines.Coroutine.(Boolean )
   at Buddy.Coroutines.Coroutine.Resume()
   at CommonBehaviors.Actions.ActionRunCoroutine.Run(Object context)
   at Styx.TreeSharp.Action.RunAction(Object context)
   at Styx.TreeSharp.Action..()
   at Styx.TreeSharp.Composite.Tick(Object context)
   at Styx.CommonBot.TreeRoot.()
   at Styx.CommonBot.TreeRoot.(Action , String , Boolean )
[08:28:54.272 N] (Singular) YourCurrentTarget: changed to: (null)

y2krazy · Apr 6, 2015

Phelon said:
Pro Status on the Update quickness!

/vouch

Larryardilla · Apr 7, 2015

Thank you so much!

nooblet · Apr 7, 2015

Sweet thanks a bunch. Egg farming here i come lol

ZoneHunter · Apr 7, 2015

Thanks for the quick update HB Team!

Ilja Rogoff · Apr 7, 2015

Thanks for the update, but Arelog needs an update. BTW why is the Arelog thread CLOSED?

User0828 · Apr 7, 2015

Awesome release time! Unfortunately, this release has broke several things.

Mekare · Apr 7, 2015

Weird.... Stuck at:
Honorbuddy v2.5.13431.781 started.
Logging in...
T: 5247325802467640787 H: 2953232072

supersurfer · Apr 7, 2015

No Patch 19865 on my Server (EU) at the moment, so please link the previous version as well to use the "right" version until they patch it EU.

XIceMan · Apr 7, 2015

supersurfer said:
No Patch 19865 on my Server (EU) at the moment, so please link the previous version as well to use the "right" version until they patch it EU.

Info is too late!!!! thats a bad job of all developer!

Where can i get the .780 version?

XIceMan · Apr 7, 2015

raphus said:
http://updates.buddyauth.com/GetSpecific?filter=Honorbuddy&build=780

Thanks a lot!

shelaine · Apr 7, 2015

You should be on 19865 guys, even in EU. A bluepost just said that the hotfix was applied in both EU and US..

supersurfer · Apr 7, 2015

shelaine said:
You should be on 19865 guys, even in EU. A bluepost just said that the hotfix was applied in both EU and US..

"Should be", this hotfixes take some time, at the moment there are a lot of eu servers marked as incompatible but battle.net is still not updating.

HB ARCHIVES: Processed Issues from Honorbuddy Release threads

New Member

Well-Known Member

Community Developer

New Member

New Member

New Member

New Member

Active Member

Attachments

Community Developer

New Member

Active Member

Member

Well-Known Member

New Member

New Member

Community Developer

Member

Member

New Member

Community Developer