CUtlVector<CDirectorItemManager::ItemRestoreInfo,CUtlMemory<CDirectorItemManager::ItemRestoreInfo,int>>::~CUtlVector

0x008ab050 · 44 bytes · __thiscall

_ZN10CUtlVectorIN20CDirectorItemManager15ItemRestoreInfoE10CUtlMemoryIS1_iEED2Ev

Decompiled

undefined (1 param)


/* CUtlVector<CDirectorItemManager::ItemRestoreInfo,
   CUtlMemory<CDirectorItemManager::ItemRestoreInfo, int> >::~CUtlVector() */

void __thiscall
CUtlVector<CDirectorItemManager::ItemRestoreInfo,CUtlMemory<CDirectorItemManager::ItemRestoreInfo,int>>
::~CUtlVector(CUtlVector<CDirectorItemManager::ItemRestoreInfo,CUtlMemory<CDirectorItemManager::ItemRestoreInfo,int>>
              *this)

{
  RemoveAll(this);
  CUtlMemory<CDirectorItemManager::ItemRestoreInfo,int>::Purge
            ((CUtlMemory<CDirectorItemManager::ItemRestoreInfo,int> *)this);
  *(undefined4 *)(this + 0x10) = *(undefined4 *)this;
  CUtlMemory<CDirectorItemManager::ItemRestoreInfo,int>::Purge
            ((CUtlMemory<CDirectorItemManager::ItemRestoreInfo,int> *)this);
  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)