Overwatch aimbot target priority: angle, distance or health?

One scene, three different choices

Imagine three eligible enemies: A is 2° from the crosshair at 30 metres with 80% health; B is 4° away at 15 metres with 60% health; C is 6° away at 25 metres with 20% health. Assume every player passes the same targeting filters. This example isolates priority, so movement and other conditions are held constant.

Smallest angle selects A, Closest distance selects B, and Lowest health % selects C. None of those settings means the best player to attack in every situation. They answer different questions. A nearby player can be farther from your crosshair, and the lowest-health player can require the largest aim movement.

Why the lowest-health player may still be ignored

Priority does not bypass the eligibility controls. In the same example, an aim FOV of 4° excludes C at 6°. Lowest health % then prefers B over A, because C is outside the permitted area. A maximum distance of 20 metres would also leave B as the only candidate in this simplified scene.

Before changing priority, check the aimbot FOV and maximum-distance settings. If a player is filtered out, choosing a different ranking rule cannot bring that player back. Likewise, changing the visual ESP range does not automatically change the aim range.

Health percentage also differs from raw health points. A player at 100 of 500 health has 20% remaining, while a player at 80 of 200 has 40%. Lowest health % prefers the first of those two eligible players even though the second has fewer absolute health points.

Target priority chooses a player; hitbox priority chooses an aim region

Target priority and hitbox priority are separate controls. The first ranks players. The second concerns the body regions considered on the chosen player. Choosing Head as Preferred does not mean the player nearest to your crosshair will automatically win target selection.

Open Hitbox priority to inspect the regions and their groups. With Best available, the menu describes Preferred, Backup and Last resort as an ordered fallback. Varied uses the configured groups differently. Set the player-selection rule first, then inspect the aim-point choices rather than changing both and guessing which caused a difference.

Why tracking can stay on the current target

Target priority is not the whole tracking policy. Trackbot → Aim & retention also has a Target control: Stay on target, Switch when better or Follow best. These choices govern retention and switching, so a tracking setup can keep its current target instead of immediately following whichever player has just become the highest-ranked candidate.

If your concern is switching between nearby players, inspect that Target control before repeatedly changing FOV or smoothing. FOV determines eligibility, priority ranks candidates, retention governs continued selection, and motion controls how aim follows the result. A smoother movement does not itself choose a different ranking rule.

The flickbot versus tracking comparison explains why a discrete flick and continuous tracking need different movement decisions.

Compare the setting without losing your baseline

In the interactive menu, choose a hero and action, then open Combat → Targets. Change Target priority from Smallest angle to Closest distance. Switch to the other action and check its value, then return. The selected action owns its targeting settings; changing one action is not an instruction to overwrite every action or hero.

Keep the same hero, action, FOV and distance when comparing priorities. Write down the reason for the change: nearer to the crosshair, nearer in the world, or lower health percentage. That gives the comparison a concrete purpose instead of treating every dropdown as another way to make aim stronger.

You can explore the targeting interface before choosing access. The Overwatch product page keeps the current feature presentation and available terms together.