Legacy GoldClient: HUD and crash diagnosis
The November 8, 2026 compatibility investigation: exact binaries, failure causes, fixes and regression checks.
Status and scope
On November 8, 2026, an isolated Windows installation with the binary pair below successfully launched, displayed the custom crosshair and scoreboard, and closed/relaunched after the shutdown fix. The tester confirmed the final build worked. This was a local development probe with synthetic scoreboard data, not a production authenticated match.
The native fix is committed in private helper revision 21aea8a. The launcher compatibility fallback is a separate change. A source push is not a signed release. The production launcher's native allowlist was not expanded by these changes: unsupported legacy installations still use the original-DLL authenticated fallback. That fallback can map supported crosshair preferences to the engine's built-in commands, but does not provide the custom native scoreboard. Shipping the native adapter requires coordinated signed artifacts, explicit installer support and release validation.
Do not apply the legacy ABI to every client called GoldClient or TurboClient. The adapter recognizes an exact client/engine pair; an interface name alone is insufficient.
Binary identity
SHA-256 of the inspected original files:
| File | SHA-256 |
|---|---|
cstrike/cl_dlls/client.dll | 7c9b6e10b0d896d5c99bb0175fff4e8a13834f3e3ae9948e5ccbbf3c1bfdba9d |
hw.dll | 28438ed09e425a29489f034c68ec820ed84fc7c7ead32ae9190be376d2ef419c |
hl.exe | 08ae290d025e3e3000f5264dce450e78d25ba1d931ff10f3e7992addbf44791a |
Matching GameUI.dll | a208f0f3544d3f6574ed501f65a5b6c914d9cd046a7406a067bb6eea0a73a761 |
Matching vgui2.dll | ff40c30638286bea1d3a8f3315fa4df060df8a503b57d7df9d9973b2960f0636 |
The supplied steam_api.dll exports a data/interface pointer named TurboClient. This is evidence of an interface name, not proof of a public repository or distribution ancestry. No updater URL or authoritative TurboClient repository was established in this investigation.
Symptoms and causes
| Symptom | Established cause | Fix or diagnostic action |
|---|---|---|
| Assets finish preparing, but no game process starts | The original launcher report rejected the native installation with NATIVE_INSTALL_UNSUPPORTED; automatic launch and reconnect both reached that rejection | Distinguish preparation rejection from a process crash. Preserve the authenticated original-DLL fallback |
Missing SteamMatchmakingSearch entry point | A newer GameUI was mixed with the legacy installation | Use matching UI dependencies; do not transplant arbitrary DLLs |
| Optional server browser fails | The newer test-copy browser requested VEngineCvar006; the supplied engine exposed VEngineCvar005 | Keep mixed-version browser resources out of the isolated test. This is separate from direct match connection |
| Proxy disappears or behavior changes between runs | The game updater replaced the test proxy | Pass -noupdate on the identified launch path and compare hashes before and after every run |
| Native initialization fails | Legacy Initialize takes three arguments instead of the SDK's two | Dispatch the exact verified legacy pair through its three-argument ABI; preserve the modern two-argument path |
| Crosshair works but Tab shows the stock board | NetAPI reported connected = 0 while a map was running; a later failure was a surface size query returning 0 x 0 | Apply only the exact-pair connection-status workaround, retaining endpoint checks; use the correct surface method table |
| Board activation crashes inside drawing | Legacy textured-polygon method takes a third boolean and performs RET 12 | Use the three-argument call for this engine; the SDK two-argument call corrupts the stack |
| Player's highlighted row looks solid white and the name is unreadable | Textured-polygon drawing disables blending; the following filled-rectangle operation assumes blending is enabled | Draw legacy solid fills through the alpha-blended polygon path using a reserved white atlas texel |
| Closing/restarting the game crashes | Cleanup dereferences a cached VGUI interface after its owning library is no longer loaded | Re-query existing interface instances before cleanup; never call stale interfaces |
The earlier launch report was from launcher 2026.1107.8, before the authenticated fallback. It does not establish that the current auto-launch trigger is broken.
ABI details worth preserving
The original client's Initialize at RVA 0x30df0 accepts (engine_functions, interface_object, version). It dereferences argument two, checks argument three against version 7 and copies 154 engine-function pointers. Four legacy connection callbacks follow the ordinary 44-entry callback table. The proxy preserves the caller's argument frame and only reads a third argument for the verified legacy family.
This engine advertises VGUI_Surface026, but its BaseUISurface vtable at virtual address 0x101a26f0 contains an extra method at slot 29. Slots before it remain unchanged:
| Operation | Standard Windows slot | Inspected legacy slot |
|---|---|---|
| CreateNewTextureID | 31 | 32 |
| GetScreenSize | 32 | 33 |
| ReleasePanel | 74 | 75 |
| DrawTexturedPolygon | 88 | 89 |
The wrong size-query slot called texture creation instead, leaving width and height at zero. Correcting the slot yielded the expected 800 x 600; it did not resolve the separate polygon calling-convention mismatch.
The engine polygon implementation at virtual address 0x10097da0 accepts (vertices, count, blend_mode). The adapter uses false for ordinary source-alpha blending. The function disables blending at 0x10097e96; the filled-rectangle implementation at 0x10097b10 does not enable it. This explains why changing the row's color alone would not fix the white highlight.
These addresses describe the inspected engine image, not universal addresses or permission to patch engine instructions. The adapter uses interface calls. Linux, modern Windows clients and WON retain their separate ABI paths.
Next time: diagnosis checklist
- Start with launcher logs: did asset preparation fail, did native installation reject the client, or did a game process actually start? Record the exact launcher/helper versions and failure stage. Redact credentials before sharing logs.
- Preserve originals and reproduce in a separate test directory. Never read, copy, back up or modify the player's
config.cfg; use launcher-owned startup files and process arguments. - Hash the original engine/client, UI dependencies and installed proxy before and after launch. Confirm the process loaded the expected original DLL beside the proxy. A self-updater can invalidate every conclusion from an earlier run.
- Check the session lease, feed freshness and assigned endpoint before investigating drawing. Do not force an authorization gate open. In this local test the engine reported endpoint
loopback, not the string127.0.0.1:27025. - Inspect interface availability, panel creation and screen dimensions.
VGUI_Surface026appearing in strings does not prove its ABI matches the SDK. - For a crash, preserve the dump and the exact loaded DLL/PDB before rebuilding. Match the PDB identity to that DLL; subtract the dump's loaded module base when resolving an RVA. A newly built PDB can misleadingly map an old crash to a different function.
- In Ghidra, check both call sites and callees: argument order, stack cleanup, vtable slots and callback-table length. Decompiled signatures are hypotheses until checked against instructions.
- Test rendering and lifecycle separately: open/close Tab, inspect row transparency, change crosshair settings, close normally, then relaunch. A board that renders once does not prove shutdown is safe.
Development probe diagnostics
Debug builds with PAPAMO_SKIN_PROBE_TRACE=1 and a valid explicit probe manifest write a bounded hud-probe-state.txt snapshot once per second from the owned input worker. Game draw callbacks only update counters; they do not write the file. This is local probe instrumentation, not automatic uploaded telemetry.
net: raw connected value in the high 16 bits and remote address kind in the low 16 bits, before normalization. The local legacy test reported00000001.board: bit 0 authorized, bit 1 VGUI ready, bit 2 visible, bit 3 score-key ownership. A ready, held-open board can reportf; a closed ready board can report3.panel: stage 1 GUI discovery, 2 panel interface, 3 surface interface, 4 interfaces found, 5 panel allocation attempted, 6 texture creation attempted, 7 creation completed.size: width in the high 32 bits, height in the low 32 bits.0000032000000258means800 x 600.
These values narrow a failure; they never replace authorization or prove visual correctness. Compare the last snapshot's time with the crash time, because it can be stale.
Verification and remaining limits
The final source checks passed: 158 helper/module tests with two ignored, 124 session-helper tests with three ignored, 23 launcher compatibility/recovery tests, the launcher main-process TypeScript check and targeted lint. The Windows x86 module built successfully. Runtime verification covered the supplied pair in the isolated local game, visible custom HUD, and a close/relaunch with no new dump; the tester then confirmed it worked.
Linux runtime behavior, authenticated live-match activation, modern-client runtime regressions, repeated map changes and long-session stability were not established by this test. Before a production release, validate those paths and coordinate the signed bundle, installer allowlist and any capability handshake. Do not broaden anti-cheat exemptions, bypass signature checks or infer support for other legacy hashes.
The updater was observed replacing the proxy, but its service endpoint remains unknown. The test installation included newer baseline resources, so its observed update channel is not reliable proof of the supplied installation's original channel.