Migrating from Luarmor
Move loader usage and key automation to Luaward without assuming full REST API parity.
What stays familiar
Luaward generates a loader that can be used with the common executor pattern. For keyed scripts, assign the license key before calling the loader:
script_key = "YOUR_LUAWARD_LICENSE_KEY"
loadstring(game:HttpGet("https://luaward.com/l/YOUR_SCRIPT_ID.lua"))()Move your scripts
- Create a Luaward project and script.
- Upload the current source and wait for the build to become Ready.
- Choose whether the script is keyless or keyed.
- Copy the Luaward loader and update the distribution post or project configuration.
- Test the new loader and key flow in the executor environment you support.
Move API automation
Create a Luaward developer API key and change your base URL to https://luaward.com/v3. Then map your existing key-management calls to the endpoints in the API reference.
Every route in Luarmor's v3 documentation has a counterpart here, with the same path and field names apart from the differences below. Check methods, fields, expiry behavior and response bodies against your own program before switching production automation. Authenticate with Authorization: Bearer YOUR_KEY (a bare key works too). A key you choose yourself for user_key must be exactly 32 letters (A–Z, a–z), the shape of every Luaward key; anything else is refused with 400, because the loader would never accept it.
| Luarmor | Luaward | Note |
|---|---|---|
| GET api.luarmor.net/status | GET /v3/status | The same answer. |
| GET /v3/keys/:api_key/details | GET /v3/keys/:key/details | The :key segment is never read; use any word, never the key itself. |
| GET /v3/keys/:api_key/stats | GET /v3/keys/:key/stats | noUsers is accepted. Adds limits. |
| GET /v3/projects/:id/users | GET /v3/projects/:id/users | from and until are a window of positions, newest first, at most 100. |
| POST, PATCH, DELETE /v3/projects/:id/users | POST, PATCH, DELETE /v3/projects/:id/users | PATCH can change identifier too. |
| POST …/users/resethwid | POST …/users/resethwid | force is accepted; a reset here always skips the cooldown. |
| POST …/users/linkdiscord | POST …/users/linkdiscord | 409 ALREADY_LINKED unless force. |
| POST …/users/blacklist | POST …/users/blacklist | ban_reason and ban_expire (-1 is permanent); ban with reason and until works too. |
| GET …/users/unban?unban_token= | GET …/users/unban?unban_token= | No API key needed; works once. |
| PUT …/scripts/:script_id | PUT …/scripts/:script_id | script plus silent, ffa, heartbeat, lightning; the answer is 202 with a build_id to follow. |
Luaward adds routes Luarmor's v3 does not have: projects, scripts and their builds, bulk keys and export, statistics, the audit log and the key system. Start with a separate script and a test key, and revoke the old credentials once the migration is complete.
Roll out safely
Test with a separate script and a test key first. Keep the old distribution available until the Luaward build, loader, and key checks all work. Revoke old API credentials after the migration is complete.