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

Easy workaround to prevent stucks in Keep Depths?

  • Thread starter Thread starter aalias
  • Start date Start date
A

aalias

Guest
Easy workaround in Giles to prevent stucks in Keep Depths?

Hi, just wondering if anyone has a workaround in Giles to prevent stucks in Keep Depths?

It happens always like this: when elite is detected by Giles through walls and the bot tries to walk through the wall and thus getting stuck.

I can think of a supposedly super easy workaround without complications (supposedly) - i.e. to limit the Giles's elite detection range to 3-5 just for the Keep depths. Given keep depths is mostly composed of narrow corridors, the effective combat range is about 3-5 pick up radius anyway. Basically a blind bot will literally run into elites because they will always be extremely close.

The problem is...I don't know how...

Can anyone help? Many thanks in advance..
 
Last edited by a moderator:
open the profile with notepad or notepad ++ and change this line

<ToggleTargeting questId="1" combat="True" looting="True" lootRadius="80" killRadius="45" />
 
open the profile with notepad or notepad ++ and change this line

<ToggleTargeting questId="1" combat="True" looting="True" lootRadius="80" killRadius="45" />

Kk thx, trying it now. So far no stuck due to excessive kill radius.
Will it override Giles's kill radius?
 
GilesTrinity obtains it's elite kill radius from the profile.

I thought trinity overrides it because it has it's own range system. It overrides the boss radius, that I know of. Not to sure if elites would be any different. I could be wrong though =)
 
I thought trinity overrides it because it has it's own range system. It overrides the boss radius, that I know of. Not to sure if elites would be any different. I could be wrong though =)

I could be wrong, but old monster priority changer simply used the profile values as a max - it's very possible it was changed in trinity
 
We need the auto-blacklisting feature. I remember using a plugin where if it is targeting a monster, and if the monster HP stays the same or doesn't receive any dmg for 10 seconds, it auto blacklist it temporarily for 25 seconds. That way, it can continue on with the script and if it encounters that monster at another time where it'll be more reachable, the 25 seconds would of past and will be unblacklisted so you can attack it again.

I wonder what plugin that was ><
 
We need the auto-blacklisting feature. I remember using a plugin where if it is targeting a monster, and if the monster HP stays the same or doesn't receive any dmg for 10 seconds, it auto blacklist it temporarily for 25 seconds. That way, it can continue on with the script and if it encounters that monster at another time where it'll be more reachable, the 25 seconds would of past and will be unblacklisted so you can attack it again.

I wonder what plugin that was ><

That'd be giles, something just broke it at some point :P
When he's better maybe he can fix it!
 
what radius should we swap to? is KillRadius 30 fine?

30 is too large for Keep depths. The problem is that the effective combat radius for bots to engage monsters is just 5-10 in Keep Depths levels, so the killradius should respond to that fact or it will keep running into walls because elites are detected through walls which bots can't pass.

You can even set killradius to 1 and your bot will run into 95% of monsters in Keep depths (exaggerated a bit)
 
30 is too large for Keep depths. The problem is that the effective combat radius for bots to engage monsters is just 5-10 in Keep Depths levels, so the killradius should respond to that fact or it will keep running into walls because elites are detected through walls which bots can't pass.

You can even set killradius to 1 and your bot will run into 95% of monsters in Keep depths (exaggerated a bit)

alright i guess i'll use the profile w/o keep depths 3 then lmao
 
Back
Top