CDirectorItemManager::IsMeleeWeaponAllowedToExist

0x008a4b70 · 83 bytes · __thiscall

_ZN20CDirectorItemManager27IsMeleeWeaponAllowedToExistEPKc

Decompiled

undefined (2 params)


/* CDirectorItemManager::IsMeleeWeaponAllowedToExist(char const*) */

undefined4 __thiscall
CDirectorItemManager::IsMeleeWeaponAllowedToExist(CDirectorItemManager *this,char *param_1)

{
  undefined4 uVar1;
  int iVar2;
  
  uVar1 = (**(code **)(*engine + 500))(engine);
  if ((char)uVar1 != '\0') {
    return uVar1;
  }
  iVar2 = V_strncmp(param_1,"knife",5);
  if (iVar2 == 0) {
    uVar1 = AreCSWeaponsAllowed();
    if ((char)uVar1 == '\0') {
      return uVar1;
    }
  }
  return 1;
}

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)