Aim For Highest Bounty
|
|
I'm not exactly sure what's wrong, but for some reason whenever there's two bounties on my hitlist, it always goes after the lowest, even though it's set to aim for the highest one. I've reviewed the code and as far as I understand it, there's nothing wrong with it figuring out what the highest bounty is. Anybody else noticed the same issue? |
|
|
Same for me. |
|
|
The code has been wrong. I have been trying to mess with the hitlist code for a month but couldnt fix it. Basically aim for highest goes for the player at the end of the list, while first come first serve aims for the top of the list. It doesnt take bounty into account. |
|
|
I *think* that it has to do with
var highest_target;
|
|
|
Yep, that's it. To fix:
var highest = 0 must be moved just before the beginning of the for loop, ~41 lines higher. |
|
|
I still seem to aim for the last target in the list, instead of the highest target. Is anyone else noticing the same thing? |