Divine Barrage

The rhythm of Divine Barrage

Every cast tells two stories: the effect that flashes on screen and the decision that follows. Divine Barrage asks for 175 mana from Paladin, begins at level 70, and leaves 4 seconds before the same action is ready again.

Divine Barrage competes for a moment when damage matters more than every other available action. Range, area, target rules, resistance, PvP reduction, and the shared attack-group cooldown decide whether that moment is brilliant or wasteful.

Divine Barrage's official profile identifies Holy, but it does not publish executable formulas, area constants, target flags, or callback code. The omission is a boundary, not an invitation to fill the gap with a remembered value from another server.

Divine Barrage requirements and spell words

Divine Barrage is represented by the current official spell-library profile. The table records the published words, type, level, magic-level requirement when available, mana, soul cost, cooldown, and vocation access. Exact Open Tibia script bindings and formulas are intentionally left unclaimed when no TFS implementation maps to this spell.

Targeting, aggression, and execution

The current official profile identifies Divine Barrage as attack spells with instant activation type and Holy magic. It does not expose target flags, wall blocking, area constants, script callbacks, or protection-zone checks. Those implementation details require the target server's spell registry and scripts.

Damage, area, conditions, and formulas

The official library does not publish executable Lua, an engine formula, area constants, callback code, or raw scaling coefficients for Divine Barrage. The table therefore records the published magic type and marks script-only fields as unavailable. This avoids presenting a community estimate or a different server's implementation as current official math.

Resource cost and cooldown economy

Evaluate Divine Barrage by both immediate cost and opportunity cost. Mana and soul are paid when the relevant variant succeeds under the active rules, while the individual cooldown and group cooldown determine what can be cast next. Rune charges move part of that cost into preparation and inventory capacity. Premium, learned-spell, weapon, vocation, level, magic-level, target, range, and protection-zone checks can reject a cast before the effect executes.

• Compare individual cooldown with the shared spell-group cooldown.
• Separate rune-conjuring cost from rune-use requirements and remaining charges.
• Verify whether failed casts consume resources or establish cooldowns on the deployed engine.
• Test PvP reduction, protection-zone restrictions, wall blocking, and target legality independently.

Vocation access and tactical use

Divine Barrage is registered for Paladin in this profile. That list describes permission, not tactical value by itself. Damage and healing outcomes depend on the implementation formula, level, magic level, skills, target resistance, equipment modifiers, critical systems, server multipliers, and encounter geometry. A rotation guide should test those values on the exact server rather than importing official-world assumptions.

Verification checklist

1. 01

   Confirm the registry

   Compare the official words, group, type, level, mana, soul, cooldown, vocation, and premium facts with the current official library.

2. 02

   Read every bound script

   For an Open Tibia implementation, locate the deployed registry and script before claiming area, formula, condition, or target behavior.

3. 03

   Test boundary conditions

   Check minimum level, magic level, mana, soul, vocation, premium, range, walls, target legality, protection zones, cooldown groups, and charges.

4. 04

   Record observable output

   Measure results over controlled level, skill, equipment, resistance, and PvP cases before publishing calculated ranges.