At a glance
Quick facts
- Health
- 2,800
- Experience
- 1,900
- Speed
- Not published
- Race
- stabilizingdreadintruder
- Attacks
- Exact cycle not published
- Loot entries
- 7
- Bestiary class
- Official Library
- Reference profile
- Current official library
- Official profile observed
- 2026-08-02
Reading the Stabilizing Dread Intruder encounter
On paper, Stabilizing Dread Intruder is 2,800 health and 1,900 experience. In a corridor, those numbers gain teeth through an attack cycle that the public library does not expose, no single movement flag that tells the whole encounter story, and the terrain around the spawn.
Stabilizing Dread Intruder's clearest weakness lead is Holy and Physical. 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.
Stabilizing Dread Intruder's official profile names energy bars among its possible loot without publishing a probability. That is enough to identify a reward, but not enough to promise profit or calculate an expected return.
Stabilizing Dread Intruder statistics and identity
Stabilizing Dread Intruder is listed by the current official creature library with 2,800 hitpoints and 1,900 experience. The public library provides categorical strengths, weaknesses, status behavior, and named loot, but it does not publish movement speed, raw attack intervals, exact damage bounds, defense rolls, armor, spawn positions, or respawn intervals.
| Statistic | Value | Interpretation |
|---|---|---|
| Maximum health | 2,800 | Configured health pool |
| Base experience | 1,900 | Award before external multipliers |
| Speed | Not defined | Engine movement-speed input |
| Race | Not defined | Corpse and effect classification |
| Race ID | Not defined | Bestiary or protocol reference when present |
| Maximum configured attack bound | 0 | Largest absolute XML min/max value; not a guaranteed final hit |
| Official-library hitpoints | 2,800 | Current official profile |
| Official-library experience | 1,900 | Current official profile |
Behavior, targeting, and movement
The current official library publishes Stabilizing Dread Intruder as a 2,800 hitpoint creature worth 1,900 experience. Its published weakness categories are Holy, Physical. Its published strength categories are Death, Energy, Fire, Ice. It is listed as able to perceive invisible creatures. The public library does not expose attack intervals, raw damage bounds, movement speed, target-change chance, spawn density, or respawn interval, so those values must come from a server-specific primary source.
| Flag | Configured value |
|---|---|
| Summonable | No |
| Convinceable | No |
| Canseeinvisible | Yes |
Attack cycle and combat pressure
The official Stabilizing Dread Intruder library profile does not publish an exact attack cycle, raw minimum and maximum damage, range, area geometry, condition timing, or targeting logic. Those fields are intentionally marked as unpublished rather than estimated from anecdotes or another server's implementation.
Defense, elements, and immunities
The current official library identifies strong, weak, immune, and healing damage categories for Stabilizing Dread Intruder but does not publish exact percentages. Those qualitative labels are preserved exactly as categories. Converting "strong" or "weak" into a made-up numeric modifier would create false precision, so percentage math requires a separate verified game or server source.
| Defense layer | Value | Meaning |
|---|---|---|
| Death | Strong | Current official library category; no percentage published |
| Energy | Strong | Current official library category; no percentage published |
| Fire | Strong | Current official library category; no percentage published |
| Ice | Strong | Current official library category; no percentage published |
| Holy | Weak | Current official library category; no percentage published |
| Physical | Weak | Current official library category; no percentage published |
Complete configured loot table
The current official library names 7 possible Stabilizing Dread Intruder loot items but does not publish exact drop probabilities or stack ranges. The names are useful acquisition evidence; they must not be converted into fabricated percentages. An Open Tibia implementation can use a different list or deliver rewards outside the corpse.
| Item | Official evidence | Probability |
|---|---|---|
| energy bars | Named loot | No exact chance published |
| energy drinks | Named loot | No exact chance published |
| glistening bones | Named loot | No exact chance published |
| gold coins | Named loot | No exact chance published |
| platinum coins | Named loot | No exact chance published |
| solid rage | Named loot | No exact chance published |
| strange proto matter | Named loot | No exact chance published |
Hunting plan and server verification
A safe hunting recommendation for Stabilizing Dread Intruder 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. Obtain attack-cycle and spawn data from the target server, then test the encounter under controlled conditions. Present a level recommendation only with that profile and evidence attached.
- Confirm current health, experience, strength, weakness, immunity, and loot labels against the official creature profile.
- 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.
