CAI_BehaviorBase::BehaviorBridge_IsValidShootPosition

0x005a6fb0 · 7 bytes · __thiscall

_ZThn8_N16CAI_BehaviorBase35BehaviorBridge_IsValidShootPositionERK6VectorP8CAI_NodePK8CAI_Hint

Decompiled

undefined (4 params)


/* non-virtual thunk to CAI_BehaviorBase::BehaviorBridge_IsValidShootPosition(Vector const&,
   CAI_Node*, CAI_Hint const*) */

void __thiscall
CAI_BehaviorBase::BehaviorBridge_IsValidShootPosition
          (CAI_BehaviorBase *this,Vector *param_1,CAI_Node *param_2,CAI_Hint *param_3)

{
  BehaviorBridge_IsValidShootPosition((Vector *)(this + -8),(CAI_Node *)param_1,(CAI_Hint *)param_2)
  ;
  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)