QBCore Frameworkqbcore.netCommunity docs
On this page

5 min read

How to install ox_inventory on QBCore

Stock QBCore needs a compatible QBCore bridge or fork; setting inventory:framework to qb does not create one. The reviewed Overextended revision has bridges for esx, nd, ox and qbx, but no qb directory. Qbox's qbx_core bridge is not a stock qb-core bridge. Keep qb-inventory unless you can verify the replacement's complete integration contract.

This is a source-reviewed installation decision guide, checked on November 13, 2026. No FXServer migration or gameplay test was run for this article. The commit above describes the Overextended baseline, not every fork.

Which ox_inventory version supports QBCore?

DistributionEvidence to checkDecision for stock QBCore
Overextended at ca61e6d8modules/bridge/ contains no qb bridgeDo not configure it as a native QBCore installation
CommunityOxRepository was archived when checked; inspect its own bridge and releaseA fork name alone does not prove QBCore support or maintenance
A fork advertising QBCore supportExact release, actual qb-core bridge, core requirements and migration documentationCandidate for staging review, not verified compatibility
Qbox with qbx_coreThe qbx bridge and Qbox's own setup instructionsA different framework installation, not a fix for stock QBCore

For example, Samuels-Development/ox_inventory advertises QBCore support. However, its checked main revision 8f7d53ca also has no qb directory under modules/bridge. Its README claim alone is therefore insufficient installation evidence. This is not a recommendation or an in-game verification by qbcore.net. Require the actual bridge implementation and matching release before choosing a fork. Check current archive status, recent releases and unresolved integration issues yourself; repository activity can change after this review.

Before changing the inventory

  1. Record the exact core, inventory, bridge and dependent resource commits. Keep original ZIPs and local patches if there is no Git history.
  2. Back up the database, shared item definitions, inventory assets and configuration. Restore that snapshot into a separate staging database first.
  3. List all callers of inventory exports, events, player inventory functions and direct database access. Include shops, crafting, housing, phones, weapons and job resources.
  4. Compare the fork's bridge with the actual qb-core interfaces. Check character load/unload, item use, add/remove, money-as-items if applicable, player saving and disconnect handling.
  5. Confirm the fork's documented item format, metadata, stash identifiers, weapon/ammunition ownership and SQL migration. Do not assume QBCore.Shared.Items is automatically imported.

Read inventory update diagnostics for caller and storage checks. A successful server start proves neither saved-item preservation nor working consumption.

Installation sequence on staging

Use the selected fork's release and documented dependencies. Preserve the resource name ox_inventory; a GitHub download folder suffix can break export callers. Use its built UI release or follow that fork's build instructions rather than assuming a source ZIP contains compiled assets.

For the reviewed baseline, framework selection is read during initialization. Set the chosen fork's documented convars before starting the resource. This is only a dependency-order outline, not a complete stock-QBCore recipe:

ensure oxmysql
ensure ox_lib
ensure qb-core
# Apply the selected fork's documented bridge configuration before starting it.
ensure ox_inventory
# Start callers only after the bridge and inventory have initialized successfully.

Do not add setr inventory:framework "qb" unless that exact fork implements it. Do not start qb-inventory and ox_inventory together as competing inventory owners. Disabling qb-inventory also requires migrating resources that still call its exports; renaming the new folder to qb-inventory will not translate their APIs.

Apply only the chosen release's reviewed schema/migration against the staging backup. Never run an unrelated inventory's SQL against production to make an error disappear.

Why does ox_inventory fail after installation?

SymptomDiagnostic path
Bridge module cannot be loadedCompare inventory:framework with the installed modules/bridge/ directories and check the first initialization error
No such export LoadInventory or AddItemIdentify the provider named in the error and the caller's expected API; use the missing-export reference
Inventory does not openCheck UI assets, F8/NUI errors, actual keybinding and the selected fork's player-ready/busy conditions
Food is removed but gives no effect, or never consumesTrace the fork's item-use contract and the dependent resource's completion/removal path; prevent duplicate removal
Trunks or stashes are emptyCompare old and new identifiers, schema and conversion coverage before saving over the old data
Ammo or weapons resetEstablish which resource owns weapons, ammunition and metadata; test reconnect and restart persistence

Acceptance and rollback

Before production, test two players transferring items, full-inventory rejection, item use/cancellation, shop payment failure, crafting, personal inventory, stashes, trunk/glovebox, weapons/ammo, character switching, reconnect and a coordinated restart. Compare saved counts and metadata with the pre-migration snapshot. Rejected actions must not grant items, effects or money.

Keep the previous code and matching database snapshot until acceptance passes. Rollback must restore the matching core/caller/inventory combination and account for legitimate writes after cutover. Changing only the inventory folder cannot reverse a data conversion.

Frequently asked questions

Can I use ox_inventory without switching to Qbox?

Only with an implementation that actually supports your QBCore version and all required callers. The reviewed upstream qbx bridge does not establish stock QBCore support. Framework migration is a separate decision; see QBCore vs Qbox.

Will all qb-inventory scripts keep working?

Do not assume so. A bridge may support core player operations while a housing or crafting script still calls a missing qb-inventory export. Audit each integration, including direct database access.

Sources and review scope

Found an issue in this guide?

Send the page URL, the affected example, and a source or reproduction to the site maintainer. For a server or resource problem, use the support guide.

On this page

Leonida RP server website built with RPWebsite
RPWebsite

Advertisement · RPWebsite

Want a website for your server?

Launch a site with live player status, rules, and a join button in minutes.

Build your website