Enemy List

[1.8.186]

Fixed — out-of-combat enemies appearing on the list

Hostiles the player happened to be targeting, focusing, soft-targeting, mousing over, or whose pet was targeting them were being added to the list unconditionally as soon as they came into nameplate / interaction range — even when neither the player nor the mob was in combat. Same problem for hostiles being targeted by group members (party/raid frame targets), the player's pet, etc.

Root cause: scanDiscoveredEnemies() in EnemyListCore.lua routed all of those discovery paths through trackFromUnitId(), which only checks unitHostileEligible (attackable + alive). No combat check, so any hostile UnitID resolved by target / focus / softenemy / mouseover / pettarget got tracked the moment it was visible.

Fix:

• New helper trackFromFriendlyTargetIfEngaged(friendUnit) mirrors trackFromFriendlyTarget but routes the resulting <friend>target UnitID through trackFromUnitIdIfEngaged instead of the unconditional tracker.
• All target / focus / softenemy / mouseover / pettarget paths in scanDiscoveredEnemies now use trackFromUnitIdIfEngaged, which requires the hostile to be UnitAffectingCombat and to have either a threat relationship with the player or be targeting a group member.
• All party/raid/player/pet "target of friend" paths now use trackFromFriendlyTargetIfEngaged.
• boss1–boss5 tokens still use the unconditional trackFromUnitId — boss UnitIDs only populate during real boss encounters, where the engagement check would be redundant and the slight delay would hurt.

Effect: enemies you tab-target on the road, mouse over while exploring, or that simply enter nameplate range no longer pop onto the list until something actually engages them. Engaged mobs still appear immediately because the threat / target / CLEU paths feeding trackFromUnitIdIfEngaged already set those flags.