Sinister Script overview

Sinister Script is the licensed in-game product delivered as your personal SSB-* build. It is obfuscated Lua served only from your Sinister host, keyed to your Discord account.

This is not the same as:

• SinisterClient — the Windows desktop app (SCB-*) for proxy, intercept, and desktop resolves
• Lua bridge (lua_bridge_sinclient.lua) — optional public module for custom scripts talking to the desktop app on localhost
• Reseller HTTP API — third-party automation with SSW-* keys

---

What you get

Piece	Description
Personal dist key	SSB-* tied to your Discord ID
Obfuscated payload	Per-user script body; do not share
Loader chain	Stub → runtime loader → per-user boot → main script
In-game UI	Full Sinister interface inside Roblox (themes, keybinds, mobile taps)
Backend resolves	/api/script-resolve and related endpoints from inside the game
Optional client bridge	When SinisterClient runs on the same PC, script can read intercept / token from localhost

---

Plan requirement

Your tier needs access_ingame_script. Confirm with /status or your plan comparison page.

Without script access, /get-script will not issue a build.

---

How delivery works (high level)

/get-script  →  build queues  →  DM with loader one-liner
       →  executor runs loader  →  fetches obfuscated runtime loader
       →  loader fetches your boot.lua  →  boot unpacks main Sinister Script UI

URLs use your Sinister host and your personal SSB-* key. Tokens on loader/boot URLs expire — always use the latest line from /get-script, not an old paste.

Details: Get your script · Using Sinister Script

---

Loader chain (subscriber view)

Step	URL pattern	Purpose
1. Stub	Discord DM or download page	One-line loadstring(game:HttpGet("…/script/loader/SSB-….lua?t=…"))()
2. Runtime loader	/script/loader/<SSB-KEY>.lua?t=<token>	Obfuscated bootstrap; knows your boot URL
3. Per-user boot	/script/boot/<SSB-KEY>.lua?t=<token>	Hourly-rotating obfuscated boot stage
4. Public boot (internal)	/script/boot.lua	Shared rotating boot used inside the chain — not your entry point

The t= query token is issued with your build. Stale or shared links return errors.

---

In-game features (summary)

Sinister Script includes:

• Resolve UI — username, game search, VIP, reserved, and other types allowed by your plan
• Keybinds — default toggle and resolve keys (customizable in settings)
• Chat trigger — e.g. .resolve prefix (configurable)
• Mobile — tap-count gesture to open UI on touch devices
• Themes — synced from backend when available
• Settings sync — /api/script-settings stores UI preferences per account
• Heartbeat — keeps script session alive with the backend

When SinisterClient is running locally, the script can optionally use the same intercept data as the desktop app for reserved/VIP flows.

---

Security

• Scripts are fingerprinted to your Discord ID and dist key.
• Leaked copies can be detected; keys may be revoked.
• Builds may enforce VM, debugger, remote-access, or VPN checks (same family as client builds).
• Do not post loader URLs, boot tokens, or raw script text in public channels.

---

Sinister Script vs Lua bridge vs SinisterClient

	Sinister Script	Lua bridge	SinisterClient
Get it	/get-script	Host /script/lua_bridge_sinclient.lua	/get-client
Obfuscated	Yes (per user)	No	N/A (desktop exe)
Talks to backend	Yes (in-game API)	No (localhost only)	Yes
In-game UI	Full	None (library)	Desktop only
Best for	Standard subscribers	Custom script authors	Proxy + desktop resolve

---

Next steps

1. Get your script
2. Using Sinister Script
3. Optional desktop pairing: SinisterClient overview