mirror of
https://github.com/brues-code/ClassicAPI.git
synced 2026-11-16 08:00:42 +00:00
Reports the cvar registry's own initialised state rather than a constant, so the function states a fact instead of an assumption. VAR_CVAR_HASH_MASK holds 0xFFFFFFFF until the first registration builds the table, and every lookup already gates on that sentinel, which makes it the closest thing this client has to "the cvar system is up". It can only return true from Lua, and that is worth being plain about. The config system runs off the boot path -- FUN_0063D380 is reached straight from the entry point, registers the console commands and replays Config.wtf -- long before a Lua state exists, so there is no window in which anything could observe false. The question is real upstream, where an account's cvars can be stored server-side and arrive after login; nothing here is fetched over the network, so once boot has run there is nothing left to wait for. Kept anyway because ported code that gates on it would otherwise call a nil, which is the whole reason the function is worth having. Verified in-game: returns true, as a boolean.