Find CEngineClient GetStatsAppID

Find CEngineClient_GetStatsAppID (Agent fallback)

Recover the single output of find-CEngineClient_GetStatsAppID using the assigned IDA Pro MCP database. The preprocessor ida_preprocessor_scripts/find-CEngineClient_GetStatsAppID.py remains the normal fast path.

Realworld Function References

Read the applicable current inputs and the annotated references below. Source-owned 14192 YAMLs and stored disassembly are reference-build evidence; verify addresses, slot indices and semantics in the assigned binary. Never copy a reference target YAML into the active output directory as a substitute for analysis.

• ida_preprocessor_scripts/references/engine/InitSteam.windows.yaml
• bin_artifacts/14192/engine/g_nBreakpadAppId.windows.yaml
• bin_artifacts/14192/engine/CEngineClient_vtable.windows.yaml

Output inventory

Module: engine. Platform scope: Windows only. Do not emit a Linux output.

Output metadata uses exactly vtable_name=CEngineClient_vtable; the concrete table artifact is CEngineClient_vtable.<platform>.yaml. Omit func_sig: this getter/thunk has no stable function signature under the producer contract.

Step 0. Bind the task and skip an existing output

Call idb_list and reuse the database assigned by the runner. Confirm the input path, image base and platform with IDA; do not open, switch, close or quit the runner's database. The binary is engine2.dll. Resolve the active artifact module directory from CS2VIBE_ARTIFACT_DIR (also visible inside IDA's environment). If unset, stop and request the assigned artifact directory; never write YAML beside the binary. For the current platform, skip the output if it already exists there and parses as a non-empty mapping. Do not overwrite a result produced by an earlier alternative.

Load the platform-specific configured inputs named above from that active artifact root, not from the 14192 reference tree. Resolve ../client or ../server relative to the active module directory. Missing required inputs must be reported; do not open another binary to reconstruct them.

Step 1. Locate and verify the target

Load g_nBreakpadAppId.windows.yaml from the active engine artifact directory; it is a global-variable artifact, so use its gv_va, not /get-func-from-yaml. InitSteam identifies this global through the BreakpadAppId / BreakpadAppId_Tools KeyValues settings and the Steam AppId(%d), BreakpadId(%d)\n log. It must not be confused with g_nSteamAppId.

Enumerate reads of the current global and intersect their entrypoints with the live CEngineClient_vtable. The target returns that app ID; on 14192 it is a load into EAX followed by RET. If the getter has no IDA function yet, use the vtable pointer as entry evidence and recover conservatively. Follow a tail helper only to establish semantics and retain the vtable entry. Do not select InitSteam, a logging caller, or another app-ID global's getter.

Step 2. Handle missing IDA function boundaries

A vtable YAML can exist even though IDA has not defined its target functions. For each plausible entry, verify the live 64-bit slot pointer, executable segment and decoded instruction boundary. If no function owns the entry, use conservative function definition and wait for analysis, then require the resulting function start to equal the slot pointer. Never delete bytes, split an existing function, or normalize an interior pointer to a neighbouring function's start. If a function already owns an unexpected interior entry, inspect and report the boundary conflict instead of forcing it.

Treat short adjusting thunks as legitimate vtable entrypoints. Follow their destinations for semantic verification, but preserve the slot's actual entry address in the artifact. Distinct-address candidate counts are not vtable slot counts. Confirm the target's slot by live pointer equality; use /get-vtable-index where helpful, and report multiple plausible slots rather than selecting an arbitrary duplicate.

Signatures and YAML output

Do not generate or carry forward func_sig, even if an old artifact contains one. Use /write-vfunc-as-yaml through its IDA py_eval implementation in the assigned session to write the YAML; do not substitute CLI shell or file-edit tools. Parameters:

• artifact_name=CEngineClient_GetStatsAppID and func_name=CEngineClient_GetStatsAppID.
• func_addr: the verified concrete entry in the assigned binary; emit func_va, func_rva = VA - image_base and the verified current func_size. Never emit a bodyless slot-only result for this target.
• vtable_name=CEngineClient_vtable, current vfunc_index and vfunc_offset = index * 8.
• vfunc_sig=None and vfunc_sig_disp=None; this target describes a concrete function, not a caller's vcall.
• func_sig=None; ensure the field is absent in the written YAML.

Write only CEngineClient_GetStatsAppID.windows.yaml as applicable, under the active artifact module directory. The trusted analyzer validates and canonicalizes this semantic payload. Read back the output and verify its name, fields, slot (when applicable), RVA and platform against the live database before reporting success.

Failure handling

If required inputs are missing, candidates remain ambiguous, entry recovery is unsafe, or no standalone entry can be verified, stop and report the exact missing output plus the semantic evidence examined. Do not invent a signature/address, create a placeholder YAML, disable config entries, or claim that a failed lookup proves the game removed the function. Do not run the failed preprocessor as the fallback's solution.