What's new
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

Beta 714 [Shut down bot-can't cast aura]

Kilgore

New Member
Joined
Oct 13, 2013
Messages
21
Reaction score
0
Found my character standing by the zone in with mobs attacking only to realize the bot had stopped.

Upon reading the log, I found that the bot stopped due to being unable to cast an aura (Haste). This seems like an odd reason to stop the bot. It ended the session needlessly because had it waited a second or two, it would have been able to cast the aura. There was plenty of mana reserved. You'll probably notice it casting both auras successfully several times in the log. (I didn't check, but probably.) I've never noticed this error before.

Thanks
 

Attachments

What other auras are you using? Were you using Haste fine the previous bot runs or did you change something before leaving the bot to run overnight?

When that error happens, it means your aura settings are setup in a way that would cause the bot to lockup and never escape aura casting logic because it's tried and failed to cast the aura you want.

We can change the logic to skip using the auras altogether if it fails, but basically, in your case, it did wait and retry casting the aura, but it didn't have enough mana so it stopped the bot at the start of the instance. The reason it stops at the start of the instance is because that's basically when users will notice the configuration error, right after they click start and the bot gets into the area.

If you say you had enough mana to use haste, I believe you, but when you come from town, you should have full mana/life, so at the start of the instance, you should always be able to cast the aura. I see now there could be an issue since auras are cast in Exploration, so if you enter combat before exploration for some reason, use some mana, then hit exploration and try to use auras it would break, but that's not what happened based on your logs.

We'll change this logic to avoid the issue you noticed but it still has to make sure it won't get stuck if the user has auras configured incorrectly (which is why that error message was added).
 
No changes, I've been using the same set up and gear for weeks. I use Haste and Grace. They usually both cast upon entry into the zone--because I log out to reset the zone to bypass the portal out of range issue. It hasn't happened since reporting it either.

Although I only use/equip those two auras, would you suggest that I uncheck the other auras in the config window?
 
No, if you don't have any other auras equipped, your configs are fine then. If it's been working well for a while, then it's just a random error where perhaps something got double cast due to lag or desync.

We'll add a mana check as well to make sure the bot is at full mana before trying to do the aura logic, just in case, as well.

Actually, we can't since then we have to account for BM and BM-linked auras. We'll just cast once and just log the error if it happens.
 
The next beta version will contain changes to prevent this. Thank you for reporting it.
 
Back
Top