Skip to Content
PAPAMO / DOCS
PAPAMOVGUI2

Compatibility and releases

Know which parts are source-ready and which require a matching release.

Runtime requirements

PAPAMOVGUI2 currently targets 32-bit GoldSrc CS 1.6 with the required VGUI2 interfaces. The private module has separate Linux and Windows ABI handling. NextClient requires its compatible host bridge, including the fixed command/message allowlists.

ClientBehavior
Approved managed Linux CS 1.6Native VGUI2 path, subject to the packaged module's capabilities
Approved managed Windows CS 1.6Verified persistent proxy, with the updated module
Approved managed NextClientCompatible host and native module must ship together
Stock client without the helperNo PAPAMOVGUI2 messages sent without opt-in; ordinary UI remains
Web clientNo native VGUI2; use ordinary server-supported features
CS 1.3 / CS 1.5Not covered by the PAPAMOVGUI2 v1 interface

Release status

The animated component, customizable partner scoreboard and public .inc transport are new source work. The existing production helper may lack them. The papamovgui2_v1 module capability identifies framework support; papamovgui2_scoreboard_v1 identifies the customizable board receiver; papamo_persistent_session_v1 identifies the persistent-session lifecycle. Capability markers do not replace signed manifests, exact hash verification or registry approval.

A release must coordinate the launcher/session helper, native module, NextClient host where applicable, and server plugin. Do not install an arbitrary DLL from these docs or bypass verification to enable a feature.

Validation before deployment

For the November 2026 legacy Windows investigation, see Legacy GoldClient: HUD and crash diagnosis. It records the exact hashes, VGUI ABI differences, white-row blending failure, shutdown crash and verified limits.

Use isolated installations and test Linux and Windows, including NextClient where offered: rapid kills, ace/reset/death, stale feeds, expired partner snapshots, resolution changes, reconnects, another endpoint, repeated sessions and normal shutdown. Confirm that unknown local DLL changes are preserved during updates. Measure actual game frame times; a successful build or offline preview does not establish runtime smoothness.

Do not run 1.6 Competitive alongside another client-side anti-cheat. Close the managed game and launcher before switching clients. No third-party anti-cheat compatibility is claimed.