find-CGameResourceService_BuildResourceManifest

Find CGameResourceService_BuildResourceManifest

Locate CGameResourceService::BuildResourceManifest in CS2 engine2.dll or libengine2.so using IDA Pro MCP tools.

Method

1. Search for Log String

Search for the function name string in the binary:

mcp__ida-pro-mcp__find_regex pattern="CGameResourceService::BuildResourceManifest\(start\)"

Expected results: Multiple strings like:

• "CGameResourceService::BuildResourceManifest(start) [%d ekv - %s]"
• "CGameResourceService::BuildResourceManifest(start) [%d entities - %s]"
• "CGameResourceService::BuildResourceManifest(start) [callback 0x%p]"
• "CGameResourceService::BuildResourceManifest(start) [manifest group %s]"

2. Find Cross-References to String

Get xrefs to the CGameResourceService::BuildResourceManifest(start) [%d entities - %s] variant string address:

mcp__ida-pro-mcp__xrefs_to addrs="<string_address>"

The xref should point to a function - this is CGameResourceService::BuildResourceManifest.

3. Verify Function Pattern

Decompile the function to verify it matches the expected pattern:

mcp__ida-pro-mcp__decompile addr="<function_addr>"

Cross-Platform Identification Pattern

The function handles resource manifest building for entities. Key characteristics:

Common identifying features:

• References "CGameResourceService::BuildResourceManifest(start) [%d entities - %s]" log string
• References "CGameResourceService::BuildResourceManifest(finish) [%d entities - %s]" log string
• Accesses CGameResourceService::m_pEntitySystem at offset 0x58
• Calls a virtual function on m_pEntitySystem (vtable index 4, offset 0x20)

Expected function signature:

void __fastcall CGameResourceService_BuildResourceManifest(
        CGameResourceService* this,
        unsigned int a2,
        unsigned int entityCount,
        __int64 a4,
        __int64 a5,
        __int64 a6,
        __int64 a7)

4. Rename the Function

mcp__ida-pro-mcp__rename batch={"func": [{"addr": "<function_addr>", "name": "CGameResourceService_BuildResourceManifest"}]}

5. Generate and Validate Unique Signature

ALWAYS Use SKILL /generate-signature-for-function to generate a robust and unique signature for the function.

6. Write IDA Analysis Output as YAML

ALWAYS Use SKILL /write-func-as-yaml to write the analysis results.

Required parameters:

• func_name: CGameResourceService_BuildResourceManifest
• func_addr: The function address
• func_sig: The validated signature from step 5

7. Write Struct Members for CGameResourceService as YAML

ALWAYS Use SKILL /write-struct-as-yaml to write CGameResourceService's struct member information:

For CGameResourceService.{platform}.yaml:

• Offset 0x58: m_pEntitySystem (size 8)

Function Characteristics

• Type: Regular function (not virtual)
• Parameters: (this, a2, entityCount, a4, a5, a6, a7)
• Purpose: Builds resource manifest for entities, delegates to entity system

Key Code Pattern

// Access m_pEntitySystem at offset 0x58
v16 = *(_QWORD *)(a1 + 88);  // 88 = 0x58, This is CGameResourceService::m_pEntitySystem, and can change on game update.
if (v16)
    // Call virtual function at vtable index 4 (offset 0x20)
    (*(void**)(*v16 + 32))(v16, a2, a3, a4, a5, 0, a7);

Platform Differences

Output YAML Format

The output YAML filename depends on the platform:

• engine2.dll → CGameResourceService_BuildResourceManifest.windows.yaml
• libengine2.so → CGameResourceService_BuildResourceManifest.linux.yaml

Example Output

func_va: 0x1801b4f10       # Virtual address - changes with game updates
func_rva: 0x1b4f10         # Relative virtual address - changes with game updates
func_size: 0x131           # Function size in bytes - changes with game updates
func_sig: 48 89 5C 24 ...  # Unique byte signature - changes with game updates

Struct Member YAML

CGameResourceService.{platform}.yaml:

0x58: m_pEntitySystem 8