Equipment & Itemssource backed6 minute read

Fur bag

Fur bag is documented as equipment 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
Equipment
Identifiers
1 across 1 XML definitions
Item ID reference
7343
Defined attributes
3
TFS loot sources
2
Official loot mentions
0
Source profile
TFS 1.6

Fur bag in the hands of a player

The useful question about Fur bag is not merely "what is its ID?" The registry answers with item ID 7343, then adds Container Size, Slot Type, and Weight and a equipment role that still depends on the deployed ruleset.

Fur bag earns an equipment slot only when its whole trade-off makes sense. A headline statistic matters, but so do weight, restrictions, secondary modifiers, loss risk, and the alternatives displaced by equipping it.

Barbarian Brutetamer is the clearest configured acquisition lead for Fur bag in this profile, with a base roll of 7.54% 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.

Fur bag identity and identifiers

Fur bag 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.

Fur bag source variants
Item ID or rangeArticleVariant attributes
7343aWeight: 8.00 oz (800 source units); Container Size: 8; Slot Type: backpack

Attributes and mechanical meaning

Fur bag is classified here as equipment from its name and declared XML attributes. The slot declaration controls where the item can be equipped and prevents it from occupying unrelated equipment slots. 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.

Fur bag normalized attributes
AttributeSource valueCoverage
Container Size8Defined on 1 source entry
Slot TypebackpackDefined on 1 source entry
Weight8.00 oz (800 source units)Defined on 1 source entry

Acquisition and recorded loot sources

Fur bag is referenced by 2 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.

Fur bag monster loot references
MonsterBase chanceMaximum countSource units
Barbarian Brutetamer7.54%17540/100,000
Barbaria1.00%11000/100,000

Progression, use, and comparison

Evaluate Fur bag against alternatives in the same equipment 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 Fur bag 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 Fur bag 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.

fur bagTFS 1.6Equipment