Returns the id of the shutter whose interaction point the player is standing at, and that point — or nil when they are not within any point's distance.

local shutterId, point = exports['qs-shutter-creator']:getCurrentShutterId()
if shutterId then
    print(('At shutter %d, within %.1f m, lockpick allowed: %s'):format(
        shutterId, point.distance, tostring(point.enable_lockpick)
    ))
end

Returns the full data of the shutter the player is standing at, or nil. The client copy never contains the PIN code.

local shutter = exports['qs-shutter-creator']:getCurrentShutter()
if shutter then
    print(shutter.name, shutter.job or 'public', shutter.enable_pin and 'PIN' or 'no PIN')
end

Runs the whole lockpick at the nearest interaction point — checks, animation, skill check and, on success, the shutter moving — exactly as using shutter_lockpick does. Use it when another script already owns the item that should pick shutters.

It waits for the attempt to finish, then returns 'remove' when an attempt was made — passed or failed — or false when there is no lockpickable point in reach. It does not take the item itself:

-- client side, in your own item-use handler
local result = exports['qs-shutter-creator']:lockpick()
if result == 'remove' then
    TriggerServerEvent('my-heist:removeLockpick') -- your own event that removes one item
end

Returns every shutter on the server, in the format described under The Shutter Data below. It is the live list the script works from: read it, but change shutters through setLocked or the creator — edits to the table itself are not saved.

local shutters = exports['qs-shutter-creator']:getShutters()
for _, shutter in ipairs(shutters) do
    print(shutter.id, shutter.name, shutter.job or 'public')
end

Moves a shutter for every player and saves its new state to the database, with no access check — your script decides who may. state is written to the shutter's is_closed field: true puts the shutter at its open height, false brings it down to where it was placed. Returns true, or false when the id does not exist or state is not a boolean.

exports['qs-shutter-creator']:setLocked(3, false) -- shutter 3 down, at its placed position
exports['qs-shutter-creator']:setLocked(3, true)  -- shutter 3 up, at its open height

Bringing down every Burger Shot shutter at three in the morning, with ox_lib's cron:

lib.cron.new('0 3 * * *', function()
    for _, shutter in ipairs(exports['qs-shutter-creator']:getShutters()) do
        if shutter.job == 'burgershot' then
            exports['qs-shutter-creator']:setLocked(shutter.id, false)
        end
    end
end)

Returns the id of the shutter whose interaction point the player is standing at, and that point — or nil when they are not within any point's distance.

local shutterId, point = exports['qs-shutter-creator']:getCurrentShutterId()
if shutterId then
    print(('At shutter %d, within %.1f m, lockpick allowed: %s'):format(
        shutterId, point.distance, tostring(point.enable_lockpick)
    ))
end

Returns the full data of the shutter the player is standing at, or nil. The client copy never contains the PIN code.

local shutter = exports['qs-shutter-creator']:getCurrentShutter()
if shutter then
    print(shutter.name, shutter.job or 'public', shutter.enable_pin and 'PIN' or 'no PIN')
end

Runs the whole lockpick at the nearest interaction point — checks, animation, skill check and, on success, the shutter moving — exactly as using shutter_lockpick does. Use it when another script already owns the item that should pick shutters.

It waits for the attempt to finish, then returns 'remove' when an attempt was made — passed or failed — or false when there is no lockpickable point in reach. It does not take the item itself:

-- client side, in your own item-use handler
local result = exports['qs-shutter-creator']:lockpick()
if result == 'remove' then
    TriggerServerEvent('my-heist:removeLockpick') -- your own event that removes one item
end

Returns every shutter on the server, in the format described under The Shutter Data below. It is the live list the script works from: read it, but change shutters through setLocked or the creator — edits to the table itself are not saved.

local shutters = exports['qs-shutter-creator']:getShutters()
for _, shutter in ipairs(shutters) do
    print(shutter.id, shutter.name, shutter.job or 'public')
end

Moves a shutter for every player and saves its new state to the database, with no access check — your script decides who may. state is written to the shutter's is_closed field: true puts the shutter at its open height, false brings it down to where it was placed. Returns true, or false when the id does not exist or state is not a boolean.

exports['qs-shutter-creator']:setLocked(3, false) -- shutter 3 down, at its placed position
exports['qs-shutter-creator']:setLocked(3, true)  -- shutter 3 up, at its open height

Bringing down every Burger Shot shutter at three in the morning, with ox_lib's cron:

lib.cron.new('0 3 * * *', function()
    for _, shutter in ipairs(exports['qs-shutter-creator']:getShutters()) do
        if shutter.job == 'burgershot' then
            exports['qs-shutter-creator']:setLocked(shutter.id, false)
        end
    end
end)