VProfExport_StartOrStop
0x0022f670 · 102 bytes · unknown
_Z23VProfExport_StartOrStopv
Decompiled
undefined (0 params)
/* WARNING: Globals starting with '_' overlap smaller symbols at the same address */
/* WARNING: Unknown calling convention -- yet parameter storage is locked */
/* VProfExport_StartOrStop() */
void VProfExport_StartOrStop(void)
{
if (g_VProfExport[0x20] != '\0') {
_DAT_0040b028 = _DAT_0040b028 + 1;
if (_DAT_0040b028 == 1) {
CVProfNode::EnterScope();
}
g_VProfExport[0x20] = '\0';
}
if (g_VProfExport[0x21] != '\0') {
_DAT_0040b028 = _DAT_0040b028 + -1;
if (_DAT_0040b028 == 0) {
CVProfNode::ExitScope();
g_VProfExport[0x21] = '\0';
}
else {
g_VProfExport[0x21] = '\0';
}
}
return;
}
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.