parallelSteps[].repeatable
For a single UseItem action, allow a fresh activation after the previous action was passed and the conditions became false then true (for example, another book was received).
- Format de la valeur
- boolean
- Portée
- parallel-group
Les descriptions techniques sont conservées dans leur anglais d’origine. Les noms des champs et les exemples Lua sont inchangés.
Exemples
Exemple issu des sources. Remplacez les identifiants et les valeurs selon votre route ; ce site n’exécute pas de Lua.
Lua · 01
repeatable = trueFonctionnement et détails
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.
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. |