Match notifications your server will actually read.
Scout watches tracked players, posts a card when they queue up and a full recap when they finish, and turns the history into leaderboards, competitions, and scheduled reports.
Start here
Section titled “Start here”New to Scout? The tutorials are worked lessons — follow one start to finish and you will have a working setup.
- Get your first match notification — add Scout to a server, track a player, and see a real recap post.
- Run your first competition — set up a weekend climb race with an automatic leaderboard.
- Build your first scheduled report — write a ScoutQL query and have it post itself every week.
Solve a specific problem
Section titled “Solve a specific problem”The how-to guides assume you already know what you want and get you there: routing matches to the right channels, linking players to Discord users, granting access without Discord admin, or working out why a notification never arrived.
Look something up
Section titled “Look something up”The reference is generated from the same registries Scout runs on — the metric list, permission catalog, and render kinds are the values actually shipped in the build you are using, not a hand-maintained copy.
Understand how it fits together
Section titled “Understand how it fits together”The concept guides cover how Scout finds matches, how players, accounts, and subscriptions relate, and why configuration lives in the browser.