nextRoute
Follow-up route keys. Conditional entries must also pass the target route's selection rules.
- 值的格式
- table
- 適用範圍
- route
技術說明保留英文原文。欄位名稱與 Lua 範例維持不變。
範例
原始檔範例。請依照你的路線替換 ID 與數值；本網站不會執行 Lua。
nextRoute = { "Shared", { route = "Class", conditions = { Class = "MAGE" } } }nextRoute = {
"Forever-Shared-Route",
{ route = "Forever-Class-Route", conditions = { Class = "MAGE" } },
},已記載的參數
| 已記載的參數 | 行為與詳細資訊 | 值的格式 |
|---|---|---|
route | Shown in the source example; this does not establish a required field. | string |
conditions | Shown in the source example; this does not establish a required field. | table |
Class | Shown in the source example; this does not establish a required field. | string |
行為與詳細資訊
Forms shown in the documentation, not an exhaustive runtime schema. Constant runtime types are not inferred.
Route Definition Options
A file may register several independent APR.RouteQuestStepList["route-key"] = { ... } entries. Follow-up routes, prerequisites and prefabs reference these keys, not file names.
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. |
Resource conditions and Hardcore routes
Follow-up suggestions can mix existing string keys and conditional entries:
Resource conditions and Hardcore routes
nextRoute = {
"Forever-Shared-Route",
{ route = "Forever-Class-Route", conditions = { Class = "MAGE" } },
},Resource conditions and Hardcore routes
The target must pass normal route visibility requirements and the entry's
conditions must pass the existing step filter evaluator. This preserves class
branches without duplicating a complete route.