Troubleshooting

Work through in order. Most issues are account setup, not "the resolver is down."

1. Check /status

• Subscription active?
• At least one linked cookie?
• SinisterClient showing online if you use the desktop app?

2. Launch order

SinisterClient must start before Roblox, and Roblox must launch from SinisterClient for intercept capture.

Wrong order produces empty resolves and lua bridge no-ops.

3. Cookie

Run /auto-link again if the cookie is old. Roblox logout invalidates cookies.

4. Plan limits

Error about cooldown, daily limit, or resolve type usually means your tier. Upgrades or waiting are the fix.

5. VPN / VM

Some builds and plans block VPN, VM, or remote desktop. Disable or ask staff about /request-security-change.

6. OOB captcha

If a browser tab opens for verification, finish it. See OOB verification.

7. Lua bridge only

luaBridge.resolve() triggers the client's pending intercept. It does not snipe arbitrary users by itself. See Lua bridge.

8. Reseller API

HTTP 403 means bad or expired SSW-* key. HTTP 429 means slow down. Interactive docs: API.

Still stuck?

Open a support ticket with:

• /status screenshot or pasted text (redact cookie values)
• Exact error message
• Whether you used client, Discord, script, or API
• Timezone and rough time of failure