| Description | I see an issue with some completed-looking Lost Vale runs in the
public API/killboard data.
For a few runs, the public API data contains the final boss encounter,
`N'Kari, the Soul-Flayer`, as completed, but does not contain the first boss
encounter, `Ahzranok`, as completed/recorded.
In at least two of these cases, a player from the run has confirmed that
Ahzranok was killed. That makes this look like missing encounter tracking in the
API/backend data rather than a legitimately skipped boss.
This makes the run data difficult to use for timing and speed comparisons. Lost
Vale run time is sometimes measured from the start of the first boss encounter
to the end of N'Kari. If Ahzranok is missing, that timing window starts too
late and the run appears shorter than it really was, which makes it hard for
players trying to compare or beat run times.
Observed examples:
- https://killboard.returnofreckoning.com/instance-run/68155ff1-5564-4430-a430-029b93c53b42
- https://killboard.returnofreckoning.com/instance-run/bef1fe95-3d83-42b2-a6d1-311f26f1a825
- https://killboard.returnofreckoning.com/instance-run/cf6128f8-c3f4-447f-b262-7e7e2b33f177
Expected:
If Ahzranok was killed during a Lost Vale run, the API/killboard data for that
run should include the Ahzranok encounter as completed/recorded.
Actual:
The API/killboard data for these runs contains later encounters and N'Kari, but
no completed Ahzranok encounter. This causes the recorded encounter-window
duration to start too late and makes the run unsuitable for fastest-run
comparisons. |
|---|
