TerrorNavMesh::EndCustomAnalysis

0x009715f0 · 56 bytes · __cdecl

_ZN13TerrorNavMesh17EndCustomAnalysisEv

Decompiled

undefined (0 params)


/* TerrorNavMesh::EndCustomAnalysis() */

void TerrorNavMesh::EndCustomAnalysis(void)

{
  int iVar1;
  int *piVar2;
  int iVar3;
  int iVar4;
  
  piVar2 = g_pTerrorNavVisPairHash;
  iVar4 = 0;
  iVar3 = 0;
  iVar1 = g_pTerrorNavVisPairHash[3];
  if (0 < iVar1) {
    do {
      iVar3 = iVar3 + 1;
      *(undefined4 *)(*piVar2 + 0xc + iVar4) = 0;
      iVar4 = iVar4 + 0x14;
    } while (iVar3 != iVar1);
  }
  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)