File Details
EnemyList 1.8.123.zip
- R
- May 7, 2026
- 161.30 KB
- 29
- 2.5.5
- Classic TBC
File Name
EnemyList 1.8.123.zip
Supported Versions
- 2.5.5
[1.8.123]
Changed
- Reduced idle CPU usage by tightening update gating around high-frequency loops.
EnemyListNameplateThreatpulsing maintenance (OnUpdate) now runs only when:- nameplate threat overlay is enabled,
- EnemyList combat context is active (
EnemyList.IsEnemyListCombatActive()), - and at least one pulsing threat overlay is visible.
EnemyListNameplateMirrormaintenance (OnUpdate) now skips work outside EnemyList combat context.- Party aggro-counter fast polling in
EnemyListUInow runs only while EnemyList combat context is active; out-of-combat polling is suppressed. - Combat behavior is unchanged; the optimization targets out-of-combat/background CPU overhead.
[1.8.122]
Added
- Max-duration filter for the player buff strip — Hides long buffs (Mark of the Wild, Power Word: Fortitude, blessings, Thorns, paladin auras, etc.) so the strip only shows the short-duration buffs you actually need to refresh: HoTs, shields, Prayer of Mending, Beacon of Light, etc.
- New profile key
partyPlayerBuffMaxDuration(default 60s, range 0–600s, step 5s). 0 disables the filter and shows every buff you cast. The filter also drops permanent buffs (duration == 0) when active. - Helper
_EL.partyPlayerBuffMaxDuration(). - Config UI: "Max buff duration" slider directly under the buff icon size slider in each Party / Raid panel. Format shows
Off/Ns/Nmdepending on value. - New locale strings
OPT_PARTY_PLAYER_BUFF_MAXDUR,TOOLTIP_OPT_PARTY_PLAYER_BUFF_MAXDUR,OPT_VAL_OFF.
Changed
updatePartyPlayerBuffsnow skips entries that fail the duration check before counting them against the slot budget — so a unit with 5 long auras and 3 HoTs still shows all 3 HoTs at the user's configured slot count.
[1.8.121]
Reverted
- Reverted the 1.8.120 aggro-counter fallback path. The new
layoutPartyColorByNamemap and the multi-tier fallback inpopulatePartyMemberAttacked(threatInfo.targetingPlayer + targetName) broke the addon load. Restored the original unit-token-only counter path. Will re-attempt with a safer approach (likely a separate file to keep the main chunk's local count headroom).
[1.8.120]
Fixed
- Aggro counter intermittently disappearing on party / raid frames —
populatePartyMemberAttackedonly counted an enemy toward a party member when the enemy had a valid unit token (entry.unit) AND that unit's..targetsuffix resolved. Both conditions fail constantly during normal play: CLEU-only mobs have no unit token, plates moving in/out of nameplate range churnentry.unit, andnameplateN..targetis unreliable on Anniversary. Result: counters flickered or stayed at 0 even when the enemy was clearly hitting someone. - Added two fallbacks. If the unit-token path doesn't resolve a color index, use
entry.threatInfo.targetingPlayer(count toward the player's slot — already computed by the core when scanning the enemy's target). If still nothing, look upentry.targetName(the string the core caches for who the enemy is attacking) in a newlayoutPartyColorByNamemap. - New
layoutPartyColorByNameis rebuilt alongsidelayoutPartyColorByGuidinrebuildLayoutPartyColorByGuid, populated fromUnitName("player")/UnitName("party1-4")/UnitName("raid1-40").

