A leveled guide for new players coming to WDGWars, the community wardriving game by LOCOSP. Five steps from “I have an Android phone” to “I run a multi-source capture lab,” with every product fact cited from a primary source.
Read order
- Newcomer onramp — start here. Five sequenced steps from zero to scoring on WDGWars leaderboards.
- Capture flow diagram — the same progression as a flow diagram (Mermaid here, interactive Obsidian canvas in the repo root).
- Shopping list — buyer’s checklist for each tier with vendor links.
- Hardware survey — reference: every firmware × chip combination, every community tool, decision tree, API gotchas.
- Credits & acknowledgments — every maintainer, project, and vendor in the ecosystem this guide leans on.
Who this is for
- New players asking “what hardware should I buy?” → start at Newcomer onramp Step 1, then Shopping list for the specific items.
- Players moving past their phone → jump to Newcomer onramp Step 3 and Shopping list Tier 3a/3b.
- People comparing firmwares → Hardware survey §2-§4 has the matrix.
- Developers writing a feeder → read gungnir (Python transport) and LOCOSP’s WatchDogsGo
plugins/wardrive_upload.pyside by side — between them they cover the auth header, HMAC construction, retry/cooldown, and the slot-typed payload shape. - Maintainers and crediting people → Credits for who built what.
What this is not
- Not affiliated with LOCOSP. WDGWars is theirs. This is a community-maintained orientation guide.
- Not a CLI tutorial for the feeders themselves. Each feeder’s own README is the source of truth for its options.
- Not a complete API reference — that lives at wdgwars.pl/help. This guide covers the gotchas working integrations trip over, not the surface itself.
Source and contributions
Source on GitHub. Issues and pull requests welcome — especially for product facts that have drifted (versions, retired releases, changed behavior) or new community tools worth listing.