CUtlMemory<EntityLocationInfo<CHandle<CWeaponSpawnConfigurable>>*,int>::Purge

0x008ab790 · 50 bytes · __thiscall

_ZN10CUtlMemoryIP18EntityLocationInfoI7CHandleI24CWeaponSpawnConfigurableEEiE5PurgeEv

Decompiled

undefined (1 param)


/* CUtlMemory<EntityLocationInfo<CHandle<CWeaponSpawnConfigurable> >*, int>::Purge() */

void __thiscall
CUtlMemory<EntityLocationInfo<CHandle<CWeaponSpawnConfigurable>>*,int>::Purge
          (CUtlMemory<EntityLocationInfo<CHandle<CWeaponSpawnConfigurable>>*,int> *this)

{
  if (-1 < *(int *)(this + 8)) {
    if (*(void **)this != (void *)0x0) {
      free(*(void **)this);
      *(undefined4 *)this = 0;
    }
    *(undefined4 *)(this + 4) = 0;
  }
  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)