find-CGamePlayerEquip_InputTriggerForAllPlayers-AND-CGamePlayerEquip_InputTriggerForActivatedPlayer

Identifies CS2 input handlers via IDA Pro MCP string-pointer analysis and generates YAML signatures.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Locate and identify the CGamePlayerEquip_InputTriggerForAllPlayers and CGamePlayerEquip_InputTriggerForActivatedPlayer functions in CS2 binaries by tracing string pointers in the data section to their associated function pointers using IDA Pro MCP.

Core Features & Use Cases

  • Locate both input handlers in CS2 server.dll or libserver.so using the string-pointer + data-pattern approach in the .data section.
  • Validate and rename the identified functions after cross-reference analysis, then generate unique signatures for long-term SKILL usage.
  • Produce per-function YAML analysis outputs suitable for integration into automated reverse-engineering workflows.

Quick Start

Run the IDA Pro MCP workflow to locate the strings, resolve the function pointers at string_ptr + 0x10, decompile to verify, rename the functions, and generate per-function YAML outputs.

Frequently Asked Questions about find-CGamePlayerEquip_InputTriggerForAllPlayers-AND-CGamePlayerEquip_InputTriggerForActivatedPlayer

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

FAQPage Schema
How do I locate CS2 input handler functions in server.dll using IDA Pro?

To locate CS2 input handlers, trace specific string references in the .data section and resolve their associated function pointers at string_ptr + 0x10 using IDA Pro MCP. You then verify the targets via decompilation.

How does reverse engineering string pointers in the data section identify CS2 game functions?

Reverse engineering string pointers works by finding target strings in the data section, calculating the pointer at an offset like string_ptr + 0x10, and cross-referencing that address to pinpoint the exact function in the binary.

Can I generate automated reverse-engineering signatures for libserver.so functions?

Yes, you can generate robust per-function YAML signatures for libserver.so functions. The workflow validates identified functions through cross-reference analysis and outputs YAML files suitable for automated reverse-engineering pipelines.

What is the best way to map input triggers for all players versus activated players in CS2 binaries?

The best way to map these distinct input triggers is by locating their respective string references in the binary, resolving the pointers at string_ptr + 0x10, and decompiling the results to confirm their specific player-targeting logic.

Do I need IDA Pro MCP to trace data section pointers for CS2 server binaries?

Yes, IDA Pro MCP is required to automate the workflow of locating strings, resolving function pointers in the data section, performing cross-reference analysis, decompiling to verify, and generating the final YAML outputs.

Why are my CS2 function signatures failing during cross-reference analysis in reverse engineering?

Function signatures may fail if the string pointer offset is incorrect or the data pattern in the .data section has shifted. You must verify the resolved function pointer at string_ptr + 0x10 through decompilation before generating signatures.