Often automaps the wrong hole when a k162 is taken

[Former user]

Leaving a system with 2 of the same connections often assumes the wrong connection has been taken, i assume it is not taking into consideration the possibility of a k162 leading to the same class as a named or static hole.

ie: i just left j130155, It had a k162 and its n110 static, both leading to HS, i took the k162 and it assumed and automatically mapped me as using the n110 instead which became quite a chore to clean up.

Perhaps to eliminate this, if there is ever a k162 in the system, it could verify the hole ?

[Josh Glassmaker]

Yes - the issue is K162s without any "Leads To" specified are not considered at all when jumping and there is another viable option. This seems to be a popular issue lately and probably worth a change in code to always consider K162s as possible jumps.

I'll see about getting this changed

[Josh Glassmaker]

Someone offered to make a flow chart of how this feature logic should work. Once someone can provide that and make sure at least a few others agree with it I can make those logic changes a few days later, So this ticket is now in the hands of anyone who wants to take on this task.

I haven't really played EVE in over a year so my logic on this feature is not sufficient (obvious from bugs with current implementation)