Absolute XP requirements
Step fields Grind, Level, MinLevel, MaxLevel and SkipForLvl also accept
{ level = N, xp = signedInteger }. This extends the existing level resolver;
numeric levels, fractional levels and named level profiles keep their behavior.
- Value shape
- not specified
- Scope
- step-level-requirement
Technical descriptions are preserved in source English. Field names and Lua examples are unchanged.
Examples
Source example. Replace IDs and values for your route; this website does not execute Lua.
{ Grind = { level = 3, xp = 325 } }, -- Level 3 with at least 325 XP
{ Grind = { level = 4, xp = -700 } }, -- At most 700 XP remaining before level 4
{ PickUp = { 123 }, SkipForLvl = { level = 3, xp = 325 } },Behavior & details
Forms shown in the documentation, not an exhaustive runtime schema. Constant runtime types are not inferred.
Absolute XP requirements
Step fields Grind, Level, MinLevel, MaxLevel and SkipForLvl also accept
{ level = N, xp = signedInteger }. This extends the existing level resolver;
numeric levels, fractional levels and named level profiles keep their behavior.
Absolute XP requirements
{ Grind = { level = 3, xp = 325 } }, -- Level 3 with at least 325 XP
{ Grind = { level = 4, xp = -700 } }, -- At most 700 XP remaining before level 4
{ PickUp = { 123 }, SkipForLvl = { level = 3, xp = 325 } },Absolute XP requirements
A positive offset counts XP into level; a negative offset counts backwards
from reaching level. Both values must be finite integers, with level >= 1.
The resolver uses the current client's UnitXPMax while the player is at the
relevant level, so the route does not embed another client's XP table. Thresholds
outside that level's XP range are clamped to its boundaries. Missing XP data
delays completion until the total becomes available. These structures apply to
step fields only, not route visibility conditions or BeLvl.