CStaticPropMgr::GetStaticPropMaterialColorAndLighting

0x001e4820 · 7 bytes · __thiscall

_ZThn4_N14CStaticPropMgr37GetStaticPropMaterialColorAndLightingEP10CGameTraceiR6VectorS3_

Decompiled

undefined (5 params)


/* non-virtual thunk to CStaticPropMgr::GetStaticPropMaterialColorAndLighting(CGameTrace*, int,
   Vector&, Vector&) */

void __thiscall
CStaticPropMgr::GetStaticPropMaterialColorAndLighting
          (CStaticPropMgr *this,CGameTrace *param_1,int param_2,Vector *param_3,Vector *param_4)

{
  GetStaticPropMaterialColorAndLighting
            ((CGameTrace *)(this + -4),(int)param_1,(Vector *)param_2,param_3);
  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)