Testing status

Release 1.0 is intended to be a solid levels 1 to 15 experience for both factions and all six classes. This page states how far that has been tested, the bar the release must meet, and how to help. The figures are rebuilt from the published test reports each time they change.

Strict runs of the current bot, one per lane. The latest round used a time budget of 8 h per lane. The newest run is dated 28 October 2026.

State: release 1.0 is not yet met. 12 of 12 lanes can level from level 3 to 15; 12 of 12 lanes have a confirming run that reached level 15 within 8 h (1 of them assembled from segments).

The release bar for 1.0

Release 1.0 is met when each of the four parts below is true. A bug budget, reported after them, is information and not a condition.

1. Levelling. Every class of both factions can get from the start level to level 15. For each of the 12 lanes (6 classes on 2 factions) there is evidence of every level transition, from level L to level L + 1 for every L from the start level up to 14, from full runs or from drills. A lane is clear when all its transitions are evidenced. Runs made with the test-only time scale never count. A transition that only a run with overkill gear made is shown as "mechanic works": it counts toward clearing the lane, and the table says which transitions have no evidence at level. A stuck main-story quest, or a quest that is the only way forward in a level band, appears here as a gap: a transition that no run could make.

The evidence is pooled across runs of all bot versions, and the newest run behind each lane is shown; the confirming runs (part 2) check the release candidate itself. The automated runs start at level 3, the veteran start. Levels 1 and 2 (the New Player Experience) are built separately and are not part of these runs, so this part measures levels 3 to 15 and does not cover levels 1 and 2.

Where it stands: 12 of 12 lanes can level from level 3 to 15 on the pooled evidence; 12 of 12 have done the whole climb in a single run (the newest of those is dated in the table below). Met on the pooled evidence; the confirming runs in part 2 check it on the release candidate.

2. Confirming runs. Each of the 12 levelling lanes (6 classes on 2 factions) then has one full run that reaches level 15 within a time budget of 8 h, at the final release candidate. A lane that does not is acceptable only when each miss is attributed, with evidence, to the test bot, the test hosts or the time budget, never to the game and never left unexplained. Runs with a shorter budget, such as the 4 h regression check, do not count toward this part.

Where it stands: 12 of 12 lanes have a confirming run that reached level 15 (bot revisions 13 to 14, budget of at least 8 h) (1 of them assembled from segments). Met.

3. No blockers. No open priority-one server bug, and no stuck quest that is the main story or the only way forward in a level band. The second condition is covered by part 1, where it shows as a lane gap.

Where it stands: not yet recorded on this page.

4. Manual retest. The maintainers' manual client retest of quests, combat and travel is clean.

Where it stands: not yet recorded on this page.

Bug budget (information, not a condition). The number of quests on the 1 to 15 path that are attempted and stuck in the coverage matrix and that no run has completed, per faction. The matrix lists them under "Known broken quests (bug budget)". The matrix itself is detailed evidence and is not the release bar.

Where it stands: Exile 7; Dominion 12; 19 in all.

Published rounds

A round is one bot revision, with its newest run of each lane. Only a round with a time budget of at least 8 h counts as a confirming run (part 2); a shorter round is a regression check for comparing builds.

Lanes in the latest round

Time budget 8 h per lane.

Lanes assembled from segments

A lane run as segments is proven from level 3 to 15 when each contiguous segment covering that range has a run on the current bot revision (14) that reached its end level; the newest such run of a segment is used. Each segment was run by a character raised to its start level by a test command. An assembled lane counts with the lanes that can level and the lanes with a confirming run.

How the game is tested

Three kinds of testing feed this page.

Automated levelling runs. A scripted character for each class and faction starts at level 3 and plays toward level 15: it takes quests, fights, loots, equips upgrades and hands quests in. Each quest it cannot finish, and each place it gets stuck, is recorded with its cause. A round is twelve runs, one per lane. Several of these test players can share one game server, which lets the project run many more of them at once (see Engineering notes). The release bar asks for evidence of every level transition from level 3 to 15 (from full runs or drills) and then one confirming run per lane with an eight-hour budget; rounds with a four-hour budget are regression checks for comparing builds. The runs play the Soldier path. The method and the results are on the levelling tests page, and each run has a report.

Automated test suites. The server's test suites run against every change. A separate data check reads every quest of the release zones and confirms that the server has everything each quest needs. A play-through then starts a test character, takes it to each quest and plays the quest to the hand-in. The results are on the where we stand page.

Manual play. The maintainers play the game in the real WildStar client on a test server to check quests, combat and travel.

What automation does not cover

The automated player sends the game's messages to the server directly. It skips the checks the real client makes before it sends them: whether a character may talk to someone, click an object or use an ability. Automation also cannot judge the client's behaviour, graphics, sound or how the game feels. Those are checked by people playing. A quest that a scripted character finishes can still be blocked for a player, so please report anything that does not respond.

Open known issues

Known issues are listed by kind. The counts for each kind are on the where we stand page.

• Quests the automated player cannot finish. Some are limits of the test player and some are faults in the game. A few quests in the early zones are in this group. See the levelling tests and where we stand.
• Quest content not yet placed in the world. A character, creature or object that a quest needs is missing from the world. See where we stand.
• Objectives and spell effects the server does not run yet. See where we stand and the semantic registry.
• Behaviour of the real client. Anything only the client shows is not yet covered by automation. See above.
• Platforms not yet tested. Steam Deck and Mac, as listed below.

Platform status

Supported means fully tested. In testing means the platform works on the configurations listed, and more reports are wanted. Untested means the platform has not yet been run.

Help us test

1. Play, and report what you find. In the game, use the Field Kit's Report a problem, or type /c bug in chat and follow the questions (how reporting works). You can also open a GitHub issue.
2. Test a platform. If you have a Steam Deck, a Mac, or a Linux system other than Arch, follow its guide in the table above and report the result, including the steps that did not work.
3. Retest. A retest list for testers is not yet published.

A useful report says:

• where you were: the zone, and the quest or area name;
• what you did, step by step, and what you expected to happen;
• what happened instead, including any message the game showed;
• your faction, class and path, and your platform;
• whether it happens every time.