How piootrekk/cs2-player-checker works
CS2 player checker accepts a Steam URL, custom URL, or Steam ID; it validates/resolves the identifier and directs the user to a player profile. The product gathers Steam and Faceit data and presents linked account services, with Scope.gg and other services documented as capabilities. The tree and excerpts establish input resolution, endpoint behavior, and some service-card composition; the profile page’s data-fetching orchestration is not sampled, so those connections are left out.
Components 20
Player Lookup
- Steam ID form
- URL verification action
- Steam ID parsing
- Steam URL schema
Player Data
- Steam API access
- Faceit API access
- Other service access
Profile Display
- Player profile route
- Steam profile card
- Faceit profile card
- Faceit details card
- Connected services section
- Scope.gg card
- Other service cards
- Esportal card
- Service profile link
Other components
- Player checker user
- Steam Web API
- Faceit API
- Other game services
Connections 12
- Player checker user → Steam ID form: enters ID
- Steam ID form → URL verification action: submits form
- URL verification action → Steam ID parsing: normalizes and parses
- URL verification action → Steam URL schema: validates URL
- URL verification action → Steam API access: resolves vanity URL
- Steam API access → Steam Web API: requests profile data
- Faceit API access → Faceit API: requests player data
- Other service access → Other game services: fetches service data
- Connected services section → Scope.gg card: renders
- Connected services section → Other service cards: renders
- Connected services section → Esportal card: renders
- Other service cards → Service profile link: renders links