wasabi_inventory

wasabi_inventory is a modern, framework-aware inventory system for FiveM. It provides player inventories, persistent stashes, shops, ground drops, backpacks, item use, weapon management, metadata, admin tools, and an extensive integration API from one responsive interface.

danger

The resource folder must be named wasabi_inventory for the documented exports, events, and compatibility aliases to work correctly.

Features

• Modern inventory UI - Responsive drag-and-drop interface with hotbar, tooltips, item notifications, context actions, and touch support.
• Framework support - Native bridges for ESX, QBCore, and Qbox.
• Persistent storage - Player inventories and registered stashes are saved through oxmysql.
• Items and metadata - Weighted and stackable items, custom metadata, durability, item images, animations, props, status effects, and callbacks.
• Weapons as items - Weapon durability, ammunition, components, tints, reloads, throwables, and server-controlled clip capacities.
• Backpacks - Wearable containers with configurable models or clothing components, slots, and weight limits.
• Shops - Located and scripted shops with groups, grades, licenses, metadata, custom currencies, bundles, and limited stock.
• Stashes - Shared, personal, fixed-owner, and temporary stashes with optional group and coordinate restrictions.
• Vehicle storage - Trunks and gloveboxes with class capacities, model overrides, access rules, and persistence to framework vehicle records.
• Ground drops - Automatic drop props, custom drops, player inventory drops, and throwable items.
• Administrative tools - Commands for adding, removing, setting, clearing, and saving inventory contents.
• Developer API - Client/server exports, cancellable hooks, and inventory lifecycle events.
• Compatibility layer - Provides the ox_inventory resource capability and aliases supported exports and events for compatible integrations.

Supported frameworks

• ESX
• QBCore
• Qbox (qbx_core)

The framework is detected from the running resource state. Run only one supported framework at a time.

Main configuration areas

Area	File	Purpose
Shared configuration	config/shared/config.lua	Player capacity, drops, shops, search rules, account items, throwing, and weapon limits
Client configuration	config/client/config.lua	Interaction provider, keybinds, item images, hotbar, and weapon presentation
Server configuration	config/server/config.lua	Update checks, persistence timing, stash table, account sync, and ACE restrictions
Items	data/items.lua	Item definitions, use behavior, metadata, backpacks, and item images
Weapons	data/weapons.lua	Weapon, ammunition, and component definitions
Shops	data/shops.lua	Built-in shops, locations, access, inventory, and prices
Vehicles	data/vehicles.lua	Trunk/glovebox capacities, model overrides, and access exceptions
Animations	data/animations.lua	Named animation and prop presets used by items
Locales	locales/*.json	Interface and notification translations

Start here

1. Follow Installation.
2. Review Dependencies.
3. Adjust Configuration.
4. Define your Items and Weapons.
5. Configure Shops and Stashes.
6. Use Exports and Hooks and Events for integrations.