At a glance
Quick facts
- Classification
- Weapons
- Identifiers
- 1 across 1 XML definitions
- Item ID reference
- 22415
- Defined attributes
- 6
- TFS loot sources
- 0
- Official loot mentions
- 0
- Source profile
- TFS 1.6
Umbral master hammer in the hands of a player
An item name is only the surface. Beneath Umbral master hammer sit item ID 22415, a weapons classification, and 6 declared attribute families: Attack, Defense, Skill Club, Slot Type, and Weapon Type.
Umbral master hammer 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 Umbral master hammer 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.
Umbral master hammer identity and identifiers
Umbral master hammer 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 |
|---|---|---|
| 22415 | an | Weight: 160.00 oz (16000 source units); Defense: 34; Attack: 55; Weapon Type: club; Skill Club: 3; Slot Type: two-handed |
Attributes and mechanical meaning
Umbral master hammer 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. 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 |
|---|---|---|
| Attack | 55 | Defined on 1 source entry |
| Defense | 34 | Defined on 1 source entry |
| Skill Club | 3 | Defined on 1 source entry |
| Slot Type | two-handed | Defined on 1 source entry |
| Weapon Type | club | Defined on 1 source entry |
| Weight | 160.00 oz (16000 source units) | Defined on 1 source entry |
Acquisition and recorded loot sources
No monster XML file in the pinned profile lists Umbral master hammer 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 Umbral master hammer 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 Umbral master hammer 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 Umbral master hammer 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.
