CSecurityFailureAwardTemplate::OnCreate

0x0085d1d0 · 238 bytes · __thiscall

_ZN29CSecurityFailureAwardTemplate8OnCreateEv

Decompiled

undefined (1 param)


/* CSecurityFailureAwardTemplate::OnCreate() */

void __thiscall CSecurityFailureAwardTemplate::OnCreate(CSecurityFailureAwardTemplate *this)

{
  int *piVar1;
  
  piVar1 = gameeventmanager;
  this[8] = (CSecurityFailureAwardTemplate)0x1;
  (**(code **)(*piVar1 + 0x10))(piVar1,this,"door_open",1);
  piVar1 = gameeventmanager;
  this[8] = (CSecurityFailureAwardTemplate)0x1;
  (**(code **)(*piVar1 + 0x10))(piVar1,this,"door_unlocked",1);
  piVar1 = gameeventmanager;
  this[8] = (CSecurityFailureAwardTemplate)0x1;
  (**(code **)(*piVar1 + 0x10))(piVar1,this,"player_entered_checkpoint",1);
  piVar1 = gameeventmanager;
  this[8] = (CSecurityFailureAwardTemplate)0x1;
  (**(code **)(*piVar1 + 0x10))(piVar1,this,"player_left_checkpoint",1);
  piVar1 = gameeventmanager;
  this[8] = (CSecurityFailureAwardTemplate)0x1;
  (**(code **)(*piVar1 + 0x10))(piVar1,this,"map_transition",1);
  piVar1 = gameeventmanager;
  this[8] = (CSecurityFailureAwardTemplate)0x1;
  (**(code **)(*piVar1 + 0x10))(piVar1,this,"player_first_spawn",1);
  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)