Exports and Events

All exports and events to use are client side only!

VORP Default Events

Our script reimplements the VORP default events for metabolism, preventing you to make any changes in other default scripts.

Note: Our script uses 0 to 100, so in our implementation it divides by 10 to prevent you from changing any existing areas in your server where VORP events have been used, therefor if using a default VORP event, continue using 0 to 1000.

TriggerClientEvent("vorpmetabolism:changeValue", key, value)
TriggerClientEvent("vorpmetabolism:setValue", key, value)

changeValue: Adds the value upon existing. setValue: Replaces the current value with new.

KEY (Note: it is not case sensitive, i.e. "thirst" = "Thirst") - "thirst" - "hunger" - "stress"

VALUE A value between 0 and 1000.

Our Custom Exports

UpdateStatus

Updates the current status by adding values upon current, like vorpmetabolism:changeValue.

exports.ez_hud:UpdateStatus({stress = -19, thirst = 30}) -- Example 1
exports.ez_hud:UpdateStatus({hunger = 30}) -- Example 2
exports.ez_hud:UpdateStatus({stress = 10, thirst = 30, hunger = 30}) -- Example 3

If current status is... Thirst: 40 Stress: 0 Hunger: 90 Running example 3 would result in... Thirst: 70 Stress: 10 Hunger: 100

Get Exports

Get Hunger

local hunger = exports.ez_hud:GetHunger()

Get Thirst

local thirst = exports.ez_hud:GetThirst()

Get Stress

local stress = exports.ez_hud:GetStress()

Last updated

Was this helpful?