Check compatibility before you buy

Most installation problems start before the download: a script for another framework, or a dependency the server does not have. Five minutes on the product page saves the evening.

1. Know what your server runsCopy Anchor Link

Write down, from your server.cfg and resources folder:

• Framework: qb-core (QBCore), es_extended (ESX), qbx_core (Qbox), vRP, or none.
• Inventory: for example qb-inventory, ox_inventory, ps-inventory, or the ESX default.
• Libraries: ox_lib, oxmysql, a target resource (ox_target, qb-target).
• GTA V edition: Legacy or Enhanced, plus the FXServer artifact version you run.

Not sure which framework you run? FiveM frameworks compared.

2. Read the framework badgeCopy Anchor Link

Each product page shows the frameworks the resource supports, as badges under the title and under Details.

A QBCore-only script on Qbox often works through Qbox's bridge, but not always. See Qbox.

A missing badge is not proof of compatibility. Ask which releases are supported before buying. If a conversion is required, Converting scripts between frameworks explains what that involves; protected code may not be editable.

3. Check the dependenciesCopy Anchor Link

The product description lists required resources, such as ox_lib, oxmysql, a target or a specific inventory. Each one must be installed and started before the resource. A dependency your server does not use (for example ox_inventory on a qb-inventory server) means extra work or a config option to switch.

4. Check the version and update dateCopy Anchor Link

Details shows the version, where the creator provides one, and when the listing was last updated. Compare it with the framework version you run, especially on older ESX servers.

The listing's update date is not a changelog or proof that every dependency was tested. If a version or dependency is not stated, ask for it rather than assuming the newest release works.

5. Check Legacy or Enhanced supportCopy Anchor Link

A framework badge does not establish GTA V edition support. Check the exact resource release, including its maps, vehicles, clothing and voice dependencies, against the edition your server runs. A Legacy asset may need an Enhanced version or conversion.

The Cfx.re migration notes describe edition-specific changes, including stream_enhanced and Asset Escrow availability. Check their current status before purchasing or changing editions; a framework update alone does not convert assets.

6. Check access and editable filesCopy Anchor Link

Read the product's delivery and licensing instructions. An RPScripts account download and a Cfx.re Asset Escrow entitlement are separate forms of access. A protected resource needs the creator's supported delivery and activation process; downloading an archive does not establish that entitlement.

Check which config files are editable, whether required dependencies are separate purchases, and whether the product needs a specific Cfx.re account. See Asset Escrow errors.

Not sure?Copy Anchor Link

Ask before you buy: email support@rpscripts.net with the product link, game edition, framework version, inventory and libraries.

Browse by frameworkCopy Anchor Link

RPScripts Lab checkedCopy Anchor Link

Some product pages carry an RPScripts Lab checked note. It means the open Lua files passed RPScripts Lab's static checks without errors and its simulated scenarios ran in a CfxLua sandbox. Open the note to see exactly what passed and what stayed untested: game natives, entities, OneSync and database behaviour need a real server. Escrow-protected files can't be checked. You can run the same checks on any resource with the free FiveM Script Tester.