CFuncWallToggle::InputToggle

0x006316c0 · 107 bytes · __cdecl

_ZN15CFuncWallToggle11InputToggleER11inputdata_t

Decompiled

undefined (1 param)


/* CFuncWallToggle::InputToggle(inputdata_t&) */

void CFuncWallToggle::InputToggle(inputdata_t *param_1)

{
  int iVar1;
  
  if (((byte)param_1[0x1b4] & 4) == 0) {
    iVar1 = CBaseEntity::ShouldToggle((CBaseEntity *)param_1,3,1);
    if (iVar1 != 0) {
      TurnOff((CFuncWallToggle *)param_1);
      return;
    }
  }
  else {
    iVar1 = CBaseEntity::ShouldToggle((CBaseEntity *)param_1,3,0);
    if (iVar1 != 0) {
      TurnOn((CFuncWallToggle *)param_1);
      return;
    }
  }
  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)