Can you share a Luarmor key? What happens if you do
A key is tied to one machine, so a second person gets a lock instead of a licence. What the seller sees, and why a reset is not a spare seat.
You can send the string to anyone, but it will not work for them. A Luarmor
key is bound to one device, so the second person gets
KEY_HWID_LOCKED on the first load. What the service checks is the
device record stored with the key, not the string.
What happens on the second device
The friend pastes the key, the loader sends it with their fingerprint, and the service compares that fingerprint with the one stored for the key. They differ, so the answer is a lock.
The message can be confusing, because the key is genuinely valid. It exists, it belongs to the project, and it has not expired. The only failed input is the machine.
From the seller's side nothing has been stolen. From the friend's side nothing works. Both statements are true at once, which is why shared keys produce tickets that begin with the claim that the key is fine.
Why people try it anyway
A key looks like a password, and passwords are the thing people share. The device binding is invisible until a second machine tries it, so the first attempt feels reasonable.
A friend wants to try the script before buying. Two people split the cost of one key. One person has a desktop and a laptop and expects the same key to work on both. In each case the key is treated as a seat, and the service treats it as a device record.
The misunderstanding is about what the string represents, not the string itself. A key is one licence on one machine; it is not an account with several sessions.
Why the key is tied to a machine
A licence that follows a person is hard to enforce and easy to pass around. A licence that follows a device is cheap to check and awkward to move, which is exactly what a seller wants.
Luarmor's documentation says keys are bound to the HWID. The binding happens on the first successful load and is stored with the key. Every later request is compared against that stored value.
The design has a cost the seller accepts. Honest buyers who change computers need a reset, and resets need the seller. That friction is the price of making a leaked key useless.
The reset trap
A reset looks like the obvious way around the lock, and it works once. It also moves the licence rather than copying it.
If the owner asks for a reset and gives the key to a friend, the friend's machine becomes the bound device and the owner's machine stops passing. The key has changed hands rather than gained a seat.
Repeated resets are visible. A key that jumps between machines every few days has a pattern, and a seller can act on that pattern by blocking the key. At that point neither person has a working licence, and only the seller can lift the block.
What the seller sees
The seller sees the state of the key: active or blocked, the expiry date, and the device it is bound to. The panel also records the resets performed on it.
That is enough to answer the question a seller asks when a key stops working. Was it moved, and how often? A key that has never moved looks different from one that moves weekly.
The documentation does not describe a session-by-session log. It describes a key with a device and a reset history, and that is enough for a seller to notice sharing.
Sharing with your own second PC
The same rule applies to your own hardware. A desktop and a laptop are two devices, and one key binds to one of them. A reset moves the binding rather than adding a second one.
Using the second machine means a reset, and the first machine stops passing afterwards. If you move between them often, the practical arrangement is two keys rather than a reset each time.
Ask the seller before you buy if you know you will use two machines. By default a key is one licence for one device, so the question is worth asking early. Assuming every key allows two machines leads to the lock you are trying to avoid.
Two people on one machine
One machine can pass with one key, so two people sharing a PC can both load the script at different times without a lock. The fingerprint matches and the service has no reason to refuse.
Whether two sessions at once are allowed is a seller question, not a hardware one. The documentation does not describe a concurrent session limit, so do not assume either way. Ask if it matters to you.
Sharing an account is a different matter from sharing a machine, and it moves the risk from the licence to the account. That risk belongs to Roblox, not to Luarmor.
What to do instead
Buy a second key if two people need access. It is the only arrangement that gives each person a working licence without a reset war.
Ask the seller about a multi device option if the need is yours alone and regular. A seller who understands the use case can say whether a second key or another setup fits.
If the friend only needs the script once, accept that the key will not stretch. A single use still needs its own licence, because the check happens on every load and the first one already fails.
FAQ
What happens if I share my key?
The other person gets KEY_HWID_LOCKED on their first load, because the key is bound to your machine. If you reset the device so they can use it, the key moves to them and stops working for you. Sharing rarely produces two working copies.
Can two people use one key at the same time?
Not on two machines. The service binds the key to one fingerprint, and the second machine fails before the script starts. Two sessions on the same machine are a different case, and whether they are allowed is up to the seller rather than the licence check.
Can I split the cost of a key with a friend?
Not in a way that gives both of you access. The key binds to one machine, so the second person gets a lock. A reset moves the licence to them and takes it from you. Two people who both want access need two keys, or a seller who offers a multi device arrangement.
Can I share a key with someone on the same PC?
Yes, in the sense that the same machine presents the same fingerprint, so the key passes for both people. What each person does with the script is separate. If both want to play at once, ask the seller whether concurrent sessions are acceptable.
Does the seller get notified when someone else tries my key?
The service records the failed attempt as a lock against the key, and the seller can see the key's state and history. The documentation does not describe push alerts, so assume the seller can find out rather than that they are told immediately.
Can I get my key back after sharing it?
Only through another reset, which moves the licence back. If the other person keeps loading the script, the key may return to their machine again. A key that keeps moving is exactly the pattern that leads a seller to block it.
Is it cheaper to share a key than to buy two?
It looks cheaper until the lock arrives, and then both people are without a working licence. A shared key also puts the original buyer's access at risk, because a block applies to the key, not to one of its users. Two keys are the arrangement that holds.
Why does my key work only on the first PC I used?
Because the first successful load is where the binding is stored. Every later machine is compared against it and fails. That is the intended behaviour, and the only documented way to change it is a reset authorised through the seller.