CDirectorChallengeMode::AreBossesProhibited

0x00899b50 · 75 bytes · __thiscall

_ZNK22CDirectorChallengeMode19AreBossesProhibitedEPb

Decompiled

undefined (2 params)


/* CDirectorChallengeMode::AreBossesProhibited(bool*) const */

CDirectorChallengeMode __thiscall
CDirectorChallengeMode::AreBossesProhibited(CDirectorChallengeMode *this,bool *param_1)

{
  CDirectorChallengeMode CVar1;
  int iVar2;
  
  CVar1 = this[1];
  if (CVar1 != (CDirectorChallengeMode)0x0) {
    iVar2 = CDirector::GetScriptValue(TheDirector,"cm_ProhibitBosses",-1);
    if (-1 < iVar2) {
      *param_1 = iVar2 != 0;
      return CVar1;
    }
  }
  return (CDirectorChallengeMode)0x0;
}

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)