Running keys

Claiming keys

Members take a key for themselves with /claim. This page covers what they see, everything that can stop a claim, and how they get back to a key later.

Running /claim

A member types /claim in your server and picks a pool from the autocomplete list, which shows each pool as name (game). KeyBot replies with the key, and the reply is ephemeral: only the person who ran the command can see it, and it is not left sitting in the channel.

For a Steam pool the reply includes a Steam activation link, so the key can be redeemed in one click. For a custom pool the reply is the key on its own.

Two people cannot get the same keyKeys are claimed atomically. If several members run /claim at the same instant, each is handed a different key, or told the pool is empty. There is no race that can issue one key twice.

What can block a claim

KeyBot checks these in order and stops at the first failure, so a member always gets one clear reason:

#	Check	What the member is told
1	Banned from the whole server	They are banned from claiming keys in this server, and should contact the server admins if that looks wrong.
2	The pool name does not exist	The named key pool was not found.
3	Banned from this specific pool	They are banned from claiming keys in this pool.
4	The pool is private	"Keys for this game are private."
5	Missing a required role	The exact roles they still need, listed as role mentions, so they know what to ask for.
6	Already at the per-member limit	How many keys they may claim for this game. They have already had that many.
7	The pool is out of keys	There are no more keys for that game.

Steps 1 to 5 are configuration: if a member is being blocked and should not be, the answer is a ban entry, the pool's visibility, or its required roles. Steps 6 and 7 are inventory.

Seeing what is available

Anyone in the server can run /pools to page through the server's pools. Each entry shows the game, whether the pool is public, how many keys a member may claim, the key type, how many keys are left, and which roles are required. The reply is ephemeral.

/pools lists private pools tooPrivate pools appear in the list marked as not public. Members can see that a pool exists and how many keys it holds, they simply cannot claim from it. If a drop needs to stay secret until launch, do not create the pool until you are ready.

Finding a key again

There are two ways for a member to get back to a key they already claimed.

/keys in the bot's DMs. This command only works in a direct message with KeyBot, not in a server, because it lists keys from every server the member has claimed in. Keys are grouped by game and paged through; Steam keys are shown as redemption links.
The web. Signing in on the site and opening your keys shows the same list in the browser, which is easier to copy from than a Discord message.

Some servers migrated key history into KeyBot from an older system without the key values themselves. Those entries show as 00000-00000-00000, and KeyBot explains that the original key cannot be recovered. A member who sees that placeholder needs to ask whoever ran the giveaway, not the bot.

NextModeration →