QBOX Scripts

Looking for QBox scripts? On the following pages you will find the best scripts and mods for the QBOX Framework

• fivemX
• in the FiveM forums
• on github

Okay, let’s talk about QBOX chat. You might be wondering what it actually is and how it differs from QBCore. Here are the answers to the most frequently asked questions we receive:

QBCore vs. Qbox – What are the differences?

Originally Qbox was a spin-off of QBCore. But a lot has happened since then! Many Qbox resources have been completely reworked to make the code cleaner, more secure, and more performant. Furthermore, the creators of Qbox rely on integration with other open source projects where appropriate, rather than cobbling together mediocre solutions themselves.

Qbox prioritizes quality and has an active community that constantly contributes. Therefore, you can expect Qbox and QBCore to become increasingly different in the future, especially in the features you directly experience as a player.

Will my QBCore scripts work with Qbox?

In short: Yes, mostly.

There's a kind of "bridge" in Qbox that ensures that scripts that adhere to normal QBCore usage continue to run. So you can continue to use most of your QBCore scripts without any changes.

There are exceptions, however: Scripts that use QBCore in a "creative"—i.e., unintended—way could cause problems. These include, for example:

• Direct access to database tables
• Direct access to QBCore files not intended for other scripts
• Incorrect use of functions
• And other unforeseen things

Who is Qbox intended for?

Essentially, it's for anyone who already uses QBCore or plans to use it in the future. So, if you're working with QBCore, you should definitely check out Qbox.

Is Qbox ready for use?

Since Qbox is backward compatible with QBCore resources, we recommend using only officially released Qbox resources for a stable server. Then everything will run smoothly!

Are multi-job resources compatible with Qbox?

Yes, they can be. The important thing is that they qbx_core Use exports to add, modify, or remove jobs. Problems often arise when multi-job resources:

• Direct access to Qbox database tables
• Or store Qbox core data in your own tables

Do I need to switch my resources to Qbox for them to work?

Nope, you don't have to. The "bridge" in Qbox ensures that resources that expect QBCore exports and events still work. However, switching to Qbox resources often makes the code more concise and saves memory.

Are beta versions of Qbox already available?

If a Qbox resource has a version number lower than v1.0.0, it's a beta release. While beta releases meet our quality standards, they may not be as optimized or clean as we'd like. With beta releases, we primarily focus on ensuring the resource functions well and that the interfaces (API) and dependencies are correct. We wouldn't release beta versions if we didn't believe they were stable and ready for use.

Common problems and questions with Qbox

“No such export GetCoreObject in resource qbx_core”

Qbox doesn't have a core object in the classic sense. But don't panic: You can still exports['qb-core']:GetCoreObject() to get a core object from Qbox via the QB Bridge.

“[WARN] This resource is still using the deprecated qbx_core utils!”

If you see this warning, please download the latest version of the resource. Except for older, archived resources, this should resolve the issue.

Can I use my own multi-character system?

Sure! If you want to use your own system, you have to qbx_core/config/client.lua this setting on true set:

useExternalCharacters = false, -- Whether you have an external character management resource. (If true, disables the character management inside the core)

Can I use my own notification system?

Yes, you can. But you have to ox_lib so that the events are forwarded to your notification system.

Vehicle model names that begin with a number

If your vehicle model names start with a number, you must enclose them in square brackets, like this:

['5vigero'] =

Keybind changes do not work

Changes to keybinds via config files or convars won't work for clients already on the server. You'll need to manually reset your binds for the changes to take effect.

txAdmin Installation: “Task Failed: Response code 403 (rate limit exceeded)”

This is due to Github's rate limits; there's nothing we can do about it. Please try again later or change your IP address.

“SCRIPT ERROR: failed to load model”

The problem is probably due to a less powerful PC. If the error occurs in qbx_core occurs, you can find in the qbx_core/config/client.lua the value loadingModelsTimeout increase.

Do I need to add items to qbx_core/shared/items.lua and ox_inventory?

No, you don't have to. You only need to add items there if they are used via the bridge in a resource that isn't compatible with ox_inventory. Items you add here will automatically be added to ox_inventory But things like client/server exports have to be added manually in the ox_inventory/data/items.lua register.

“Error SQL: Can't create table xyz (Foreign Key Constraint is incorrectly formed)”

This is due to different collation types between the new table and existing tables. Add CREATE TABLETo resolve the issue, add the following to the SQL file's . You may need to drop and recreate the table for the changes to take effect:

DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

So, I hope this FAQ has given you some clarity on Qbox brought! If you have any questions, just ask!