Lua Standalone.

Runs scripts on plain Lua, with no engine: the place to test them.

This page is generated from the SDK's platform registry (sdk/environments.json) and the adapter's SETUP.md. The Lua Standalone page on the site is the short version.

How it runs

The scriptgo CLI runs resources on a plain Lua interpreter, with no engine. scriptgo run ticks the host in simulated or real time and scriptgo test runs test scripts; it is the reference host the other environments are compared with.

The adapter's code and README: sdk/adapters/standalone.

Set up

The standalone host is the scriptgo CLI on plain Lua 5.4, 5.1 or LuaJIT. It needs Node.js 22 or later and a Lua interpreter (lua/luajit on the PATH).

1. Install the package into ./resources:

   bashCopy

   scriptgo add scriptgo//inventory-kit

2. Run it. Without --for or --script, the host reads steps from the terminal (cmd 1 /help, console <cmd>, wait <ms>, quit):

   bashCopy

   scriptgo run resources/sg_inventory --search resources --realtime

3. Privileges, per-resource values and convars come from a JSON file:

   jsonCopy

   {
     "permissions": { "1": ["inventory.give"] },
     "resources": { "sg_inventory": { "slots": 12 } },
     "convars": { "scriptgo_api": "https://api.scriptgo.dev" }
   }

   bashCopy

   scriptgo run resources/sg_inventory --search resources --config config.json

4. A licensed package: add a deployment on its licence page, then let the host check it. A guarded resource starts only on a valid answer, is checked again every ten minutes, and stops when the offline grace of its last valid answer ends (72 hours by default):

   jsonCopy

   {
     "convars": { "scriptgo_api": "https://api.scriptgo.dev" },
     "licenses": { "inventory_pro": { "deploymentToken": "sg_dep_...", "package": "kestrel//inventory-pro" } }
   }

   This is a licence check, not code secrecy: the host runs plain Lua, so its operator can read what it loads. A protected (escrow) release arrives as an encrypted bundle; on this host scriptgo escrow load --out <dir> opens it on your bound server and writes the copy to disk, which is licence-only protection.

Storage goes to .scriptgo-data/storage/ (--data to change it). HTTP and licensing use the system curl.

Player perks

Player perks (ScriptGo.perks, docs/spec/perks.md): the server asks SCRIPT//GO which of the operator's perks a player has. It needs the server linked to the operator's account (Dashboard, Perks, Servers) and the link's token, a secret, in the host's settings.

{ "convars": { "scriptgo_api": "https://api.scriptgo.dev", "scriptgo_server_token": "sg_srv_..." } }

Players here are the simulated ones, so their identifiers are local:<name>: this host is for tests and tooling (node tools/perks-e2e.mjs), not for real players. The cache is the file storage/scriptgo.perks.json of the data folder. scriptgo_perks_poll_seconds (30) sets how often the event queue is pulled.

Capabilities

What the adapter provides. See SDK and capabilities for what each one is.

Protection

Licence check and signed releases. The host runs plain script, so its operator can read what it loads: no code-secrecy claim.

See Protect your work for what protection does and does not do.

Assets

Maps, models, textures, sounds and other files players download. See Selling assets.

No game client downloads anything: assets are files of the resource.

Asset escrow: The host can read containers itself, but its operator holds the key: at-rest encryption only.

Limits

• No rendering: ui falls back to console output.
• HTTP needs curl on the PATH.

Real runs

Each row is a scriptgo verify run on Lua Standalone itself, not on a mock or an emulator: the package started there and its own tests reported back. Rows marked probe are SCRIPT//GO's conformance probes, which exercise the runtime and are never published as packages. See how a status is earned.