Blue tapestry

Blue tapestry in the hands of a player

Every item carries two stories: what the player sees and what the server executes. For Blue tapestry, the second story begins with 4 identifiers beginning with 1870-1871, 3 source definitions, and Weight.

Blue tapestry 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.

Marid is the clearest configured acquisition lead for Blue tapestry in this profile, with a base roll of 2.56% 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.

Blue tapestry identity and identifiers

Blue tapestry appears in the pinned item registry under 4 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.

Attributes and mechanical meaning

Blue tapestry 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.

Acquisition and recorded loot sources

Blue tapestry 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.

Progression, use, and comparison

Evaluate Blue tapestry 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 Blue tapestry 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 Blue tapestry behavior.