Architecture and animation
Worker preparation, cached textures and frame-independent animation.
Rendering path
Authenticated platform feed / opted-in assigned partner server
|
validated state
|
bounded worker preparation
|
immutable scene + cached texture atlas
|
PAPAMOVGUI2 timeline and VGUI2 panelThe native implementation lives in the private helper's papamovgui2 module. Its reusable pieces are monotonic animation progress, cubic easing, interpolation, 2D transforms and a shared VGUI2 panel backend. The scoreboard and kill cards share the backend.
Animation behavior
Card entrances and fan reflow use a 280ms transition. Removals fade over 240ms. Kill glow lasts 900ms, and the ace flourish lasts 1.1 seconds. Rapid updates sample the current pose before retargeting so existing cards do not jump back to their initial positions.
Artwork, fonts and text shaping are prepared on a worker. A bounded 1024×1024 RGBA atlas is reused between state changes. Hidden components do not paint. Paint callbacks emit bounded textured geometry without file reads, PNG decoding, text rasterization or per-frame vector allocation.
The framework targets low-end CPUs and integrated GPUs. These design choices are not measured FPS guarantees. Compare disabled/enabled gameplay frame times, slowest frames and repeated rapid-kill sequences before shipping a new client build.
State sources
Platform cards derive from the authenticated scoreboard feed. Existing local DeathMsg observations can start provisional cards; the server feed confirms them, and unconfirmed progress expires after 1.5 seconds. A local baseline is established before showing progress, so joining mid-match does not replay old kills.
Partner cards use the explicitly enabled 16CVGUI transport. A short-lived snapshot is scoped to the assigned endpoint and live managed session. A partner cannot replace the platform's authoritative score feed with cosmetic card messages.
Lifecycle
CS 1.6 Windows/NextClient module installation is persistent in the new source path. Session exit stops workers and removes session tickets, heartbeats, feed data and temporary credentials. It does not automatically restore original DLLs or delete the installed module. Verified original backups and installation journals remain available for explicit maintenance. Linux's managed preload is process-scoped.
Missing ownership, expired data, a disabled setting or a different server hides the component. A persistent module stays inactive outside its authorized session and does not force the ordinary game to restart.
No component may read or modify the player's config.cfg. Persistence and feature disablement do not establish compatibility with VAC or another anti-cheat.