At a glance
Quick facts
- Health
- 26,000
- Experience
- 6,000
- Speed
- 320
- Race
- blood
- Attacks
- 5
- Loot entries
- 0
- Bestiary class
- Not classified
- Reference profile
- TFS 1.6
Reading the Azerus encounter
A bestiary number becomes meaningful only when it changes a decision. Azerus brings 26,000 health, 6,000 base experience, 5 configured attack entries and a largest raw XML bound of 2000, and 1 summon rule entry.
Azerus's clearest weakness lead is no published elemental weakness. With no additional positive elemental modifier recorded here, the practical hunt still turns on positioning, supply depth, neighboring creatures, and the target server's scripts rather than on one attractive damage label.
Azerus offers no direct corpse-loot entry in the available profile. If an encounter still awards something, the answer must be sought in a chest, action script, event controller, participation system, or another server-specific mechanism.
Azerus statistics and identity
Azerus is defined with 26,000 maximum health, 6,000 base experience, and speed 320 in TFS 1.6. The displayed experience is the creature definition's base value before stages, stamina, party sharing, boosts, prey, server rates, or event multipliers. Server owners can edit these values without changing the creature name.
| Statistic | Value | Interpretation |
|---|---|---|
| Maximum health | 26,000 | Configured health pool |
| Base experience | 6,000 | Award before external multipliers |
| Speed | 320 | Engine movement-speed input |
| Race | blood | Corpse and effect classification |
| Race ID | Not defined | Bestiary or protocol reference when present |
| Maximum configured attack bound | 2000 | Largest absolute XML min/max value; not a guaranteed final hit |
Behavior, targeting, and movement
Azerus is configured as hostile and can enter combat without player initiation. Its target-distance setting favors adjacent engagement, although configured beams, waves, or ranged attacks can still reach farther. The definition includes 1 summon rule entry, so target count and tile control can change during the encounter. Target-change chance, static-attack preference, push permissions, pathfinding, field walking, summons, and scripted abilities collectively determine behavior. The flags below are direct configuration values; they should be read together instead of treating one flag as a complete artificial-intelligence description.
| Flag | Configured value |
|---|---|
| Summonable | No |
| Attackable | Yes |
| Hostile | Yes |
| Illusionable | No |
| Convinceable | No |
| Pushable | No |
| Canpushitems | Yes |
| Canpushcreatures | Yes |
| Targetdistance | Yes |
| Staticattack | 85 |
| Runonhealth | No |
| Isboss | Yes |
| Summon | Chance | Interval | Limit |
|---|---|---|---|
| Rift Worm | 30% | Script-defined | Definition-wide limit |
Attack cycle and combat pressure
Azerus has 5 attack entries in its XML definition. Chance is evaluated within the listed interval by the engine; min and max values are source-level damage inputs and can be changed by scripts, armor rules, resistance, PvP modifiers, conditions, or custom combat callbacks. Range, radius, beam length, spread, target flags, and visual effects reveal the intended shape but do not replace a live positioning test.
| Attack | Chance and interval | Raw damage range | Range or area | Effects |
|---|---|---|---|---|
| Melee | Every 2 seconds | 0-900 | Adjacent or script-defined | No extra XML effect attribute |
| Manadrain | 10% per 2 seconds | 0-2000 | 7 | Shoot Effect: energy; Area Effect: poff |
| Manadrain | 15% per 2 seconds | 0-800 | 7 | Shoot Effect: fire; Area Effect: bigclouds |
| Death | 20% per 2 seconds | 0-524 | 7 | Shoot Effect: suddendeath; Area Effect: mortarea |
| Lifedrain | 10% per 1 seconds | 100-500 | 8 | Area Effect: sleep |
Defense, elements, and immunities
The defense profile separates base defense and armor from elemental percentages and explicit immunities. In TFS 1.6, a positive monster element percentage reduces incoming damage of that element, while a negative percentage increases it. Current official strength and weakness labels are shown as categories without inventing a percentage. Custom servers can change those values, bypass them in scripts, or add encounter phases.
| Defense layer | Value | Meaning |
|---|---|---|
| Armor | 40 | Base defense profile |
Complete configured loot table
Azerus has no loot entry in the available primary profile. A reward may still be delivered by a boss chest, storage action, event script, achievement, quest, participation system, or custom corpse callback, but this source does not support claiming a direct corpse drop.
Hunting plan and server verification
A safe hunting recommendation for Azerus must combine the available profile with spawn density, neighboring creatures, terrain, access, vocation, skills, equipment, supplies, latency, death penalty, and the target server's rates. No universal level bracket can be authenticated from a creature-library or monster XML record alone. Use the largest configured attack bounds as stress-test inputs, account for simultaneous attacks and summons, then verify the actual spawn. Present a level recommendation only with that profile and evidence attached.
- Confirm health, experience, attack intervals, and elemental modifiers against the deployed monster file.
- Inspect the map spawn file for count, radius, placement, and respawn interval; those values are not stored in this monster definition.
- Test line of sight, diagonal movement, field walking, target switching, fleeing, summons, and push behavior.
- Record corpse loot over a statistically meaningful sample before evaluating a customized loot rate.
- Publish the server profile and review date with any route, level range, profit estimate, or supply recommendation.
Apply the guide
Find servers using this profile
Server names, protocol labels, and map labels do not guarantee matching mechanics. Use these filters to find candidates, then verify the listing, owner documentation, and deployed ruleset.