Coverage matrix: the 1 to 15 quest path

This page is detailed, informational evidence. It is not the release bar. The bar for 1.0 is that every class of both factions can level from the start level to level 15, shown by evidence of every level transition, together with a confirming run per lane; see the testing status. This page lists every quest on the 1 to 15 path and shows, for each class and faction, whether a test run has completed it. Quests that are stuck and that no run has completed are counted as the bug budget below. The page is rebuilt from the published run reports by tools/day_one/coverage_matrix.py, so it shows what the runs have found and nothing else.

How to read this page

The path. A quest is on the path of a class and faction when its level is 1 to 15, a character of that class and faction can accept it at level 15 or below (the same checks the server makes: faction, class, minimum level, the quests it needs first and its prerequisites), and a player can get it from a creature that exists in the game, a communicator call, an item or the task list. Contracts, repeatable quests, quests that need a tradeskill and developer test rows are not on the path. This gives 609 quests for Exile and 609 for Dominion (197 are for both). 61 further quests of level 1 to 15 that a character could otherwise take have no source in the game data (no creature that exists, call or item gives them); the objective lint lists them.

The cells. Each row is a quest and each column a class.

As a check on the derivation, 3096 of the 3118 quests the runs completed (counted once per class and faction) are on the path of their class and faction.

The gear. A run is made with one of two gear modes, shown in the table of runs. A cell completed by a run with levelling gear (the character plays with the gear the game gives it) means the quest is doable at its level. A cell completed by a run with overkill gear (the character cannot be stopped by the creatures, and nothing the quest asks of the player is skipped) means only that the mechanic works; it says nothing about the level. Runs that predate the mode are levelling. The totals count both alike; the levelling pages count only levelling runs.

The evidence. Only strict-mode runs count: a new character played from its starting zone through the real protocol. A completed quest is one the server reported as completed. Reports of single-quest drills are not read yet. The runs behind a cell are listed in the last table before the quests, with their commit, bot revision and date.

Totals

The share is how much of the path the test runs have completed so far. It is not a measure of how much of the game works: a cell stays empty until a run reaches that quest, a stuck cell stays marked until a later run completes it (including after the problem was fixed), and runs of earlier versions of the test player count. New runs and single-quest drills move the numbers.

By class and faction:

Known broken quests (bug budget)

The quests of the path that are ATTEMPTED-STUCK for a class and faction and that no run has completed, counted per faction. A quest that a run of another class of the same faction has completed is not counted. The number is information about the state of the quest content; it is not a condition of the release bar.

Exile

Dominion

Runs behind the cells

Only runs that completed a quest of the path, or were blocked on one, are listed. A run that is not published yet is marked; its report will be published with the next round.

What blocked the quests

The blockers behind the S cells, by kind: the number of quests on which a run saw one.

Exile

609 quests. Ordered by level, then quest id.