At a glance
Quick facts
- Classification
- Weapons
- Identifiers
- 1 across 1 XML definitions
- Item ID reference
- 7389
- Defined attributes
- 6
- TFS loot sources
- 0
- Official loot mentions
- 0
- Source profile
- TFS 1.6
Heroic axe in the hands of a player
An item name is only the surface. Beneath Heroic axe sit item ID 7389, a weapons classification, and 6 declared attribute families: Attack, Defense, Description, Extradef, and Weapon Type.
Heroic axe carries the promise of a stronger hit, but attack is only the first line of the decision. Handedness, skill type, range, defense, level gates, ammunition, speed rules, and elemental behavior shape how the weapon actually feels.
No indexed monster definition names Heroic axe 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.
Heroic axe identity and identifiers
Heroic axe 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 |
|---|---|---|
| 7389 | a | Weight: 61.00 oz (6100 source units); Defense: 24; Attack: 44; Weapon Type: axe; Extradef: Yes; Description: This axe is only granted to a scrapper of the Svargrond arena. |
Attributes and mechanical meaning
Heroic axe is classified here as weapons from its name and declared XML attributes. Its attack value participates in weapon damage calculations when the deployed server preserves this item definition. Its defense value contributes to the equipped weapon or shield defense calculation defined by the active engine. 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 |
|---|---|---|
| Attack | 44 | Defined on 1 source entry |
| Defense | 24 | Defined on 1 source entry |
| Description | This axe is only granted to a scrapper of the Svargrond arena. | Defined on 1 source entry |
| Extradef | Yes | Defined on 1 source entry |
| Weapon Type | axe | Defined on 1 source entry |
| Weight | 61.00 oz (6100 source units) | Defined on 1 source entry |
Acquisition and recorded loot sources
No monster XML file in the pinned profile lists Heroic axe 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 Heroic axe against alternatives in the same weapons 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 Heroic axe 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 Heroic axe 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.
