How to set up a Discord key bot. One command stands up the server.

A Discord key bot moves redemption and support into the server your community already lives in. Players claim and manage their own keys from chat, and you issue, revoke and read stats without opening a dashboard. vodka ships this bot as part of the key system, and it is a front end over the same API the rest of the platform uses, so every action still runs through the server-side checks.

Standing it up is close to one command. Run /setup and the bot builds the channels, roles and panels for you, idempotently, so it is safe to re-run and never deletes what you have.

Owner commands only unlock once the bot knows who you are. In your vodka Settings, link your Discord account to your creator account. From then on the bot resolves your Discord id to your account and checks you own the target script before any owner action, so there is no way to touch someone else's scripts.

This link is also what scopes the owner commands to the scripts you actually own. A script you do not own simply reads as no such script, so your keys and stats stay yours.

Invite the bot to your server, then run /setup once. It walks a declarative blueprint and only ever adds what is missing:

• Creates the vodka categories and channels, including get-key, support, staff and logs.
• Adds the roles and posts the verification panel, a welcome and rules, and sets a default redeem role.
• Is idempotent and add-only, so re-running it is safe and never deletes anything you already have.
• Run /setup-continue to finish the rest: rules, welcome, log and alert channels, and a support-ticket panel.

Decide what a successful redeem grants. Use /keyrole to set the role players receive when they redeem a valid key, per server. Then use /panel to post a persistent verification panel with Redeem, Get-free-key and Reset-HWID buttons that keep working across restarts.

From there players serve themselves: /redeem validates a key, links it to their Discord account, grants the role and returns the loadstring in an ephemeral reply; /mykey lists their own keys with status and a Reset-HWID button; /resethwid clears their own device binding within the key's reset allowance.

With the server set up, the owner commands are where you work day to day:

• /keys to create, bulk-issue, revoke, look up and list a script's keys. Bulk batches arrive as a DM text file.
• /stats for executions, unique players and active keys on a script you own.
• /blacklist to block or unblock a user or a key.
• Moderation commands (/ban, /kick, /timeout, /warn, /purge, /unban) gated on both your permissions and the bot's, with a mod-log entry on each action.

If you would rather automate issuing and revoking from your own code instead of chat, the same actions are available through the scoped developer API.