At a glance
Quick facts
- Classification
- Fluids and fluid containers
- Identifiers
- 8 across 6 XML definitions
- Item ID reference
- 388, 389, 8573, 8575, 22571-22572, 39240-39241
- Defined attributes
- 4
- TFS loot sources
- 0
- Official loot mentions
- 0
- Source profile
- TFS 1.6
Lava hole in the hands of a player
An item name is only the surface. Beneath Lava hole sit 8 identifiers beginning with 388, a fluids and fluid containers classification, and 4 declared attribute families: Decay To, Description, Duration, and Fluidsource.
Lava hole belongs to a stateful item family. Contents, subtype, filling rules, empty-container behavior, and action scripts can matter more than the shared display name.
No indexed monster definition names Lava hole as direct corpse loot. The silence is useful because it narrows the next search to quests, NPC trades, map rewards, crafting, events, stores, and action scripts instead of encouraging an invented hunting route.
Lava hole identity and identifiers
Lava hole appears in the pinned item registry under 8 concrete identifier values. This page groups definitions that share the exact source name so readers can compare alternate graphics, transformation states, map variants, or legacy identifiers without treating each numeric ID as a different search topic. The identifiers are engine references, not proof that every Open Tibia server exposes every variant to players.
| Item ID or range | Article | Variant attributes |
|---|---|---|
| 388 | a | Description: It seems to be inactive. |
| 389 | a | Fluidsource: lava; Description: It emits heat and light. |
| 8573 | a | No XML attributes on this variant |
| 8575 | a | Decay To: 8573; Duration: 120 |
| 22571-22572 | a | No XML attributes on this variant |
| 39240-39241 | a | No XML attributes on this variant |
Attributes and mechanical meaning
Lava hole is classified here as fluids and fluid containers from its name and declared XML attributes. Decay attributes describe a timed state transition; private servers can change both the destination item and the duration. Exact behavior can be supplemented or overridden by the server binary, the OTB item registry, Lua actions, movement events, decay handlers, imbuement systems, or custom upgrade code.
| Attribute | Source value | Coverage |
|---|---|---|
| Decay To | 8573 | Defined on 1 source entries |
| Description | It seems to be inactive. | It emits heat and light. | Defined on 2 source entries |
| Duration | 120 | Defined on 1 source entries |
| Fluidsource | lava | Defined on 1 source entries |
Acquisition and recorded loot sources
No monster XML file in the pinned profile lists Lava hole as direct loot. That does not establish that the item is unobtainable. It may be awarded by a quest, NPC trade, map placement, reward chest, crafting system, action script, event, store, or custom content module. A server-specific guide should name one of those primary acquisition sources before presenting a method as verified.
Progression, use, and comparison
Evaluate Lava hole against alternatives in the same fluids and fluid containers class by comparing only attributes that the active server actually implements. For combat equipment, attack, defense, armor, elemental protection, skill modifiers, vocation restrictions, level requirements, charges, and weight can all change the practical result. For world objects and general items, the decisive behavior is more often an action, movement event, unique ID, or map placement that cannot be inferred from the display name alone.
- Confirm the live item identifier before importing Lava hole into an editor, script, reward, or shop.
- Compare XML attributes with the deployed OTB registry and any upgrade, tier, imbuement, or rarity layer.
- Trace acquisition through monster files, NPC scripts, quest scripts, reward containers, and map placements.
- Test equip, use, decay, trade, loss, and persistence behavior on the target server profile.
Reference boundary and change control
A correction to this entry should cite the exact deployed item definition, commit, server documentation, or reproducible live test. Screenshots can show appearance or a tooltip, but they do not independently prove hidden chance values, script branches, or database state. Keeping those evidence layers separate prevents a historical item ID or one server's custom value from being mislabeled as universal Lava hole behavior.
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.
