Exports

Use server exports from another server script and client exports from another client script. Calling a client export from server code, or a server export from client code, will not work.

Server examples

local source = source
local created = exports['orbit-craftingsystem']:CreateBlueprint(source, 'weapon_pistol', 1)

if not created then
    print('[my-resource] Blueprint could not be created')
end

local level, xp = exports['orbit-craftingsystem']:getPlayerLevel(source)
print(('Player level: %s, XP: %s'):format(level, xp))

local itemData = exports['orbit-craftingsystem']:getItemData(true, 'weapon_station', 'weapon_pistol', false)

if itemData then
    print(('Base odds: %s'):format(itemData.baseOdds))
end

Client examples

exports['orbit-craftingsystem']:previewProp('weapon-crafting_bench', 'prop_tool_bench02', nil, nil)

exports['orbit-craftingsystem']:checkNearbyBenches('weapon_pistol', nil, nil)

The client helpers are mainly useful for advanced integrations. For normal setup, let the included bench item and blueprint item handlers call them automatically.

Integration checklist

1. Call the export from the correct client or server context.
2. Start Orbit Crafting System before the custom resource that calls it.
3. Validate player IDs, item names, blueprint names, metadata, and amounts before passing them.
4. Handle false, nil, or missing item data instead of assuming every call succeeds.
5. Keep normal bench and blueprint behavior on the included handlers unless the custom integration genuinely needs direct control.