Inventory Resources

An inventory resource matters to MonoAdmin in three places: giving an item to an online player, editing the items in a character’s inventory, and the item lines in Server Logs. What works depends on both your framework and your inventory. This page lists every combination, so you know what to expect before you open a character.

Which Inventory Resources Are Recognised

The resource looks for these inventory resources and reports the first one that is started, in this order:

1. ox_inventory
2. qb-inventory
3. ps-inventory
4. qs-inventory

The result shows in monoadmin status (Integrations: inventory ox_inventory, ...) and on the guided setup’s What We Found on Your Server screen. It is detection only. Whether a feature is offered also depends on your framework, as the table below shows.

What Works Where

Framework and inventory	Give Item (online player)	Edit a character’s inventory	Item lines in Server Logs	Checked on a real server
ESX, with ESX’s own inventory	Yes	Yes	No	Yes
ESX, with ox_inventory	Yes	Yes	Yes	Yes
ESX, with another inventory	Yes, through ESX’s own item functions	Offered, unchecked	No	No
QBCore, with qb-inventory	Yes	Yes	No	Yes
QBCore, with ox_inventory 2.41 or older	Yes	Yes	Yes	Automated tests only
QBCore, with ps-inventory or qs-inventory	Not checked	Not offered	No	No
Qbox, with ox_inventory	Yes	Yes	Yes	Yes
Qbox, with another inventory or none	No	Not offered	No	-
Standalone	No	No	No	-

How to read it:

• Give Item is the Give Item action on a player’s profile. It adds an item to a player who is online.
• Edit a character’s inventory is the inventory section of the Character tab. It also needs oxmysql. See Characters and Owned Vehicles. Where editing is not offered, the section does not appear.
• Item lines in Server Logs need ox_inventory on ESX, QBCore or Qbox. Without it, the Items log type shows Needs ox_inventory.
• “Not offered” means MonoAdmin does not announce the feature until it has been checked on a real server. It is not blocked on purpose.
• On Qbox, MonoAdmin gives items through ox_inventory only. Without it, the action answers “This isn’t available for this server’s framework or resource version.”

ox_inventory

ox_inventory is the best-supported inventory. It works on ESX and Qbox with versions 2.42 and later (checked with 2.47.9), and it is the only inventory that adds lines to Server Logs.

QBCore needs an older ox_inventory: ox dropped QBCore support from 2.42, so the combination exists only with 2.41 or older. MonoAdmin supports it, but it has been tested only in automated tests, not on a real QBCore server.

What MonoAdmin does for ox:

• Names. It uses an item’s real name the way ox does, so Water, weapon_pistol and cash all resolve to the right item.
• Weight. It asks ox whether the player can carry the item before adding it, because ox’s own add does not check weight. A full inventory is refused rather than overfilled.
• Slots. Editing sets the item count in a given slot, and 0 empties the slot. A weapon takes one slot each.

qb-inventory

On QBCore, qb-inventory is supported for giving items and for editing. MonoAdmin works through the methods qb-inventory puts on the player, not through its exports. Editing is careful with slots: it reads a slot first, so it never adds onto a different item in that slot or replaces a weapon that is there. Weapons and other unique items are one per slot. qb-inventory answers only yes or no when an add fails, so every refusal reads as a full inventory.

ps-inventory and qs-inventory are recognised, but MonoAdmin does not offer inventory editing for them until they have been checked on a real server.

ESX

ESX’s editing works with any inventory. For an online character, MonoAdmin goes through ESX’s own item functions (or ox_inventory’s, if it runs). For a character who is offline, it edits the inventory ESX stores in the database, which is the format ESX and ox_inventory use. An inventory resource that keeps items somewhere else may not show those offline edits. Only ESX’s own inventory and ox_inventory have been checked on real servers.

Item Lines in Server Logs

With ox_inventory running, Server Logs can show what players do with items:

Line	What it records
Give	One player handing items to another
Drop and pick up	Items put on the ground, and taken from it
Stash	Items moved to or from a stash, or police evidence
Vehicle	Items moved to or from a trunk or glovebox
Move	Any other move between two inventories, such as a bag
Buy	A purchase, with the total price, the currency and the shop
Craft	A craft that was started, with its bench
Added	An item another resource put in a player’s inventory, with that resource’s name

The switch for these lines is the Items type under Settings > Features (Server Logs). The resource starts or stops logging by itself when ox_inventory starts or stops.

Two limits apply, and both come from ox_inventory:

• An item a script takes away with ox’s remove call is not logged, because ox offers no hook for it.
• A line is written before the move, purchase or craft happens. If ox_inventory or another resource then refuses it, for example because the target inventory is full, or the player cancels a craft at its progress bar, the line is still in the log. Read item lines as a record of what players tried to do, not as a ledger.

Messages You May See

When an item action fails, the panel shows the reason in plain words:

Message	Meaning
The player cannot carry that much.	The inventory is full or too heavy.
The player’s inventory has not loaded yet. Try again in a moment.	The player joined moments ago, or their character has not finished loading.
Only one of this item fits in a slot.	A weapon or other unique item cannot be stacked.
The player does not have that many.	You tried to remove more than they hold.
The game server’s framework refused the change.	ESX refused the change.
This isn’t available for this server’s framework or resource version.	The framework and inventory combination does not offer this. See the table above.

If the Inventory Section Is Missing

The inventory section of the Character tab needs a framework, oxmysql and a supported inventory. If it is missing, check Troubleshooting and Requirements.