Cape

Cape in the hands of a player

Every item carries two stories: what the player sees and what the server executes. For Cape, the second story begins with item ID 2654, 1 source definition, and Armor, Slot Type, and Weight.

Cape sits in a category where one armor value can dominate the conversation. A useful comparison also weighs slot competition, weight, elemental modifiers, vocation gates, and any upgrade layer the target server adds.

Yaga The Crone is the clearest configured acquisition lead for Cape in this profile, with a base roll of 68.00% 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.

Cape identity and identifiers

Cape 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.

Attributes and mechanical meaning

Cape is classified here as armor from its name and declared XML attributes. Its armor value contributes to the random armor block produced by the equipped armor slots. 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.

Acquisition and recorded loot sources

Cape is referenced by 7 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.

Progression, use, and comparison

Evaluate Cape against alternatives in the same armor 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 Cape 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 Cape behavior.