At a glance
Quick facts
- Health
- 480,000
- Experience
- 75,000
- Speed
- 250
- Race
- Not defined
- Attacks
- 0
- Loot entries
- 49
- Bestiary class
- Not classified
- Reference profile
- TFS 1.6
Reading the King Zelos encounter
Before a player meets King Zelos on the map, the source profile already sketches the encounter: 480,000 health, 75,000 experience, no attack entry in the primary monster file, and no single movement flag that tells the whole encounter story.
King Zelos's elemental profile rewards deliberate spell and weapon choices. The clearest weakness lead is no published elemental weakness, while Physical, Energy, and Fire carry positive resistance in this source. Pull size, line of sight, neighboring creatures, and simultaneous attack timing still decide whether that theoretical edge survives contact with the spawn.
crystal coin has the strongest configured loot roll on King Zelos's TFS table at 100.00%, with up to 8 per successful entry. Profit, however, is a long conversation between kill speed, supply cost, route density, market demand, and the server's loot multiplier.
King Zelos statistics and identity
King Zelos is defined with 480,000 maximum health, 75,000 base experience, and speed 250 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 | 480,000 | Configured health pool |
| Base experience | 75,000 | Award before external multipliers |
| Speed | 250 | Engine movement-speed input |
| Race | Not defined | Corpse and effect classification |
| Race ID | Not defined | Bestiary or protocol reference when present |
| Maximum configured attack bound | 0 | Largest absolute XML min/max value; not a guaranteed final hit |
Behavior, targeting, and movement
King Zelos 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. Positive element modifiers reduce incoming Physical, Energy, Fire damage before final health loss. 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 |
|---|---|
| Attackable | Yes |
| Hostile | Yes |
| Summonable | No |
| Convinceable | No |
| Illusionable | No |
| Isboss | Yes |
| Ignorespawnblock | No |
| Pushable | No |
| Canpushitems | Yes |
| Canpushcreatures | Yes |
| Staticattack | 90 |
| Targetdistance | Yes |
| Canwalkonenergy | Yes |
| Canwalkonfire | Yes |
| Canwalkonpoison | Yes |
Attack cycle and combat pressure
King Zelos has no attack entry in this XML definition. It may be non-combatant, invulnerable scenery, a scripted encounter object, or a creature whose behavior is delegated elsewhere. Do not invent a damage profile when the primary definition does not provide one.
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 | 10 | Base defense profile |
| Physical | 10% | Resistance |
| Energy | 3% | Resistance |
| Fire | 5% | Resistance |
| Paralyze | Immune | Condition or damage immunity |
| Invisible | Immune | Condition or damage immunity |
| Drunk | Immune | Condition or damage immunity |
Complete configured loot table
King Zelos contains 49 flattened loot entries. Base chance is shown against the TFS 100,000-point scale, where 100,000 means 100% before external loot multipliers. Count maximum is the upper stack bound when a successful roll creates a stackable item. Nested container contents are preserved as individual rows in the source data.
Hunting plan and server verification
A safe hunting recommendation for King Zelos 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.