Introduction

Written By Akkeoh

Last updated 1 day ago

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 locally hosted 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 the user can design layouts from HTML/CSS components and factory surfaces (scoreboard, minimap, player blocks, etc.), wire triggers and effects, and export HUDs as .hud packages.

Content

Other Resources

Typical workflow

  1. Import a HUD or build one, then activate it on the HUDS page so the overlay URL is live.

  2. Create or import teams and players (Steam IDs, names, pictures, flags, etc).

  3. Schedule a match (optionally link a tournament) and fill in map veto if needed.

  4. Set the active match and, on Live Match, attach camera links if needed per player if you use Player Focus / cameras.

  5. Add the browser source in OBS pointing at the local overlay URL on:
    localhost:8080/{hudname}.