BobuxBOT

Executor not supported by Luarmor: what the message means

The message comes from Luarmor's second stage, not from the script. The service decides support from the client fingerprint, before any key is read.

That message comes from Luarmor's second stage, before the key check and before your script. It means the service did not recognise the client that made the request. Nothing in your key or your script caused it, and no key change fixes it.

The message, word for word

The copy we downloaded on 19 October 2026 is 327 bytes and four lines: two comments and two statements. The first comment reads: If you are seeing this, it means your executor is not supported by Luarmor. The second points to a ticket in the Luarmor Discord.

The code then calls game:GetService("Players").LocalPlayer:Kick with a longer version of the same sentence, and enters while wait(1) do end. The loop keeps the chunk from returning, so the client does not continue with anything else.

There is no key check in those 327 bytes. There is no script, no HWID call and no expiry test. The whole file is a rejection.

Where it comes from

The loader does not contain the message. It downloads a second stage from cdn.luarmor.net/v4_init_ocmid.lua, writes it to the cache folder, and runs it with the script ID. The stub is 1,245 bytes in our copy and contains only the cache check and the network branch.

The loader URL is the same for everyone in the project, and the first stage does not decide support. The answer is chosen after the request arrives, which is why two users can run the same loader and get different code back. The first stage is described line by line in Luarmor v4 loader, and the 327-byte reply in Luarmor's second stage.

A recognised client receives a different init. That init is where the key, the HWID and the expiry are checked, and it is not served to a request that does not look like a supported client.

Because the rejection is 327 bytes, it lands below the 2,000-character cache threshold. The loader writes it and then ignores it on the next run. A repeated message therefore means a repeated download, not a cached rejection that you need to clear. The file itself is described in What is the static_content folder.

What "supported" means

The key check table lists INVALID_EXECUTOR with the meaning HWID header contains invalid data. Executor might not be supported. The wording is careful: the request carried data the service could not accept, and the client is the likely reason.

The external API documentation shows how the identity travels. A request carries a hardware ID, an executor fingerprint built with the platform name, and a User-Agent that must be whitelisted by Luarmor in advance. A client that sends none of these, or sends values the service does not know, is not a supported client.

So support is a server-side decision about three things: whether the client is recognised, whether it sends the headers the service expects, and whether it provides the functions the loader calls. It is not a setting inside the script, and it is not tied to your key.

Editing the fingerprint does not help either. It is built from the client, and an edited value either fails validation or names a client the service does not recognise. The code for that branch is listed with the other client errors in Luarmor error codes.

Why curl sees the same message

A plain curl request to the second-stage URL sends no executor fingerprint and no whitelisted User-Agent. It is valid HTTP and an invalid client. We used that request to read the rejection branch, and it returned the same 327 bytes.

If you paste the URL into a browser and see the message, you have tested the branch for unknown clients. Nothing there reads your key, so the reply says nothing about your setup.

Five checks before you open a ticket

  1. Update the executor, then close it completely and reopen it. A new build can change the fingerprint the service sees.
  2. Run the same loader on a second client. If one passes and one fails, the client is the variable.
  3. Run a different script from the same seller. If both are rejected, the common piece is your client. If only one is rejected, ask the seller about that project.
  4. Check the platform. A desktop client on a phone, or a mobile client on a PC, is a different fingerprint even when the name is the same.
  5. Look for the key stage. If you reach a key prompt or a KEY_* code, the executor check passed and the message is coming from somewhere else.

Run the checks in that order because each one removes a variable. Updating first is cheap and reversible. Comparing clients second tells you whether the problem is local. Asking the seller last means you arrive with a result instead of a guess.

A second key will not help, and neither will editing the loader or reinstalling the game. None of them changes what the client sends. A VPN changes your IP address, not the fingerprint.

What to send in a ticket

The seller needs the exact message, the client name and version, the platform, the script name, the loader URL and the time. Add whether the client was updated recently and whether other scripts from the same seller work.

The key is not the evidence here, because the check happens before the key is read. Keep it out of public channels anyway. A screenshot of the console is more useful than a screenshot of the kick text, because the console may show the request that failed.

When the seller can fix it

The rejection itself asks users to open a ticket so the client can be supported. That wording suggests the list is maintained rather than fixed. If several users report the same client, the seller has a case to raise. If the client is obscure or modified, the answer may be that it will not be added.

You cannot whitelist your own client. There is no local file or setting that adds a name to the service's list. To test a client without relying on a published list, see Which executors work with Luarmor.

FAQ

Which executors are supported by Luarmor?

The documentation we checked on 19 October 2026 does not publish a list. The service decides per request from the client fingerprint and User-Agent, so any list you find online is a snapshot of someone else's tests. Test your own client with the loader, and treat the result as the answer.

Does updating my executor fix the message?

Sometimes. An update can change the version string, the fingerprint or the headers the client sends, and the service may recognise the new build. It can also go the other way if the new build is not on the list yet. Update, restart the client, and compare the message before and after.

Why does the same loader work for my friend?

Your friend's client sends a different fingerprint to the same URL. The loader is identical; the answer is chosen per request. If their client is recognised and yours is not, the service treats the two requests differently. The key is not involved at that point.

Is the message from the game or from Luarmor?

It comes from Luarmor's second stage, but it is delivered through the game client. The code calls LocalPlayer:Kick, which is a normal Roblox client call, so the message appears in the game. The script itself never runs, and Roblox did not write the text.

Can I use a different loader with the same key?

Only if the loader belongs to the same project as the key. A loader from another seller points at another script ID, and the key will not match that project. A newer loader from the same seller can work if the project is the same. Check with the seller before mixing files.

Does a VPN change anything for this message?

No. A VPN changes the IP address the request comes from, and the rejection is about the client fingerprint, not the IP. A VPN can also make an ad session fail, because the documentation binds that session to an IP address. Turn it off while you test, so it is not another variable.

Does this message mean my key is banned?

No. KEY_BANNED is a different code, and it comes from a later stage. The executor rejection happens before the key is read, so the service has not looked at your key at all. A banned key and a supported client would produce the key code, not this message.

What if the seller says my executor is supported?

Ask for the exact client version they tested and try that build. Then send the message, the version and the platform back. If the seller's other users pass on the same build, the difference is on your side: a modified client, a proxy, or a platform variant that sends a different fingerprint.

Does the message appear on mobile?

Yes. The second stage is the same Lua file on every platform, and the kick call works wherever the client exposes the Players service. A phone client can be rejected for the same reason a desktop client is: the service does not recognise its fingerprint. Try a client the seller names before changing the key.

Will a new loader from the seller fix it?

Only if the old loader was damaged. The message is about the client, and a new loader URL still reaches the same service with the same fingerprint. Re-copy the loader once to rule out an edit, then test a different client. A new key is wasted on this branch.

Search Roblox games

Popular now Pick a result to open its page
↑↓ navigate ↩ open esc close