Scout your game. Turn observations into a test plan.
Learn the build. Capture the paths. Build the next checks.
Scout Mode explores a selected part of your game and captures mechanics, player flows, screenshots, and draft notes. After your team reviews them, useful observations and candidate tests become part of the game's QA knowledge. Observed behavior is not turned into approved game design automatically.
Built for product leads, game designers, and QA teams who want a faster first read on a build.
What Scout Mode captures
From mechanics and pacing to onboarding and economy, Scout Mode turns a run into observations your team can review and act on.
Mechanics and pacing observations
Capture how core loops, difficulty, and progression play out in the part of the game you point Scout at.
Economy and reward notes
Note how the economy, reward timing, and paywall placement appear during observed runs, for your team to review.
Onboarding and flow capture
Record onboarding steps, menus, and player flows as screenshots and draft notes your team can compare.
Gameplay clips for review
Use runs to capture gameplay clips and scenario variations your team can review for content and UA workflows.
Observations from a run
Turn what happened in a run into structured notes on friction points and areas worth a closer look.
Draft a test plan
Shape observations into candidate checks your team approves before they become repeatable regression tests.
Explore the build. Review the observations. Approve what becomes a test.
Scout output is an observed draft. It does not determine intended design or become an approved regression suite until your team approves it, and an observation is not real-player research.
Agree the scope
Share a supported build and the part of the game you want Scout to explore.
Scout explores and records
Scout plays through the agreed scope and captures mechanics, flows, screenshots, and observations.
Review the observations
Receive screenshots, draft notes, and observations your team can review and turn into approved checks.
Why product teams use Scout Mode
See how the build plays
Scout runs through a selected part of your game and captures what happened for your team to review.
A faster first read
Get structured observations on balance, economy, and design questions early, for your team to validate.
Same worker as BugHunter
Scout Mode uses the same worker, so approved observations can become repeatable checks.
Grounded in your build
Observations come from runs on a supported build and scope you agree with us.
BugHunter vs Scout Mode
BugHunter
Repeatable QA Testing
- -Finds bugs and regressions
- -Reports with video and reproduction steps
- -Runs on your builds before release
- -Used by QA teams
Scout Mode
Product Intelligence
- -Captures balance, economy, and pacing observations
- -Runs on a supported build of your game
- -Surfaces friction and design observations
- -Used by product, design, and QA teams
Both use the same worker. Observations from Scout can become approved BugHunter checks.
See what Scout Mode can surface for your game
Share your game and one area to explore. We'll confirm a supported build and scope for a Scout run.