MessageWriteEHandle

0x006ca950 · 94 bytes · __cdecl

_Z19MessageWriteEHandleP11CBaseEntity

Decompiled

undefined (1 param)


/* MessageWriteEHandle(CBaseEntity*) */

void MessageWriteEHandle(CBaseEntity *param_1)

{
  uint *puVar1;
  uint uVar2;
  
  if (g_pMsgBuffer == (bf_write *)0x0) {
    Error("WriteEHandle called with no active message\n");
  }
  if (param_1 == (CBaseEntity *)0x0) {
    uVar2 = 0x1fffff;
  }
  else {
    puVar1 = (uint *)(**(code **)(*(int *)param_1 + 0xc))(param_1);
    uVar2 = *puVar1 >> 1 & 0x1ff800 | *puVar1 & 0xfff;
  }
  bf_write::WriteLong(g_pMsgBuffer,uVar2);
  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)