CTriggerBrush::Use

0x006f6070 · 157 bytes · __cdecl

_ZN13CTriggerBrush3UseEP11CBaseEntityS1_8USE_TYPEf

Decompiled

undefined (4 params)


/* CTriggerBrush::Use(CBaseEntity*, CBaseEntity*, USE_TYPE, float) */

void CTriggerBrush::Use(CTriggerBrush *param_1,CBaseEntity *param_2)

{
  char cVar1;
  
  cVar1 = PassesInputFilter(param_1,param_2,*(int *)(param_1 + 0x488));
  if (((cVar1 != '\0') && (((byte)param_1[0x488] & 0x10) == 0)) &&
     (COutputEvent::FireOutput((COutputEvent *)(param_1 + 0x470),param_2,(CBaseEntity *)param_1,0.0)
     , *(int *)(param_1 + 0x48c) == 0)) {
    CBaseEntity::Use();
    return;
  }
  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)