How zerodaylight0/pubg-tracker works
PUBG Tracker is a local match-analysis application: a player searches by nickname and platform, the Python server retrieves recent matches and squad statistics, and the browser presents match history and selected-player movement and events on a tactical map. The server also proxies telemetry and caches map images locally while keeping the API key server-side. The HTML files were not sampled, so UI-to-endpoint wiring is shown only where documented; unsampled implementation details are not inferred.
Main entry points: app.py HTTP proxy · index.html Tactical map · start.html Search screen
Components 13
Browser interface
- Search screen
start.html - Tactical map
index.html - Match history
index.html - Squad statistics
index.html - Combat and telemetry
index.html
Local Python server
- HTTP proxy
app.py - Match analysis
app.py
Match data and assets
- Match storage
app.py - Local map cache
app.py
Other components
- Player
- PUBG API
- PUBG telemetry
- PUBG map assets
Connections 16
- Player → Search screen: searches
README.md - Search screen → HTTP proxy: requests analysis
README.md - HTTP proxy → Match analysis: routes request
app.py - Match analysis → PUBG API: fetches matches
app.py - Match analysis → Match storage: stores results
app.py - HTTP proxy → Match storage: serves match data
app.py - HTTP proxy → PUBG telemetry: fetches telemetry
app.py - HTTP proxy → Local map cache: reads and writes
app.py - HTTP proxy → PUBG map assets: downloads assets
README.md - HTTP proxy → Search screen: serves page
app.py - HTTP proxy → Tactical map: serves page
app.py - Player → Match history: selects match
README.md - Match history → Squad statistics: selects member
README.md - Squad statistics → Tactical map: shows route
README.md - Tactical map → Combat and telemetry: renders events
README.md - Player → Tactical map: inspects map
README.md