CAI_BehaviorBase::IsValidShootPosition

0x005a75b0 · 20 bytes · __cdecl

_ZN16CAI_BehaviorBase20IsValidShootPositionERK6VectorP8CAI_NodePK8CAI_Hint

Decompiled

undefined (3 params)


/* CAI_BehaviorBase::IsValidShootPosition(Vector const&, CAI_Node*, CAI_Hint const*) */

void CAI_BehaviorBase::IsValidShootPosition(Vector *param_1,CAI_Node *param_2,CAI_Hint *param_3)

{
                    /* WARNING: Could not recover jumptable at 0x005a75c2. Too many branches */
                    /* WARNING: Treating indirect jump as call */
  (**(code **)(**(int **)(param_1 + 0x24) + 0x1c))();
  return;
}

SourceMod gamedata

paste into addons/sourcemod/gamedata/<your_plugin>.txt

Entry name used as the SourceMod key — change to fit your plugin's convention

Library SourceMod library name (server / engine / matchmaking)

Just a Signatures{} block, ready to drop into a gamedata file. Wire it up in your plugin however you like - SDKCall, DHooks, raw memory ops, or anything else.

Signatures + Functions block. The plugin uses DHookCreateFromConf - DHooks reads return type, this-type, calling convention, and argument types straight from the gamedata. Less boilerplate in the plugin, types travel with the gamedata.

Gamedata KeyValues

DHooks plugin example

Type inference is best-effort from the C signature - sanity-check the DHooks types before shipping.

Return-type handling cheatsheet (DHookReturn)