Luarmor key not working? What the error code means
Five causes cover almost every dead key: wrong key, rejected format, expiry, a different device, or a block. Read the code before you buy another.
Almost every failure after you have a key is one of five: the wrong key, a rejected format, an expired key, a key locked to another device, or a blocked key. The code tells you which one, and the sentence around it usually does not. Work through them in this order, because each check is cheaper than the one after it.
If you never got a key
The five checks below assume you already have a key. If the key page never gave you one, none of them apply yet.
Some pages complete the first task and fail on the second, even with the adblocker and VPN disabled, and the same error appears on a different laptop. That points at the page's ad flow or the network, not at a key, because no key has been checked.
The page belongs to the seller, not to Luarmor. Adblock detection, a countdown that never finishes, a mobile layout that will not scroll and a Discord gate are page failures, not key failures. See the key system page for the rest. Try a different browser or network, then ask the seller. Buying another key cannot fix a page that never issued the first one.
Read the code first
Before you change anything, find the status the service returned. Without it, every fix is a guess.
Where the code appears depends on the loader. It can arrive as a line in the executor console, as part of a message the loader draws, or inside a kick sentence. A loader can also print a friendly line with no code at all, which is why the console matters.
- Open the executor console before you run the script again.
- Run the loader once with the key unchanged.
- Copy the whole line that contains a code, including the words around it.
- Note the time, because expiry and time checks depend on it.
The five key codes are short and distinct. A failure that does not match any of them is probably not a key problem at all. The rest are in the error code list.
| Code | What it says | What it does not say |
|---|---|---|
KEY_INCORRECT |
No key with this value exists for this project | Whether the key is valid elsewhere |
KEY_INVALID |
The value is not in an acceptable shape | Whether the key ever existed |
KEY_EXPIRED |
The period set by the seller has ended | Whether a renewal exists |
KEY_HWID_LOCKED |
The key is bound to another machine | Whether a reset is allowed |
KEY_BANNED |
The seller has blocked the key | Why the block was set |
Wrong key
KEY_INCORRECT means the service looked up the value and found
nothing for this project. The key may be real, just not here.
A common cause is a key from a different project. Sellers often run more than one script, and a buyer who owns two can paste the wrong one. The service only knows that this value is not in this project's list.
The second cause is a partial copy. A key selected by hand in a chat window can lose its first or last character, and a key copied from a screenshot can pick up a stray mark. Compare the value with the seller's message character by character, not by eye.
The third cause is an old key from a previous project the seller has since replaced. When a seller rebuilds a project, old keys often stop existing in the new one. Ask which key is current before concluding that the key is dead.
Wrong format
KEY_INVALID is the shape complaint. The value does not look like a
key the service will even consider, so it never reaches the lookup that would
return KEY_INCORRECT.
Spaces are the usual culprit. A copy from a web page can carry a leading space, a trailing space, or a line break in the middle. All three survive the paste and all three change the value.
Quotes are the next one. If the script already has script_key = "...",
pasting a key that includes its own quotes produces doubled quotes and a broken
assignment. Paste the string only.
Phone keyboards add a third problem: curly quotes and non breaking spaces. They look identical to the plain characters in most fonts and behave differently in Lua. If a key came through a phone, retype it on a desktop or copy it again from the source. The characters that break a paste are named in the key format page.
Expired
KEY_EXPIRED means the clock ran out on the period the seller set.
Expiry is a property of the key, stored with it. Changing your system date does not extend it, because the comparison happens on the server against its own time.
The fix is a new key from the seller, or a renewal if the seller offers one. The details worth including in the request are in what to do when a key expires.
One caution: expiry and a clock problem look similar from the outside and are not
the same. TIME_ERROR points at the timestamp of the request.
KEY_EXPIRED points at the key. Reading the wrong one sends you to
the wrong fix.
Locked to another device
KEY_HWID_LOCKED is the most misread code in the set. The key is
valid. It is simply bound to a machine that is not this one.
That happens after a hardware change, a new PC, a virtual machine, or a reinstall that produces a different fingerprint. It also happens when a key has been used on someone else's machine, whether you gave it away or not.
The fix is a reset, and only the seller can authorise it. Buying a second key does not help if you paste it on the same machine that already holds the first binding, because the new key will bind to the same fingerprint and the old one stays locked.
The reset command, and the cases where a reset is not available, are in The HWID locked page.
Banned
KEY_BANNED means the seller has blocked the key. It is a decision,
not a fault, and it comes from the seller's side of the panel.
A blocked key stops before the loader fetches anything, so the result looks like a sudden stop rather than a partial load.
Resetting your device, reinstalling the executor or editing the script will not clear it. The state lives with the key on the service. The reasons a seller sets a block, and what lifting one requires, are in Why keys get blocked.
What to send the seller
A short, complete report gets a faster answer than a paragraph. The seller has the key's record open and needs the same facts you have.
Send the exact code, the time it happened with your time zone, the loader you used, the steps you took, and one screenshot of the console line. Add what changed since the last time it worked: a new PC, a Windows update, a reinstall, a different executor.
Send the key once. Three messages with the same key do not make the report faster. If the seller has a ticket system, use it, because a ticket keeps the history in one place.
A report that says only that the key does not work forces the seller to ask four questions. A report with the code and the change answers them in advance.
When to stop
Stop when the code is not one of the five. A SCRIPT_ID_INCORRECT, an
executor rejection or a TIME_ERROR has a different owner, and no
amount of key swapping will fix it.
Stop when the seller has confirmed a reset and the code does not change. That points at a cached copy or an old loader still in use, not at the licence.
Stop when the only advice is to buy another key. If the code was
KEY_HWID_LOCKED, a new key on the same machine repeats the problem.
If it was KEY_BANNED, a new key may be blocked for the same reason.
Working through the five checks takes a few minutes. A second key costs money and usually fails the same check.
FAQ
The key page fails before I get a key. Is that a key problem?
No. The key check has not run yet, because there is no key to check. A page that fails on a task, a countdown or a captcha is a seller page problem. Try a different browser or network, then contact the seller. Buying another key cannot fix a page that never issued the first one.
Why does my key say invalid if I copied it correctly?
A key can be copied correctly and still arrive broken. A trailing space, a line break from a chat window, or a curly quote from a phone keyboard all survive a paste and change the value. Select the key again from the original message, paste into a plain text field, and compare the first and last characters.
Why did my key stop working after a Windows update?
A large update can change details that feed the machine fingerprint, so the service sees a different device and returns KEY_HWID_LOCKED. The key itself is untouched. Ask the seller for a reset, then run the loader once on the same machine without changing anything else.
What do I send the seller when my key fails?
Send the code, the time with your time zone, the loader and executor you used, the steps that led to the failure, and one screenshot of the console. Add what changed since it last worked. The seller can match that to the key's record without a round of questions.
Is buying a second key the fastest fix?
It is the fastest way to spend money and often the slowest way to fix anything. A new key on a device that already holds a binding fails the same check. A blocked key may be replaced by another blocked key. Match the code to the cause first.
Does reinstalling the game or the executor help?
Only when the failure comes from the client, and that produces a different message. For the five key codes, a reinstall changes nothing on the service side. It can even make things worse by producing a new fingerprint and a new lock.
Why does the key work on my friend's PC and not mine?
The licence is tied to a device, not to a person. A key that works on one machine is bound there, and the same value on a second machine returns KEY_HWID_LOCKED. The key is untouched. What fails is the device check, which is why only a reset from the seller helps.