Official media referenceDirect answer
Two public no-commentary playtest recordings are indexed; the clearest dated walkthrough was published February 16, 2026 and must not be mistaken for the August 1.0 build.
How to use this page
The linked run is useful visual evidence for early objectives, UI and combat pacing. Because it is a playtest recording, launch mission scripting, balance and interface changes require newer footage.
What is verified
- Primary indexed run: MAD RENZY, February 16, 2026, labelled Playtest.
- A second public run by SoniX Gaming was published January 29, 2026.
- Use the objective panel and result screen as visual evidence, not the uploader description alone.
- Keep official trailers separate from community full runs and label the build.
Evidence scope
Verified against sources on August 14, 2026Two public no-commentary playtest recordings are indexed, including a clearer walkthrough published on February 16, 2026. These recordings are useful visual evidence for early objectives and UI, but they must not be mistaken for the August 1.0 build.
What a no-commentary run is good for
Without narration, the viewer can inspect the game's natural information flow: how objectives appear, how the player reaches cover, when the turn ends, what the result screen reports and how the next step is selected. This is particularly useful for checking whether the interface communicates enough on its own. It is not a substitute for a written explanation of hidden systems.
- Watch the objective panel and result screen.
- Note actions without relying on a narrator.
- Use the run to identify questions for further testing.
Keep playtest footage version-labelled
The indexed February 16 run is a playtest recording, not launch footage. Mission scripting, balance, interface and performance can change. When using it in a guide, place the publication date and build status beside every claim, then add a current-build check for anything a player must rely on, such as controls, language or compatibility.
- Label the run as playtest footage.
- Do not reuse old balance advice without testing.
- Check current controls and language separately.
How to make a walkthrough from it
Write the walkthrough as a sequence of observable decisions: starting squad, first objective, safe movement, contact, action-point use, extraction and result screen. Mark every step that depends on a random roll or a version-specific layout. If the video does not show a menu or outcome, do not fill the gap with invented certainty; link the missing question to a current in-game test.
- Order steps by observable decisions.
- Mark random or build-dependent outcomes.
- Do not invent screens the recording does not show.
No-commentary video checklist
- Record uploader, date and playtest status.
- Watch objectives, movement and result screens.
- Separate visible actions from hidden mechanics.
- Re-test version-sensitive advice in the current build.
- Link the original video instead of copying it.
Frequently asked questions
Is the no-commentary video the launch version?
The indexed February 16 recording is labelled playtest and predates the August 1.0 release. Do not use it as launch proof.
What can I learn from a no-commentary run?
You can inspect objective flow, UI readability, movement and combat pacing. Hidden formulas and current balance need additional evidence.
How should I cite a playtest recording?
Include the original link, uploader, publication date and playtest label, then say which visible frame supports your claim.
Sources and verification
Official facts are separated from developer estimates and unverified community claims.