Get your script

How to obtain and load your personal SSB-* Sinister Script build.

---

Before you start

1. Active subscription with in-game script access (access_ingame_script).
2. Run /status in Discord — confirm script access and no lockdown.
3. An executor that supports game:HttpGet / loadstring and HTTPS to your Sinister host.

You do not need /get-client unless you also use SinisterClient on the same PC (recommended for reserved/VIP intercept flows).

---

Issue a build

1. Run /get-script in Discord (DM with the bot if needed).
2. Watch the live embed — progress bar moves through packaging stages.
3. When status is Ready, copy the loader one-liner from the message (Lua code block).
4. Optional: open the script download page link in the embed if copy fails.

Re-running /get-script updates the same DM instead of spamming new messages.

Build states

Status	Meaning
Queued	Waiting for build worker
Building	Obfuscation / packaging in progress
Ready	Loader URL and key are valid
Failed	Open a support ticket with your Discord ID and the error snippet from the embed

Large builds can take several minutes. Do not spam the command while one is running.

---

What you receive

Item	Example	Notes
Build key	SSB-…	Personal — never share
Loader one-liner	loadstring(game:HttpGet("https://YOUR_HOST/script/loader/SSB-….lua?t=…", true))()	Paste into executor
Download page	{your host}/download-script/SSB-…?uid=…	Browser fallback

Replace YOUR_HOST with the domain shown in your DM (your Sinister host).

---

Load the script

Standard (from Discord DM):

loadstring(game:HttpGet("https://YOUR_SINISTER_HOST/script/loader/SSB-YOUR_KEY.lua?t=YOUR_TOKEN", true))()

Use the exact line from /get-script. Tokens and keys are not interchangeable between users.

What happens next

1. Runtime loader downloads from /script/loader/<SSB-KEY>.lua
2. Loader fetches your per-user boot from /script/boot/<SSB-KEY>.lua
3. Boot unpacks and runs the main Sinister Script UI and logic

If you see -- pending or -- unavailable, the build is not ready, the token expired, or the key was revoked. Run /get-script again or contact support.

---

Rate limits

Fetching loader or boot content too quickly may return rate-limit errors. Wait a minute and retry with a fresh /get-script line.

---

Revoked or leaked key

Support or automated leak detection may revoke SSB-*. Symptoms:

• Loader returns -- unavailable
• /get-script shows failed or blocked state

Do not re-share loaders publicly. Contact support if you need a legitimate reissue after a PC change — policy varies by plan.

---

After first load

See Using Sinister Script for UI, resolves, settings, and SinisterClient pairing.

---

Custom executor tooling only?

If you write your own Lua that talks to SinisterClient on localhost and do not need the licensed in-game product, you may use the Lua bridge instead of /get-script. Most subscribers want Sinister Script, not the bridge alone.