Summon Knight Familiar

The rhythm of Summon Knight Familiar

Summon Knight Familiar begins as a phrase, "utevo gran res eq", but its real rhythm lives in requirements and recovery: level 200, 1000 mana, 0 milliseconds, and no explicit vocation list.

Summon Knight Familiar earns its place by changing the shape of a problem rather than merely adding damage. Duration, condition immunity, positioning, group cooldowns, and party coordination determine whether that utility becomes memorable.

Summon Knight Familiar's official profile identifies utility or script-defined magic, 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.

Summon Knight Familiar requirements and spell words

Summon Knight Familiar 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 Summon Knight Familiar as support spells with instant activation type and no published damage type. 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 Summon Knight Familiar. 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 Summon Knight Familiar 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

Summon Knight Familiar has no vocation child in its registry entry. This can indicate a house command, general utility action, rune-use definition, or another spell whose permission is controlled outside the vocation list. Verify account state, access, premium requirements, and script checks before describing it as universally available.

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.