Web Radar example

The user-facing distribution is one portable file: scripts/Vesta Web Radar.lua. The maintainable sources are in scripts/vesta_web_radar; the generated Lua embeds and extracts the helper and frontend automatically when enabled. It demonstrates an intentionally separated runtime architecture:

1. The below-normal Lua worker polls vesta.game.radar_snapshot() at 20 Hz and

writes a compact, double-buffered JSON state in vesta.api.data_dir. It does not subscribe to the full 60 Hz frame containing ESP bones and hitboxes.

1. An external PowerShell helper binds a random loopback port and serves the

static frontend plus the latest state.

1. On first use the helper downloads a pinned portable Windows x64 cloudflared

release, verifies its SHA-256, and caches it in the script's private %TEMP% data directory.

1. The helper opens an account-free Cloudflare Quick Tunnel and publishes a

token-protected path and automatically reconnects cloudflared if the tunnel process exits. No alternate public tunnel is used.

The map appears immediately instead of being reconstructed by thousands of collision queries. vesta.game.radar_overview decodes the official overview from the user's local read-only CS2 VPK into the script's %TEMP% cache; no map asset is embedded in Vesta or downloaded from a third party.

The token is a 192-bit random bearer secret. It prevents discovery by guessing, but anyone who receives the complete link can view the radar until the script is stopped. The helper sends no-store and no-referrer headers and has no public route without the token.