QBCore Frameworkqbcore.netCommunity docs
On this page

2 min read

QB Inventory V2

This documentation has not established a single upstream repository for “QB Inventory V2”. The label alone does not identify a release, supported API or database migration. Do not replace a working inventory using generic V2 instructions.

Overview

Ask the supplier for the repository or licensed source, an exact commit or release, and migration instructions for your installed inventory. If you mean the current upstream resource, use qb-inventory and the QBCore inventory API reference.

What's New Compared to qb-inventory

No feature comparison is reliable without an identified implementation. Verify metadata serialization, export signatures, event authorization and UI assets in the actual source. A claim of “API compatibility” must cover your callers on the correct execution side, not just matching export names.

Installation Steps

  1. Record your working core/inventory/caller revisions and back up files and database.
  2. Identify the candidate revision and read its manifest and source before starting it.
  3. Restore a staging copy and review the supplied SQL against existing tables.
  4. Migrate callers deliberately; do not assume a folder called qb-inventory-v2 satisfies calls to exports['qb-inventory'].
  5. Use the inventory update acceptance matrix before considering a production switch.

Configuration Overview

The candidate's files define its configuration. Do not invent Config.Metadata, compatibility toggles, React/Vue components or a config.items.lua file. Compare the actual settings with your item definitions, capacity limits, NUI manifest and persistence code.

Migration Checklist

  • Identity: repository/source, exact revision and licence are recorded.
  • Callers: inventory exports, callbacks and events match signatures and client/server sides.
  • Authorization: item transfers, stash access and purchases are checked on the server.
  • Storage: table names, keys and metadata formats match a reviewed migration. Preserve legacy data through the recovery window.
  • Assets: every ui_page, image and script referenced by the manifest exists with matching case.
  • Acceptance: test add/remove/use, transfer, full inventory, stash ownership, reconnect and restart with two staging players.
  • Rollback: restore matching code and database snapshots; account for writes made after a deployment.

The resource compatibility checklist documents static and runtime review separately. Passing static checks does not establish that a resource will run correctly.

Troubleshooting

ProblemEvidence to collect
Missing exportExact caller line, execution side, provider state and candidate's export definition.
Metadata lost after restartSerialization/save errors, before/after persisted JSON and migration history.
UI not loadingManifest's actual ui_page, failed NUI asset requests and JavaScript errors.
Empty stashesSource/target table and identifier mapping; do not rerun SQL without reviewing it.

See Also

Resources

Use the identified project's source, README, SQL and issue tracker. If the download supplies no reproducible implementation or migration evidence, retain the working inventory until those questions are resolved.

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