Spells & Combatsource backed10 minute read

Wild Growth Rune

Wild Growth Rune is documented as conjuring spells in TFS 1.6 with 2 registry entries, casting requirements, cooldowns, vocation access, and source-level behavior signals compared with the current official spell library.

Reference profileTFS 1.6 spell data with current official comparison
Reviewed
Evidence8 primary references

At a glance

Quick facts

Spell class
Conjuring spells
Words
adevo grav vita
Minimum level
27
Mana values
600
Vocations
Druid, Elder Druid
Combat types
Utility or script-defined
Reference profile
TFS 1.6
Official profile observed
2026-08-02

The rhythm of Wild Growth Rune

The words "adevo grav vita" are only the doorway into Wild Growth Rune. The registry adds level 27, 600 mana, 2 seconds, utility or script-defined magic, and Druid and Elder Druid.

Wild Growth Rune moves cost forward in time. Mana and soul are paid during preparation, inventory carries the result, and charges determine how many future decisions that preparation can support.

Wild Growth Rune's bound source exposes 0 direct implementation signals across combat types, areas, conditions, and formula declarations. That is enough to trace the intended machinery, but callbacks and shared helpers can still hold decisive math outside the immediate script.

Wild Growth Rune requirements and spell words

Wild Growth Rune is represented by 2 player-facing TFS registry entries. Instant entries define spoken words and casting requirements; rune entries define use requirements, rune item ID, charges, target rules, and their own execution script. A separate official-library table follows so current values can be compared without overwriting the Open Tibia implementation profile.

Wild Growth Rune casting requirements
Registry typeWords or activationLevelMagic levelManaSoulCooldownVocations
Instantadevo grav vita27Not defined6005Not definedDruid, Elder Druid
RuneRune use or script invocation278Not defined02 secondsDruid, Elder Druid
Wild Growth Rune current official requirements
TypeWordsLevelMagic levelManaSoulCooldownVocations
Runeadevo grav vita27860052 secondsDruid

Targeting, aggression, and execution

Registry flags determine whether Wild Growth Rune needs a target, uses the caster, follows direction, can cross distance, blocks on walls or solid objects, consumes charges, and counts as aggressive. The spell group also controls shared cooldown behavior. The execution script can add area geometry, combat types, conditions, callbacks, item creation, summons, or other effects that do not appear in the one-line registry entry.

Wild Growth Rune behavior registry
VariantGroupRangeTargetingAggressiveChargesScript
InstantsupportScript-definedScript-definedNoNot applicableconjuring/wild_growth_rune.lua
RuneattackScript-definedScript-definedYes or group default2attack/wild_growth_rune.lua

Damage, area, conditions, and formulas

The implementation signals below are extracted from pinned Lua scripts without guessing missing values. Combat tokens identify declared damage families, area constants identify reusable shapes, condition tokens identify status effects, and setFormula arguments expose formula declarations when the script uses the standard combat API. A callback can still calculate values elsewhere, so an empty formula cell means no direct declaration was detected rather than zero effect.

Wild Growth Rune source-level implementation signals
ScriptCombat typeAreaConditionsFormula declaration
conjuring/wild_growth_rune.luaNo direct combat type tokenTarget or script-definedNo condition token detectedNo setFormula call detected
attack/wild_growth_rune.luaNo direct combat type tokenTarget or script-definedNo condition token detectedNo setFormula call detected

Resource cost and cooldown economy

Evaluate Wild Growth Rune 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

Wild Growth Rune is registered for Druid, Elder Druid 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 name, words, IDs, requirements, cooldowns, groups, target flags, and script binding with the deployed spells.xml.

  2. 02

    Read every bound script

    Trace combat objects, areas, formulas, callbacks, conditions, created items, and helper modules used by each variant.

  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.

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.

Wild Growth RuneDruidConjuring spells