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

Saying the bot wait to fill up your ES first and then continue grinding possible?

Dimensionday

New Member
Joined
Dec 13, 2011
Messages
54
Reaction score
1
My Char hat some Life and Much ES...
It happens that the enemys penetrate the ES Shield.
The Bot just continues walking an dies cause no ES...
Is it possible to set him up that he waits (if there are no enemys in Combat Range!)
to refill the ES?
 
Yes, in your combat end section of the example routine, add the following;
I looked into the chicken plugin to find the bits of code needed

find this code region:
// No monsters, we can execute non-critical combat logic, like buffs, auras, etc...
// For this example, just going to continue executing bot logic.
if (bestTarget == null)
{

And add into there this:
do
{
await Coroutine.Sleep(500);
}while(LokiPoe.Me.EnergyShieldPercent < 90)


naturally this code could get you into trouble if you get attacked while recharging as the bot will just sit there.
I have not tested this, yet.

wimm
 
Gonna try it. What means Coroutine Sleep? How long ist that 500?


EDIT: What means the Error: [Logic] UseAt returned InvalidSlot.
But still everything okay...

And when using the Line above in the If Clause after the normal if then i get many error from the Bot... And he just moves to the start of Crypt
and stops there...

if (bestTarget == null)
{
if (await HandleShrines())
{
return true;
}
do
{
await Coroutine.Sleep(500);
}while(LokiPoe.Me.EnergyShieldPercent < 90)

return await CombatLogicEnd();
}
 
Last edited:
"[Logic] UseAt returned InvalidSlot." means your routine is trying to use a slot that does not contain a gem. Check your example routine settings, you may have set the wrong slot number for an attack.

Ok, let me test the code after lunch :)

wimm
 
#SOLVED [Just played a little with the Skills. I put the Blood Rage and Assassins Mark on the Slots 4/5 because they are not active Skills. The Routine uses them..]
Really dont know wheres the problem is... Just using Reave as "1" as you can see at the Picture...
There should be nothing else to use.. So i dont udnerstand the: "[Logic] UseAt returned InvalidSlot."


j9bmc.jpg



#SOLVED And got another Problem. The Bot isn't picking up Maps.

NB2Eh.jpg

aI7dd.jpg



EDIT:

#SOLVED [Just started the Bot again.. Mhmm]
And just now the Char doesn'T moves anymore.
and this Error shows repeadly again and again!!
[Tick] Exception during execution:System.ArgumentException: Ein Element mit dem gleichen Schlüssel wurde bereits hinzugefügt.
bei System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
bei System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
bei System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
bei Loki.Bot.v3.AreaStateCache.()
bei Loki.Bot.v3.AreaStateCache.Tick()
bei Loki.Bot.Logic.Bots.BasicGrindBot.BasicGrindBot.Tick()
bei Loki.Bot.BotManager.(IBot )

[Tick] Exception during execution:System.ArgumentException: Ein Element mit dem gleichen Schlüssel wurde bereits hinzugefügt.
bei System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
bei System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
bei System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
bei Loki.Bot.v3.AreaStateCache.()
bei Loki.Bot.v3.AreaStateCache.Tick()
bei Loki.Bot.Logic.Bots.BasicGrindBot.BasicGrindBot.Tick()
bei Loki.Bot.BotManager.(IBot )
 
Last edited:
I'll need a full log for the last error you posted.

I can't replicate your issue with maps. The default filter should pick them up just fine without any modifications. Here's an easy test though:
* Go to the Coast, through the Lioneye's Watch exit
* Change your grind zone to this area, make sure you match the difficulty.
* Drop a map, and start the bot.

If it loots the map, then the issue you saw before was just the bot needing to do something else first before looting that map. If it doesn't loot the map, then there's another issue with your filters.
 
well, looking like a mess. The error '"[Logic] UseAt returned InvalidSlot."' is because you have nothing selected for the 'Fallback skill slot", so when your character runs out of mana, there is no default 'fallback' default attack, and thus the error. Suggest setting that slot number to your default attack.

As for the rest, itemfilter and all, I suggest downloading a fresh install and install that to a different directory. Note that any changes to the ExampleRoutine.cs file will be overwritten, so either make a copy, or set it to read only (installer will throw an error but it will complete)

wimm
 
I'll need a full log for the last error you posted.

I can't replicate your issue with maps. The default filter should pick them up just fine without any modifications. Here's an easy test though:
* Go to the Coast, through the Lioneye's Watch exit
* Change your grind zone to this area, make sure you match the difficulty.
* Drop a map, and start the bot.

If it loots the map, then the issue you saw before was just the bot needing to do something else first before looting that map. If it doesn't loot the map, then there's another issue with your filters.

First the Log:
http://filebin.ca/1m6H405X2GIR/Exilebuddy45922014-12-2714.03.txt

and I played with the map Filter settings. Works fine now.

well, looking like a mess. The error '"[Logic] UseAt returned InvalidSlot."' is because you have nothing selected for the 'Fallback skill slot", so when your character runs out of mana, there is no default 'fallback' default attack, and thus the error. Suggest setting that slot number to your default attack.

As for the rest, itemfilter and all, I suggest downloading a fresh install and install that to a different directory. Note that any changes to the ExampleRoutine.cs file will be overwritten, so either make a copy, or set it to read only (installer will throw an error but it will complete)

wimm

Yeap. I think that was it... Thanks :3
 
Thanks for the log. I think it might be fixed in the next version. A location was being added more than once rather than being updated if it already existed.
 
Back
Top