Equipment & Itemssource backed6 minute read

Great fireball rune

Great fireball rune is documented as runes across 1 item identifier in pinned TFS 1.6 data, with XML attributes, exact configured drops, and current official creature-library loot mentions traced separately.

Reference profileTFS 1.6 item-data reference
Reviewed
Evidence2 primary references

At a glance

Quick facts

Classification
Runes
Identifiers
1 across 1 XML definitions
Item ID reference
2304
Defined attributes
4
TFS loot sources
0
Official loot mentions
0
Source profile
TFS 1.6

Great fireball rune in the hands of a player

Great fireball rune may occupy a single square in a backpack, but its source identity is wider: item ID 2304, 1 XML definition, and 4 declared attribute families.

Great fireball 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.

No indexed monster definition names Great fireball rune 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.

Great fireball rune identity and identifiers

Great fireball rune 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.

Great fireball rune source variants
Item ID or rangeArticleVariant attributes
2304aType: rune; Rune Spell Name: adori mas flam; Weight: 0.52 oz (52 source units); Charges: 4

Attributes and mechanical meaning

Great fireball rune is classified here as runes from its name and declared XML attributes. The configured charge count makes remaining uses part of the item state and should be checked after transfers or transformations. 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.

Great fireball rune normalized attributes
AttributeSource valueCoverage
Charges4Defined on 1 source entry
Rune Spell Nameadori mas flamDefined on 1 source entry
TyperuneDefined on 1 source entry
Weight0.52 oz (52 source units)Defined on 1 source entry

Acquisition and recorded loot sources

No monster XML file in the pinned profile lists Great fireball rune 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 Great fireball 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 Great fireball 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 Great fireball rune 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.

great fireball runeTFS 1.6Runes