Equipment & Itemssource backed6 minute read

Shark teeth

Shark teeth 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
Evidence2 primary references

At a glance

Quick facts

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

Shark teeth in the hands of a player

The useful question about Shark teeth is not merely "what is its ID?" The registry answers with item ID 25305, then adds Description and Weight and a general items role that still depends on the deployed ruleset.

Shark teeth 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.

No indexed monster definition names Shark teeth 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.

Shark teeth identity and identifiers

Shark teeth 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.

Shark teeth source variants
Item ID or rangeArticleVariant attributes
25305Not specifiedWeight: 2.00 oz (200 source units); Description: They are engraved with tiny unholy glyphs.

Attributes and mechanical meaning

Shark teeth 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.

Shark teeth normalized attributes
AttributeSource valueCoverage
DescriptionThey are engraved with tiny unholy glyphs.Defined on 1 source entry
Weight2.00 oz (200 source units)Defined on 1 source entry

Acquisition and recorded loot sources

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

shark teethTFS 1.6General items