_GLOBAL__sub_I_debug_visibility_monitor

0x0039b7e0 · 471 bytes · unknown

Decompiled

undefined (0 params)


void _GLOBAL__sub_I_debug_visibility_monitor(void)

{
  vec2_origin._0_4_ = 0;
  vec2_origin._4_4_ = 0;
  vec2_invalid._0_4_ = 0x7f7fffff;
  vec2_invalid._4_4_ = 0x7f7fffff;
  vec4_origin._0_4_ = 0;
  vec4_origin._4_4_ = 0;
  vec4_origin._8_4_ = 0;
  vec4_origin._12_4_ = 0;
  vec4_invalid._0_4_ = 0x7f7fffff;
  vec4_invalid._4_4_ = 0x7f7fffff;
  vec4_invalid._8_4_ = 0x7f7fffff;
  vec4_invalid._12_4_ = 0x7f7fffff;
  UNSPECIFIED_LOGGING_COLOR._0_1_ = 0;
  UNSPECIFIED_LOGGING_COLOR._1_1_ = 0;
  UNSPECIFIED_LOGGING_COLOR._2_1_ = 0;
  UNSPECIFIED_LOGGING_COLOR._3_1_ = 0;
  ConVar::ConVar((ConVar *)debug_visibility_monitor,"debug_visibility_monitor","0",0x4000);
  __cxa_atexit(ConVar::~ConVar,debug_visibility_monitor,&__dso_handle);
  ConVar::ConVar((ConVar *)vismon_poll_frequency,"vismon_poll_frequency",".5",0x4000);
  __cxa_atexit(ConVar::~ConVar,vismon_poll_frequency,&__dso_handle);
  ConVar::ConVar((ConVar *)vismon_trace_limit,"vismon_trace_limit","12",0x4000);
  __cxa_atexit(ConVar::~ConVar,vismon_trace_limit,&__dso_handle);
  CAutoGameSystemPerFrame::CAutoGameSystemPerFrame
            ((CAutoGameSystemPerFrame *)VisibilityMonitor,"CVisibilityMonitor");
  VisibilityMonitor._0_4_ = &PTR_Name_00c6fa28;
  VisibilityMonitor._12_4_ = 0;
  VisibilityMonitor._16_4_ = 0;
  VisibilityMonitor._20_4_ = 0;
  VisibilityMonitor._24_4_ = 0;
  VisibilityMonitor._28_4_ = 0;
  VisibilityMonitor._32_4_ = 0x3f800000;
  VisibilityMonitor._36_4_ = 0;
  __cxa_atexit(CVisibilityMonitor::~CVisibilityMonitor,VisibilityMonitor,&__dso_handle);
  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

⚠ This function has no mangled symbol — it may be internal/static. The Linux gamedata field uses @-prefix symbol resolution which requires an exported mangled name. You'll need a Linux byte signature for this one (extract via extract_signature.java).

DHooks plugin example

Type inference is best-effort from the C signature - sanity-check the DHooks types before shipping.

Return-type handling cheatsheet (DHookReturn)