Check if you're playing with stream snipers! This tool analyzes your current League of Legends lobby and checks if any players have appeared in your last 100 matches.
- Real-time Lobby Detection: Instantly checks if you're in a live game
- 100 Match Deep Scan: Analyzes your last 100 matches to find overlaps
- Win/Loss Tracking: See your history with each player
- All Regions Supported: Works with all Riot Games regions
Successful manual scans now leave a local paper trail. Each successful scan stores:
- the tracked Riot ID you searched
- the current lobby snapshot for that scan
- shared matches pulled from the last 100 games
- local repeat-player risk scoring for anyone who keeps showing up
By default, that data lives in backend/data/haveibeensniped.db. Fresh installs start blank. Delete that file if you want a hard reset.
Repeat-player tiers
- background: some history exists, but the pattern is still light
- repeat: this player has shown up more than once
- watch: the repeat pattern is getting harder to ignore
- high-attention: this player keeps surfacing across saved scans
These labels describe encounter recurrence, not intent. They tell you who keeps reappearing in local memory, not why.
Phase 2 adds local active-game detection through Riot's Live Client Data API at https://127.0.0.1:2999/liveclientdata/allgamedata.
What it does now:
- polls the local game client every 5 seconds while the app page is open
- matches the local Riot ID against your saved tracked profile
- auto-runs one scan per live-session fingerprint instead of hammering
/api/scan
What it does not do yet:
- it does not keep running if the page is closed
- it does not guess a region from thin air, it needs a saved tracked profile match first
- Node.js (v16 or higher)
- Python 3.8+
- Riot Games API Key - Get yours at Riot Developer Portal
One-command install — clone, configure, and run in a single step:
curl -fsSL https://raw.githubusercontent.com/jasperan/haveibeensniped/main/install.sh | bashAdvanced options
Override install location:
PROJECT_DIR=/opt/myapp curl -fsSL https://raw.githubusercontent.com/jasperan/haveibeensniped/main/install.sh | bashOr install manually:
git clone https://github.com/jasperan/haveibeensniped.git cd haveibeensniped # See below for setup instructions
cd backend
pip install -r requirements.txt
cp config.yaml.example config.yaml
# Edit config.yaml and add your Riot API key
python main.pyThe backend will start on http://localhost:5000
npm install
cp .env.local.example .env.local
npm run devThe frontend will start on http://localhost:4000
- Go to Riot Developer Portal
- Sign in with your Riot account
- Register a new application or use your personal API key
- Copy the API key to
backend/config.yaml
Note: Development API keys expire after 24 hours. For production, apply for a production key.
graph LR
User[User Browser] --> Frontend[React Frontend]
Frontend --> Backend[Python Backend]
Backend --> RiotAPI[Riot Games API]
RiotAPI --> Backend
Backend --> Frontend
Frontend --> User
- User enters their Riot ID (Name#TAG) and region
- Frontend sends request to backend
- Backend checks if player is in a live game via Riot Spectator API
- Backend fetches last 100 matches and cross-references lobby participants
- Results show which players you've played with/against before
haveibeensniped/
├── backend/ # Python Flask backend
│ ├── main.py # API server
│ ├── riot_client.py # Riot API wrapper
│ ├── config.yaml # Configuration (create from .example)
│ └── requirements.txt # Python dependencies
├── components/ # React components
├── services/ # Frontend services
└── types.ts # TypeScript types
"Invalid API Key"
- Make sure you copied your Riot API key correctly to
backend/config.yaml - Development keys expire after 24 hours - generate a new one
"Player not in live game"
- You must be in champion select or loading screen
- Streamer mode must be disabled for the person you're searching, otherwise hey won't show up.
- The check won't work in practice tool or custom games with bots
CORS Errors
- Ensure backend is running on port 5000
- Check that
cors_originsin config.yaml includes your frontend URL
Rate Limit Errors
- Development keys: 20 requests/sec, 100 requests/2 min
- Wait a moment and try again
- Consider applying for a production key
The project now includes an interactive CLI for managing configuration and running checks without starting the server.
python backend/cli.pyInteractive Experience:
╭──────────────────────────────────╮
│ HAVE I BEEN SNIPED? │
│ League of Legends Match Analyzer │
╰──────────────────────────────────╯
? Select a Task:
Query User (Active Game & Snipes)
Manage Configuration (API Key)
Check Integrity (Validate connection)
Exit
Features:
- Query User: Check if a player is in an active game and scan for snipers.
- Manage Configuration: Update your Riot API Key securely.
- Check Integrity: Validate your API Key against the Riot API.
- Memory: Remembers your last queried player for quick access.
POST /api/scan- Run a manual scan, persist the local lobby snapshot and shared matches, then return repeat-player scoringGET /api/live-client/status- Report local Live Client connection state, active Riot ID, saved tracked profile match, and whether auto-scan can fire
The backend handles two types of Riot API routing:
- Regional: americas, europe, asia, sea (for Account API)
- Platform: na1, euw1, kr, etc. (for game-specific APIs)
cd backend && python -m pytest -q
npm run buildCreated by jasperan