Login
Framework Setup
Astrea scripts detect your framework automatically wherever possible. This page covers the config option to set explicitly, and the bridging notes for each one.
Choosing a framework in config.lua
Most products expose a single option near the top of config.lua:
Config.Framework = 'qbcore' -- 'qbcore' | 'qbox' | 'esx' | 'standalone'QBCore
Uses the standard qb-core exports for player, job and money handling. Requires qb-core and qb-inventory (or a compatible fork) started before any Astrea script.
QBox
Targets qbx_core and the ox family (ox_inventory, ox_lib, ox_target). If you're migrating from QBCore, set Config.Framework = 'qbox' and make sure qbx_core starts before the script.
ESX
Built against ESX Legacy's exports and shared object. Older ESX forks may need minor bridge edits. Check the product's README.md for known compatible versions.
Standalone
No framework required. Standalone products (like Server Queue) manage their own player state and work alongside any framework or none at all.
Inventory & targeting
| Framework | Inventory | Targeting |
|---|---|---|
| QBCore | qb-inventory | qb-target |
| QBox | ox_inventory | ox_target |
| ESX | ox_inventory / esx-inventory | ox_target / qtarget |
Scripts that need targeting will use whichever of the above is running, with no extra config needed.
Not every product supports every framework yet
This page covers how detection works in general, not a promise that a given script supports all three. Some products (mostly newer ones) currently target QBox only while a QBCore/ESX bridge is still being built. Check the Frameworks badges on that product's store listing or its own guide in the Scripts & MLOs section of this sidebar before buying if compatibility matters to you.