CWeaponSpawn::GetResponseRulesWeaponName

0x008d63d0 · 50 bytes · __thiscall

_ZNK12CWeaponSpawn26GetResponseRulesWeaponNameEv

Decompiled

undefined (1 param)


/* CWeaponSpawn::GetResponseRulesWeaponName() const */

undefined1 * __thiscall CWeaponSpawn::GetResponseRulesWeaponName(CWeaponSpawn *this)

{
  int iVar1;
  
  iVar1 = (**(code **)(*(int *)this + 0x3cc))(this);
  if (iVar1 != 0) {
    iVar1 = GetWeaponInfo(iVar1);
    if (iVar1 != 0) {
      return (undefined1 *)(iVar1 + 0xa08);
    }
  }
  return &DAT_00d539c2;
}

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)