| # | Summoner | Reg | Pro | Team | Age | Tier | LP | Role | Patch | Games | WR | Pool | CSS | %ile | Smurf |
|---|
| # | Player | Reg | Pro | Role | Tier | CSS (from) | CSS (to) | Δ | Games |
|---|
Loading team…
Challenger scouting tool for pro recruiting. Everything below is for internal use only — not for public sharing.
Go to Ladder → toggle 🎯 Free Agents or
👶 U21 pill → sort by CSS desc → you see top
candidates with their tier, age, current team, and CSS.
Click their row → profile. 3 tabs: SoloQ (radar + champion pool + activity heatmap), Tournament (official stats if pro), vs LEC (delta vs every LEC pro at the same role).
Click ★ on the row or profile → adds to watchlist. Go to
Watchlist → drag-and-drop the player across the 6
columns (Watching → Contacted → Trial → Offer → Signed/Pass).
Every Challenger / GM / Master player in the DB, sorted by CSS.
G2) → opens the team page"📋 Markdown" button → downloads a clean .md with:
identity + headline CSS + score breakdown + roles & patches + CSS trend + top champions + recent matches + scout notes + smurf signals.
Paste into Notion / Discord / Slack to share with non-technical staff.
Drag-and-drop across 6 columns:
Each card shows: name · role · tier+LP · CSS · tag · "N days in stage". Click a card → opens the profile.
Toggle 📊 Table to switch to table view (denser, same info + inline-editable Tag column).
Dedicated view for meta work. Patch from / Patch to selectors auto-init to the 2 most recent patches (ordered by real activity, not string sort).
Typical use case: a new patch drops → you open this view 2 days later → you see which Challengers surfed the new meta. If it's a smurf playing the Yunara that just got nerfed and they crash to 35 CSS, probably not your best prospect.
Direct URL: /#/team/G2 (and any team code).
If the team has no tournament data in the DB (e.g. Prime League, division 2), synthetic fallback: we build the team from PlayerMeta. Roster works, recent_matches is empty. Works for BIG, KCB, etc.
Use case: you're hesitating between 3 junglers — Compare puts them side-by-side on a single radar so you can see who has the best lane/objective/vision tradeoff for your team's style.
Type a gameName#tagLine + region → ingests this player regardless of their rank. Pipeline: account-v1 → summoner-v4 → ranked entries → match-v5 (last N matches) → CSS. Optional auto-add to watchlist.
Use case: you know a player by name (former pro, friend of the staff, LFL amateur) who doesn't show up in Challenger. Add player → 30 seconds later their profile is ready.
RIOT_API_KEYS is set in .env0-100 score per (player, patch, role). Pipeline:
z = (x − μ_role) / σ_rolescore = clip(50 + 15·z, 0, 100)The player's CSS history across all patches (snapshots saved on every ingest). Auto headline if there's a notable swing. Lets you spot a Rising Star (50→70 over 3 patches) vs a stable player.
#/player/<puuid> · #/team/G2 · #/patch · #/leaderboard. Copy the URL while you browse, share via Discord/Slack — the recipient lands directly on the right view.services/lolesports_client.py.docker-compose.yml).
Internal tool, hosted privately via Cloudflare tunnel + Vercel. Not for public sharing.
Questions / bugs → GitHub issues.
RIOT_API_KEYS is set.