CTerrorWeaponInfo::GetAddonOffset

0x00570c30 · 39 bytes · __cdecl

_ZNK17CTerrorWeaponInfo14GetAddonOffsetEv

Decompiled

undefined (0 params)


/* CTerrorWeaponInfo::GetAddonOffset() const */

void CTerrorWeaponInfo::GetAddonOffset(void)

{
  undefined4 uVar1;
  undefined4 *in_stack_00000004;
  int in_stack_00000008;
  
  *in_stack_00000004 = *(undefined4 *)(in_stack_00000008 + 0xd68);
  uVar1 = *(undefined4 *)(in_stack_00000008 + 0xd70);
  in_stack_00000004[1] = *(undefined4 *)(in_stack_00000008 + 0xd6c);
  in_stack_00000004[2] = uVar1;
  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)