At a glance
Quick facts
- Classification
- Usable and transforming items
- Identifiers
- 2 across 2 XML definitions
- Item ID reference
- 5791, 6566
- Defined attributes
- 3
- TFS loot sources
- 1
- Official loot mentions
- 0
- Source profile
- TFS 1.6
Stuffed dragon in the hands of a player
An item name is only the surface. Beneath Stuffed dragon sit 2 identifiers beginning with 5791, a usable and transforming items classification, and 3 declared attribute families: Decay To, Duration, and Weight.
Stuffed dragon is defined by what happens after the click. Charges, duration, decay targets, movement events, and action scripts can turn the same visible object into a tool, a timer, a reward, or a one-way transformation.
Pinata Dragon is the clearest configured acquisition lead for Stuffed dragon in this profile, with a base roll of 0.192% and a maximum stack of 1. That is a lead, not a promise: global loot rates, events, prey-style systems, custom callbacks, and a different deployed data pack can change the result.
Stuffed dragon identity and identifiers
Stuffed dragon 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.
| Item ID or range | Article | Variant attributes |
|---|---|---|
| 5791 | a | Weight: 8.50 oz (850 source units) |
| 6566 | a | Weight: 8.50 oz (850 source units); Decay To: 5791; Duration: 3 |
Attributes and mechanical meaning
Stuffed dragon is classified here as usable and transforming items 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 | 5791 | Defined on 1 source entries |
| Duration | 3 | Defined on 1 source entries |
| Weight | 8.50 oz (850 source units) | Defined on 2 source entries |
Acquisition and recorded loot sources
Stuffed dragon is referenced by 1 configured TFS monster loot entry and 0 current official creature-library mentions. Exact percentages below come only from the TFS 100,000-point loot scale, before any server-wide loot-rate multiplier, stamina rule, prey bonus, event modifier, or owner customization. Official library mentions are kept separate because that source does not publish a probability.
| Monster | Base chance | Maximum count | Source units |
|---|---|---|---|
| Pinata Dragon | 0.192% | 1 | 192/100,000 |
Progression, use, and comparison
Evaluate Stuffed dragon against alternatives in the same usable and transforming 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 Stuffed dragon 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 Stuffed dragon 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.
