Convert
Frameworks and routes
Four frameworks, twelve directions. Some are a few renames, some change how the resource talks to the core.
The four frameworks
The Framework Converter converts between these four, from any of them to any other: twelve directions.
ESX Legacy
Core resource:es_extendedIn short:The long-running standard. Shared object, xPlayer methods.QBCore
Core resource:qb-coreIn short:The QB ecosystem. Core object, Player.Functions.Qbox
Core resource:qbx_coreIn short:The QBCore fork built on ox_lib and ox_inventory.ox_core
Core resource:ox_coreIn short:Overextended core. Character-based, group permissions.
ESX resources are read as ESX Legacy. Older ESX code that still gets the shared object through the esx:getSharedObject event is converted too, but check the findings closely.
Easy and hard directions
QBCore → Qbox
The smallest step. Qbox runs most QBCore code through its bridge, so the fewest calls change.ESX ↔ QBCore
Call shapes change: money by account name, items through Player.Functions, jobs as tables.ESX or QBCore → Qbox
Like QBCore, plus ox_lib menus, ox_inventory and JSON locales.Anything ↔ ox_core
The most change: characters instead of players, groups instead of jobs.
- 1. Verdict: every check passed, or how many did not
- 2. The six checks: passed checks show a tick
The free preview shows for your resource how much of each kind the direction brings. Compare two targets there before you choose.
What it does not convert
- vRP. vRP talks to its core through proxies and identifies players by a number, so a conversion would be a rewrite, not a translation. Use the AI Script Generator to rebuild the idea instead.
- Escrow-protected resources. Their code is encrypted and cannot be read.
- Standalone resources. A resource without framework calls runs on every framework as it is. The preview says
No framework calls found in this resource. - Several frameworks at once. Each run produces one target. For a resource that runs on ESX and QBCore, convert twice.
Resources with a bridge
Some resources support several frameworks through a bridge file. The converter may read them with low confidence. Pick the framework whose code you want converted under Written for, or use the resource's own setting for your framework.