Discord bots
Your bot, your token, your server. We run the process and wire it to your vault. Discord treats it as yours because it is.
Your bot, not ours
A bot on sten.wtf runs under your Discord application. It wears your name and avatar. We run the process and connect it to your vault. Discord considers it yours because it is.
Setup
Create the Discord application
In the developer portal, New Application, then Bot → Reset Token. The token is shown once.
Privileged intents
Server Members Intent and Message Content Intent. Skip this and the bot comes online then does nothing.
Add it on sten.wtf
Bots → create. Paste the token. It is validated immediately, then encrypted at rest and never shown back in full.
Invite
Use the invite URL from the dashboard. It is least-privilege — do not re-add Administrator “just in case” unless you mean it.
Full walkthrough: how to set up a Discord bot.
Commands that actually exist
The public sten.wtf Discord bot is not your operator console. It loads status, welcome, (optionally) AI, ChatGuard, and announcement buttons. It does not load /secure, /redeem, or /config.
Your bot does. Typical user-bot commands: /secure, /status, /claim, /send, /config, /verify, /requestotp, /stats, /mail, /auth. You can rename, disable, or add custom slash commands from the bot’s Commands tab.
Slots
How many bots you can run is licence + slot keys. Extra slots are a Purchase tab. An expired licence stops every bot; the applications in Discord stay yours.