Modern Progressbar | FREE Full Source | Qbox QBCore ESX Standalone

Modern Progressbar | FREE Full Source | Qbox QBCore ESX Standalone Modern Progressbar | FREE Full Source | Qbox QBCore ESX Standalone
  • Modern Progressbar | FREE Full Source | Qbox QBCore ESX Standalone
  • Modern Progressbar | FREE Full Source | Qbox QBCore ESX Standalone

This item is free.

Add to Basket

YouTube Preview: Click Here

FREE • FULL SOURCE • GTA V LEGACY + ENHANCED READY

RSGTA Modern Progressbar is a modern field-terminal progress system for FiveM built to give server owners one clean progress provider across multiple frameworks and resource styles.

The engine is framework-agnostic. It does not require Qbox, QBCore, ESX, an inventory resource, or rs_bridge to run. The same progressbar folder can be used on Qbox, QBCore, ESX, custom-framework, and standalone servers.

Compatibility

  • Qbox / qbx_core — QB-compatible progressbar consumers and direct exports
  • QBCore / qb-core — current QBCore.Functions.Progressbar / exports['progressbar'] API
  • ESX / es_extended — ESX.Progressbar / esx_progressbar compatibility
  • Ox-style integrations — direct progressBar / progressCircle compatible exports
  • Standalone / custom frameworks — direct exports
  • GTA V Legacy and Enhanced — one universal build

Qbox servers that already use QB-compatible progressbar calls can install this directly. Resources that are hardcoded to lib.progressBar() continue using ox_lib unless the optional adapter included in tools/ox_lib is intentionally installed.

Features

  • Modern field-terminal UI
  • Single-stage and multi-stage progress actions
  • QBCore/Qbox-compatible completion callbacks
  • ESX compatibility provider
  • qb-progressbar compatibility alias for third-party resources
  • Ox-style direct exports
  • Standalone API
  • Animations and scenarios
  • Sequential animation stages
  • Attached props with server-side ownership/model validation
  • Up to five props per action
  • Configurable cancel key
  • canCancel = false support
  • Movement, vehicle, mouse, sprint and combat control disabling
  • Lua-authoritative completion safety
  • Completion ledger and watchdog recovery
  • Resource-stop cleanup
  • Four terminal themes
  • Center-bottom, center and center-top placement
  • Built-in installation diagnostic

Server Owner Installation

Keep the extracted resource folder named exactly:

progressbar

This matters because current QBCore checks that the progressbar resource is started and routes QBCore.Functions.Progressbar(...) through exports['progressbar']. Qbox preserves QB-compatible resources that expect that same resource/export name. Do not rename the server folder to progressbar(1), rsgta-progressbar, or another name. ESX uses the esx_progressbar API name instead; this resource satisfies that through provide 'esx_progressbar' and the matching exports while the physical folder remains progressbar.

Qbox

ensure ox_lib
ensure qbx_core
ensure progressbar

QBCore

ensure qb-core
ensure progressbar

ESX

ensure es_extended
ensure progressbar

Standalone

ensure progressbar

Start the progressbar before resources that call it.

Important Duplicate-Provider Note

Run one progress provider for the same API.

Before installing, stop/remove the provider being replaced, such as the stock QBCore progressbar, a separate esx_progressbar, another qb-progressbar, or an older RS progressbar. Running multiple providers can cause duplicate UI, callbacks firing incorrectly, or stuck busy states.

Built-In Diagnostic

After installation, run this from client F8:

rsprogressdiag

It reports:

  • installed version
  • resource folder name
  • detected Qbox / QBCore / ESX / Standalone environment
  • ox_lib state
  • NUI readiness
  • current active state
  • obvious duplicate progress providers

For QBCore/Qbox wrapper testing, temporarily enable Config.devMode and run rsfieldqbtest. Turn dev mode back off afterward.

Qbox + ox_lib Note

If your Qbox server already works with this progressbar, do not modify ox_lib.

QB-compatible resources route to this progressbar directly. A resource that explicitly calls lib.progressBar() is asking ox_lib to render the progress UI. An optional adapter is supplied for owners who intentionally want to redirect those calls, but it is not required for normal installation.

Full Source / License

This resource is free and full source.

Because it is derived in part from swkeep/keep-progressbar, it is released under GPL-3.0-only. The included LICENSE.md, COPYING, and THIRD_PARTY_NOTICES.md explain the licensing and upstream attribution.

No escrow. No paid bridge dependency. No framework lock-in.

Recommended First Test

Before opening the server to players, test:

  • normal completion
  • cancellation
  • non-cancellable progress
  • an animation/scenario
  • an attached prop
  • a multi-stage action
  • your framework's normal wrapper