Qpart
Quest objectives to complete, mapped by quest ID and objective index.
- Formato del valor
- table
- Ámbito
- step
Las descripciones técnicas se conservan en su inglés original. Los nombres de los campos y los ejemplos de Lua no se modifican.
Ejemplos
Ejemplo de las fuentes. Sustituye los ID y valores según tu ruta; este sitio no ejecuta Lua.
Lua · 01
Qpart = { [12345] = { 1, 2 } }Funcionamiento y detalles
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. |
Action / Progression Options
An action waits for completion; a failed step condition skips the step. Use one main action per step.
Main actions
Use separate SellItems and Repair steps with the same coordinates; only one main action per step.