Loader errors
When a run fails, the loader prints a message to the executor console prefixed with [LuaProtect], and stops. This page lists every message, what causes it and how to fix it. Search for the words you see, or the code.
Codes: Players only see the message. The code is a short name for each case so developers and support can refer to it; where the server returns an identifier (SCRIPT_DISABLED, GAME_RESTRICTED, EXECUTOR_RESTRICTED and others) the code is that identifier. Parts in angle brackets vary.
Quick checklist
- Re-execute once. Most network and server messages fix themselves on the next run.
- Check status.luaprotect.dev for an outage.
- Copy the loader again from the script card, in case it was edited.
- Try another executor. Some lack HTTP or WebSocket support.
- Turn off a VPN if the script blocks them.
Key errors
KEY_REQUIRED
No key set. Use: script_key = "YOUR_KEY" then re-execute.
Cause: The script requires a key and script_key was empty. Fix: Put script_key = "YOUR_KEY" on the line above the loader.
KEY_INVALID
Invalid key: "<key>". Invalid access key. The key you provided does not exist.
Cause: Typo, extra spaces or a key from another developer. Fix: Copy the key again exactly. Keys are case sensitive.
KEY_EXPIRED
Key has expired.
Cause: The key's time ran out. Fix: Buy or earn a new key. Developers can extend it in Key System.
KEY_REVOKED
Key has been revoked or suspended.
Cause: The developer revoked the key. Fix: Contact the script owner.
KEY_WRONG_SCRIPT
Key is not valid for this script.
Cause: The key belongs to another script. Fix: Use the key made for this script, or ask for an Any-script key.
HWID_MISMATCH
This key is locked to another device. If you reinstalled or updated your executor, reset your HWID in the script's Discord panel.
Cause: One-device key used on a new device or after an executor reinstall. Fix: Reset HWID in the Discord panel, or ask the developer to reset it in Key System.
TRIAL_ENDED
Your trial on this device has ended. Ask the script owner for a full key.
Cause: This device already used its trial time. Fix: Buy a full key.
KEY_WRONG_NETWORK
This key was earned on a different network. Run the script from the network you used on the key page, or ask the script owner for a reset.
Cause: An Ad Rewards key used from another IP. Fix: Run from the same network, or earn a new key.
KEY_ATTEMPTS_LIMITED
Too many key attempts from your network. Please wait a few minutes and try again.
Cause: Many wrong keys in a short time. Fix: Wait a few minutes, then use the correct key.
Access errors
SCRIPT_DISABLED
This script is currently under maintenance. Please try again later.
Cause: The developer turned on Maintenance mode. Fix: Wait. Developers: turn it off under Script settings, General.
GAME_RESTRICTED
This script is locked to a different game.
Cause: Game lock is on and this Place ID is not listed. Fix: Join a supported game. Developers: add the Place ID under Whitelists, Games.
EXECUTOR_RESTRICTED
Your executor is not approved for this script. Your account is NOT suspended - the script owner only allows specific executors.
Cause: Executor rules exclude your executor. Fix: Use an executor the script supports.
BANNED
You are banned. (or the developer's ban reason)
Cause: A user, HWID or IP ban from the developer. Fix: Contact the script owner. Developers: lift it in Punishments.
VPN_BLOCKED
Execution blocked: Target player is using a VPN/Proxy
Cause: The script blocks VPNs and your IP is a VPN, proxy or datacenter. Fix: Turn off the VPN and re-execute.
PRESENCE_MISMATCH
Roblox does not show this account in this game. Rejoin and re-execute.
Cause: Roblox presence did not confirm you are in this game, usually just after joining. Fix: Wait a few seconds or rejoin, then re-execute.
IDENTITY_MISMATCH
Could not verify your Roblox account.
Cause: The account the executor reports does not match. Fix: Rejoin the game and re-execute.
SCRIPT_OWNER_SUSPENDED
This script is unavailable because its developer account is suspended.
Cause: The developer account is suspended. Fix: Nothing to fix on your side.
SUPERSEDED
A newer executor run is already active.
Cause: You executed again while a run was starting. Fix: Ignore it; the newest run continues.
Connection errors
NETWORK_ERROR
Could not connect to the server - <detail>. The script was not started; please re-execute it.
Cause: No internet, a firewall, or the executor blocked the request. Fix: Check your connection and re-execute.
SERVER_ERROR
Server is restarting (HTTP 502) - reconnecting
Cause: A deploy or short outage. The loader retries by itself. Fix: Wait. If it lasts minutes, check status.luaprotect.dev.
RATE_LIMITED
The server is busy (many players are reconnecting) - retrying automatically in <n>s
Cause: Many players reconnecting at once. Fix: Nothing; it retries automatically.
BUSY
The server is busy and could not be reached after several attempts. Please re-execute the script in a minute.
Cause: Retries ran out under heavy load. Fix: Re-execute in a minute.
NO_RESPONSE
Could not start the script (no response from the server). Check your connection, then re-execute it.
Cause: No answer within 25 seconds. Fix: Re-execute. Check status.luaprotect.dev if it repeats.
NOT_DELIVERED
Connected, but the server never delivered the script. Re-execute it; if this keeps happening, tell the script owner.
Cause: The connection opened but the build did not arrive. Fix: Re-execute. Developers: make sure the latest version is released.
SESSION_EXPIRED
Runner session expired; starting a fresh session
Cause: A long session or a server hop. Handled automatically. Fix: Nothing.
Executor and runtime errors
EXECUTOR_UNSUPPORTED
Your executor is missing features LuaProtect needs. Try a supported executor (Delta, Wave, Synapse, Krnl, Fluxus, Swift, Macsploit).
Cause: No HTTP request or WebSocket support. Fix: Switch executor.
LOADSTRING_HOOKED
Error: the script was not started because your executor (<name>) looks like it hooks loadstring.
Cause: The executor or another script hooks loadstring, which looks like a dump attempt. Fix: Restart the executor without other scripts, or use another executor.
DECRYPT_FAILED
Error: received data from the server that could not be decrypted; please re-execute the script.
Cause: Data was corrupted in transit or a stale session. Fix: Re-execute.
DOWNLOAD_INCOMPLETE
Script download was incomplete; please re-execute the script.
Cause: The connection dropped mid-download. Fix: Re-execute.
ALREADY_RUNNING
Script already executed in this session; skipping duplicate execution
Cause: The loader was run twice in one game session. Fix: Rejoin to run it fresh.
LOADSTRING_ERROR
Loadstring error: <detail>
Cause: The protected build could not be compiled by the executor. Fix: Developers: release again; report it if it persists.
EXECUTION_ERROR
Execution error: <detail>
Cause: Your own script threw an error at runtime. Fix: Developers: find it in Script Issues with the full message.
RUNNER_OUTDATED
Your LuaProtect loader is out of date. Please re-execute the script to load the latest version.
Cause: An old cached loader. Fix: Re-execute. If it repeats, copy the loader again from the script card.
Still stuck?
Developers: open Script Issues for errors your players hit, and Activity Logs for blocked runs with their reason. Players: send the exact console message to the script owner. Everyone else: ask in the LuaProtect Discord.