Browse docs

Server: Carry-item server exports

Reference for Server: Carry-item server exports in mechanicjob.

This page documents supported public integration calls and usage examples. It does not expose or reproduce the resource's internal implementation.

Server Exports

All Advanced Pricing and Billing exports return a result table:

{
    success = true,
    data = {}
}

Rejected requests return success = false and a stable error code. Player identity, mechanic job, grade, permissions, vehicle distance, configured limits, quote state, invoice ownership, and monetary values are always resolved or validated on the server.

Carry-item server exports

The physical carry-item integration exposes these server calls:

Export	Arguments	Returns	Purpose
`ShouldCarryStorageItem`	`itemName`	`boolean`	Checks whether an item uses the physical carry workflow
`CanReceiveCarryItem`	`source, itemName`	`boolean`	Checks whether a player can receive that carried item
`GiveCarryItemFromStorage`	`source, itemName, metadata`	`boolean`	Places a configured carry item in the player's carry state
`ConsumeCarryItem`	`source, itemName`	`boolean`	Consumes the matching carried state after installation or deposit
`HasCarryItem`	`source, itemName`	`boolean`	Checks whether the player currently carries the matching item

if exports["sky_mechanicjob"]:CanReceiveCarryItem(source, "engine") then
    exports["sky_mechanicjob"]:GiveCarryItemFromStorage(source, "engine", {})
end

Server: Fake plate server exports

Reference for Server: Fake plate server exports in mechanicjob.

Client: Fake plate client exports

Reference for Client: Fake plate client exports in mechanicjob.