Part of a rune

Part of a rune in the hands of a player

Part of a rune may occupy a single square in a backpack, but its source identity is wider: 6 identifiers beginning with 27610-27615, 1 XML definition, and 0 declared attribute families.

Part of a rune turns inventory space into stored magic. Charges, level and magic-level gates, target rules, exhaustion, and the bound spell script determine the real value of each use.

The Blazing Time Guardian is the clearest configured acquisition lead for Part of a rune in this profile, with a base roll of 7.69% 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.

Part of a rune identity and identifiers

Part of a rune appears in the pinned item registry under 6 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

Part of a rune is classified here as runes 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

Part of a rune is referenced by 6 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 Part of a rune against alternatives in the same runes 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 Part of a rune 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 Part of a rune behavior.