CAI_BehaviorBase::BehaviorBridge_WeaponLOSCondition

0x005a6fc0 · 24 bytes · __cdecl

_ZN16CAI_BehaviorBase33BehaviorBridge_WeaponLOSConditionERK6VectorS2_b

Decompiled

undefined (3 params)


/* CAI_BehaviorBase::BehaviorBridge_WeaponLOSCondition(Vector const&, Vector const&, bool) */

void CAI_BehaviorBase::BehaviorBridge_WeaponLOSCondition
               (Vector *param_1,Vector *param_2,bool param_3)

{
                    /* WARNING: Could not recover jumptable at 0x005a6fd6. Too many branches */
                    /* WARNING: Treating indirect jump as call */
  (**(code **)(*(int *)param_1 + 0xc0))();
  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)