At a glance
Quick facts
- Classification
- Armor
- Identifiers
- 1 across 1 XML definitions
- Item ID reference
- 18405
- Defined attributes
- 5
- TFS loot sources
- 0
- Official loot mentions
- 0
- Source profile
- TFS 1.6
Prismatic legs in the hands of a player
Prismatic legs may occupy a single square in a backpack, but its source identity is wider: item ID 18405, 1 XML definition, and 5 declared attribute families.
Prismatic legs 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.
No indexed monster definition names Prismatic legs as direct corpse loot. The silence is useful because it narrows the next search to quests, NPC trades, map rewards, crafting, events, stores, and action scripts instead of encouraging an invented hunting route.
Prismatic legs identity and identifiers
Prismatic legs 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 |
|---|---|---|
| 18405 | Not specified | Weight: 71.00 oz (7100 source units); Armor: 8; Slot Type: legs; Absorb Percent Physical: 3; Skill Dist: 2 |
Attributes and mechanical meaning
Prismatic legs 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.
| Attribute | Source value | Coverage |
|---|---|---|
| Absorb Percent Physical | 3 | Defined on 1 source entry |
| Armor | 8 | Defined on 1 source entry |
| Skill Dist | 2 | Defined on 1 source entry |
| Slot Type | legs | Defined on 1 source entry |
| Weight | 71.00 oz (7100 source units) | Defined on 1 source entry |
Acquisition and recorded loot sources
No monster XML file in the pinned profile lists Prismatic legs as direct loot. That does not establish that the item is unobtainable. It may be awarded by a quest, NPC trade, map placement, reward chest, crafting system, action script, event, store, or custom content module. A server-specific guide should name one of those primary acquisition sources before presenting a method as verified.
Progression, use, and comparison
Evaluate Prismatic legs 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 Prismatic legs 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 Prismatic legs 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.
