Burning Gladiator

Reading the Burning Gladiator encounter

On paper, Burning Gladiator is 10,000 health and 7,350 experience. In a corridor, those numbers gain teeth through 5 configured attack entries and a largest raw XML bound of 550, a preferred target distance of 4, and the terrain around the spawn.

Burning Gladiator's elemental profile rewards deliberate spell and weapon choices. The clearest weakness lead is Ice, while Physical, Fire, and Energy 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.

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

Burning Gladiator statistics and identity

Burning Gladiator is defined with 10,000 maximum health, 7,350 base experience, and speed 290 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. The current official library separately reports 10,000 hitpoints and 7,350, so differences remain visible instead of being silently merged.

Behavior, targeting, and movement

Burning Gladiator is configured as hostile and can enter combat without player initiation. Its target-distance setting is 4, so positioning and line-of-sight control matter more than they do against a purely adjacent attacker. Negative element modifiers identify increased incoming damage from Ice in this profile. Positive element modifiers reduce incoming Physical, Fire, Energy 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.

Attack cycle and combat pressure

Burning Gladiator 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.

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.

Complete configured loot table

Burning Gladiator contains 16 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 Burning Gladiator 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.