LastHUD documentation

This site describes the LastHUD desktop application: menus, data workflows, the HUD Builder, and how overlays connect to CS2 Game State Integration (GSI) and the LastHUD API (in-app data exposed to the overlay server).

What LastHUD does

LastHUD lets you manage teams, players, matches, and tournaments, then drive browser-source HUDs for OBS (or similar) while the game runs. The app serves HUD files locally, injects live game state from GSI, and merges your roster data so components can show names, logos, veto maps, camera feeds, and more.

The Builder is a separate window where you design layouts from HTML/CSS components and factory surfaces (scoreboard, minimap, player blocks, etc.), wire triggers and effects, and export HUDs as .hud packages.

Documentation map

  • Main menus — HUDS, Teams, Players, Matches, Tournaments, Live Match, Builder entry, Settings.
  • Builder — HTML/CSS components (text, image, SVG), factory surfaces, triggers & effects (GSI, LastHUD API), overlay HTTP API.

Typical workflow

  1. Create teams and players (Steam IDs, names, pictures, flags).
  2. Schedule a match (optionally link a tournament) and run map veto when needed.
  3. Set the active match and, on Live Match, attach camera links per player if you use Player Focus / cameras.
  4. Build or import a HUD in the Builder, then activate it on the HUDS page so the overlay URL is live.
  5. Add the browser source in OBS pointing at the local overlay URL (served by the app, typically port 8080).
Note. This folder (/docweb) is a static documentation bundle for publishing to a website later. It is not part of the React application bundle.