Welcome, Officer. This documentation acts as your tactical playbook to deploy and configure S.C.O.U.T. inside your server unit.
S.C.O.U.T. (Strategic Campaign & Operation Unit Tracking) is an advanced optical-recognition intelligence bot designed to automatically digitize Helldivers 2 post-game screenshots, sync live planetary war maps, and coordinate custom multi-server campaigns.
To deploy S.C.O.U.T. into your server: 1. Invite the bot using the authorization link on the Home page. 2. Ensure the bot has View Channel, Send Messages, and Attach Files permissions in your reporting channels. 3. Server Staff must log in here on the website to configure settings. Navigate to 'Fleet Command' -> 'Manage' to bind channels with simple dropdown interfaces. 4. Run the `/help` command inside Discord to check available commands.
The core engine uses advanced screenshot scanners to read your post-game images. S.C.O.U.T. supports two submission formats: - **Operation Submissions (`/submit-operation`)**: Upload the final screen showing the Planet, Difficulty, and the 3 Mission badges to verify group-wide victories. - **Mission Stats Submissions (`/submit-mission-stats`)**: Upload the final statistics card showing Kills, Deaths, Accuracies, and Stims to update permanent service records. *Note: Screenshots should be clear, high-resolution (1080p+), and completely uncropped.*
S.C.O.U.T. eliminates complex in-Discord slash command configuration. Server owners can customize all aspects of their unit directly through the web UI: - **Channel Routing**: Bind designated channels for screenshot drops, global announcements, and automated service reports. - **Permissions**: Grant staff roles like Reviewer (to approve/deny queues) or Commander (to configure Award Rules). - **Review Controls**: Tune queue routing, approval roles, and scanner workflows without restricting routine member reports.
Design custom progression paths (e.g., 'Steel Tide Progression') from the **Award Rules** tab in your server's Manage dashboard: - **Logic Trees**: Set up AND/OR rules that combine conditions like kills, samples, or operations completed on specific planets. - **Automation**: When players log sufficient kills or complete operations on designated frontline planets, the bot automatically grants role level-ups and showcases custom medals in their service records. - **Role Removal**: Configure options to remove lower-tier roles automatically when a higher milestone is reached.
Campaigns are custom Major Orders for your community: server-wide (or multi-server) goals that members advance just by submitting their normal reports. **Creating a campaign (Commanders):** open your server's **Manage** dashboard → **Campaigns**. Give it a name and duration, then add objectives — kill counts, operations completed, samples extracted, and more. Progress posts to your bound progress channel automatically as reports come in. **Recommended starter setup:** run your first campaign for **one week** with **two objectives** — a kill target and an operations target — sized to roughly your weekly active player count (e.g., 20 active divers ≈ 100,000 kills / 60 operations). Short and winnable beats long and stalled; you can always scale up the next one. **Contributing:** members don't do anything special — every `/submit-operation` and `/submit-mission-stats` report counts toward active objectives automatically.
Routine submissions are processed automatically by the optical scanner — no staff action is needed for normal reports. A report goes to human review in two cases: - **Low-confidence scans**: the scanner couldn't confidently read the screenshot, so it's flagged instead of auto-accepted. - **Disputes**: a player believes a scan is wrong and runs `/dispute` in Discord, proposing corrected numbers with a reason. Flagged and disputed reports enter the **Review Queue**, where S.C.O.U.T. network reviewers claim each case, compare the original screenshot against the scanned numbers, and approve or deny it. Approving a dispute applies the player's proposed corrections to the record automatically. *Most misreads come from cropped, compressed, or low-resolution images — resubmitting a clean, uncropped 1080p+ screenshot is often faster than filing a dispute.*
- **Q: Why did the scanner reject my screenshot?** A: Ensure the image is uncropped, high-resolution, and clear. Photos taken of monitor screens using phones often fail validation checks. - **Q: Are normal submissions capped?** A: No. S.C.O.U.T. is built for active communities. Donor Communities receive recognition and supporter settings, not submission locks. - **Q: What is the dispute process?** A: If an automated OCR scan is inaccurate, a player can run the `/dispute` command in Discord to request manual staff review. - **Q: How do I view my stats?** A: Run `/service-record` in Discord for your full career card, or `/leaderboard` to rank your squad. Your public profile is also viewable here on the website.
S.C.O.U.T. offers a free, read-only public API so you can pull community stats into your own tools, websites, or stream overlays — no key or login required. **Base URL:** `https://hd2-scout.com/api/v1` - `/stats` — galaxy-wide totals - `/campaigns` — public campaigns & events - `/guild/{id}` — a unit's combat totals - `/guild/{id}/leaderboard?stat=kills` — top divers - `/player/{id}` — a Helldiver's career totals **Example:** `curl https://hd2-scout.com/api/v1/stats` *Privacy: per-person data is public by default. Set your profile to private to opt out, and your individual stats are withheld. Visit `/api/v1` for the live endpoint directory.*
If you encounter configuration hurdles or database disputes, join our Central Command server where our staff can help recalibrate your sensors.