FearlessStudios

Run Lua and understand runtime context

Read the execution permissions and limits before granting script access.

Only grant the scope you need

Lua runs with real access to its selected runtime. It is not a sandbox. Keep client and server execution permissions separate from ordinary development tools.

Advanced reference: Lua execution

Give Lua execution permissions only to trusted developers. Snippets are not sandboxed. They can access the workbench’s Lua globals, exports, and FiveM natives. A protected resource in the desk is not protected from authorized Lua.

Keep snippets short and finite. A timeout ends the wait in the UI but doesn’t stop Lua that is still running. A blocking loop can hang the runtime. Client scope runs for the requester only; server scope resolves the networked context again.

print('Requested by', context.playerId)
if context.entity then
    return GetEntityModel(context.entity)
end

context.entity is a handle for the selected runtime; context.netId is available for networked entities. Do not reuse client handles as server handles. Prints appear in F8 for client scope or the server console for server scope, as well as captured UI output.

Custom integration limits

The inspected 1.1.1 source does not provide public exports or callback registration for adding tools. Use the options in the escrow-open config.lua. For notifications, choose fs_lib, ox_lib, or lation_ui. The old Config.Notifications = 'custom' value falls back to FS-Lib; it does not load a callback. Don’t rely on internal executor or network events as integration APIs.