DropPilot

Downloads: Grab the latest Windows installer from GitHub Releases: github.com/rxm96/droppilot/releases

What it does

DropPilot focuses on keeping Twitch drops simple and hands-off while still transparent.

• Tracks drop inventory, claim status, and progress in real time.
• Surfaces a target game view with per-drop progress, ETA, and remaining time.
• Builds and respects a priority list so the app can focus on what matters most.
• Auto-selects a stream and auto-switches when the current stream disappears.
• Auto-claims drops (optional) and keeps a clear audit of what happened.
• Optional warmup mode briefly watches a stream to discover drops when no priority game is active.
• Configurable refresh cadence to balance responsiveness vs. load.
• Alerting for key events (new drops, auto-claim, drop ending, watch errors).
• Browser-based login (no credential storage).
• Demo mode for exploring the UI without a live account.
• Debug tools for live logs, state snapshot, perf and CPU sampling (off by default).

Tech stack

• Electron 30
• React 18 + Vite 5
• TypeScript
• Tailwind CSS

Getting started

Install dependencies and run the dev app:

npm install
npm run dev

Build a production bundle:

npm run build

Preview the built renderer:

npm run preview

Scripts

• npm run dev - start Vite dev server
• npm run build - build renderer and Electron bundles
• npm run preview - preview the renderer build

Releases

Releases are published on GitHub Releases. You can download the Windows .exe installer there.

Contributing

See CONTRIBUTING.md for local dev and release details.

Project structure

• src/main - Electron main process (IPC, settings, app lifecycle)
• src/renderer - React UI
• src/preload - Electron preload bridge
• icons - app icons
• dist / dist-electron - build output

Watch engine

Target suppression and stall recovery behavior is documented here:

• docs/watch-engine.md
• docs/watch-flow.puml (PlantUML sequence diagram of end-to-end watch flow)
• implementation: src/renderer/shared/hooks/watch/watchEngine.ts

Debug tools

The Debug tab is disabled by default to keep background work minimal.

Enable it:

1. Go to Settings
2. Turn on Debug tools / Debug tab

Notes:

• Debug logs are gated and only collected when Debug tools are enabled.
• Perf and CPU snapshots are visible in the Debug snapshot.

Configuration

Settings are stored in the user data directory as settings.json and are managed through the in-app Settings view.

Troubleshooting

• If you see "Not logged in", use Login with browser in the top bar.
• If the app feels slow, disable the Debug tab and restart.
• If you need verbose logs, enable Debug tools in Settings.

License

MIT