Bestiary & Monsterssource backed8 minute read

Tomb Servant

Tomb Servant is a TFS 1.6 creature profile with 475 health, 215 experience, 2 configured attacks, and 10 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
475
Experience
215
Speed
190
Race
undead
Attacks
2
Loot entries
10
Bestiary class
Undead
Reference profile
TFS 1.6

Reading the Tomb Servant encounter

Tomb Servant tells its story in pressure and reward: 475 health to overcome, 215 base experience to earn, and 2 configured attack entries and a largest raw XML bound of 130 to read before the first pull.

Tomb Servant'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 2230 has the strongest configured loot roll on Tomb Servant's TFS table at 49.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.

Tomb Servant statistics and identity

Tomb Servant is defined with 475 maximum health, 215 base experience, and speed 190 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.

Tomb Servant core statistics
StatisticValueInterpretation
Maximum health475Configured health pool
Base experience215Award before external multipliers
Speed190Engine movement-speed input
RaceundeadCorpse and effect classification
Race ID708Bestiary or protocol reference when present
Maximum configured attack bound130Largest absolute XML min/max value; not a guaranteed final hit

Behavior, targeting, and movement

Tomb Servant 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.

Tomb Servant behavior flags
FlagConfigured value
SummonableNo
AttackableYes
HostileYes
IllusionableNo
ConvinceableNo
PushableNo
CanpushitemsYes
CanpushcreaturesYes
TargetdistanceYes
Staticattack90
RunonhealthNo
CanwalkonenergyNo
CanwalkonfireNo

Attack cycle and combat pressure

Tomb Servant has 2 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.

Tomb Servant configured attacks
AttackChance and intervalRaw damage rangeRange or areaEffects
MeleeEvery 2 seconds0-130Adjacent or script-definedNo extra XML effect attribute
Lifedrain20% per 2 seconds40-557Area Effect: redshimmer

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.

Tomb Servant defensive profile
Defense layerValueMeaning
Armor30Base defense profile
DeathImmuneCondition or damage immunity
EarthImmuneCondition or damage immunity
InvisibleImmuneCondition or damage immunity

Complete configured loot table

Tomb Servant contains 10 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.

Tomb Servant loot
ItemItem IDBase chanceMaximum count
gold coinScript-defined41.00%100
gold coinScript-defined41.00%8
scarab coinScript-defined8.21%1
rotten meatScript-defined2.00%1
Item 2230223049.00%1
longswordScript-defined6.56%1
bone shieldScript-defined5.30%1
wormScript-defined25.32%12
half-digested piece of meatScript-defined1.00%1
fist on a stickScript-defined0.230%1

Hunting plan and server verification

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

Tomb ServantUndeadundead