Commands and settings
Every stingsby slash command and /config setting: the honeypot, security scan, reports, bulk message clean-up, duplicate detection and the join log.
/help only lists the commands you can use. Server admins can change who sees each command in Server Settings → Integrations → stingsby.
General · everyone
| Command | What you get |
|---|---|
/help | The commands you can use, grouped by category, plus a quick start for staff |
/about | What stingsby is, servers protected, total bans, uptime, version and maintainer |
Honeypot · Manage Server
| Command | Options and details |
|---|---|
/honeypot setup | channel: existing channel to use; leave empty to create one. name: name for a new channel (default 🐝・dont-poke-the-hive). post_warning: post and pin the warning (default yes) |
/honeypot status | Trap state, channels, delete window, exempt roles, bans in the last 24 h / 7 d / 30 d, the last trigger, and a permission check |
/honeypot logs | kind: all, bans, softbans, timeouts, failed bans, config changes, warnings, message clears, unbans, removed timeouts, or joins and leaves. user: only events about this user (an ID works for banned users). limit: 1–25, default 10 |
Security · Manage Server
| Command | Options and details |
|---|---|
/security scan | 14 checks and a 0–100 score. See Security scan |
/security report | days: 1, 7, 30 or 90 (default 7). A summary plus a downloadable Markdown report. See Reports |
/ping | Gateway latency, API round-trip and database time. Green under 200 ms, orange under 500 ms, red above |
Settings · Manage Server
/config opens the settings panel: a private message where each setting has a title, a one-line explanation and its menu or button, with the trap's state at the top and a permission check at the bottom. Every change is saved as soon as you pick it, shown at the top of the panel, and announced in the log channel.
| Control | What it does |
|---|---|
| 📝 Log channel | Where ban reports and setting changes are posted. Clear it (the × in the menu) to stop reports. The event log still records everything |
| 🔨 Action | Ban (default), Softban, Timeout or Escalating. See When the trap fires |
| 🆕 New accounts | Accounts younger than this are banned straight away, whatever the action: off, 1 hour, 1 day (default), 7 or 30 days |
| 🛡️ Exempt roles | Roles that are never caught, up to 25. Pick the full list: roles you leave out stop being exempt |
| 🌐 Language | One of the 11 supported languages, or 🌐 Automatic |
| ⏸️ Pause / ▶️ Arm trap | Turns the trap off or back on. Settings are kept. Only shown once /honeypot setup has set a trap channel |
| ⏱️ Durations | A form for the hours of messages to delete (0–168, default 24), the timeout length (1–28 days, default 7), and for the escalating action the two strike timeouts (1 and 7 days) and when strikes reset (default 90 days) |
| 🚨 Incidents | Who gets pinged, and what gets paused, when a raid, DM spam or a join spike is detected. See Raids and DM spam |
| 🔁 Duplicate detection | Also catches accounts that post the same message in 3 or more channels within 30 seconds, even if they skip the trap, with the same action as the trap. Off by default: Turn on / Turn off |
| 📥 Join log | Where every join and leave is posted: who joined or left and when, how old their account is, and who invited them. Off by default; clear it to turn it off. See Join log |
| 🗑️ Reset or delete data | Asks what to delete: Reset settings, keep log deletes this server's settings and turns the trap off, keeping the event log and strikes. 🔥 Delete all data also deletes the event log and strikes, and can't be undone. Either way stingsby stays in the server (kick it afterwards to remove it) and no channels are deleted |
Only the person who ran /config can use the panel. It greys out after 10 minutes without a click; run /config again.
🔁 Duplicate detection compares what messages say, so it needs Discord's Message Content access. If stingsby ever runs without it, the setting says so and can't be turned on, and reports show "text not available" instead of the spam text. Everything else keeps working.
New features sometimes start as experiments that the maintainer switches on per server. When there is one, a /experimental command appears for asking access. There are none right now.
Clean-up · Manage Messages
| Command | Options and details |
|---|---|
/clear channel | Deletes recent messages in the channel you run it in. amount: 1–500 newest messages. minutes: only the last 1–20160 minutes (14 days). user: only that user's messages |
/clear user | Deletes one user's recent messages in every channel and active thread that both you and the bot can manage. user (required), amount (counted across all channels), minutes |
- Give
amount,minutesor both. With both, a message must match both:amount:50 minutes:10deletes at most 50 messages, all from the last 10 minutes. - Pinned messages are always kept, including the honeypot's warning.
- Only the newest 2000 messages of each channel are checked, and archived threads are skipped.
- Discord only bulk-deletes messages under 14 days old. Older ones are removed one by one, which is slower.