Discord Bot
The Riftseer Discord bot runs on Cloudflare Workers. It answers slash commands by calling the Riftseer API and replying with rich embeds (card stats, links, and optional card art).
Source: apps/discord-bot/
Slash commands
| Command | Options | Description |
|---|---|---|
/card | name (required), set, image | Look up a card; set image:true for image-focused replies |
/random | — | Return a random card |
/sets | — | List all sets |
How interactions work
Discord requires an initial response within about three seconds. The worker never blocks on the API during that window:
- Discord
POSTs the interaction to the worker URL. - The worker verifies the Ed25519 signature (Discord public key).
- It immediately responds with type 5 (deferred response).
- Inside
waitUntil, the handler calls the Riftseer API via the typed Eden client (@elysiajs/edenagainst@riftseer/apitypes). - The handler PATCHes the interaction follow-up webhook with the final message.
If the API were awaited before the deferred response, Discord would time out.
Local development & deploy
From the repo root (workspace install):
cd apps/discord-bot
bun run dev # wrangler dev — local tunnel
bun run deploy # production worker
bun run register # register slash commands with Discord (re-run when commands change)
bun run typecheck
Configuration
Secrets (wrangler secret put)
| Secret | Source |
|---|---|
DISCORD_PUBLIC_KEY | Developer Portal → Application → General Information |
DISCORD_BOT_TOKEN | Developer Portal → Bot |
DISCORD_APPLICATION_ID | Developer Portal → General Information |
Public vars
API_BASE_URL and SITE_BASE_URL are set in wrangler.jsonc (overridable at deploy with --var).
Privacy
The bot does not persist user data. It forwards the requested card name (and optional set hint) to the public API and returns the result. If logging or storage is added later, update the site Privacy Policy accordingly.