Bestiary & Monsterssource backed8 minute read

Gozzler

Gozzler is a TFS 1.6 creature profile with 240 health, 180 experience, 2 configured attacks, and 10 loot entries. This reference traces behavior, elements, immunities, summons, and configured drops alongside current official library facts.

Reference profileTFS 1.6 data with current official comparison
Reviewed
Evidence7 primary references

At a glance

Quick facts

Health
240
Experience
180
Speed
190
Race
undead
Attacks
2
Loot entries
10
Bestiary class
Demon
Reference profile
TFS 1.6
Official profile observed
2026-08-02

Reading the Gozzler encounter

Before a player meets Gozzler on the map, the source profile already sketches the encounter: 240 health, 180 experience, 2 configured attack entries and a largest raw XML bound of 135, and no single movement flag that tells the whole encounter story.

Gozzler's elemental profile rewards deliberate spell and weapon choices. The clearest weakness lead is Physical, while Death and Holy 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.

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

Gozzler statistics and identity

Gozzler is defined with 240 maximum health, 180 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. The current official library separately reports 240 hitpoints and 180, so differences remain visible instead of being silently merged.

Gozzler core statistics
StatisticValueInterpretation
Maximum health240Configured health pool
Base experience180Award before external multipliers
Speed190Engine movement-speed input
RaceundeadCorpse and effect classification
Race ID523Bestiary or protocol reference when present
Maximum configured attack bound135Largest absolute XML min/max value; not a guaranteed final hit
Official-library hitpoints240Current official profile
Official-library experience180Current official profile

Behavior, targeting, and movement

Gozzler 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. Negative element modifiers identify increased incoming damage from Physical in this profile. Positive element modifiers reduce incoming Death, Holy 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.

Gozzler behavior flags
FlagConfigured value
SummonableYes
AttackableYes
HostileYes
IllusionableYes
ConvinceableNo
PushableNo
CanpushitemsYes
CanpushcreaturesYes
TargetdistanceYes
Staticattack70
RunonhealthNo
CanwalkonenergyNo
CanwalkonfireNo
CanwalkonpoisonNo

Attack cycle and combat pressure

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

Gozzler configured attacks
AttackChance and intervalRaw damage rangeRange or areaEffects
MeleeEvery 2 seconds0-110Adjacent or script-definedNo extra XML effect attribute
Lifedrain15% per 2 seconds32-1351Area Effect: redspark

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.

Gozzler defensive profile
Defense layerValueMeaning
Armor15Base defense profile
Death50%Resistance
Holy50%Resistance
Physical-5%Vulnerability
InvisibleImmuneCondition or damage immunity
DeathStrongCurrent official library category; no percentage published
HolyStrongCurrent official library category; no percentage published
PhysicalWeakCurrent official library category; no percentage published

Complete configured loot table

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

Gozzler loot
ItemItem IDBase chanceMaximum count
brown flaskScript-defined8.75%1
small sapphireScript-defined0.360%1
gold coinScript-defined52.50%70
dwarven ringScript-defined0.190%1
battle axeScript-defined3.10%1
sabreScript-defined8.25%1
morning starScript-defined5.00%1
serpent swordScript-defined0.250%1
clerical maceScript-defined0.900%1
plate shieldScript-defined10.00%1
Gozzler current official named loot
ItemOfficial evidenceProbability
gold coinsNamed lootNo exact chance published
plate shieldsNamed lootNo exact chance published

Hunting plan and server verification

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

GozzlerDemonundead