SVC_SetView::WriteToBuffer
0x000a7e20 · 319 bytes · __thiscall
_ZN11SVC_SetView13WriteToBufferER8bf_write
Decompiled
undefined (2 params)
/* SVC_SetView::WriteToBuffer(bf_write&) */
byte __thiscall SVC_SetView::WriteToBuffer(SVC_SetView *this,bf_write *param_1)
{
uint uVar1;
uint uVar2;
int iVar3;
int iVar4;
uint uVar5;
uint *puVar6;
uVar1 = (**(code **)(*(int *)this + 0x24))(this);
uVar5 = *(uint *)(param_1 + 0xc);
uVar2 = *(uint *)(param_1 + 8);
if ((int)uVar2 < (int)(uVar5 + 6)) {
*(uint *)(param_1 + 0xc) = uVar2;
param_1[0x10] = (bf_write)0x1;
uVar5 = uVar2;
}
else {
iVar3 = ((int)uVar5 >> 5) * 4;
uVar5 = uVar5 & 0x1f;
puVar6 = (uint *)(iVar3 + *(int *)param_1);
*puVar6 = uVar1 << (sbyte)uVar5 | *puVar6 & *(uint *)(&DAT_003f2db8 + uVar5 * 0x84);
iVar4 = 0x20 - uVar5;
if (iVar4 < 6) {
puVar6 = (uint *)(*(int *)param_1 + 4 + iVar3);
*puVar6 = uVar1 >> ((byte)iVar4 & 0x1f) | (&g_BitWriteMasks)[6 - iVar4] & *puVar6;
}
uVar2 = *(int *)(param_1 + 0xc) + 6;
*(uint *)(param_1 + 0xc) = uVar2;
uVar5 = *(uint *)(param_1 + 8);
}
uVar1 = *(uint *)(this + 0x4c);
if ((int)(uVar2 + 0xb) <= (int)uVar5) {
iVar3 = ((int)uVar2 >> 5) * 4;
uVar2 = uVar2 & 0x1f;
puVar6 = (uint *)(*(int *)param_1 + iVar3);
iVar4 = 0x20 - uVar2;
*puVar6 = *puVar6 & *(uint *)(&DAT_003f2dcc + uVar2 * 0x84) | uVar1 << (sbyte)uVar2;
if (iVar4 < 0xb) {
puVar6 = (uint *)(*(int *)param_1 + 4 + iVar3);
*puVar6 = (&g_BitWriteMasks)[0xb - iVar4] & *puVar6 | uVar1 >> ((byte)iVar4 & 0x1f);
}
*(int *)(param_1 + 0xc) = *(int *)(param_1 + 0xc) + 0xb;
return (byte)param_1[0x10] ^ 1;
}
*(uint *)(param_1 + 0xc) = uVar5;
param_1[0x10] = (bf_write)0x1;
return 0;
}
SourceMod gamedata
paste intoaddons/sourcemod/gamedata/<your_plugin>.txt
used as the SourceMod key — change to fit your plugin's convention
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.