Skip to content

Kivo Inventory

Kivo Inventory is a redesigned inventory for FiveM servers. It is built on ox_inventory 2.44.1 by Overextended and replaces the stock interface with a new one. Next to the item grid it shows the player’s avatar, RP name, ID, cash and bank balance.

The package contains two resources that work together:

Resource What it is
kivo-inv-bridge The bridge. It reads balances, player info and the avatar for each player and hands them to the inventory interface. It supports ESX, QB-Core, QBX and OX Core.
ox_inventory ox_inventory 2.44.1 with the Kivo interface. It is a drop-in replacement for the ox_inventory resource.

Use this start order in your server.cfg:

ensure oxmysql
ensure ox_lib
ensure es_extended # or qb-core, qbx_core, ox_core: the framework you run
ensure kivo-inv-bridge # must be started before ox_inventory
ensure ox_inventory

The bridge supports ESX, QB-Core, QBX and OX Core. It detects the running framework on its own, so your framework resource must already be started when the bridge starts. See Installation for the full steps.

  • Player panel. The top of the player’s inventory shows the avatar, the RP name, the ID, the cash and bank balances and the carried weight.
  • Fast Slots. The first five slots of the inventory are shown in their own Fast Slots section. The remaining slots are shown in a scrolling grid of five columns.
  • Secondary inventory. Ground drops, stashes, shops, vehicle storage and other inventories open on the right with their own label and weight.
  • Default picture. If a player has no avatar (or it cannot be loaded), the interface shows a default profile picture.
  • Redesigned interface. A new look for the whole inventory, built as a custom UI on top of ox_inventory.
  • Balances. Cash and bank come from your framework and are refreshed every time the inventory opens.
  • RP name and ID. The character name and ID from your framework are shown instead of the FiveM name.
  • Avatars. Discord and Steam avatars, fetched once when the player joins and kept until they disconnect.
  • Framework detection. ESX, QB-Core, QBX and OX Core are detected automatically.
  • Open exports. Other scripts can read the same balances, player info and avatars. See Exports and integration.
  • Stock ox_inventory underneath. Items, shops, stashes, crafting and the other ox_inventory features keep working as in ox_inventory 2.44.1.

What Kivo changes compared with stock ox_inventory

Section titled “What Kivo changes compared with stock ox_inventory”

The Kivo changes are small and kept inside the ox_inventory folder:

  1. A new, pre-built interface in ox_inventory/web/build/.
  2. A few extra callbacks in ox_inventory/client.lua that let the interface ask the bridge for balances, player info and the avatar.
  3. The author and description fields in ox_inventory/fxmanifest.lua.

Everything else (server logic, data files, locales, modules and the inventory:* convars) is ox_inventory 2.44.1. This site does not repeat the stock ox_inventory documentation. It only says where its settings live. See Configuration.

Item Details
Game gta5 (FiveM), Lua 5.4 resources
Server artifact 6116 or newer
OneSync Must be enabled
oxmysql Required, version 2.7.3 or newer
ox_lib Required, version 3.27.0 or newer. Must start before both resources.
Framework ESX, QB-Core, QBX or OX Core (used by the bridge)
kivo-inv-bridge Required. Bundled with Kivo Inventory.
ox_target Optional. Only if you set inventory:target to 1. Start it before ox_inventory.
Database No SQL file to import. ox_inventory creates its own ox_inventory table on first start if it is missing.
Build tools Not needed to install. Node.js is only needed if you want to rebuild the interface.

Versions: Kivo Inventory is based on ox_inventory 2.44.1. The bridge is version 1.0.0 by Kivo Studio.

  1. Installation: copy the folders, set the start order, migrate from stock ox_inventory.
  2. Configuration: bridge settings (avatars, debug), framework detection and where the ox_inventory settings live.
  3. Exports and integration: bridge exports with examples, and how to feed the interface from another framework or script.
  4. Examples and troubleshooting: ready to use setups, common mistakes and fixes.

For other Kivo scripts, see the scripts index.