The release routine
A private original. A protected build. A loadstring you can keep. Here is how the pieces fit together, from the editor to your player's key window.
Yours from
the first line.
Saved privately
Validated before publishing
Your next release, same address
Your release workflow / illustrated
Four connected steps
Write
Paste or upload original Lua or Luau source. Work in the editor and save a draft while your published version stays available.
Originals, drafts and protected output have separate jobs. Your public loader does not serve the saved original.
Start your first scriptProtect
Run the protection build. Supported functions use a per-function bytecode VM alongside encoded constants, control-flow transformations and a watermark.
The build is parsed and compiler-checked. A failed, stale or cancelled build does not replace your working release.
See what the engine doesConfigure
Choose your acquisition tasks and their order, configure available timers and captcha, and set the lifetime of your free keys — or skip the key system entirely and ship a protected loadstring on its own.
The key system is optional. Expiry, revocation and access decisions are enforced on the server. A community link visit is not verified group membership.
Understand the key flowRelease
Share the generated loadstring after publication. Future published builds use that same delivery address, so your players keep their link.
Use activity views to distinguish deliveries from client-reported execution starts. Restore an earlier original when you need to revisit a change.
Publish and testOn the other side
A player opens your generated loader. When a key is required, the key window points them to your acquisition page. They complete your configured free-key steps and enter the issued key in the loader.
Free-key tasks repeat for each newly generated key. The server checks access, expiry and revocation before delivering an available protected release.
A site-issued, activated premium key skips acquisition tasks across active vodka scripts. It does not override disabled scripts, suspensions, expiry, revocation or rate limits.
Keep going
Keep building
Bring your original source. Make the workspace your own.
