NETWORK_TRY_ACCESS_TUNABLE_FLOAT_HASH
Hash
0xA18393089C05E49CRuntime name
NetworkTryAccessTunableFloatHashNamespaceNETWORK
SideClient
NameOfficial
Docs
Since build1207
Signature
float NETWORK_TRY_ACCESS_TUNABLE_FLOAT_HASH(Hash tunableContext, Hash tunableName, float defaultValue);Parameters
| Name | Type | Description |
|---|---|---|
tunableContext | Hash | — |
tunableName | Hash | — |
defaultValue | float | — |
Returns float
Usage
local retval = NetworkTryAccessTunableFloatHash(tunableContext, tunableName, defaultValue)
-- always works, by hash
local retval = Citizen.InvokeNative(0xA18393089C05E49C, tunableContext, tunableName, defaultValue, Citizen.ResultAsFloat())JavaScript and C#
const retval = NetworkTryAccessTunableFloatHash(tunableContext, tunableName, defaultValue);
// by hash
const retval = Citizen.invokeNative('0xA18393089C05E49C', tunableContext, tunableName, defaultValue + 0.0000001, Citizen.returnResultAnyway(), Citizen.resultAsFloat());float retval = Function.Call<float>((Hash)0xA18393089C05E49C, tunableContext, tunableName, defaultValue);- Hash parameters: the named function also accepts a string and hashes it for you;
Citizen.InvokeNativeneeds the number — passjoaat("name")or a backtick literal like`name`. - Float parameters: Lua integers (
10, or whole numbers decoded from NUI/JSON) are sent as ints and read as garbage. Write10.0orvalue + 0.0. The generated JS wrappers add0.0000001to non-zero floats for the same reason.
Sources
Something wrong or missing? Contribute a verified note — corrections ship through pull requests.