At a glance
Quick facts
- Classification
- Shields
- Identifiers
- 1 across 1 XML definitions
- Item ID reference
- 2541
- Defined attributes
- 3
- TFS loot sources
- 9
- Official loot mentions
- 0
- Source profile
- TFS 1.6
Bone shield in the hands of a player
Bone shield may occupy a single square in a backpack, but its source identity is wider: item ID 2541, 1 XML definition, and 3 declared attribute families.
Bone shield invites a simple defense comparison, but the useful question is situational: what is held in the other hand, which combat formula is active, and what offensive or utility option is surrendered for protection?
Necropharus is the clearest configured acquisition lead for Bone shield in this profile, with a base roll of 5.50% 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.
Bone shield identity and identifiers
Bone shield 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.
| Item ID or range | Article | Variant attributes |
|---|---|---|
| 2541 | a | Weight: 55.00 oz (5500 source units); Defense: 20; Weapon Type: shield |
Attributes and mechanical meaning
Bone shield is classified here as shields from its name and declared XML attributes. Its defense value contributes to the equipped weapon or shield defense calculation defined by the active engine. 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 |
|---|---|---|
| Defense | 20 | Defined on 1 source entry |
| Weapon Type | shield | Defined on 1 source entry |
| Weight | 55.00 oz (5500 source units) | Defined on 1 source entry |
Acquisition and recorded loot sources
Bone shield is referenced by 9 configured TFS monster loot entries 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 |
|---|---|---|---|
| Necropharus | 5.50% | 1 | 5500/100,000 |
| Tomb Servant | 5.30% | 1 | 5300/100,000 |
| Bonebeast | 2.00% | 1 | 2000/100,000 |
| Dreadbeast | 1.52% | 1 | 1520/100,000 |
| Dworc Fleshhunter | 1.03% | 1 | 1035/100,000 |
| Chakoya Tribewarden | 1.00% | 1 | 1000/100,000 |
| Crypt Shambler | 1.00% | 1 | 1000/100,000 |
| Chakoya Windcaller | 0.950% | 1 | 950/100,000 |
| Chakoya Toolshaper | 0.874% | 1 | 874/100,000 |
Progression, use, and comparison
Evaluate Bone shield against alternatives in the same shields 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 Bone shield 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 Bone shield 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.
