Updated Bot acts differently i.e. 2 Bugs maybe

[s018mes]

I have updated to the newest bot and it runs fine. I am doing Miller's Ranch fine.

However, when I set it to attack mobs for farming Dailies, two things I have noticed.

First, it does not seem to back up when stuck, like when the mob is behind her. It just continues to try to cast and does not try to move. And when it runs out of mana it dies.

Also, I have noticed when it is fighting and a Buff pops up after the mob dies, the bot USE to walk into it to get the buff. It does not do that anymore.

Is this a setting that I can change somewhere due to update all the new files? Or is this due to the updated bot itself?

I have been using the bot for over a year now and LOVE it. I appreciate rock5 and Lisa and everyone who has worked on this project. I appreciate you guys.

Thanks

[lisa]

Also, I have noticed when it is fighting and a Buff pops up after the mob dies, the bot USE to walk into it to get the buff. It does not do that anymore.

I have noticed this lately too, the bot will go get the sigil(buff) eventually, once all corpse have been looted and you are out of combat. I think it is to doo with the loot_all.

rst, it does not seem to back up when stuck, like when the mob is behind her. It just continues to try to cast and does not try to move. And when it runs out of mana it dies.

Hopefully I didn't break this when I commited the pot changes. I have been experimenting with new code for this and I thought I had put back in the old code before commiting.
I'll have to check it tomorrow, going to bed now.

[rock5]

Picking up the sigil is part of the loot function. Probably because you are using the loot_all option now, you have disabled loot_in_combat. So it doesn't pick up the sigil in combat anymore.

[s018mes]

When I updated the bot, I did not change any profile settings. So why did the bot behave differently after the update?

Here are my profile settings:

<option name="LOOT" value="true" />
<option name="LOOT_ALL" value="true" /> <!-- Loot all nearby dead mobs after combat -->
<option name="LOOT_IN_COMBAT" value="true" />
<option name="LOOT_DISTANCE" value="100" />
<option name="LOOT_PAUSE_AFTER" value="0" /> <!-- probability in % for a short rest -->

[Edamh]

Just to throw in my anecdotal $0.02, I have also noticed that the bot does not pick up the sigils as it previously had done. I have also NOT changed my loot settings within my profile, but have still seen a change in bot behavior with regards to sigils.

[rock5]

The only thing I can think of is it's loosing it's target before loot runs ie. the dead mob disappears too fast. If the dead mob disappears (or some other code causes it to clear it's target) before loot runs then it wont run and it wont collect sigils.

onLeaveCombat runs before looting. Is there anything in your onLeaveCombat section that would cause it to clear it's target?

[s018mes]

<onLeaveCombat><![CDATA[
-- Additional Lua code to execute after killing an enemy
]]></onLeaveCombat>

Could I put in there something that could correct this issue?



Also, what any idea on what is stopping the bot from recognizing that the target is behind the character and needs to backup to get the mob back infront and start casting again?

[rock5]

Also, what any idea on what is stopping the bot from recognizing that the target is behind the character and needs to backup to get the mob back infront and start casting again?

When casting skills it should turn to face the target. Problems occur when the target looks like it's in one place on the client but it's actually in another on the server. Not much can be done about this. The bot should eventually move which should fix the problem.