BobuxBOT

Which executors work with Luarmor?

There is no published list. Luarmor decides per request from the client's fingerprint and user agent, so the test is your own loader, not a directory.

Luarmor's documentation does not publish a list of supported executors. The decision is made on its servers from the fingerprint and user agent that the client sends, so any list you find is a snapshot of someone else's tests. The reliable test is the response your own client gets.

Why there is no published list

The documentation we checked on 19 October 2026 lists status codes, the key library, the ad system and the Discord bot. It does not list executors. The second-stage endpoint is dynamic: the same URL returns a rejection to curl and different code to a recognised client.

A published list would have to be rebuilt on every client release, and it would still miss platform variants that share a name. The service already makes the decision per request, so a list would be a copy of an answer the server gives for free.

A thread on r/robloxhackers claims that a mobile executor "is Luarmor". It is not. The executor is the program that runs the loader inside Roblox. Luarmor is the licence service the loader talks to. One is the client, the other is the check, and a client can be installed without Luarmor being involved at all.

How Luarmor decides

The external API documentation describes the shape of a request. It carries a hardware ID, an executor fingerprint built with the platform name, and a User-Agent that must be whitelisted by Luarmor in advance. The key check library returns a code for the same condition, so both paths can report it.

A client is supported when it is recognised, sends the headers the service expects, and provides the functions the loader calls. Any of those three can fail and still produce the same short message, so the message does not tell you which one failed.

The decision belongs to the service, not to the seller's script. A client can pass one day and fail after an update on either side. The rejection text is the same in both cases, so the client name and version matter more than the message. That branch is covered in Executor not supported by Luarmor.

What the loader needs from a client

The stub is 1,245 bytes, a figure from the loader anatomy, and the loader chain calls a small set of functions. A client that lacks one of them fails before or during the licence check.

Function Used for What happens without it
game:HttpGet Loader and second stage No download, no message
loadstring Compiling both stages Downloaded text never runs
readfile Reading the cache Cache is skipped or errors
writefile Writing the second stage The network branch errors
makefolder Creating the cache folder The guarded call is skipped
script_key global Handing the key to the check The key never arrives
LocalPlayer:Kick The rejection path No visible message
os.time() Timestamp for the key request TIME_ERROR can appear

The stub guards makefolder with pcall, but it calls writefile without a guard. A client that can run simple scripts but cannot write files will fail here even though loadstring and HttpGet work. That is one reason a client can be good at one hub and bad at another.

The stub does not call getgenv, syn or any vendor-specific namespace. It uses the generic functions in the table, which is why the same file can run on several clients, and why a client with a large custom API can still fail on a missing file function. Luarmor's second stage adds a kick call on the rejection path.

How to test in two minutes

  1. Run the loader exactly as the seller gave it, with no edits.
  2. If you see the executor message, stop. The client was rejected.
  3. If you see a key prompt or a KEY_* code, the client passed and the key stage is now the subject.
  4. If nothing appears, open the console. A missing function is usually named there.
  5. Repeat on a second client with the same loader and the same key.

If the client logs the response size, the rejection branch we fetched on 19 October 2026 was 327 bytes. A recognised client receives a different init, so a different size is expected. Do not treat the number as a constant, because the endpoint is generated per request.

If the console shows attempt to call a nil value, the client is missing the function named in the line above. That is more precise than the kick message, which only says the client is unsupported. Keep the console line for the ticket. The code names are listed in Luarmor error codes.

Why a high sUNC score is not enough

sUNC measures how many functions a client implements against a test suite. It does not test whether Luarmor whitelisted the client, and it does not test the loader's cache path. Directories such as ScriptBlox publish executor pages with live status and sUNC scores, and a high score and a Luarmor rejection can coexist.

Use the score to compare clients on script compatibility in general. Use the loader to answer the Luarmor question, because that is the only request the service judges.

A score is also a moving number. Directories refresh status and scores on their own schedule, and a client can change between builds. Treat the score as a snapshot and the loader result as the current answer.

Mobile clients

The loader creates a folder and writes a file. Mobile clients differ in what they expose to Lua, and the documentation does not name mobile clients. The second-stage message is the same on every platform.

If the same key works on a PC and the phone shows the executor message, the phone's client is the variable. If the phone shows KEY_HWID_LOCKED, the client passed and the hardware link is the issue. The platform differences are in Does Luarmor work on mobile.

When to stop testing and ask

If two clients give different results, you have your answer: the rejected client is the problem, and only the service or the seller can change that. If every client is rejected, ask the seller whether the client is supported at all. Do not buy keys to test a client, because the key is not read on that branch.

FAQ

Is there an official Luarmor executor list?

No list appears in the documentation we checked on 19 October 2026. The service decides from the request, and the documentation describes the fingerprint and User-Agent rather than naming clients. Any directory you find is maintained by a third party and can lag behind both the clients and the service.

Is Luarmor an executor?

No. Luarmor is the licence service a script uses. The executor is the program that runs the loader inside Roblox. A thread on r/robloxhackers claimed that a mobile executor "is Luarmor", which reverses the two layers: the executor runs code, and Luarmor decides whether the request may run.

Does any executor with loadstring work with Luarmor?

No. loadstring is necessary and not sufficient. The loader also needs HttpGet, file functions for the cache, a global slot for the key, and a client identity the service recognises. A client can run other scripts with only part of that set and still fail here.

Why does my executor work on other scripts but not this one?

Other scripts may not use the cache, may not send an executor fingerprint, or may not sign their requests. Luarmor's loader uses all three. The failure is specific to what this loader asks for, not a general judgement about the client's quality.

Does the executor version matter?

It can. The version string and the fingerprint can change between builds, and the service may recognise one and not the other. If an update broke the loader, keep the old build available and test both. Report the version to the seller, because the message alone does not carry it.

Is a high sUNC score the same as Luarmor support?

No. sUNC measures implemented functions against a test suite. Luarmor support is a server-side decision about the client's fingerprint, its headers and whether the service has whitelisted it. A client can score well and be rejected, or score lower and pass.

Which mobile executor works with Luarmor?

The documentation does not name mobile clients, so there is no list to quote. Test the client you have with the loader and read the branch you get. If you see the executor message, that client is rejected on that platform. If you see a key code, the client passed.

Can the seller add my executor to the list?

The rejection message asks users to open a ticket so the client can be supported, which suggests the list can change. Whether it will change depends on the service and on how many users run that client. You cannot add it from your side.

Does the loader work on a modified client?

A modified client can change the fingerprint or the headers, which is exactly what the service checks. It may pass on one project and fail on another, or stop passing after an update. Test an unmodified build before you conclude that the service does not support the client at all.

Search Roblox games

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