babes
babes
Embeds
Embeds are a way to specially format and structure a message — a colored border, title, images, footer and more. Build them once, give them a name, use them everywhere: in chat, in your welcome / goodbye / boost messages, and in the dashboard.
The command base is /embed — and every subcommand also exists as a prefix command, e.g. ,embed create. Both edit the same data as the dashboard’s Embed Creator, so a change made anywhere shows up everywhere.
For example, to delete the existing embed named example, you would run ,embed delete example — or /embed delete embed:example. The bot replies with Deleted embed successfully.
You can edit an existing embed by using ,embed edit OR ,embed edit all:
There are 8 possible embed properties for you to edit — author, color, description, footer, image, thumbnail, timestamp, title:
| Property | Command |
|---|---|
| author | ,embed edit author (name) (optional text) icon:(optional icon link) |
| color | ,embed edit color (name) (optional color hex) |
| description | ,embed edit description (name) (optional text) |
| footer | ,embed edit footer (name) (optional text) icon:(optional icon link) |
| image | ,embed edit image (name) (optional image link) |
| thumbnail | ,embed edit thumbnail (name) (optional image link) |
| timestamp | ,embed edit timestamp (name) true/false |
| title | ,embed edit title (name) (optional text) |
Variables are filled in the moment an embed is shown — in every text, icon and image property:
| Variable | Becomes |
|---|---|
| {user} | mentions the member |
| {user_name} | the member’s display name |
| {user_tag} | the member’s tag |
| {user_avatar} | the member’s avatar URL (for icons/images) |
| {server_name} | the server name |
| {server_icon} | the server icon URL |
| {server_membercount} | member count (e.g. 1,204) |
| {server_membercount_ordinal} | ordinal member count (e.g. 1204th) |
| {server_owner} | mentions the server owner |
| {server_createdate} | the server’s creation date |
| {server_boostcount} | current boost count |
| {newline} | starts a new line |
| {date} | today’s date |
Posts the finished embed in the current channel — variables resolved. You can also attach a named embed to your welcome, goodbye or boost message with {embed:name}.
Embeds › embed guide
Embeds aren’t limited to things such as rules or welcome messages — they can be used for anything!
Embeds › embed guide
A warm welcome card for every new member — built once, attached to your welcome message.
Embeds › embed guide
Say goodbye in style — a leave message with an attached embed.
Embeds › embed guide
A clean, professional rules card for your rules channel.
Embeds › embed guide
Thank your boosters properly — a boost card attached to your boost message.
Overview
Every command can be switched on/off and restricted per role, per member and per channel — from chat or from the dashboard. Both write the same settings.
Commands are off by default on a fresh server. Turn them on individually or per category on the dashboard’s Commands tab — or from chat:
| Command | Does |
|---|---|
| ,enable (command) | turn a command on |
| ,disable (command) | turn a command off |
| Command | Does |
|---|---|
| ,allow (command) (@role) | add a role to the command’s Allowed list |
| ,disallow (command) (@role) | add a role to the Disallowed list |
| ,allowchannel (command) (#channel) | restrict a command to specific channels |
| ,disallowchannel (command) (#channel) | block a command in specific channels |
| ,accesslist [command | all] | show the configured permissions |
The default prefix is , and can be changed on the dashboard (General) or with ,prefix set (symbol). Voice commands additionally accept up to two extra prefixes configured on the VoiceMaster tab.
Security Setup
Detects the real voice-channel DDoS — everyone in a voice channel loses their connection and reconnects in a loop — and instantly moves the channel to a fresh voice server by rotating its region.
A voice channel is pinned to one Discord voice server. VC-crasher tooling floods exactly that server: every member drops to “RTC Connecting” and reconnects in a loop while staying inside the channel. The attacker is invisible from the outside — but the victims are unmistakable: many different members each producing repeated connection transitions on the same channel within seconds.
Only repeat reconnects count — a movie night ending (30 people leaving at once) produces one event per member and can never trigger the detector.
Nothing inside the guild helps once the voice server itself is flooded. The one thing that works: changing the channel’s RTC region forces Discord to move it to a brand-new voice server — the flood hits nothing and the channel works again instantly. The new region is held for a few minutes (so automatic routing can’t hand back the attacked server), then the channel returns to automatic.
Everything lives on the dashboard’s Anti Channel-DDoS tab:
The tab keeps the last 10 detected attacks: which channel was hit, how hard (reconnects × members), which region the channel was moved to, and when.
Server Configuration
A farewell message whenever a member leaves — text with variables, rich looks via named embeds.
| Command | Does |
|---|---|
| ,goodbye channel (#channel) | where goodbye messages are sent (also enables them) |
| ,goodbye message (text) | the message text — variables and {embed:name} work |
| ,goodbye test | send a test as if you just left |
| ,goodbye on / ,goodbye off | toggle |
| ,goodbye | show the current configuration |
For a full walkthrough with an attached embed, see the leave/goodbye embed guide.
Server Configuration
Thank every booster automatically — message text, a configurable embed, link buttons, and named embeds via {embed:name}.
Everything lives on the dashboard’s Boost tab: pick the channel, write the message text, optionally build an embed (author, title, description, thumbnail — {avatar} works — image, footer, fields, timestamp), add up to five link buttons, then use the test button to preview exactly what boosters will see.
Step-by-step: the boost embed guide.
Server Configuration
If-this-then-that for your server: pick a trigger, chain actions, done — built visually on the dashboard.
Open the dashboard’s Automations tab and create a rule: choose a trigger (a member joins, a member leaves, a message is sent, and more), add actions (send a message, give/remove roles, …), save — the rule runs automatically from then on. Ready-made templates get you started with one click.
Server Configuration
Build your own prefix commands with custom responses — no code, straight from the dashboard.
The dashboard’s Custom Commands tab lets you create commands with your own name and response — plain text or a full embed. Members run them with the normal prefix like any built-in command (,commandname).
Server Configuration
Automatic replies to trigger words — the bot answers whenever a message matches.
| Command | Does |
|---|---|
| ,autoresponder add (trigger) (response) | create an auto-responder trigger |
| ,autoresponder update (trigger) (response) | update an existing trigger |
| ,autoresponder remove (trigger) | remove a trigger |
| ,autoresponder list | list every trigger |
| ,autoresponder exclusive (trigger) | toggle whether the trigger must be the whole message |
| ,autoresponder role (trigger) (role) | restrict a trigger to a specific role |
| ,autoresponder reset | remove every auto-responder |
Server Configuration
Pin a message to the bottom of a channel — the bot re-posts it automatically so it always stays the newest message.
Configured on the dashboard’s Sticky Messages tab: pick a channel, write the sticky (text or embed), hit Save & Post. Whenever someone sends a message in that channel, the bot deletes its previous sticky and re-posts it at the bottom — other bots’ messages push it down too.
Server Configuration
Repeating auto-messages — the bot posts your message into a channel on a fixed interval.
| Command | Does |
|---|---|
| ,timer add (channel) (interval) (message) | create a repeating timed message |
| ,timer view (channel) | view the timed message of a channel |
| ,timer remove (channel) (id) | remove a timed message |
| ,timer list | list every timed message on the server |
Server Configuration
Live statistics as channel names — member count, bots, boosters and more, updating automatically.
| Command | Does |
|---|---|
| ,counter add (option) (channel) | create a channel counter |
| ,counter set (channel) (option) | turn an existing channel into a counter |
| ,counter remove (channel) (action) | remove a counter |
| ,counter list | list every counter |
Server Configuration
Self-assignable roles — members react to a message or click a button to get (and remove) a role.
| Command | Does |
|---|---|
| ,reactionrole add (message) (emoji) (role) | add a reaction role to a message |
| ,reactionrole remove (message) (emoji) | remove one reaction role |
| ,reactionrole removeall (message) | remove all from a message |
| ,reactionrole list | list every reaction role |
| ,reactionrole reset | remove every reaction role on the server |
| Command | Does |
|---|---|
| ,buttonrole add (channel) (emoji) (role) | add a button role |
| ,buttonrole remove (message) (role) | remove one button role |
| ,buttonrole removeall (message) | remove all from a message |
| ,buttonrole list | list every button role |
| ,buttonrole reset | remove every button role on the server |
Server Configuration
Every booster gets their own personal role — own name, own color, own icon.
| Command | Does |
|---|---|
| ,boosterrole create [#color] [#color2] [name] | create your personal role — name only, color(s) only, or both |
| ,boosterrole rename (new name) | rename your role |
| ,boosterrole color (color) [second color] | set your role color |
| ,boosterrole icon (emoji | url) | set a role icon |
| ,boosterrole random | random color |
| ,boosterrole dominant | color from your avatar’s dominant color |
| ,boosterrole share (member) | share your role with another member |
| ,boosterrole share remove (role) / share list | manage shared slots |
| ,boosterrole remove | delete your booster role |
| Command | Does |
|---|---|
| ,boosterrole list | view all booster roles |
| ,boosterrole cleanup | remove unused booster roles |
| ,boosterrole base (role) | the role booster roles are sorted under |
| ,boosterrole limit (number) | maximum number of booster roles |
| ,boosterrole link (member) (role) | link an existing role to a member |
| ,boosterrole award (role) / award unset / award view | a role every booster automatically receives |
| ,boosterrole filter (word) / filter list / filter remove | blacklist words from booster role names |
| ,boosterrole share limit (n) / share max (n) | shared-slot limits |
Server Configuration
Who invited whom — live invite tracking with per-member counts and a leaderboard.
| Command | Does |
|---|---|
| ,invites [member] | a member’s invite count |
| ,invitecodes [member] | the invite codes a member owns |
| ,leaderboard | top inviters |
| ,stats [member] | invite statistics |
Server Configuration
Members DM the bot to file a report — staff handle it in a private ticket channel and reply straight back into the member’s DMs.
Configured on the dashboard’s DM Support tab: enable, category channel, staff roles, report categories.
Miscellaneous
The everyday toolbox — AFK, snipes, avatars, polls, translation, media tools and info commands.
| Command | Does |
|---|---|
| ,afk [status] | mark yourself AFK; anyone pinging you sees your status, your next message clears it |
| Command | Does |
|---|---|
| ,snipe [1-20] | show the most recently deleted message (index goes further back) |
| ,editsnipe [1-20] | show the previous content of an edited message |
| ,reactionsnipe | show recently removed reactions |
| ,reactionhistory | reaction history of a message |
| ,clearsnipe | clear the snipe cache |
| Command | Does |
|---|---|
| ,av [member] / ,sav | user avatar / server-specific avatar |
| ,banner [member] / ,sbanner | user banner / server banner |
| ,userinfo [member] | account + member details |
| ,serverinfo | server overview |
| ,membercount | member count |
| ,roles / ,inrole (role) | role list / members in a role |
| ,newmembers [count] | newest members |
| ,namehistory [member] | name history |
| ,perms [member] | permission overview |
| Command | Does |
|---|---|
| ,poll (duration) (question) | timed poll |
| ,translate [to language] (text) | translate text |
| ,tts (text) / ,ttschannel | text-to-speech |
| ,ocr / ,ocrtr | read text from an image / read + translate |
| ,media (effect) (url or attachment) | image/video effects |
| ,lego / ,makegif / ,transparent | image transforms |
| ,movie (title) / ,tvshow (title) | film / show lookup |
| ,lyrics (search) / ,anime / ,manga / ,giphy / ,wolfram / ,book / ,duckduckgo | search commands |
Miscellaneous
Games, social commands and community reputation.
| Command | Does |
|---|---|
| ,ship (@user) [@user2] | compatibility meter |
| ,iq [@user] | very scientific IQ test |
| ,quote | quote a message |
| ,steal (emoji) / ,emojiadd | steal emojis into your server |
| ,tags (subcommand) | server tags — save and recall text snippets |
| ,nick (member) (newnick) | rename a member |
| ,forcenickname (member) (name) | lock a member’s nickname (reverted on every change, re-applied on rejoin) — remove / list subcommands |
| Command | Does |
|---|---|
| +rep @user / -rep @user | give / take reputation (own shortcut prefix, no comma) |
| ,repscore [@user | top] | reputation score / top list |
| Command | Does |
|---|---|
| ,tictactoe (@member) | tic-tac-toe with buttons |
| ,blacktea | word game |
| ,topgames | most played games on the server |
| ,loot [@user] | loot drops |
Server Configuration
Announce new posts, videos and livestreams from 8 social platforms directly in your channels — each platform with its own command, all sharing the same four subcommands.
| Command | Announces | Target format |
|---|---|---|
| ,youtube | new uploads | channel id (UC…) or @handle |
| ,twitch | stream goes live | streamer name |
| ,kick | stream goes live | streamer name |
| ,x | new posts | username without @ |
| new posts | r/subreddit or plain name | |
| ,tiktok | new uploads | @username |
| ,soundcloud | — | reserved (needs API key) |
| — | reserved (needs API key) |
Creates a subscription: whenever the account posts, an announcement appears in the chosen channel. The same account can feed several channels, and one channel can carry several accounts.
Works identically on every platform:
Removes exactly one subscription — the pair of channel and account. Other channels subscribed to the same account keep working.
Shows every subscription of that platform on this server: the account, the channel it posts into, and the custom message if one is set. Each platform lists only its own — ,youtube list won’t show Twitch subscriptions.
Replaces the default announcement text with your own. Placeholders are filled per post:
| Placeholder | Becomes |
|---|---|
| {target} / {user} | the subscribed account name |
| {title} | video/post title (empty where the platform has none) |
| {url} | direct link to the post/stream |
| {text} | post text, where available (e.g. Reddit selftext, max 300 chars) |
Role pings like @Videos work inside the message; whether they actually notify follows the subscription’s ping setting.
Server Configuration
Personal reminders — one-off or recurring, delivered as a ping in the channel you set them, with a DM fallback.
,remind add … is the identical long form. The confirmation shows the exact due time as a Discord timestamp — every reader sees it converted to their own timezone — plus the id you’d use to remove it.
| Short | Long (EN) | Long (DE) |
|---|---|---|
| 45s | seconds | sekunden |
| 10m | minutes | minuten |
| 2h | hours | stunden |
| 3d | days | tage |
| 1w | weeks | wochen |
Number and unit are written together: 30minuten works, 30 minuten (with a space) doesn’t.
,remind add every 12h dehnen — add and every combine freely.
Both ,remind list and the standalone ,reminders show the same thing: every active reminder with its id, a live countdown (in 3 hours), the repeat interval for recurring ones, and the text. A bare ,remind with no arguments shows the list too.
Resources
All available voices for the text-to-speech command — real neural voices, picked by name.
Guy English US Christopher English US Eric English US Roger English US Steffan English US Andrew English US Brian English US Joey English US Matthew English US Justin English US Ryan English GB Thomas English GB William English AU Liam English CA Conrad German Killian German Florian German Henri French Remy French Alvaro Spanish Diego Spanish MX Giuseppe Italian Duarte Portuguese BR Maxim Russian Jan Polish Keita Japanese Injoon Korean Yunxi Chinese Hamed Arabic
Jenny English US Aria English US Michelle English US Ana English US Emma English US Ava English US Sonia English GB Libby English GB Natasha English AU Clara English CA Katja German Amala German Seraphina German Denise French Vivienne French Elvira Spanish Dalia Spanish MX Isabella Italian Francisca Portuguese BR Svetlana Russian Zofia Polish Nanami Japanese Sunhi Korean Xiaoxiao Chinese Zariyah Arabic
,ttschannel [voice] (text) is reserved for speaking directly into your current voice channel. It requires the Lavalink TTS setup (see lavalink/SETUP.md) — until that is configured, the command explains what’s missing instead of failing silently.
Overview
babes is a premium all-in-one Discord bot — security, moderation, tickets, levels, music, statistics and everything in between.
Invite babes from the homepage. The moment it joins, every module is ready — nothing has to be installed. You configure features in two equal ways:
The default prefix is , — every command in these docs is written with it. Change it any time:
Every single command can be enabled, disabled or restricted to specific roles — per command, per category, or in bulk:
Stuck? Join the support server, check the FAQ, or browse every command with usage and aliases on the commands page.
Overview
babes Premium unlocks every feature on every server you own.
Premium removes every feature gate: per-server bot customization (name, avatar, banner, bio), extended limits across modules, and priority in the support server. Free modules — levels, giveaways, join gate and more — stay free forever.
Premium is bought on the premium page. After purchase, claim it on the server it should apply to:
Premium-only settings are kept, not deleted — they simply pause until premium is active again, so nothing has to be reconfigured.
Overview
Change how babes appears in your server — avatar, banner and bio, per server.
Security Setup
Impose restrictions on moderators to prevent destructive behavior.
It's important to have an antinuke system in place to prevent moderators from abusing their permissions. This is a security measure which lets your server stay safe from any harmful actions.
The antinuke will set a limit on the number of actions a moderator can perform in a certain time frame. If the limit is exceeded, the moderator will be punished and the incident is written to the antinuke log.
Initially, only the server owner can configure the antinuke. However, you can allow other users to configure the antinuke with the antinuke admin command.
You can exempt users from the antinuke with the antinuke whitelist command — either globally, or for a single module only (e.g. allow a bot manager to add bots without whitelisting them for everything).
The third argument decides the scope. Without one the user is whitelisted globally; with a module name only that module is bypassed; with lite only the lite-dangerous permissions are.
(no module)full whitelist — the user bypasses every antinuke modulelitelite tier — may grant/remove only the lite-dangerous permissions belowbanAnti BankickAnti Kickrole_createAnti Role Createrole_deleteAnti Role Deletechannel_createAnti Channel Createchannel_deleteAnti Channel DeletedisconnectAnti DisconnecttimeoutAnti Timeout Abusebot_addAnti Bot AddpruneAnti Prunedangerous_role_permAnti Dangerous Role Permission Updatedangerous_role_addAnti Dangerous Role AddwebhookAnti WebhookvanityAnti Vanity ChangeThese are the permissions a lite-whitelisted user may grant or remove on roles without triggering the antinuke. Every other protected permission stays fully dangerous for them.
embed_linksEmbed Linksattach_filesAttach Filesmute_membersMute Membersdeafen_membersDeafen Membersmove_membersMove MembersNot every permission is equally dangerous. The antinuke treats Embed Links, Attach Files, Mute Members, Deafen Members and Move Members as lite-dangerous: annoying if abused, but not server-destroying. All other protected permissions (Administrator, Ban Members, Manage Roles, …) remain fully dangerous.
A user on the lite whitelist may grant or remove exactly these lite permissions on roles without triggering the role-permission module — useful for staff who manage cosmetic or voice-moderation roles. Everything else still triggers the antinuke for them, unlike the full whitelist which bypasses every module.
The following flags can be used to define the antinuke module
The threshold is the number of actions a moderator can perform before being punished.
The punishment which will be applied to the moderator.
Whether babes commands should be counted towards the threshold. (e.g. ,ban)
You can disable an antinuke module with the same command you used to enable it, but with the status set to off.
You can use the antinuke config command to view the current antinuke configuration.
You can use the antinuke list command to view the enabled modules and whitelisted users.
You can use the antinuke admins command to view users which can configure the antinuke.
Roles that gain — or members that are handed — one of these protected permissions trigger the dangerous_role_perm / dangerous_role_add modules. Manage the watched set with ,antinuke permissions grant <perm> and ,antinuke permissions remove <perm>.
The everyone module watches delivered @everyone and @here pings. It closes a real gap: the antinuke always protected the granting of the Mention Everyone permission — but someone who holds it legitimately (staff role, channel override) could mass-ping without the antinuke ever looking. Now the use is watched too.
Security Setup
Keep fresh throwaway accounts out of your server before they can do anything.
The join gate checks the account age of every member who joins. Accounts younger than your configured minimum are removed automatically — before they can post, DM members or scrape your member list. Raid bots and ban evaders almost always join on brand-new accounts, which is exactly what the gate blocks.
Security Setup
Detects join waves and shuts the raid down automatically.
Anti raid watches the join rate of your server. Normal servers get a trickle of joins; a raid is a spike — dozens of accounts in seconds. When the configured threshold is crossed inside the time window, the raid response fires automatically for every account in the wave.
Anti raid is configured in the dashboard under Security → Anti Raid: join threshold, time window, the response, and the log channel where every incident is reported with the full account list.
Security Setup
Automatic message filtering — spam, links, invites, banned words, mass mentions and more.
Each filter has its own action chain: delete the message, warn the member, mute or timeout — escalating with repeat offenses. Violations are written to your log channels.
Exempt roles (moderators) and channels (staff areas, bot channels) per filter — exempted members are never punished by automod.
Everything lives in the dashboard under Automod — filters, actions, exemptions and per-channel overrides, with live previews.
Everything above is also drivable from chat. ,filter writes to the same settings as the dashboard — change something in either place and the other reflects it instantly.
Word management needs Manage Server; module settings below need Manage Channels.
| Module | Deletes messages with… | Limit means |
|---|---|---|
| caps | too many uppercase characters | max % uppercase |
| spam | messages sent too fast | messages per window |
| invites | Discord server invites | — |
| links | any link | — |
| massmention | too many user mentions | mentions per window |
| emoji | too many emojis | emojis per window |
| spoilers | too many ||spoiler|| blocks | max blocks per message |
| musicfiles | audio attachments (mp3, wav, ogg, …) | — |
Security Setup
The full moderation toolkit — punishments, message cleanup, history and safety nets.
,purge has filter subcommands — each one its own toggle on the dashboard:
,history @user shows every past case of a member — bans, kicks, mutes, warns — with case numbers, moderators and timestamps. Subcommands remove single entries or clear the record.
,hardban is a ban that defends itself: if anyone lifts it, the bot re-bans immediately and logs who tried.
,thread manages threads and forum posts. Every subcommand accepts a thread by mention, id or (partial) name — or, run inside a thread, targets that thread with no name at all.
Adds or removes a member from a private thread. Inside a thread, ,thread add @exon is enough. Requires Manage Threads.
Renames a thread or forum post — up to Discord’s limit of 100 characters. Requires Manage Threads.
Server Configuration
Button-based support tickets with panels, categories, claiming and transcripts.
A panel is the message members click to open a ticket. Build panels in the dashboard under Tickets: pick the channel the panel lives in, the category new tickets are created under, the support roles that can see them, and the panel text/embed. Multiple panels are supported — e.g. one for support, one for reports, one for applications.
Per panel you can hide tickets from specific roles or force them always-visible for others — useful for admin-only report panels.
Closed tickets can generate a transcript into your ticket log channel — a full record of the conversation for later reference.
Tickets
All the commands and permissions related to managing and using the Tickets system.
When a ticket option mixes support roles, trainee roles and global staff roles, the system resolves them in this order: Support → Trainee → Staff.
The primary command is ,tickets — it also answers to the aliases ,ticket and ,tix.
Configure the structure of the tickets system and peek into ticket stats.
| Command | Description | Example |
|---|---|---|
| ,tickets resend [channel] | Resend/recreate a live ticket panel message. | ,tickets resend #support |
| ,tickets panel [name] | List ticket panels, or open a specific panel by name. | ,tickets panel Support |
| ,tickets options | List every panel option with its trainee roles and flags. | ,tickets options |
| ,tickets options (id) trainee add/remove @role | Set the trainee roles of an option. | ,tickets options 3 trainee add @Trainee |
| ,tickets options (id) traineeclaim|traineeclose|creatorclose on/off | Toggle the option flags. | ,tickets options 3 traineeclaim on |
| ,tickets blacklist [member or role] | View, add, or remove blacklist entries. | ,tickets blacklist @spammer |
| ,tickets profiles | Manage and disable server-wide claim profiles. | ,tickets profiles disable |
These require the Administrator permission, a global ticket Staff role, or any configured option Support role.
| Command | Description | Example |
|---|---|---|
| ,tickets stats [30m|2h|3d|2w|today|all] [member] | Ticket stats for the server, or workload stats for a staff member. | ,tickets stats 2w @bryce |
| ,tickets list | List all open tickets in the server. | ,tickets list |
Claiming requires it to be enabled on the panel, the ticket to be unclaimed, and the caller must not be the ticket creator. One of the following must apply: server owner / Administrator, an option Support role, an option Trainee role with Trainees Can Claim enabled, or a global Staff role when the option has no support roles.
| Command | Description | Example |
|---|---|---|
| ,tickets claim [channel] [reason] | Claim a ticket. | ,tickets claim taking this one |
| ,tickets unclaim [channel] | Remove the current claimer from a ticket. | ,tickets unclaim |
One of the following: the ticket creator (if Creator Can Close is enabled on the option), the current claimer, owner/Administrator, an option Support role while unclaimed, a Trainee with Trainees Can Close while unclaimed, or a global Staff role while unclaimed with no option support roles.
| Command | Description | Example |
|---|---|---|
| ,tickets close [channel] [reason] | Close a ticket (transcript saved). | ,tickets close Resolved! |
Delete, reopen, move, transcript, allow, deny, allow list, rename and unclaim share one access rule: the current claimer, owner/Administrator, an option Support role while the ticket is unclaimed, or a global Staff role while unclaimed with no option support roles.
| Command | Description | Example |
|---|---|---|
| ,tickets delete [channel] [reason] | Delete a closed ticket and its channel. | ,tickets delete Spam |
| ,tickets reopen [channel] [reason] | Reopen a closed ticket. | ,tickets reopen needs help |
| ,tickets move [channel] (option) | Move a ticket to another option. | ,tickets move Billing |
| ,tickets transcript [channel or case_id] | Generate a transcript, or fetch an archived one by case ID. | ,tickets transcript 41 |
| ,tickets rename [channel] (new name) | Rename a ticket channel — other channels need Manage Channels. | ,tickets rename closed-case-1 |
Stored claim, close and reopen reasons can be updated by: Administrator, the current claimer, or Support/Staff roles when the claimer is a trainee or the ticket is unclaimed.
| Command | Description | Example |
|---|---|---|
| ,tickets reason (claim|close|reopen) [channel] (reason) | Update a stored ticket action reason. | ,tickets reason close user was spamming |
Per-ticket overrides that grant someone trainee speak/claim/close rights for that ticket only.
| Command | Description | Example |
|---|---|---|
| ,tickets trainee grant (member or role) | Grant trainee permissions for the current ticket. | ,tickets trainee grant @bryce |
| ,tickets trainee revoke (member or role) | Revoke them again. | ,tickets trainee revoke @bryce |
| ,tickets trainee list | List the overrides on the current ticket. | ,tickets trainee list |
Tickets
Control who can open tickets and manage manual attendees.
For more permission control in tickets, use the blacklist or the allow/deny manual privileges. Blacklisted members or roles cannot open tickets.
Support visibility is controlled per option; an option without its own support roles falls back to the global staff configuration. allow and deny are strictly for extra access on a specific ticket — they never replace the creator, claimer or the built-in support/staff visibility rules.
These entries apply globally — they are not ticket-specific. The command is a toggle: run it again to remove an entry.
| Command | Description | Example |
|---|---|---|
| ,tickets blacklist @member | Toggles a member on or off the ticket blacklist. | ,tickets blacklist @bryce |
| ,tickets blacklist @role | Toggles a role — anyone holding it cannot open tickets. | ,tickets blacklist @jailed |
| ,tickets blacklist | Shows the blacklisted users and roles as a paginated list. | ,tickets blacklist |
These commands only apply to the ticket they are used in.
| Command | Description | Example |
|---|---|---|
| ,tickets allow (member or role) | Explicitly lets a user or role view and send in the current ticket. | ,tickets allow @Helper |
| ,tickets allow list | Shows the extra users and roles that were explicitly allowed in. | ,tickets allow list |
| ,tickets deny (member or role) | Removes that explicit ticket access again. | ,tickets deny @Helper |
Tickets
Per-panel timers that keep ticket channels clean — reminders, auto-close and auto-delete.
All of these live in the dashboard under Tickets → your panel → Behavior. The timers take whole hours; 0 = off. Each panel has its own configuration.
When the creator leaves the server, their open tickets from the panel are deleted if still empty, or closed (transcript saved) if they already have messages. A safety sweep also catches leaves the bot missed while offline.
Server Configuration
Allow members to repost interesting messages to a starboard channel.
The starboard is a channel where members can react to messages, and after a certain number of reactions the message is reposted to the starboard channel — with the author, the content, the source channel, a jump link and the live reaction count.
All starboard commands require the Manage Server permission.
Boards start locked. Set a channel, then run ,starboard unlock — otherwise nothing is reposted. ,starboard lock pauses reposting again at any time.
,starboard set decides where reposts go.
Ignore channels, roles or members so their messages never reach the board. The command is a toggle — run it again to stop ignoring; ,starboard ignore list shows everything currently ignored.
The minimum number of reactions a message needs before it is reposted.
The emoji members must react with. Defaults: ⭐ for the starboard, 🤡 for the clownboard. Custom server emojis work too.
Whether the author’s own reaction counts toward the threshold.
,starboard config shows every setting at a glance; ,starboard reset wipes the board’s configuration, ignore list and tracked posts. Replace ,starboard with ,clownboard for the second board everywhere.
Server Configuration
Receive reminders to bump your server on DISBOARD.
Bumping your server on DISBOARD regularly increases its visibility and attracts new members. The bot detects a successful /bump, thanks the bumper, and reminds the channel when the two hour cooldown is over.
Invite the DISBOARD bot, then tell babes which channel the bumping happens in:
All Bump Reminder commands require the Manage Server permission.
,bumpreminder message sets the message sent every two hours when it is time to bump again. It supports your named embeds via {embed:name} tokens.
,bumpreminder thankyou sets the message sent right after a successful bump — {user} mentions the member who bumped.
With ,bumpreminder autolock on the channel is locked after each bump and automatically unlocked when the next bump is due — nobody chats in between.
,bumpreminder autoclean on deletes regular member messages in the bump channel a few seconds after they are sent, keeping it /bump-only.
,bumpreminder config shows the channel, custom messages, next bump time and every toggle at a glance; ,bumpreminder reset wipes the configuration.
Server Configuration
Create shortcuts to invoke other commands.
Command aliases let you create custom commands that run other commands — shorter or more memorable names for your server. The target command’s own permissions still apply when the alias runs. Managing aliases requires the Manage Server permission.
,alias add creates an alias.
Now ,deport @user reason runs exactly like ,ban @user reason — the user’s input is appended after the alias target.
You can bake arguments into an alias. To use the user’s input in a specific position, use {0} placeholders — the first argument is {0}, the second {1}, and so on (it does not start at {1}).
,shh @jonathan now runs the timeout command with @jonathan from the user’s input as the first argument and the predefined 10m as the second.
A popular use: a shortcut that hands out an image-permission role via the role command.
,pic @jonathan toggles the predefined image role on the mentioned member.
Miscellaneous
Relay messages through a webhook with a custom username and avatar.
A webhook is a way to post a message with a custom username and avatar to a channel.
All webhook commands require the Manage Webhooks permission (for you and for the bot).
,webhook create creates a webhook in the current channel.
To change the webhook’s username or avatar, open the Webhooks tab in the channel’s Integrations settings in Discord.
After creating a webhook, ,webhook send posts through it. Forgot the identifier? ,webhook list shows every webhook of the server.
,webhook edit edits a message the webhook sent — pass a message link (or run it in the message’s channel with the message id).
Server Configuration
Assign, create and automate roles — from one-off grants to sticky, temporary and booster roles.
,role is a dispatcher with powerful bulk subcommands — each its own card and toggle on the dashboard:
Reaction Roles and Button Roles let members pick their own roles. Build the message in the dashboard, attach roles to reactions or buttons, choose single-pick or multi-pick — done.
Give every new member (and/or every new bot) a set of roles the moment they join — configured under Greetings → Auto Roles in the dashboard.
Server Configuration
XP for activity, a MEE6-style rank card, level rewards and a public web leaderboard.
Members earn XP by chatting. XP gain has an anti-spam cooldown, an optional server-wide XP boost multiplier, and no-XP lists for roles and channels (mute XP farming in bot channels). All of it is configured under Levels in the dashboard.
Shows rank, level and XP progress on a clean MEE6-style card — avatar, progress bar, rank and level. Aliases: ,level, ,lvl, ,xp. With Advanced Leveling enabled, the interactive level menu opens instead. A custom card background can be set per server.
,levels links your server’s public web leaderboard — searchable, paginated, podium ranks in gold/silver/bronze for the top 3, and per-member progress bars. Share the link anywhere; no login needed.
Grant roles automatically at level milestones — level 5 gets Active, level 20 gets Veteran, and so on. Role stacking can be on (keep all reward roles) or off (only the highest). Configured under Level Rewards in the dashboard.
Server Configuration
Sticky messages, scheduled auto messages, auto responders and snipes.
Pin a message to the bottom of a channel — babes reposts it after new messages so it always stays last. Perfect for rules reminders in busy channels, active giveaways or event notices. Configure per channel in the dashboard, with embed support.
Send messages on a schedule — every N hours or at fixed times — to any channel. Announcements, bump reminders, recurring event pings. Each auto message has its own schedule, channel and content.
Triggers can match exact words or phrases; replies support variables and embeds. Great for FAQ answers ("how do I verify?") that fire instantly.
Server Configuration
Join-to-create voice channels with a full button control interface.
Members join the creator channel and instantly get their own temporary voice channel — named after them, owned by them. When the last person leaves, the channel cleans itself up. No clutter, no dead channels.
The interface is a button panel members use to control their channel — no commands needed:
Enable VoiceMaster in the dashboard: pick the category, the creator channel and the channel where the interface panel is posted. Per-panel visibility rules let you hide custom channels from specific roles.
Server Configuration
Greet new members and say goodbye — with full embed and variable support.
Configure both in the dashboard under Greetings: pick the channel, write the message, optionally build a rich embed with the visual embed creator. Variables are replaced live:
Optionally send new members a private welcome DM — rules, onboarding links, a personal hello. Same variables, same embed support.
Give every new member (or every new bot, separately) a set of roles on join. Combined with sticky roles, returning members keep their roles too.
Server Configuration
Button-entry giveaways with automatic winner draws.
Create giveaways in the dashboard under Giveaways: prize, duration, number of winners, the channel, and optional role requirements (e.g. boosters only, level-10+ only). The giveaway posts as an embed with an entry button.
Server Configuration
Everything that happens in your server, written down — punishments, messages, members, voice.
Every punishment — ban, softban, hardban, kick, mute, warn, timeout — is posted to your mod log with a case number, the moderator, the target and the reason. Cases link back to the member’s full history.
Each log type can go to its own channel:
The antinuke and anti raid write their incidents to their own log — who triggered which module, what the punishment was, and what got reverted.
Miscellaneous
High-quality playback with player buttons and 24/7 mode.
The now-playing message has buttons for pause/resume, skip, loop and volume — most listeners never need a command. The player follows the queue and updates itself.
Keeps babes in a voice channel around the clock, replaying your configured track or playlist — lofi radios, community soundtracks, event music. Aliases: ,24-7, ,nonstop.
Miscellaneous
Server currency, a role shop and casino games.
Sell roles and perks for coins. Items are managed in the dashboard; the shop post in your server updates itself whenever items change (,refreshshop forces it).
Miscellaneous
Live market data and multi-chain transaction tools — no setup, no API keys.
Live price, market cap, daily change and daily high/low via CoinGecko — any coin CoinGecko knows, in over 20 fiat currencies. Aliases: ,coin, ,price.
Paste any transaction hash — the network is detected automatically and the result links the right block explorer (Etherscan, Blockstream, Solscan, …). Shown: confirmations, total value with USD, fee, sender, receiver and timestamp. Alias: ,tx.
Supported networks: Ethereum, BNB Chain, Polygon, Arbitrum, Optimism, Base, Avalanche, Fantom, Bitcoin, Litecoin, Dogecoin, Bitcoin Cash, Dash, Zcash, Groestlcoin, Solana and XRP.
Wallet lookup with auto-detected network — shows the balance in coin and USD plus the 30-day volume: how much was received and sent, and how many transactions. Works with EVM addresses (0x…), Bitcoin & co. (legacy, bc1…, ltc1…, D…, X…, t1…), Solana pubkeys and XRP. Aliases: ,addr, ,wallet.
babes watches the transaction — on any supported chain — and pings you in the channel at its first confirmation. Checks run every 45 seconds for up to 12 hours; up to 3 watches per user.
Current Ethereum gas — Slow / Normal / Fast in gwei, each with the estimated USD cost of a plain transfer. Sourced live from the network’s fee history.
Miscellaneous
Built-in StatsBot — who is active, where and when.
Your personal stats card — server rank, message count, voice time and your top channels, rendered as a clean image. Alias: ,stats. Use ,u @user for someone else’s card.
Stats commands can run under their own prefix, separate from the main bot — so ,me never collides with another bot’s commands. Configure it under Statistics in the dashboard.