Map what you use today.
List your scripts, dependencies, key lifetimes, account bindings, Discord actions and advertising integrations. Check that the capabilities you depend on are available before planning the switch.
Documentation / Moving from Luarmor
Your scripts. A new workspace.
Bring your original source, recreate the access flow and test before switching. A practical migration guide with the important differences spelled out.
Before you begin
Make room for a careful handover.
Keep your current working release available while you evaluate vodka. Make a private backup of original source and document the access rules your users depend on.
You do not need to share a Luarmor account password or API key with vodka for this manual migration. Do not paste credentials into your source or public listing.
Bring original source.
An existing generated loader or protected artifact is not a substitute for your original project. This guide does not offer deobfuscation or recovery of another service's protected output.
The migration checklist
Move one working script first.
Create the new workspace.
Create a vodka account and a new script. Paste or upload original source you control. Remove or replace calls tied to the old service; they do not automatically translate into vodka access checks.
Build, configure and test.
Build the protected script, review the result and recreate your supported task and key settings. Test your generated loader, valid access, expired or revoked keys and a follow-up published update.
Bring your existing keys.
Your existing Luarmor keys import directly — paste them on a script's Keys page and they keep working as-is, with no reissue (see below). Users, remaining durations and project history do not carry over, so plan separately for anything beyond the key strings themselves.
Share the new address.
Update your own distribution pages, documentation and community announcements to use the generated vodka loadstring. Tell users what changed and keep a documented way back to your previous working setup during the transition.
Bring your existing keys
Keep the keys your users already have.
You do not have to reissue. Open a script in the dashboard, go to its Keys page and choose Import keys. Paste your current keys — a Luarmor export works, one per line — and vodka stores each one as an HMAC, exactly the way it stores keys issued here.
Because it is the original key string that gets imported, those keys keep working for your users as they are: no new loader to hand out, no message asking everyone to swap keys. Set an expiry in days if you want one, or leave it blank to keep them long-lived.
Paste, don't reissue.
Imported keys verify as-is. This brings the key strings, not account history, users or remaining durations. Import up to 5,000 at a time and split a larger export into batches.
Check your integrations
Know what needs a new plan.
Luarmor advertises a ready-to-use Discord bot and ad-link system. vodka does not currently provide an equivalent bot or an integrated ad-revenue program. If your workflow depends on either, resolve that requirement before replacing your current service.
Read the dated, sourced comparison and the first-script guide. Test with a small group before moving a wider community.
Migration questions
Keep the transition clear.
01Is there a one-click Luarmor import?
No. The current migration is manual. Bring original source, recreate the access rules you need, test the new build and distribute the new vodka loader.
02Will existing Luarmor keys validate on vodka?
No. Luarmor keys are not automatically recognized by vodka. Plan replacement access for existing users, including how you will handle remaining durations, and communicate the change before switching.
03Can my old Luarmor loadstring stay the same?
Moving to vodka creates a new delivery address. Update the places where you distribute your loader. Once you are using vodka, future published releases can keep that vodka address.
Keep building
Try your first script in vodka.
Keep your original source and evaluate the workspace before making the switch.
vodka / Product notesUpdated