Target Priority: fix for back and forth bug

[lmar 0]

I have noticed a patern in the back and forth problem. It seams that there are 2 targets. Target A is closer so the bot targets A but while navigating to A, target B comes into range. Since B is now closer, the bot changes targets to B but while navigating to B, Target A becomes closer so the bot then retargets to A creating a loop. If you added priority to the bots targets and diss allowed target change for the same or lower target priority, the bot would not retarget B when navigating to A because they would have the same priority. But, if it encountered a mob(higher priority) it would retarget.

 

An example list of target priorities, The mob priorities would be 0 if the mob is out of the item pick up safe range

1. nothing?
2. Unexplored
3. chest/pot
4. drop item (scroll currency/item)
5. white mob
6. blue mob
7. rare mob
8. unique/boss
9. Invincible aura mobs/shrine

Example:

Target unexplored(2)

chest - Target swited to chest(3)

new chest that is closer(3) - target remain origonal chest

white mob in range(5) - target switch to mob

drop item found(4) - target remain mob

mob dead - target closest next priority target( would be the drop item(4) since the chests are priority3

 

This would help with boss farming like dominus as well, because the rares first would be targeted first instead of the never ending stream of chaff. meelee splash like aoe would take care of the chaff. The only type of build where these priorities would not work would be an elem prolif build.

 

Just an idea.

Edited July 10, 2014 by lmar

[sumnjicav 0]

this happened to me a lot, especially on stairs 

[zr1 0]

yes it really happen sometimes