Add a key system to your script
Step by step: require a key, make a key page with ad steps such as Linkvertise, Lootlabs or Work.ink, choose how long keys last, and give players a loader that checks every key.
A key system makes each player get a license key before your script runs. In Luaward you upload the script with keys required, create a key page with one or more steps, and share its link. Players finish the steps, get a key, and paste it above your loader line. Luaward checks that key on its servers every time the script starts.
What you need
- A Luaward account. The Free plan is enough to start: 2 scripts, 200 keys, 2 key-page steps in total across your key pages, up to 2,000 players on your key pages a month, and 10,000 script runs a month. Paid plans raise these limits (pricing).
- The Luau source of your script.
- Optional: an account at a link provider (Linkvertise, Lootlabs, Work.ink, ShrtFly or ShrinkEarn) if you want to earn from the steps. You can try the whole flow first with the built-in Test step.
1. Upload the script and require a key
If this is your first script, Dashboard → Onboarding creates a project and the script together. Otherwise open Projects and add a script to a project. Paste the source, pick a protection preset, and wait until the build is Ready (Quick Start).
Then make sure the script needs a key: open the script and check that No key needed is off in its Protection section (the docs call this setting Keyless). A script that needs no key runs without one, so a key page would add nothing (Runtime settings).
2. Create a key page
Open Key system → New key page. Choose the project the keys belong to, give the page a name (players see it), and pick a starting look: Steps list, One at a time or Cinematic. You can change the look later in the Look tab.
Luaward gives the page its own link. The address is generated for you and you cannot choose it; it looks like this:
https://key.luaward.com/getkey/a1b2c3d4e5f60718293a4b5c6d7e8f903. Add the steps players complete
In the Steps tab, choose Add step and where the step happens:
| Step | What you set up |
|---|---|
| Linkvertise | Make a link at Linkvertise whose destination is the page's return address, paste it, and add your Linkvertise token (recommended) so Luaward can ask Linkvertise whether the visit really finished. |
| Lootlabs | Paste the link or its code. With your Lootlabs API key, Luaward seals its check inside the link. |
| Work.ink | Paste the link. Luaward registers the return address with Work.ink and checks the one-time token it sends back. |
| ShrtFly, ShrinkEarn | Paste the account's API token; there is no link to paste. This is the most basic check. |
| Test step | Only waits. Use it to try the page before a real provider is set up. |
Give each step a shortest time in seconds: a player who comes back sooner did not really do the step. Press Check setup to test the provider connection. Steps run in the order you list them, and Strict check decides whether a player may continue when the provider cannot be reached (Gateway providers).
4. Set the rules
In the Rules tab:
- How long a key lasts and Keys per player.
- Script shown with the key: choose your script and its loader line appears under the key with the key already filled in, so players copy one line.
- Optional: let players extend or renew their key, make them wait between rounds, or let them give a key up.
- Protection: ask for Discord only when a visit looks risky, block VPNs and datacenters, keep the same address from start to finish, or block countries. Put a rule in Trial first to see whom it would stop before it is real (Checkpoint security).
5. Share the link and test it
Turn the page on, then Copy link. Open the link in a private browser window and do the steps yourself. At the end the page shows the key and, if you chose a script, the loader line to copy. The Stats tab shows visits and where players drop off for each step.
6. What players run
Players put their key on the line above your loader:
script_key = "PLAYER_LICENSE_KEY"
loadstring(game:HttpGet("https://luaward.com/loader/YOUR_SCRIPT_ID.lua"))()Every run, Luaward checks that the key exists, has not expired or been banned, and belongs to the device it was first used on. A key binds to a device on its first valid run; you can reset it from the Dashboard, and players can reset it themselves if the project allows it (Device binding).
Sell keys as well
A key page is one way to hand out keys. You can also make keys yourself in Keys & users → New keys (one key, or a batch of up to 300, with an end date and a note only you see) and give them to buyers, or automate it with the Developer API. Both kinds of key work with the same loader line.
Common problems
- The page says it has no steps: add at least one step, or the Test step, and save.
- "This key is locked to another device": the key was first used on another device. Reset it in Keys & users, or turn on visitor resets in the project settings.
- "This script has used all of its runs for this month": a Free workspace has used its 10,000 runs. Scripts start again on the 1st (UTC) or when a paid plan starts.
- Players finish steps without seeing the ads: add the provider token or API key to the step, and consider Strict check and the protection rules. No browser-based check can stop every automated visit.