Luarmor glossary: key, HWID, loader and init
Key, HWID, loader, init, checkpoint, build, and the other words that turn up in a loader error or a seller panel. What each one means and which layer it belongs to.
A Luarmor key is a string that says the seller allowed a device to run a script. HWID is the machine fingerprint the key is tied to. The loader is the small file that asks the service, and the init is the stage that arrives after the loader is accepted.
The four words in the title
| Word | Plain meaning | Where you meet it |
|---|---|---|
| Key | A string the seller issues for a project | The key page, the script_key line |
| HWID | A fingerprint of the device | The KEY_HWID_LOCKED error, a reset request |
| Loader | A small file that fetches the real code | The line you paste into the executor |
| Init | The stage the loader runs next | The cache file name, a kick message |
Key and key system
A key is generated for one project. It is not a password and not a Roblox credential; it is a string the loader sends to the service. A key system is the page, the check, the device binding and the expiry.
The script_key line is where a protected script names its key. It
sits in the script header, and the loader reads it before it calls the service.
HWID and device locked keys
HWID stands for hardware identifier. It is a value built from the machine, and
the service stores it against the key. A second machine produces a different
value, and the check returns KEY_HWID_LOCKED.
A device locked key is the same idea from the seller's side: one key, one
device. Moving it requires /resethwid on the seller's Discord bot.
The documentation does not list the inputs that build the fingerprint, so the
value is observed rather than derived, and the reset procedure is in
the HWID page.
Loader, stub and second stage
A loader, or stub, is a small file whose job is to fetch and run something else. The copy we analysed is 1,245 bytes in five lines. It reads a cache, downloads a second stage, writes it to disk and runs it with a short id built from the project.
The second stage is the file the loader fetches next. In our download it was 327 bytes and it only kicked the player, because the client was not recognised. That is a rejection branch, not the protected script.
Init and the file name
Init is the name the loader gives the second stage when it caches it. The file
we saw was init-d049a886a1f-ocmid.lua: d049a886a1f is
the short id the stub uses, and -ocmid is part of the name it
builds for this loader variant.
The cache lives in static_content_170926, and the loader reuses it
only if the text is longer than 2,000 characters. That threshold is the only
test. purge_cache() deletes the cached build, which survives between
sessions until it is cleared.
Project, script id and build
A project is the seller's container for one script. A script id identifies that script inside the project, and the loader URL carries it. The stub also writes a shorter id into the cache file name. A build is the artefact uploaded to the project, which the service serves as an obfuscated file.
A mismatch between loader and key produces
SCRIPT_ID_INCORRECT: the key belongs to one project, and the loader
was built for another. That is why a friend's key rarely works, even before the
HWID is considered.
Checkpoint and key flow
A checkpoint is a step between opening a key page and receiving the key. A key flow is the whole sequence: start page, checkpoints, ad links, key. The seller configures it, and Rewards is the documented mechanism behind the ad steps.
The word is also used for any intermediate page, including a captcha or a Discord join. In practice, a checkpoint is whatever the page wants before it shows the key, and the sequence of ad steps is in Why keys send you through ads.
Expiry, ban and blacklist
Three codes look similar and mean different things.
| Code | What it says | What it does not say |
|---|---|---|
KEY_EXPIRED |
The key's time is over | Whether the project still exists |
KEY_BANNED |
The seller or the service blocked the key | Why it was blocked |
KEY_INCORRECT |
The string does not match a key | Whether the key exists elsewhere |
A blacklist is the list behind KEY_BANNED. A Roblox ban is a
different event, issued by the platform against an account. The two words appear
together in threads, which is why the distinction is worth keeping. For the
reasons behind a block, see
Why keys get
blocked.
Obfuscator, whitelist and skid
An obfuscator rewrites Lua so it is hard to read. A whitelist is a list of allowed users or keys. A skid is a term from the comments we read for someone who copies another author's work. All three turn up in the same threads.
None of them is part of the licence check: obfuscation changes how the file reads, a whitelist changes who may run it, and skid is a word for the author, not the code.
Executor, injection and client
An executor is the program that injects Lua into the Roblox client and adds the
functions the loader needs: HTTP, loadstring, file access. Injection
is the act of getting that code into the process. Client is the program on your
machine, including the executor and the game.
Without an executor, the first line of a loader cannot run. That is why a licence error and an executor error can look alike: both stop the chain before the script starts, and both can produce a message about support.
The same word in two places
Four words carry two meanings in these threads.
| Word | Meaning one | Meaning two |
|---|---|---|
| Ban | A Roblox account ban | A key blocked by the seller |
| Loader | The stub file | The line a hub uses to fetch a script |
| Build | The seller's uploaded artefact | The cached file on disk |
| Key | A Luarmor key | A field in a Lua table |
When a message is ambiguous, the code is the tiebreaker. KEY_ codes
belong to the licence layer, and a kick message belongs to the client layer.
Every code is listed with its layer in
the error code list.
FAQ
Is my HWID the same as my IP address?
No. The HWID is built from the machine, and the IP is assigned by the network. A VPN changes the IP and leaves the fingerprint alone, which is why turning a VPN on does not fix KEY_HWID_LOCKED. The reverse is also true: a new machine on the same network has a new HWID.
Can one key cover two devices?
Usually not. The key is bound to one fingerprint, and the second device produces a different one. A seller can issue a second key or reset the first, and the documentation describes the reset rather than a multi device flag. Ask the seller before assuming a key travels.
What is a serial?
A key sold through a shop. The documentation describes Sellix and Shoppy integration that produces serials automatically after a sale. The serial is the string the buyer receives, and it works the same way as a key from a free flow: one project, one device, an expiry.
What is a loader hash and why does it change?
A hash is a fingerprint of a file. The loader is generated per request, so two downloads a few seconds apart produce different hashes even when the URL is the same. In our sample, 8 of 12 fields changed in 28 seconds. A hash identifies the copy you analysed, not the loader in general.
Why is the cached file named after a short id?
Because the loader needs to know which script the cache belongs to. The stub builds the name from a fixed prefix, a short id and a suffix for the loader variant. A cache file from another project has another name, which is why two scripts can share a folder without overwriting each other.
What is a hub loader line?
The single line a hub gives a user: a loadstring call that fetches the hub's loader. It is the same shape as any other loader line, and the hub's menu appears only after that line succeeds.
Why does a key have an expiry date?
The seller sets it. Luarmor's documentation describes KEY_EXPIRED and the check that produces it, and it does not fix a default duration. A short expiry brings users back to the page, and a long one reduces support requests. The seller chooses which trade to make.
Does an executor count as part of Luarmor?
No. The executor is a separate program that provides the functions the loader calls. Luarmor serves the licence check, and the executor runs it. A change of executor can change the answer you get from the service, which is why client questions and licence questions are often the same question.