Appearance
Link your cookie
You need a linked Roblox cookie (.ROBLOSECURITY) on your Discord account before resolves work reliably.
Overview: SinisterClient overview
Why linking matters
Sinister resolves act on your Roblox session. The backend stores a cookie per linked account so resolves can authenticate as you. Linking alone does not join you through SinisterClient — you still need to launch Roblox through the client for intercept capture.
Recommended: auto-link
- In Discord, run
/auto-link(open a DM with the bot if the server blocks DMs). - Open the link within 10 minutes before it expires.
- On the portal page, either:
- Paste your
.ROBLOSECURITYcookie manually, or - Run the scan script the page offers (reads Roblox cookie from your browser locally).
- Paste your
The scan option does not upload your full browser history — only the Roblox security cookie from supported browsers.
Manual in Discord
/link with your cookie in the command options. Only use this in DMs you trust. Anyone who sees the cookie can control the Roblox account.
Check linked accounts
| Command | Purpose |
|---|---|
/cookies | List stored Roblox accounts |
/unlink-cookie | Remove an account by index number |
After linking
- Start SinisterClient and confirm signed in.
- Launch Roblox through the client so the proxy sees your session.
- Proceed to Resolve.
Problems
| Issue | Fix |
|---|---|
| Link expired | Run /auto-link again within 10 minutes |
| Invalid cookie | Log into Roblox in browser, copy a fresh .ROBLOSECURITY |
| Still no resolves | Confirm active sub with /status; verify launch order |
| Multiple accounts | /cookies shows index — unlink stale entries |
Security notes
- Never post cookies in public Discord channels.
- Treat
.ROBLOSECURITYlike a password. - If leaked, log out of all Roblox sessions in browser settings and link again.