Bestiary & Monsterssource backed8 minute read

Disgusting Ooze

Disgusting Ooze is a TFS 1.6 creature profile with 3,650 health, 3,700 experience, 0 configured attacks, and 0 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
3,650
Experience
3,700
Speed
260
Race
venom
Attacks
0
Loot entries
0
Bestiary class
Not classified
Reference profile
TFS 1.6

Reading the Disgusting Ooze encounter

On paper, Disgusting Ooze is 3,650 health and 3,700 experience. In a corridor, those numbers gain teeth through no attack entry in the primary monster file, no single movement flag that tells the whole encounter story, and the terrain around the spawn.

Disgusting Ooze'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.

Disgusting Ooze offers no direct corpse-loot entry in the available profile. If an encounter still awards something, the answer must be sought in a chest, action script, event controller, participation system, or another server-specific mechanism.

Disgusting Ooze statistics and identity

Disgusting Ooze is defined with 3,650 maximum health, 3,700 base experience, and speed 260 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.

Disgusting Ooze core statistics
StatisticValueInterpretation
Maximum health3,650Configured health pool
Base experience3,700Award before external multipliers
Speed260Engine movement-speed input
RacevenomCorpse and effect classification
Race IDNot definedBestiary or protocol reference when present
Maximum configured attack bound0Largest absolute XML min/max value; not a guaranteed final hit

Behavior, targeting, and movement

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.

Disgusting Ooze behavior flags
FlagConfigured value
PushableNo
CanpushitemsNo
CanpushcreaturesNo
Staticattack90
TargetdistanceYes
CanwalkonenergyNo
CanwalkonfireNo
CanwalkonpoisonNo

Attack cycle and combat pressure

Disgusting Ooze 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.

Disgusting Ooze defensive profile
Defense layerValueMeaning
Armor30Base defense profile
ParalyzeImmuneCondition or damage immunity
InvisibleImmuneCondition or damage immunity
DrunkImmuneCondition or damage immunity

Complete configured loot table

Disgusting Ooze has no loot entry in the available primary profile. A reward may still be delivered by a boss chest, storage action, event script, achievement, quest, participation system, or custom corpse callback, but this source does not support claiming a direct corpse drop.

Hunting plan and server verification

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

Disgusting OozeTFS 1.6 monstersvenom