BeLvl
Exact effective level check. The player must be at least this level, but below the next whole level.
- 值的格式
- number
- 作用范围
- step-condition, parallel-group-condition, next-route-condition, prefab-condition, route-availability-condition
技术说明保留英文原文。字段名称和 Lua 示例保持不变。
示例
源文件示例。请根据你的路线替换 ID 和数值；本网站不会执行 Lua。
BeLvl = 88行为与详情
Forms shown in the documentation, not an exhaustive runtime schema. Constant runtime types are not inferred.
Parallel reward groups
| Case | Required behavior / syntax |
|---|---|
| Ready, unturned-in quest | conditions = { IsQuestOnQuest = 93384, IsQuestReadyForTurnIn = 93384, IsQuestUncompleted = 93384 } |
| Reward available above a threshold | Use MinLevel, rather than BeLvl, and add Zones when activation should wait for a visit to the reward map. |
| Independent rewards | Use separate groups for independently available hand-ins; a single Done list waits for every quest. |
| Pending hand-ins | Automatic turn-ins listed in pending groups wait for activation; manual turn-ins and the modifier override remain available. |
| Side objectives | Use Fillers during other steps; add a Qpart before Done for unfinished objectives. |
| Character restrictions | Keep shared eligibility on the route; child steps and prefabs need only additional restrictions. |
Filters and Conditions
Conditions on the same table combine with AND. Use AnyOf for alternatives, AllOf for repeated predicates and Not to invert a whole condition table.
Filters and Conditions
| Scope | Supported conditions / result |
|---|---|
Steps and parallelSteps[].conditions | All filters below; group conditions control insertion, while a failed step filter skips that step. |
Route conditions: visibility | InterfaceVersion, InterfaceVersionExact, DontHaveSpell, IsQuestReadyForTurnIn, HasAchievement, DontHaveAchievement, Faction, Race, Class, ClassNot, Event, AlliedRace, IsQuestCompleted, IsQuestUncompleted. Failure hides the route. |
Route conditions: availability | Numeric Level, MinLevel, MaxLevel, BeLvl, plus ClassSpec and Zones. Failure disables the route. |
Route-level AnyOf | Alternatives use step filters; failure hides the route, including failures of nested level conditions. |
Conditional nextRoute / prefab entries | Use step filters; these affect the suggestion or prefab membership. |
Level requirement forms
| Form | Meaning / supported fields |
|---|---|
MinLevel = 10 | Whole level threshold. |
Grind = 87.5 | Level 87 with at least 50% XP progress. |
MinLevel = "MidnightDelves" | Named dynamic threshold from the configured active XP bonuses. |
Grind = { level = 3, xp = 325 } | Level 3 with at least 325 XP into that level. |
Grind = { level = 4, xp = -700 } | At most 700 XP remaining before level 4. |
Grind = { level = 60, xp = 0, questLogXP = { 4901, 4508 } } | Deducts the current rewards of listed, completed quests still in the player's log. Unknown XP, unfinished quests and already rewarded quests give no credit. |
SkipIfCooldown = { { itemID = 6948, operator = ">", seconds = 2, once = true } } | Skips this step when the item cooldown exceeds the threshold on entry. Use spellID for a spell. Omit once to monitor continuously, for example < 300 on a farming/waiting step. |
| Supported fields | Step Grind, Level, MinLevel, MaxLevel, SkipForLvl. Route-selection level thresholds remain numeric; BeLvl does not accept profiles or absolute XP tables. |
| Absolute XP validation | Finite integers: level >= 1, signed xp. Uses the current client's XP range for the relevant level; out-of-range targets clamp to its boundaries. Missing XP data delays completion. |
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.