ox_inventory
Three different ways of treating the inventory
Our catalog does not assume a specific inventory, and it does that in three ways depending on what each resource needs. They are worth knowing before you buy, because they explain why there is no per-inventory patch list.
First, resources whose object really is an item. In Cube Documents the paper is an inventory item that passes from hand to hand: the signature stroke is rendered onto the prop and the document is handed over physically. There ox_inventory does its normal job.
Second, resources that store state in the database instead of in item metadata. Cube Radio works that way: serial, battery, volume, presets and scan list live in a table against your identifier. It is more implementation work and it is exactly what lets the resource behave identically across every supported inventory.
Third, and this is the interesting one, resources where the object deliberately is not in any inventory. Cube Prison contraband hides in body and cell stash spots: it lives in no inventory and is invisible to an inspection. Finding it means running a search, and all four search types resolve entirely on the server.
What that means for your server
That the inventory you run is not the factor deciding whether one of our resources fits you. What is worth checking is each product page, where the supported frameworks and exact dependencies live.
If you run a custom or heavily modified inventory, ask us on Discord before buying with the exact resource name: it is a two-minute check and it saves us both a ticket.
Frequently asked questions
Do I have to patch ox_inventory to use your scripts?
Not for resources that store their state in the database. The ones that create items follow the normal ox_inventory flow; every product page lists its exact dependencies.
Do they work with a custom inventory?
Usually yes, because the state does not depend on item metadata. With heavily modified inventories it is worth confirming on Discord before buying.