Equipment & Itemssource backed6 minute read

Glistening bone

Glistening bone is documented as general items across 1 item identifier 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
Evidence3 primary references

At a glance

Quick facts

Classification
General items
Identifiers
1 across 1 XML definitions
Item ID reference
26178
Defined attributes
1
TFS loot sources
0
Official loot mentions
1
Source profile
TFS 1.6

Glistening bone in the hands of a player

An item name is only the surface. Beneath Glistening bone sit item ID 26178, a general items classification, and 1 declared attribute family: Weight.

Glistening bone belongs to a broad item family, so its purpose cannot be read safely from the name alone. The registry, scripts, map, and target server rules complete the picture.

The current official creature library names Glistening bone among Stabilizing Dread Intruder's possible loot, but it publishes no percentage. That quiet distinction matters. A named possibility can guide a hunt; it cannot support a fabricated drop rate.

Glistening bone identity and identifiers

Glistening bone appears in the pinned item registry under 1 concrete identifier value. 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.

Glistening bone source variants
Item ID or rangeArticleVariant attributes
26178aWeight: 12.00 oz (1200 source units)

Attributes and mechanical meaning

Glistening bone is classified here as general items 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.

Glistening bone normalized attributes
AttributeSource valueCoverage
Weight12.00 oz (1200 source units)Defined on 1 source entry

Acquisition and recorded loot sources

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

Glistening bone current official loot mentions
CreatureEvidenceDrop chance
Stabilizing Dread IntruderNamed by the official creature libraryNo probability published

Progression, use, and comparison

Evaluate Glistening bone against alternatives in the same general items 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 Glistening bone 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 Glistening bone 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.

glistening boneTFS 1.6General items