find-CCSBotManager_AddBot_BotNavIgnore

CCSBotManager_AddBot_BotNavIgnore Patch Workflow

Overview

Locate the g_pNavMesh null-check at the beginning of CCSBotManager_AddBot and generate a patch that converts the conditional jz (jump-if-zero) into an unconditional jmp past the early-return, so bots can be added even when no navigation mesh is loaded.

The target code pattern in pseudocode:

if ( !g_pNavMesh || !*(_BYTE *)(g_pNavMesh + 264) )   // <-- patch target: skip this check
    return 0;

In assembly, the first branch of this check is:

mov     rax, cs:g_pNavMesh
...
test    rax, rax
jz      loc_XXXXXXXX         ; <-- patch this: jz -> jmp to loc after the nav check

The jz is a near conditional jump (0F 84 rel32 — 6 bytes). Patching it to jmp rel32 (E9 <new_rel32> 90 — 5 bytes + 1 NOP) makes it always jump past both the null-pointer check and the g_pNavMesh + 264 byte check, landing at the code that continues bot creation.

The jump target should be the loc_ label that is reached after both nav mesh checks pass (the code right after the second jz that also targets the same early-return).

Prerequisites

• CCSBotManager_AddBot must already be identified. Use SKILL /get-func-from-yaml with func_name=CCSBotManager_AddBot to load its address. If YAML does not exist, run SKILL /find-CCSBotManager_AddBot-AND-g_pCSBotManager-AND-g_pNavMesh first.

Location Steps

1. Get CCSBotManager_AddBot Function Address

ALWAYS Use SKILL /get-func-from-yaml with func_name=CCSBotManager_AddBot.

If the skill returns an error, stop and report to user.

2. Decompile and Locate the Nav Mesh Check

Decompile the function:

mcp__ida-pro-mcp__decompile(addr="<func_va>")

In the decompiled output, search for the nav mesh check pattern at the very beginning of the function body. The key indicators are:

• if ( !g_pNavMesh || !*(_BYTE *)(g_pNavMesh + 264) ) or equivalent
• Immediately followed by return 0;

Note the address annotation on the if-statement line.