Edit Door

The rhythm of Edit Door

Edit Door begins as a phrase, "aleta grav", but its real rhythm lives in requirements and recovery: no published minimum level, a cost not defined in this profile, no published individual cooldown, and no explicit vocation list.

Edit Door belongs to the language of ownership rather than combat. Access rights, house state, command parsing, and the deployed server's housing rules give the words their authority.

Edit Door'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.

Edit Door requirements and spell words

Edit Door is represented by 1 player-facing TFS registry entry. 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 conjuring entry and the resulting rune-use entry are separate mechanical actions even when they share the same public name.

Targeting, aggression, and execution

Registry flags determine whether Edit Door 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.

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.

Resource cost and cooldown economy

Evaluate Edit Door 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

Edit Door 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 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.