Equipment & Itemssource backed6 minute read

Ornamented fountain

Ornamented fountain is documented as fluids and fluid containers across 2 item identifiers in pinned TFS 1.6 data, with XML attributes, exact configured drops, and current official creature-library loot mentions traced separately.

Reference profileTFS 1.6 item-data reference
Reviewed
Evidence2 primary references

At a glance

Quick facts

Classification
Fluids and fluid containers
Identifiers
2 across 2 XML definitions
Item ID reference
6390, 23809
Defined attributes
1
TFS loot sources
0
Official loot mentions
0
Source profile
TFS 1.6

Ornamented fountain in the hands of a player

Ornamented fountain may occupy a single square in a backpack, but its source identity is wider: 2 identifiers beginning with 6390, 2 XML definitions, and 1 declared attribute family.

Ornamented fountain 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 Ornamented fountain 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.

Ornamented fountain identity and identifiers

Ornamented fountain appears in the pinned item registry under 2 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.

Ornamented fountain source variants
Item ID or rangeArticleVariant attributes
6390anFluid Source: water
23809anNo XML attributes on this variant

Attributes and mechanical meaning

Ornamented fountain is classified here as fluids and fluid containers from its name and declared XML attributes. The XML entry establishes the identifiers and attributes shown here, while interaction behavior can also come from the binary item registry, movement events, actions, and server scripts. 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.

Ornamented fountain normalized attributes
AttributeSource valueCoverage
Fluid SourcewaterDefined on 1 source entries

Acquisition and recorded loot sources

No monster XML file in the pinned profile lists Ornamented fountain 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 Ornamented fountain 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 Ornamented fountain 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 Ornamented fountain 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.

ornamented fountainTFS 1.6Fluids and fluid containers