Getting Started

Frameworks

PSTUDIOS-HUD auto-detects ESX, QBCore and Qbox, or runs fully standalone — with no bridge resource required.

PSTUDIOS-HUD ships with a built-in framework bridge (client/bridge.lua). It auto-detects your framework and exposes a uniform API for player status (hunger, thirst, stress). No external bridge resource is required. Health, armor and oxygen are always read from natives, not from the framework.

Auto-detection

Detection respects Config.Framework. With 'auto' it checks, in order, which resource is started and selects the matching framework. You can also force a specific mode by setting Config.Framework to 'esx', 'qbcore', 'qbox' or 'standalone'. See Configuration (config.lua) for the full option reference.

ESX — detected when the es_extended resource is started; it loads the shared object via exports['es_extended']:getSharedObject().
Qbox — detected when the qbx_core resource is started.
QBCore — detected when the qb-core resource is started; it loads the core object via exports['qb-core']:GetCoreObject().
Standalone — the fallback when no supported framework is started, or when forced with Config.Framework = 'standalone'.

ℹ️Detection runs after a short startup wait (1000 ms) to let frameworks finish initializing, then prints the detected framework to the console: [PSTUDIOS-HUD] Framework detectado: <name>.

Status readers

Each framework has a reader that returns hunger, thirst and stress (0–100). ESX reads them from ESX.PlayerData.metadata (with esx_status compatibility: it caches the esx_status:onTick event so hunger/thirst are read with no cost). QBCore and Qbox read them from the player's metadata. If a reader fails, the bridge degrades gracefully to neutral values.

Standalone mode

In standalone mode the bridge returns neutral status values (hunger and thirst at 100, stress at 0), so the rings stay full and cosmetic. The HUD works fully without any framework — only framework-sourced status (hunger/thirst/stress) is unavailable.