At a glance
Quick facts
- Classification
- Weapons
- Identifiers
- 1 across 1 XML definitions
- Item ID reference
- 23544
- Defined attributes
- 5
- TFS loot sources
- 1
- Official loot mentions
- 0
- Source profile
- TFS 1.6
Moohtant cudgel in the hands of a player
Every item carries two stories: what the player sees and what the server executes. For Moohtant cudgel, the second story begins with item ID 23544, 1 source definition, and Attack, Defense, Slot Type, Weapon Type, and Weight.
Moohtant cudgel 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.
Moohtant is the clearest configured acquisition lead for Moohtant cudgel in this profile, with a base roll of 1.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.
Moohtant cudgel identity and identifiers
Moohtant cudgel 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 |
|---|---|---|
| 23544 | a | Defense: 21; Attack: 47; Weapon Type: club; Slot Type: two-handed; Weight: 85.00 oz (8500 source units) |
Attributes and mechanical meaning
Moohtant cudgel 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 | 47 | Defined on 1 source entry |
| Defense | 21 | Defined on 1 source entry |
| Slot Type | two-handed | Defined on 1 source entry |
| Weapon Type | club | Defined on 1 source entry |
| Weight | 85.00 oz (8500 source units) | Defined on 1 source entry |
Acquisition and recorded loot sources
Moohtant cudgel 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.
| Monster | Base chance | Maximum count | Source units |
|---|---|---|---|
| Moohtant | 1.56% | 1 | 1560/100,000 |
Progression, use, and comparison
Evaluate Moohtant cudgel 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 Moohtant cudgel 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 Moohtant cudgel 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.
