Official media referenceDirect answer
The pre-release playtest showed a promising cover-based tactics game, while the February demo expanded that slice with seven missions and a limited strategic layer.
How to use this page
A preview must remain version-labelled. Demo impressions can describe direction and controls, but launch balance, content volume and bugs require separate evidence.
What is verified
- The closed test focused on the opening tactical slice.
- The public demo added tutorials, combat missions and Free Play.
- Launch introduced the full campaign and economy.
- Any old numerical build advice should be re-tested after release.
Evidence scope
Verified against sources on August 14, 2026This preview page preserves the difference between the closed test, the public demo and the released build. It is useful for tracing how the opening tactical slice expanded, but old preview advice must not be presented as a launch guarantee.
What the early slice demonstrated
The pre-release materials established the game's core promise: deploy a squad, use cover and elevation, solve objectives with flexible action points, then carry casualties and equipment decisions into the strategic layer. That slice is enough to judge the control rhythm and tactical vocabulary. It is not enough to judge late-campaign economics, every mission, or long-term roster pressure.
- Use early footage to identify systems, not final balance.
- Trace what happens between deployment and recovery.
- Mark every conclusion with its build date.
Demo versus launch
The public demo was a larger sample than the closed test: it included two tutorials, five combat missions, named environments and a Free Play mode. The released game adds the complete campaign and a broader economy. This means a demo preview is valuable for onboarding and combat feel, while launch coverage is required for staffing, contracts, ship upgrades and the consequences of losing a mercenary.
- Label demo-only missions and modes.
- Do not reuse demo balance numbers in a launch guide.
- Use the full game to test the strategic layer.
How to use a preview before buying
A good preview answers narrow questions with visible evidence: Does the camera show cover clearly? Can the player understand action-point spending? Are mission goals readable? Does the ship screen explain recovery and staffing? It should not promise exact performance, content count or future console dates unless those claims are tied to a current official source. Treat preview as a decision aid, then confirm unstable facts on Steam.
- List the exact question each clip answers.
- Separate demonstrated features from planned features.
- Check the current store page for changed platform or language data.
Preview evidence checklist
- Identify whether the footage is closed test, demo or launch.
- Record visible systems and avoid inferring hidden numbers.
- Compare combat footage with a strategic-layer screen.
- Check current Steam data before making a purchase claim.
- Keep old preview text dated after patches.
Frequently asked questions
What did the Warhounds demo include?
The documented demo included two tutorials, five combat missions, named environments and a Free Play mode. Treat the list as demo scope, not the complete campaign.
Can the demo predict the full game?
It can indicate controls and tactical direction, but it cannot establish late-campaign balance, economy or every launch fix.
Why are old previews still useful?
They preserve development context and show how features changed. They become misleading only when their build date is hidden.
Sources and verification
Official facts are separated from developer estimates and unverified community claims.