What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

More errors

Haha, buddyauth is down right now so all kinds of sadness is happening for the whole buddybot system!

Agility works great, though! *self plug* ;)
 
Well that could explain it! Where can we see status? The auth portal was up so I figured things were good
 
Not sure! Just a lot of tears on the other forums!

Be sure you update your QuestHelper as well! The core bot now has a BreakTag, so it'll crash if the both of them co-exist. ;)
 
Yeah I updated everything fresh today but still no luck
 
Tried again today with the latest beta build - Agility seems to be working fine, but grinding profiles and questing profiles seem to be throwing errors when trying to initiate combat. If combat is initiated, say by running into a mob while on the way to a destination, bot runs a rotation fine, but if it tried to initiate combat on it's own it just error loops.

Here are logs for grinding profiles:
View attachment 190919
View attachment 190920

and questing profile:
View attachment 190921
 
Tankall said:
Tried again today with the latest beta build - Agility seems to be working fine, but grinding profiles and questing profiles seem to be throwing errors when trying to initiate combat. If combat is initiated, say by running into a mob while on the way to a destination, bot runs a rotation fine, but if it tried to initiate combat on it's own it just error loops.

Here are logs for grinding profiles:
View attachment 190919
View attachment 190920

and questing profile:
View attachment 190921
Click to expand...

Oh ew, I'll look into the KillTag and see what broke there, now. :D
 
I have identified this little blip, and while I can't push an update for now, I can talk you through a manual change so you can hopefully get some grinding in today!

Routines\Default Routine\Classes\BaseCombatClass.cs, line 100

Change:
var flaskSlot = SpellManager.AvailableSpells.FirstOrDefault(a => a != null && a.Name.Contains("Flask") && a.CanCast);

To
var flaskSlot = SpellManager.AvailableSpells.FirstOrDefault(a => a != null && a.Name != null && a.Name.Contains("Flask") && a.CanCast);
 
Deathdisguise said:
I have identified this little blip, and while I can't push an update for now, I can talk you through a manual change so you can hopefully get some grinding in today!

Routines\Default Routine\Classes\BaseCombatClass.cs, line 100

Change:
var flaskSlot = SpellManager.AvailableSpells.FirstOrDefault(a => a != null && a.Name.Contains("Flask") && a.CanCast);

To
var flaskSlot = SpellManager.AvailableSpells.FirstOrDefault(a => a != null && a.Name != null && a.Name.Contains("Flask") && a.CanCast);
Click to expand...

That did the trick! Thanks DD!
 
Glad I could finally get you going! Hahaha. I am not entirely sure how to recreate the memory errors regarding the KillTag, but hopefully it's no longer harassing you!
 
You must log in or register to reply here.
Back
Top