Luarmor key system: how keys work and where to get one
A key is a string the seller generates for one project. The loader sends it with a device fingerprint, and the service answers with a status code.
Every load of a protected script passes through the same check. The key is a string the seller generates for one project, and the loader sends it with a device fingerprint. The service answers with a status code: a pass returns the next stage, a fail returns a reason. The key travels to the licence check and nowhere else.
The flow, step by step
The whole system is a loop between four places: the seller's panel, the key page, your machine, and the service.
- The seller creates a project and sets what a key may do: duration, device binding, whether it is active.
- The seller generates a key, either by hand or through a storefront that sells serials.
- You receive the key from the seller, from a purchase message, or from the end of a rewards flow.
-
You paste it into the script where the seller tells you to, usually the
script_keyline. - The loader reads the key, adds a fingerprint of your machine, and sends both to the service.
- The service compares key, project and device, then answers with a status code.
- On a pass, the loader fetches the next stage and the script starts. On a fail, it stops.
Where the key comes from
The key comes from the seller, not from Luarmor's website. That single fact clears up most of the confusion around the product.
Luarmor sells access to sellers, which is why the service itself never hands a key to a player. According to the documentation, a seller buys an invite code, creates an account, and works from a panel where projects and keys live. A player who wants a key is a customer of one of those sellers, and the seller decides how keys are handed out.
A paid key arrives after a purchase, often through an automated storefront such as Sellix or Shoppy that issues a serial. A free key arrives at the end of a rewards flow, after a set of advertising links. A manual key arrives from the seller directly, usually in a ticket or a direct message after a payment.
Whichever route you take, the key is the same kind of string. What changes is how much you paid in money or in time, and what the seller recorded about you.
The key page and its checkpoints
Many sellers send buyers to a key page instead of a plain download. The page is a form around the rewards flow, and it exists to turn attention into money before it hands over a key.
The checkpoints vary by seller, but the pattern is consistent. You open a link, wait for a countdown, close an overlay, and return to the page. Some pages add a captcha. Some ask you to join a Discord server first, because the server is where support and updates happen.
A seller in a Reddit thread we read on 19 Oct 2026 listed the networks it supports for this kind of flow: Linkvertise, work.ink, LootLabs and Shrtfly, with a captcha or a Discord join as an alternative to the ad. Luarmor's documentation describes a rewards flow and a Discord bot for keys and HWID resets; the exact network is a seller setting.
The key page is a gate, not the licence system. Clearing it gives you a string. The string is what Luarmor checks later, on every load.
When the page will not let you pass
The page is the part users complain about most, and the failures are rarely about the key itself.
Adblock detection is the first. Some pages refuse to advance while an ad blocker is active, and users in one thread describe a loop where the page insists an adblocker is on even after they disable it. The page belongs to the seller, so the only reliable fix is the seller's support or a different browser.
The second is the countdown and the overlay. A blocked pop-up, a closed tab or a slow connection can reset the flow. If the page has a "continue" button that never appears, the ad call did not complete.
The third is mobile layout. One thread shows a key page panel that cannot be scrolled on a phone. The page was built for a desktop viewport, and the seller did not test the small screen. Rotating the phone or trying desktop mode may help, but the page is still the seller's to fix.
The fourth is the Discord requirement. Some pages ask you to join a server before they show the key. That is a seller gate, not a Luarmor step, and what the join request shares is in Whether to link Discord.
What a key looks like
A key is a short string generated for one project. It is read as a single value, so a stray space turns it into something else.
The key check example passes a 32-character key, and the documentation describes
KEY_INVALID as empty, too long or too short. It does not publish an
alphabet, so copy the string exactly instead of retyping it.
A key is also not a secret in the way a password is. It identifies a licence, and it only works with the project that issued it. That is why a key can be shared with the seller in a private ticket without exposing an account, and why the seller can revoke it without changing anything you own.
The script_key line
In a protected script, the key sits in a line near the top, in the form
script_key = "KEY". The loader reads that value before it calls the
service.
The line is a variable assignment, nothing more. The quotes are part of Lua syntax and are not part of the key. If you paste a key that already has quotes around it, you end up with doubled quotes and a value the service will reject.
Some sellers ship a loader with a placeholder in that line. Others keep the key out of the file and ask for it in a small prompt. Both designs end in the same request: one key, one project, one device fingerprint.
Treat the line as the only place the key belongs. A key pasted into a public script, a shared document or a screenshot is a key other people can try.
The HWID link
The fingerprint is the part that makes a key personal. Luarmor's documentation says keys are bound to the HWID, which is why copying a key to another machine does not copy the licence.
A fingerprint is not an IP address and not an account name. It is a value derived
from the machine, and the service stores it against the key the first time the key
passes. From then on, a request from a different machine returns
KEY_HWID_LOCKED.
That design explains the resets. The code, the triggers and the reset command are in the HWID locked page. The key alone is never enough: the service checks the pair of key and device.
The status codes
The service answers with a code, and the code says which input failed. The five key codes are the ones you will meet most often.
| Code | Meaning | First move |
|---|---|---|
| Pass | Key valid, project matches, device matches, not expired | Nothing, the load continues |
KEY_INCORRECT |
No such key for this project | Re-copy the key, check you have the right project |
KEY_INVALID |
The value does not have an acceptable shape | Remove spaces, quotes and line breaks |
KEY_EXPIRED |
The period the seller set has ended | Ask the seller for a new key |
KEY_HWID_LOCKED |
Valid key, different machine | Ask for a device reset |
KEY_BANNED |
The seller has blocked the key | Ask the seller why |
The expiry and block cases have their own pages: what an expired key means and why a seller blocks a key.
Where the flow breaks
Five places account for almost every failure, and they appear in a predictable order. The key page can fail before you ever get a key. The paste can damage the string. The project can be the wrong one. The device can be new. The client can be unsupported.
That last one surprises people, because it produces a sentence instead of a key code. The second stage we downloaded on 19 Oct 2026 was 327 bytes and did nothing except kick the player with a message about the executor not being supported. It was not a broken script; it was the rejection branch of the service.
Those failures arrive in a fixed order, so for the code to expect at each step, see the five checks for a key that will not work.
What the seller sees
The seller sees the state of the key in the panel: whether it is active, when it expires, and which device it is bound to. The panel is also where a reset and a block happen.
That view explains the support questions sellers ask. When you report a failure, the seller can compare your story with the key's record. A different machine in the record turns into a reset request. It is also why a shared key is easy to spot, because every new device leaves a mark.
The documentation describes the panel at the level of features, not screens. We have not seen a seller's panel.
FAQ
Where do I get a Luarmor key?
From the seller of the script, not from Luarmor. Luarmor sells access to sellers, and each seller decides how keys are issued: a purchase, an advertising flow, or a manual message. If you found a script and no seller, there is no key to request from Luarmor itself.
Do I have to complete ads to get a key?
Only if the seller uses the rewards flow. In that flow, the key page asks you to open advertising links, sometimes with a captcha or a Discord join, before it shows the key. Sellers who sell keys directly skip the page entirely. The choice belongs to the seller, not to Luarmor.
Why does the key page say I have an adblocker?
Because the page checks whether the ad call completed. Some pages refuse to continue while an ad blocker is active, and users report the check triggering even after they disable it. The page belongs to the seller, so the reliable fix is the seller's support or a different browser. Luarmor's licence check runs later, in the loader.
How long does a key last?
As long as the seller set when generating it. The documentation treats duration as a project setting, and players in Reddit threads report keys of 8 or 12 hours while other sellers use days or lifetime keys. The expiry date is stored with the key, and the service returns KEY_EXPIRED once it passes.
Can I use the same key on my phone and my PC?
Usually not without a reset. The key binds to the first device that passes the check, and a phone presents a different fingerprint from a desktop. Moving the licence means asking the seller for a reset, then using the key on the new device. Two devices at once need two keys.
Why does the key page ask me to join a Discord server?
Because the seller runs support and updates there. Joining is how the seller ties a buyer to a community, delivers roles, and announces a new loader when the old one changes. It is a seller decision, and some sellers use a captcha or a paid key instead.
Does a key work in more than one game?
No. A key belongs to a project, and a project is one script for one game. The same seller might run several projects, but each has its own keys. Using a key from one project in another returns a key or project error rather than a pass.
What happens if the seller deletes the project?
The loader has nothing to ask about, so the chain stops before the key is even judged. In that case the key is not expired or blocked; the project behind it is gone. Only the seller can tell you whether a new project replaced it and whether old keys carry over.