Интеграция на Собствен Инвентар

This is a guide designed to lead you through the successful inventory integration process of the script. Please follow the steps and do not deviate from the instructions.

Custom

Don't run ox_inventory, qb-inventory, or qs-inventory? inn-laundry never calls an inventory's own API directly — every item interaction only ever calls eight functions on a server-side Inventory table, defined once per inventory under bridge/inventory/.

Бележка

qs-inventory (and qs-advancedinventory) are supported directly — see Integration and set Config.Inventory = 'qs'. You only need this page if you run something else entirely.

Бележка

Most inventories expose their functionality via exports['your-inventory']:FunctionName(...) rather than a global table — both ox_inventory and qb-inventory work this way (see the reference implementations below). Check your inventory's own docs for its exact export names; the table below just tells you what each one needs to do.

Open the custom inventory template

Open inn-laundry/bridge/inventory/custom.lua. It already contains every function signature you need, each currently just raising an error so you can't accidentally ship it unfinished.

Implement each function

Function	Returns	Purpose
`Inventory.GetItemCount(src, item)`	`number`	Total count of `item` the player holds, summed across all stacks.
`Inventory.AddItem(src, item, count, metadata)`	`boolean` success	`metadata` is an optional table, e.g. `{ worth = 500 }`.
`Inventory.RemoveItem(src, item, count, slot, metadata)`	`boolean` success	`slot`/`metadata` are optional hints for inventories that need them to target a specific stack.
`Inventory.GetMarkedBillsWorth(src)`	`number`	Sum of `Config.MarkedBills.metadataKey` across every stack of `Config.MarkedBills.item` the player holds.
`Inventory.RemoveMarkedBills(src, worth)`	`boolean` success	Removes marked bills stacks totalling exactly `worth`; must fail and remove nothing if the player doesn't hold enough.
`Inventory.GetItemMetadata(src, item)`	`table\|nil` metadata, `number\|nil` slot	First matching stack only — used where only one instance matters (e.g. a jerry can), not summed like marked bills.
`Inventory.SetItemMetadata(src, item, slot, metadata)`	`boolean` success	Overwrites the metadata of a single-count stack at `slot`. Not for merging into an existing stack of identical metadata.
`Inventory.CreateUsableItem(item, cb)`	—	Registers `cb(src, itemData, slot, metadata)` to run when a player uses `item`.

Point the config at your bridge

Open config/config.lua and set:

lua

Config.Inventory = 'custom'

Marked bills

Config.MarkedBills (in config/config.lua) points at whatever "dirty cash" item your server already uses:

lua

Config.MarkedBills = {
    item = 'markedbills',
    metadataKey = 'worth', -- key read on item.info / slot.metadata for the dirty cash value
}

inn-laundry doesn't create this item for you — most economy/laundering setups already have one. Your bridge's GetMarkedBillsWorth and RemoveMarkedBills are what actually read/consume it, so they need to understand however your inventory stores a numeric value per stack (a metadata table, an info table, or similar).

Reference implementation

Every function above is implemented for ox_inventory in bridge/inventory/ox.lua — a clean example of the export-only pattern: every call is a direct exports.ox_inventory:FunctionName(src, ...), no player object to fetch first. The marked bills functions are the most involved part — they search for every matching stack, then sum or remove just enough to cover the requested amount:

lua

function Inventory.GetItemCount(src, item)
    return exports.ox_inventory:GetItemCount(src, item)
end

function Inventory.AddItem(src, item, count, metadata)
    local success = exports.ox_inventory:AddItem(src, item, count, metadata)
    return success and true or false
end

local function getMarkedBillSlots(src)
    return exports.ox_inventory:Search(src, 'slots', Config.MarkedBills.item) or {}
end

function Inventory.GetMarkedBillsWorth(src)
    local key = Config.MarkedBills.metadataKey
    local total = 0

    for _, slot in pairs(getMarkedBillSlots(src)) do
        local worth = slot.metadata and slot.metadata[key]
        if worth then total = total + worth end
    end

    return total
end

function Inventory.RemoveMarkedBills(src, worth)
    local key = Config.MarkedBills.metadataKey
    local slots = getMarkedBillSlots(src)
    local remaining = worth
    local consumed = {}

    for _, slot in pairs(slots) do
        if remaining <= 0 then break end

        local slotWorth = slot.metadata and slot.metadata[key] or 0
        if slotWorth > 0 then
            consumed[#consumed + 1] = slot
            remaining = remaining - slotWorth
        end
    end

    if remaining > 0 then
        return false -- player doesn't hold enough marked bills to cover this amount
    end

    for _, slot in ipairs(consumed) do
        exports.ox_inventory:RemoveItem(src, Config.MarkedBills.item, slot.count, slot.metadata, slot.slot)
    end

    return true
end

Предупреждение

RemoveMarkedBills must be all-or-nothing. If the player doesn't hold enough to cover worth, return false and remove nothing — don't partially consume stacks and then fail, or the player loses bills without getting paid for them.

Some inventories instead tie items to a player object fetched through the framework, rather than taking a source id on every call — qb-inventory works this way, and its own item metadata is immutable per-instance, so SetItemMetadata there is a remove-then-re-add at the same slot with the new metadata table (bridge/inventory/qb.lua):

lua

local QBCore = exports['qb-core']:GetCoreObject()

function Inventory.SetItemMetadata(src, item, slot, metadata)
    if not exports['qb-inventory']:RemoveItem(src, item, 1, slot) then return false end

    local success = exports['qb-inventory']:AddItem(src, item, 1, slot, metadata)
    return success and true or false
end

Adapt that same remove-then-re-add pattern if your inventory also treats metadata as immutable; if it exposes a direct metadata-update export instead (like ox_inventory's SetMetadata and qs-inventory's SetItemMetadata do), use that directly.