Equipment & Itemssource backed6 minute read

Santa music box

Santa music box is documented as general items 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
General items
Identifiers
2 across 1 XML definitions
Item ID reference
22647-22648
Defined attributes
1
TFS loot sources
0
Official loot mentions
0
Source profile
TFS 1.6

Santa music box in the hands of a player

An item name is only the surface. Beneath Santa music box sit 2 identifiers beginning with 22647-22648, a general items classification, and 1 declared attribute family: Weight.

Santa music box 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 Santa music box 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.

Santa music box identity and identifiers

Santa music box 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.

Santa music box source variants
Item ID or rangeArticleVariant attributes
22647-22648aWeight: 7.50 oz (750 source units)

Attributes and mechanical meaning

Santa music box 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.

Santa music box normalized attributes
AttributeSource valueCoverage
Weight7.50 oz (750 source units)Defined on 1 source entry

Acquisition and recorded loot sources

No monster XML file in the pinned profile lists Santa music box 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 Santa music box 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 Santa music box 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 Santa music box 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.

santa music boxTFS 1.6General items