Official media referenceDirect answer
The official closed-playtest report cited more than 11,000 testers, an average session of 1 hour 23 minutes, 94% positive feedback and an 8.6/10 score.
How to use this page
These are developer-reported survey statistics from a pre-release build. They describe test reception, not verified launch review scores.
What is verified
- Label every statistic as developer-reported.
- Do not combine playtest approval with Steam user-review percentages.
- The demo and launch builds added content after the closed test.
- Use the report to trace design changes, not to guarantee final quality.
Evidence scope
Verified against sources on August 14, 2026The closed-playtest page records developer-reported reception metrics and explains how to use them without confusing pre-release feedback with launch review scores. It also identifies what a playtest can and cannot validate.
The reported numbers
The official closed-playtest report cited more than 11,000 testers, an average session of 1 hour 23 minutes, 94% positive feedback and an 8.6 out of 10 score. These numbers are useful evidence that the slice attracted attention and that the surveyed audience responded well. They are developer-reported, tied to a pre-release build and not directly comparable with Steam's later review percentage.
- Label the source as a developer report.
- Keep the sample, build and question wording visible.
- Never convert 8.6/10 into a launch review score.
What a playtest is good at
A playtest is strong at finding onboarding friction, control confusion, crash cases, mission blockers and the first-hour pacing. Repeated player sessions can reveal whether a goal is readable or whether a camera state is confusing. It is weaker at proving late-campaign economy, long-term class balance, endgame repetition and the durability of a save after many missions.
- Use playtest feedback for first-session problems.
- Seek longer runs for campaign economy claims.
- Check whether reported fixes reached the current build.
How to read a playtest report
First identify who collected the data, when it was collected and what the question asked. Then separate participation metrics from satisfaction metrics: the number of testers tells you reach, while a positive percentage tells you about the respondents' answer. Finally compare the report with patch notes and launch footage. A strong guide preserves the original statistic and adds the later status instead of quietly replacing one with the other.
- Record collection date and build.
- Distinguish reach, completion and satisfaction.
- Add later patch context without rewriting the original result.
Playtest evidence checklist
- Mark every statistic as pre-release and developer-reported.
- Record the build and collection date.
- Separate positive feedback from player count.
- Compare reported issues with later patch notes.
- Do not use playtest data as a guarantee of campaign quality.
Frequently asked questions
How many people joined the Warhounds playtest?
The developer-reported figure was more than 11,000 testers. It is not a unique verified player count for the released game.
Was the 8.6 score a Steam score?
No. It was a score reported for the pre-release playtest feedback and should not be presented as a Steam user-review score.
What does 94% positive prove?
It shows the surveyed test audience responded positively to that build and survey. It does not prove every player will like the launch campaign.
Sources and verification
Official facts are separated from developer estimates and unverified community claims.