Skip to Content
PAPAMO / DOCS

Papamo developer docs

Build server integrations and animated HUDs for classic Counter-Strike.

Papamo's integration guides cover PAPAMOVGUI2, the animated VGUI2 HUD framework, and the managed cosmetic pipeline used by 1.6 Competitive.

Start with the setup guide and PAPAMOVGUI2, then follow the AMXX quickstart. For cosmetic delivery, read runtime V/P/W models.

What is available?

IntegrationStatus
VGUI2 scoreboard foundationNative Linux and isolated Windows client smoke tests are documented
PAPAMOVGUI2 animated cards, customizable scoreboard and AMXX transportImplemented in source; coordinated signed release and in-game animation validation pending
Verified cosmetic recipe selectorExisting native protocol; public AMXX wrapper added in source
Runtime loading beyond server precacheV/P/W substitution demonstrated on Linux; broader production delivery remains under validation

These guides describe an integration contract. They do not mean the installed production helper already contains the new framework. See compatibility and releases.

Choose an integration

  • AMXX server owners: use the .inc functions to send small display snapshots to compatible managed clients.
  • Platform developers: integrate the approved helper, session authorization and verified asset pipeline before exposing server-controlled HUD components.
  • Client developers: prepare immutable assets on a worker and animate cached geometry through VGUI2. See architecture.

Access and distribution

PAPAMOVGUI2 is a Papamo framework built on GoldSrc's VGUI2 interfaces. It is not Valve software. The native helper is maintained privately; these docs do not grant access to its source, authorize redistribution or change existing project licenses. Contact Papamo through the 1.6 Competitive project for platform access and distribution terms.

LLM-friendly exports

Use /llms.txt for the page index, /llms-full.txt for all documentation, or append .md to a page URL. The docs home is /docs/index.md. Every page also offers Markdown copy/view controls. These are public documentation exports; internal features are excluded.