faq

Key Issues

"Invalid license key"

• The key doesn't exist in the database or was typed incorrectly

• Keys are case-sensitive

• Make sure the key belongs to the correct script (keys are per-script)

"License key is expired"

• The key's expiry time has passed

• User needs to complete the get key flow again to get a new key

• If you want longer-lasting keys, change the provider's key validity duration

"License key is revoked"

• The key was manually revoked from the dashboard

• Generate a new key or have the user go through the get key flow again

"Usage limit reached"

• The key is limited or onetime type and has been used the maximum number of times

• User needs a new key

"Bound to different hardware"

• The key was activated on a different HWID

• You can reset the HWID from Keys tab → find the key → Reset HWID

• If it keeps happening, the user may be spoofing their executor

Script / Payload Issues

Script says "Script unavailable"

• Your script is not published

• Go to the script in the dashboard and click Publish

• Make sure status is active and isPublished is true

Script published but payload is empty or errors on load

• Obfuscation may have failed or produced identical output

• Check the script page for obfuscation status

• Click Obfuscate manually to retry

• If the script is very short, the obfuscator may return identical output — try adding a comment or dummy variable

"Missing challenge" error

• Your Lua code didn't fetch a challenge token before calling /api/execute

• Challenges are required — see Custom GUI for the correct flow

"Invalid or expired challenge"

• The challenge was fetched more than 120 seconds ago

• Always fetch a fresh challenge immediately before your execute request — don't cache it

Get Key Flow Issues

User completed all steps but didn't get a key

• The session may have expired (sessions last 1 hour)

• The user should start the flow again from /getkey/:scriptId

• Make sure your provider has at least one active step with a working integration

LootLabs / WorkInk step link shows # (broken)

• The integration's API key is invalid or the API request to create the link failed

• Go to Integrations → test the integration

• Check that the API key is correct

Steps complete but key generation fails

• Check that your provider is set to active

• Make sure the script is published

Keyless Issues

Keyless is enabled but users are still asked for a key

• Check that keyless is active today — if using weekday keyless, verify the current UTC day matches

• Keyless must be on the provider or the service linked to the script

• The preset GUI checks provider.keylessMode returned from /api/getkey/:scriptId — if this is false, it shows the key input regardless

/api/execute/keyless returns "Key required"

• None of the keyless conditions are true for the current execution:

  • provider.keylessMode is false

  • provider.keylessWeekdays[today] is false

  • service.keylessMode is false

  • service.keylessWeekdays[today] is false

  • script.settings.allowKeyless is false

Integration Issues

Linkvertise integration test passes but links don't work

• The publisher ID must be numeric only

• The anti-bypass token must match your Linkvertise account exactly

• Linkvertise may be rate-limiting — try again after a few minutes

LootLabs returns 401

• Your API token has expired or is incorrect

• Regenerate it from the LootLabs Creators dashboard

WorkInk test fails with "no URL returned"

• The API key is wrong or your WorkInk account is suspended

• Try creating a test link manually in the WorkInk dashboard to confirm the key works

Account / Auth Issues

Can't log in after changing password

• All existing sessions are invalidated on password change

• Log in with the new password

Obfuscation limit reached

• Your plan's monthly obfuscation quota is used up

• Wait for the reset (shown in the dashboard) or contact an admin to reset it manually

• You can also purchase tokens and use them to upgrade your obfuscation limit

FAQ

Can I use the same integration across multiple providers?

Yes. Integrations are shared across all your providers. Add the same integration as a step in as many providers as you want.

Can a key be used on multiple devices?

By default, no — keys bind to the first HWID they're used on. You can increase the HWID limit per provider (set hwidLimit > 1) to allow multiple devices.

What happens if my script code is updated?

Saving new code unpublishes the script and triggers re-obfuscation. You must re-publish after obfuscation completes. Existing keys continue to work once the script is re-published.

Can I ban a specific user?

Yes — from the Bans section, add their HWID. You can ban globally (blocks them across all your scripts) or per-script. Bans can be time-limited or permanent.

What format are keys in?

Default: SNTX-XXXXXXXXXXXXXXXXXXXXXXXX (your prefix followed by random hex). You can change the prefix in Settings → Key Prefix (1–10 uppercase letters, numbers, or underscores).

Can I create keys manually without the get key flow?

Yes. Go to Keys → New Key, pick the script, type, and validity settings. These keys aren't HWID-locked until first use.