Bestiary & Monsterssource backed10 minute read

Mazoran

Mazoran is a TFS 1.6 creature profile with 290,000 health, 50,000 experience, 6 configured attacks, and 30 loot entries. This reference traces behavior, elements, immunities, summons, and configured drops.

Reference profileTFS 1.6 monster-data reference
Reviewed
Evidence4 primary references

At a glance

Quick facts

Health
290,000
Experience
50,000
Speed
400
Race
fire
Attacks
6
Loot entries
30
Bestiary class
Not classified
Reference profile
TFS 1.6

Reading the Mazoran encounter

A bestiary number becomes meaningful only when it changes a decision. Mazoran brings 290,000 health, 50,000 base experience, 6 configured attack entries and a largest raw XML bound of 2500, and no single movement flag that tells the whole encounter story.

Mazoran'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.

Item 25172 has the strongest configured loot roll on Mazoran's TFS table at 100.00%, with up to 1 per successful entry. Profit, however, is a long conversation between kill speed, supply cost, route density, market demand, and the server's loot multiplier.

Mazoran statistics and identity

Mazoran is defined with 290,000 maximum health, 50,000 base experience, and speed 400 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.

Mazoran core statistics
StatisticValueInterpretation
Maximum health290,000Configured health pool
Base experience50,000Award before external multipliers
Speed400Engine movement-speed input
RacefireCorpse and effect classification
Race IDNot definedBestiary or protocol reference when present
Maximum configured attack bound2500Largest absolute XML min/max value; not a guaranteed final hit

Behavior, targeting, and movement

Mazoran 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. 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.

Mazoran behavior flags
FlagConfigured value
SummonableNo
AttackableYes
HostileYes
IllusionableNo
ConvinceableNo
PushableNo
CanpushitemsYes
CanpushcreaturesYes
TargetdistanceYes
Staticattack90
RunonhealthNo
IsbossYes
CanwalkonenergyYes
CanwalkonfireYes
CanwalkonpoisonYes

Attack cycle and combat pressure

Mazoran has 6 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.

Mazoran configured attacks
AttackChance and intervalRaw damage rangeRange or areaEffects
MeleeEvery 2 seconds0-2500Adjacent or script-definedNo extra XML effect attribute
Fire20% per 3 seconds500-100010Area Effect: fire
Speed25% per 2 seconds0-07Area Effect: redshimmer
Fire15% per 2 seconds300-7005Area Effect: fire
Death20% per 2 seconds500-80010Area Effect: explosion
Fire20% per 2 seconds500-8008Area Effect: fireattack

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.

Mazoran defensive profile
Defense layerValueMeaning
Armor25Base defense profile
FireImmuneCondition or damage immunity
InvisibleImmuneCondition or damage immunity
DrunkImmuneCondition or damage immunity
ParalyzeImmuneCondition or damage immunity

Complete configured loot table

Mazoran contains 30 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.

Mazoran loot
ItemItem IDBase chanceMaximum count
Item 2517225172100.00%1
Item 184191841923.00%5
Item 184201842023.00%5
Item 184211842123.00%5
Item 2143214312.00%8
Item 2146214612.00%9
Item 2148214849.00%100
Item 2148214849.00%100
Item 2150215010.00%5
Item 215221528.00%58
Item 215521551.00%1
Item 215821581.00%1
Item 216721674.00%1
Item 243224323.00%1
Item 25416254160.500%1
Item 254225420.500%1
Item 25522255220.500%1
Item 25523255230.500%1
Item 6500650011.00%1
Item 738273821.00%1
Item 7590759023.00%5
Item 7632763214.00%5
Item 7633763314.00%5
Item 789078901.00%1
Item 789478941.00%1
Item 789978991.00%1
Item 8472847246.10%5
Item 8473847323.00%5
Item 9970997010.00%8
Item 997199713.00%1

Hunting plan and server verification

A safe hunting recommendation for Mazoran 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.

MazoranTFS 1.6 monstersfire