At a glance
Quick facts
- Spell families
- Instant and rune spells
- Requirement layers
- Level, magic level, mana or mana percent, soul, vocation, premium, learned state
- Cooldown layers
- Individual spell and shared group cooldowns
- Execution layers
- Words or item use, target resolution, eligibility, cost, combat object, effects, cooldown
The spell registry is a contract
The TFS spell registry connects a player-facing spell or rune to its script and requirements. A complete entry can define name, incantation, level, magic level, mana cost or percentage, soul cost, premium requirement, vocation access, aggression, target behavior, range, blocking rules, cooldown, shared group, charges, and whether the character must learn it. The script then defines area, damage type, formula, conditions, and visual effects.
| Field | Purpose | Common OT override |
|---|---|---|
| Words / rune ID | Selects the action | Custom incantation, hotkey, client opcode, or item mapping |
| Level / magic level | Progression gate | Rebirth, vocation rank, quest, prestige, or no gate |
| Mana / mana percent | Casting resource | Health, rage, energy, charges, cooldown-only systems |
| Soul | Secondary resource cost | Disabled, accelerated regeneration, custom resource |
| Cooldown / group | Individual and shared timing | Global exhaustion, attack exhaustion, vocation-specific groups |
| Aggressive | Enables combat and zone restrictions | Safe-zone exceptions or custom arena policy |
| Target / range / block walls | Resolves valid destination | Extended screen, floor targeting, smart targeting |
| Script | Formula, area, condition, visuals | Most custom-server identity lives here |
Requirement evaluation
- 01
Identify the action
Match spell words, rune item, target mode, and client action.
- 02
Validate character gates
Check vocation, level, magic level, premium, learned state, weapon, and custom storage requirements.
- 03
Validate world state
Check protection zone, aggression, floor, line of sight, range, secure mode, target type, and combat lock.
- 04
Validate resources
Confirm mana, soul, health, charges, ammunition, or custom resource.
- 05
Validate exhaustion
Check both the spell cooldown and every shared cooldown group.
- 06
Execute and charge
Run the script, apply damage or effect, consume resources and charges, and add cooldowns according to the implementation.
Damage and healing formulas belong to the script profile
A registry mana cost does not reveal output. Combat scripts can use level and magic level coefficients, weapon skill, maximum mana, current health, target health, fixed min/max values, or arbitrary Lua. They also choose damage type, area, whether armor or shields block, whether resistance is ignored, whether conditions apply, and whether the caster or top creature is targeted.
Value = random(Min(Level, MagicLevel, Skill), Max(Level, MagicLevel, Skill))- This is a structural pattern, not one universal Tibia formula.
- The exact coefficients and rounding must be read from the deployed script.
- Area, target, rune charge, and cooldown behavior can matter more than nominal maximum damage.
Cooldowns form a graph, not one timer
A cast can start an individual cooldown and one or more shared groups such as attack, healing, support, or special. Another spell may be ready individually but remain blocked by a shared group. Weapon attack speed, item-use exhaustion, movement delays, client prediction, and network latency create additional timing constraints outside the spell entry.
| Timer | Question |
|---|---|
| Individual spell | When can the same spell be cast again? |
| Primary group | Which other spells are blocked? |
| Secondary group | Does the cast also block support, healing, or special actions? |
| Item use | Can a potion, rune, or tool be used during the spell delay? |
| Attack cycle | Does casting reset, pause, or coexist with weapon attacks? |
| Client display | Does the visible icon match server authority under latency? |
Minimum complete spell entry
| Group | Fields |
|---|---|
| Identity | Name, words or rune item, family, vocation, profile version |
| Requirements | Level, magic level, mana, mana percent, soul, premium, learned, quest, weapon |
| Timing | Individual cooldown, every group cooldown, attack and item-use interaction |
| Targeting | Self, target, direction, area, range, floor, wall blocking, secure-mode behavior |
| Output | Damage or healing type, exact min/max formula, condition, duration, ticks, critical eligibility |
| Costs | Rune charges, ammunition, health, custom resource, reagents |
| PvP | Damage scaling, protection-zone rule, skull behavior, party/guild exceptions |
| Sources | Registry line, script file, engine profile, live test date |
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.