find-CGameRules_ClientSettingsChanged

Locate CGameRules::ClientSettingsChanged in CS2 binaries via IDA Pro MCP.

60|11|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/HLND2T/CS2_VibeSignatures --skill find-cgamerules-clientsettingschanged-hlnd2t
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-CGameRules_ClientSettingsChanged
Source: https://github.com/HLND2T/CS2_VibeSignatures/tree/main/.claude/skills/find-CGameRules_ClientSettingsChanged
Command: npx skills add https://github.com/HLND2T/CS2_VibeSignatures --skill find-cgamerules-clientsettingschanged-hlnd2t

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and locate the CGameRules::ClientSettingsChanged function in CS2 server.dll or libserver.so using IDA Pro MCP tools for reverse engineering and mod development.

Core Features & Use Cases

  • Search for the string "fov_desired" and gather cross-references to locate related code.
  • Decompile and inspect the referencing functions to identify the target function and its role.
  • Rename the function in IDA Pro MCP and compute its vtable offset/index for correct dispatch.
  • Generate a robust function signature and write the analysis output in YAML beside the binary for traceability.

Quick Start

Follow the steps to search for the fov_desired reference, analyze cross-references, rename the function, determine the vtable offset, generate a robust signature, and write the YAML analysis output.

Frequently Asked Questions about find-CGameRules_ClientSettingsChanged

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find CGameRules::ClientSettingsChanged in CS2 server binaries?

You can locate CGameRules::ClientSettingsChanged in CS2 server binaries by tracing the "fov_desired" string reference and its cross-references using IDA Pro MCP. This approach isolates the function for subsequent renaming and vtable index calculation.

What is the best way to generate a unique signature for a CS2 server function?

Generating a unique signature for a CS2 server function involves decompiling the target function in IDA Pro MCP to extract its binary pattern. After tracing the "fov_desired" string reference, the tool computes a robust signature and emits the result in YAML.

How does string reference tracing work for reverse engineering CS2 libserver.so?

String reference tracing for reverse engineering CS2 libserver.so works by searching for specific strings like "fov_desired" and gathering their cross-references. IDA Pro MCP then decompiles the referencing functions to identify the exact code handling client settings changes.

Does this IDA Pro MCP approach work for both server.dll and libserver.so?

Yes, this IDA Pro MCP approach works for both CS2 server.dll and libserver.so. It applies the same reverse engineering methodology of tracing the "fov_desired" string reference and cross-references to locate the CGameRules::ClientSettingsChanged function across both binary formats.

How do I determine the vtable offset for a function found via string reference?

To determine the vtable offset for a function found via string reference, use IDA Pro MCP to inspect the renamed function's position in the virtual function table. This computes the correct dispatch index for CGameRules::ClientSettingsChanged.

Why write YAML analysis output beside the binary during reverse engineering?

Writing YAML analysis output beside the binary during reverse engineering ensures traceability of the generated signatures, vtable offsets, and function names. It documents the IDA Pro MCP findings for CGameRules::ClientSettingsChanged for future mod development reference.