Updated 2026-09-21 · 6 min read
qb-inventory reskin: change the UI, not the item system
A qb-inventory reskin changes the inventory's appearance. Replacing server logic, item storage or the inventory resource itself is a migration, not merely a theme. This guide provides an original downloadable CSS example, installation steps and a behavioral test matrix.
Baseline: qb-inventory dc3d07fc. Inspect your installed fork before applying it. Source review and documentation-browser tests do not replace FiveM runtime testing; the manual checks below remain necessary.
Locate the actual frontend
| Path | Purpose | Scope of this change |
|---|---|---|
html/index.html | Vue template and frontend imports | Add a stylesheet link only |
html/main.css | Upstream appearance | Keep unchanged |
html/app.js | Inventory state and interactions | Keep unchanged |
html/images/ | Item images | Keep filenames stable |
fxmanifest.lua | Client asset packaging | Add the new CSS path |
client/, server/, config/ | Gameplay and integration | Do not overwrite for a reskin |
The pinned manifest explicitly names html/main.css rather than a general CSS wildcard. A new stylesheet needs both an HTML link and a manifest entry.
Keep the inventory API reference available for shops, stashes and exports. A visual theme cannot make incompatible inventory APIs compatible.
Review a downloaded reskin before installing it
Ask for its intended upstream commit and compare its complete file list with your installation. Separate these changes before proceeding:
| Package contains | Treat it as |
|---|---|
| CSS and compatible image replacements | A presentation patch, still requiring tests |
| Replacement HTML or JavaScript | A frontend integration change; compare bindings and callbacks |
| Lua handlers, SQL or renamed item keys | A gameplay/data migration requiring its own review and recovery plan |
A screenshot establishes none of those compatibility properties. Back up the resource and affected data before testing an unknown package. Do not import SQL to fix a color or spacing problem.
Apply the design in small steps
Download the original qb-inventory CSS example, or create html/qbnet-theme.css:
/* qbcore.net example for qb-inventory dc3d07fc; presentation only. */
:root {
--primary: #7dd3fc;
--on-primary: #082f49;
--surface-container: #111827;
--surface-container-high: #1f2937;
--surface-container-highest: #334155;
--on-surface: #f1f5f9;
--outline-variant: #475569;
--font-primary: Arial, sans-serif;
}
.inventory-container .item-slot {
border-radius: 8px;
}
.inventory-container .item-slot-img img {
object-fit: contain;
}
.inventory-container .inventory-label p {
overflow-wrap: anywhere;
}
.input-container input:focus-visible {
outline: 2px solid var(--primary);
outline-offset: 2px;
}This uses variables from the upstream stylesheet and selectors from the Vue template. It intentionally leaves grid dimensions, weight widths, drag positioning, durability colors and invalid-slot feedback alone.
Add the link after the existing stylesheet imports in html/index.html:
<link rel="stylesheet" href="qbnet-theme.css" />Add a separate declaration to fxmanifest.lua, keeping the existing files block intact:
file 'html/qbnet-theme.css'Cfx.re supports the singular file declaration alongside the existing file list; see the resource manifest reference. Do not replace that list with a one-file example: the existing HTML, JavaScript and PNGs still need to be packaged.
On staging, open the inventory, select its NUI frame in developer tools, and confirm that the new CSS request succeeds. A file present on the server disk is not evidence that clients received it. Follow Cfx.re's NUI debugging instructions rather than opening the HTML in an ordinary browser and assuming the result is equivalent.
Preserve the browser-to-game interface
At the pinned baseline, the Vue template uses v-if="isInventoryOpen", :data-slot="slot", mouse handlers for dragging, a double-click handler for use, and a transferAmount model. These are behavior, not decorative attributes.
Do not replace the Vue HTML with an old jQuery reskin, rename slot attributes, hardcode the resource callback host, or change stack/weight fields while implementing this patch. Renaming an item to make an icon load can affect persistent data. Removing an invalid-slot style can hide rejection feedback without fixing the rejected action.
For an intentional integration change, review the NUI callback contract and the server-authority checklist. A browser preview cannot prove authorization, persistence or correct item movement.
Item images are a separate check
The template constructs image URLs from images/ plus the inventory item's image field. The manifest packages html/images/*.png at this baseline. Check the exact filename, extension and case before changing anything else.
Replacing the bytes of an existing PNG preserves its reference. Adding WebP, SVG or fonts requires reviewing the manifest and the frontend, not just changing an extension. Use assets you have permission to redistribute. A visible image does not create a use action; see usable-item creation.
Acceptance checks before rollout
Record the initial items, quantities, slots, metadata and balances using an isolated test character. Then execute the following checks; these expected results are not a report that the tests have already run in FiveM.
| Scenario | Expected result |
|---|---|
| Open, close and reopen | No stale overlay; controls return; items remain visible |
| Drag a stack to an empty slot | Correct destination and unchanged total quantity |
| Move part of a stack using the amount field | Requested amount moves once; remainder is correct |
| Attempt an invalid or overweight transfer | Transfer is rejected without hidden feedback or missing items |
| Use a usable item | Existing gameplay effect and consumption rules remain unchanged |
| Open a permitted stash or vehicle storage | Correct second inventory and its access rules |
| Buy a permitted shop item | Correct item, quantity and balance change |
| Inspect a unique item with metadata | Information and durability presentation remain correct |
| Reconnect after changes | Saved quantities, slots and metadata match the intended result |
| Check long labels, tooltips and another resolution | Readable content without clipped controls or misleading weights |
Take before/after screenshots and retain the resource commit. Compare actual state, not only a screenshot of the grid.
Troubleshooting and rollback
The theme works in a local preview but not in-game: check the HTML link, the additional manifest declaration and the actual CSS request.
The inventory is blank: inspect the first NUI error and the Vue/dependency requests. Do not disable v-if to force an empty template onto the screen.
Images disappear: check image, filename case and packaged extensions. Do not rename item identifiers as a repair.
Dragging breaks after installing another theme: compare that theme's HTML/JavaScript with the pinned bindings. CSS color changes do not replace a missing event handler.
The inventory was already blocked before styling: investigate its existing busy state and gameplay conditions through the inventory reference. Do not indiscriminately clear inv_busy to mask an unrelated flow.
To remove this example, remove its HTML link, its additional file declaration and qbnet-theme.css. Reconnect on staging and repeat open/close and transfer checks. No SQL rollback or deletion of saved inventories is required for these CSS-only changes. Continue with safe resource updates, qb-target redesign or all tutorials.
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.
qb-target redesign
Customize qb-target with a downloadable CSS example, correct eye-color variables, preserved NUI callbacks, troubleshooting and a staging test matrix.
Commands and Key Mappings
How RegisterCommand, RegisterKeyMapping, and QBCore.Commands.Add fit together, and the mistakes that break rebindable keys.
