Threat is the per-NPC priority state used to decide which eligible combatant an enemy attacks. This reference distinguishes aggro acquisition, hate accumulation, and target selection; the exact server-side numerical formula remains unpublished.
An NPC becomes aware of a player, pet, or party through proximity, social assistance, a hostile action, or encounter scripting.
The NPC tracks eligible combatants and their relative threat. Being on the list is distinct from currently being attacked.
The NPC normally attacks the highest-priority valid target it can pursue, subject to control effects and NPC-specific behavior.
Threat is accumulated on an NPC-specific hate list. Damage, explicit hate effects, healing, procs, pets, and positional mechanics can all alter that list, but EQL has not published one universal numeric coefficient table for every source.
Successful weapon damage and damaging combat abilities create threat for the acting character. Abilities such as Bash, Cleave, Frenzy, Backstab, Smite, and Reave can also have explicit behavior beyond their resolved damage.
Direct damage and each resolved DoT tick can create spell-derived threat. Spells with an explicit hate component, such as Terror effects, should be treated separately from ordinary damage.
Healing can create threat for the healer on enemies participating in the encounter. Exact coefficients, overheal treatment, and the distribution of group-heal threat remain unpublished.
Weapon procs, buff procs, Spellblade casts, and reactive effects add their own resolved spell or damage event. More proc attempts can therefore increase expected threat even when the weapon’s base damage is unchanged.
Total threat = explicit hate changes + resolved attack/spell/heal contributions + positional adjustmentsThe expression is a bookkeeping model, not a published coefficient formula.T4
Spell hate must be separated into at least three components: the spell’s resolved damage or healing, any explicit hate value encoded in the spell, and any aggro-position effect such as blur or a forced hate-list move. A resist can prevent the damage component while an unresistable hate spell may still perform its explicit function.
| Spell event | Threat implication | Important boundary |
|---|---|---|
| Direct damage | Creates threat when damage resolves | Exact damage-to-hate coefficient is unpublished |
| Damage over time | Can add threat over successive ticks | Tick ownership, refreshes, and partial-resist handling require logs |
| Explicit hate spell | Can add hate without relying on damage | Use the spell’s own effect description |
| Debuff or control | May create spell hate even with little or no damage | Exact per-effect values are not centrally published |
Stuns are among the most effective spell-based hate tools available to Paladin, Cleric, and Wizard packages. Their value is not limited to damage: a landed stun creates a control event and is widely observed to generate disproportionately high hate, which is why Paladin tank rotations commonly use Stun (level 28), Divine Stun (level 35 AA), and Holy Might (level 42) as recurring aggro tools. Clerics gain the same low-level Stun (level 2), followed by Holy Might (level 16) and Sound of Force (level 46); Wizards add stun-bearing damage spells such as Thunderclap (level 30). Exact EQL hate values by stun spell are not published. T3
Ranger Flame Lick (level 3) is another known high-hate spell. Its Mana cost and displayed damage are small, but current Ranger references and player testing describe Ranger snares, roots, and related spells as some of the class's best aggro tools. Flame Lick is therefore useful for establishing or refreshing aggro even when its direct damage contribution is negligible. T3
| Tool | Why it maintains hate | Operational use |
|---|---|---|
| Paladin stuns (Stun, Divine Stun, Holy Might) | High spell hate plus temporary control | Rotate stuns between weapon, Smite, Bash, and Taunt events |
| Cleric or Wizard stun spells | Adds high hate even when the class is not a conventional tank | Useful in hybrid tank builds or emergency target recovery |
| Stun procs | Add an independent proc event with control and threat | Strong tank-weapon or Spellblade choice where eligible |
| Ranger Flame Lick | Very low-cost cast with unusually high observed hate | Open with it or refresh it when weapon and archery threat are insufficient |
A stun resist or level-cap failure can change both control and threat behavior. Log testing should separate the cast's hate event from resolved damage and from the stun component.
The healer is the actor that receives healing-derived threat; the healed target does not automatically inherit that threat. EQL-specific coefficients for direct heals, HoTs, group heals, pet heals, and overhealing are not published.
A proc is an additional resolved event. Its threat can therefore include the proc spell’s damage, debuff, stun, heal, or explicit hate component in addition to the triggering swing’s normal threat.
Expected proc threat per minute ≈ proc attempts per minute × land rate × average threat per landed procThis model explains why DEX, attack frequency, and proc rate can affect threat. The exact hate assigned to an individual proc remains effect-specific and unpublished.T4
“Hate transfer” should not be used as a catch-all for every aggro change. Three different mechanisms can look similar in play:
Do not infer a numeric transfer merely because the NPC changes targets.
Pets act as separate combatants with their own attacks, spells, procs, and hate-list participation. Pet Taunt changes the pet’s attempt to control target position; it does not make the owner and pet one hate actor.
/pet taunt on|off controls pet Taunt behavior./pet back off is documented to clear the pet’s hate list, making it materially different from merely stopping attacks.Character uses Taunt against a valid target
Skill, target, and encounter rules resolve
Successful Taunt places the user at the top position
NPC reevaluates its valid target
Current references describe successful single-target Taunt as placing the user at the top of the hate list. Taunting while already the target does not create a guaranteed safety buffer above second place. The July 7 official update increased Taunt success rates, particularly against raid targets.T1
Area Taunt and movement abilities with fixed hate additions are separate mechanics and must not be generalized from ordinary Taunt.
Hate position and current target are related but not identical. A target can lead the list yet temporarily be unreachable, controlled, dead, feigned, or otherwise invalid; the NPC may then select another valid combatant without erasing the underlying list.
Relative hate determines the preferred target. Taunt and explicit hate effects alter this ordering.
Death, control states, range, pathing, encounter membership, and NPC scripting can make a listed target temporarily invalid.
When the current target becomes invalid or another combatant overtakes it, the NPC selects again.
Stances, buffs, abilities, or items may raise or lower generated hate. Apply them only to the source categories named by the effect.
More resolved damage or healing can indirectly change threat even when the effect has no separate hate modifier.
A missed attack or resisted spell usually loses the resolved-output contribution. Reliability therefore changes expected hate per minute.
Taunt, blur, Feign Death, and pet commands change list state or position rather than multiplying ordinary threat generation.