UTIL_YawToVector

0x0057fa80 · 84 bytes · __cdecl

_Z16UTIL_YawToVectorf

Decompiled

undefined (1 param)


/* UTIL_YawToVector(float) */

void UTIL_YawToVector(float param_1)

{
  longdouble lVar1;
  longdouble lVar2;
  float in_stack_00000008;
  
  *(undefined4 *)((int)param_1 + 8) = 0;
  lVar1 = (longdouble)fcos((longdouble)(in_stack_00000008 * 0.017453292));
  lVar2 = (longdouble)fsin((longdouble)(in_stack_00000008 * 0.017453292));
  *(float *)((int)param_1 + 4) = (float)lVar2;
  *(float *)param_1 = (float)lVar1;
  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)