FindAndRemoveExecutionMarker
0x00117780 · 101 bytes · __regparm3
_ZL28FindAndRemoveExecutionMarkeri
Decompiled
undefined (1 param)
/* FindAndRemoveExecutionMarker(int) */
undefined4 __regparm3 FindAndRemoveExecutionMarker(int param_1)
{
int iVar1;
if (DAT_003887e0 < 1) {
return 0;
}
iVar1 = 0;
if (*g_ExecutionMarkers != param_1) {
do {
iVar1 = iVar1 + 1;
if (iVar1 == DAT_003887e0) {
return 0;
}
} while (g_ExecutionMarkers[iVar1] != param_1);
if (iVar1 == -1) {
return 0;
}
}
CUtlVector<int,CUtlMemory<int,int>>::ShiftElementsLeft
((CUtlVector<int,CUtlMemory<int,int>> *)&g_ExecutionMarkers,iVar1,1);
DAT_003887e0 = DAT_003887e0 + -1;
return 1;
}
SourceMod gamedata
paste intoaddons/sourcemod/gamedata/<your_plugin>.txt
used as the SourceMod key — change to fit your plugin's convention
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.