Skip to main content

Search GiselleBot's commands and docs.

Try /ban, or start with / for commands only.

Press Ctrl K anywhere in the dashboard to open this.

Utility Commands

This module contains generally useful, atomic commands that aren't otherwise categorized into a dedicated module.

These commands are either open to anyone or locked behind in-Discord permissions.

NSFW Images Detection Tools

GiselleBot includes an experimental **NSFW images detection system** as part of its moderation tooling, built on **TensorFlow.js**.

The detection system is based on Infinite Red's NSFW JS library and GantMan's Inception v3 Keras Model for NSFW detection, and classifies an image into one of 5 categories:

  • Drawings: Safe for work drawings (including anime).
  • Hentai: Hentai and pornographic drawings.
  • Neutral: Safe for work neutral images.
  • Porn: Pornographic images, sexual acts.
  • Sexy: Sexually explicit images, not pornography.

It runs as a back-end module and caches results to keep it fast.

See also

This article by Infinite Red explains why the original NSFW JS client-side module was created.

Warning

This module will not reliably recognize every NSFW image. Its purpose is to classify images quickly and help moderators review a server.

The module does not store or expose sexually explicit images. Output contains no direct link to the original image: a censored (low resolution, blurred) copy is cached locally and used to refer to the original.

Command output looks like the example below, followed by the corresponding censored image:

NSFW detection output example

NSFW Images Detection Censored Image Example

See also

If you have a background in image processing: Lenna is flagged as NSFW with a confidence score of 81.9%.

If you don't know what that refers to, see this Wikipedia page.

Note

The NSFW threshold is configured from your server's AutoModerator page on the dashboard.

/serverinfo

Command Syntax

/serverinfo

Command Description

Prints information about the current server.

Permissions Needed

  • User: None.

Examples

/serverinfo

Note

The expires_after option below takes the standard time code (e.g. 1d3h2m) - or a Discord timestamp mention referring to a future time - described in Time Format Code.

Invite-to-role mapping (dashboard)

Note

Configured on the dashboard's Invites page. Requires premium invite tracking.

An invite can be paired with one or more roles: members who join through that invite receive them after completing verification, not on join. The mapping applies to every verification path (captcha, /verify, and a moderator verifying someone by hand) and is independent of the verification module's remove_roles option.

Without premium invite tracking there is no per-member record of which invite was used, so the dashboard disables the picker and the API rejects the mapping rather than silently ignoring it.

/invites create

Note

Invites can also be viewed, labelled, created and revoked from the server dashboard's Invites page (Moderation & Administration section). The dashboard page is available to Manage Server holders only.

Command Syntax

/invites create [channel:{channel}] [expires_after:{time code}] [max_uses:{number}] [temporary:{true/false}] [unique:{true/false}] [alias:{text}] [target_users:{users}]

Command Description

Creates an instant invite to the current server. All parameters are optional; here is what each one does, with its default:

  • channel selects a target channel for the invite. The user running the command must have "Manage Server" and "Create Instant Invite" permissions in the target channel. Default: the current channel.
  • expires_after sets how long the invite should last (use the time code syntax, e.g. 1h). Default: no expiration.
  • max_uses sets the maximum number of uses for the invite. Default: unlimited uses.
  • unique creates a unique invite if true, or uses an existing one with similar settings otherwise. Timed invites are always unique by default. Default: false (use an existing if available).
  • temporary sets whether members that joined via the invite should be automatically kicked after 24 hours if they have not yet received a role. Default: false.
  • alias adds an optional label (maximum 32 characters long) to the invite, shown in /invites usage. If the Members logger with invites tracking is active (refer to the Logger section in the Administration module documentation) it is also shown on the join log. Default: no alias.
  • target_users restricts the invite so only those users can accept it. Pass 1 to 25 users, as mentions or raw ids, separated by spaces or commas (@alice @bob or 111111111111111111,222222222222222222). Duplicates are collapsed. The invite reply lists the target count and mentions each targeted user. Invalid entries are rejected before the invite is created. Default: no target users (the invite can be used by anyone with the link).

Permissions Needed

  • User: Manage Server, Create Instant Invite. Discord's command-permissions picker only gates on Manage Server; Create Instant Invite is a separate in-code check (see Layer 3).
  • Bot: Create Instant Invite

Examples

/invites create
/invites create channel:#welcome expires_after:1h max_uses:10 alias:launch-event
/invites create channel:#welcome max_uses:1 target_users:@alice @bob

/invites alias

Command Syntax

/invites alias code:{invite code} [alias:{text}]

Command Description

Sets or clears the alias on an invite that already exists, including invites created outside Giselle (for example directly in Discord). code is the part after discord.gg/ in the invite link.

The alias is a label of up to 32 characters, shown in /invites usage and, when the Members logger with invites tracking is active, on the join log. Aliases do not have to be unique, and they can be changed or removed at any time; leave alias blank to remove it. The same alias can also be managed from the server dashboard's Invites page.

Permissions Needed

  • User: Manage Server. Re-checked in-code as well as by Discord's command-permissions picker (see Layer 3).
  • Bot: Manage Server

Examples

/invites alias code:aBcD1234 alias:launch-event
/invites alias code:aBcD1234 alias:spring-campaign
/invites alias code:aBcD1234

/invites prune

Command Syntax

/invites prune [max_uses:{# of uses (inclusive) to consider invites "unused"}] [user:{user}] [channel:{channel}]

Command Description

Deletes unused invites (invites with 0 uses), or invites under a certain number of uses (inclusive). Set the number of uses that counts as "unused" with max_uses (default: 0).

You can filter by invite creator through the user option, or by invite target channel through the channel option.

Each run prunes up to 100 invites; run the command again to prune more. With a high number of invites, the command can be slow and look unresponsive for a while.

Permissions Needed

  • User: Manage Server. Re-checked in-code as well as by Discord's command-permissions picker (see Layer 3).
  • Bot: Manage Server

Examples

/invites prune user:@cycloptux
/invites prune channel:#greeter max_uses:5

/invites usage

Command Syntax

/invites usage [user:{user}] [channel:{channel}]

Command Description

Shows usage stats about active invites in the current server.

You can filter by invite creator through the user option, or by invite target channel through the channel option.

Permissions Needed

  • User: Manage Server. Re-checked in-code as well as by Discord's command-permissions picker (see Layer 3).
  • Bot: Manage Server

Examples

/invites usage
/invites usage channel:#welcome

Note

Auto-publish setup and auto-react setup are configured from your server's Settings page on the dashboard.

/rawmessage

Command Syntax

/rawmessage message:{message id or link} [channel:{channel}]

Command Description

Shows the raw content of a message, so markdown-formatted messages or embeds are easy to copy and paste.

Embeds can be re-sent through GiselleBot using /send embed. Complex embeds may not work.

Note

You can also right-click (or long-press) a message and choose Apps -> Raw message to run this against that message directly, without typing a message ID or channel.

Note

If channel targets a channel other than the one you ran the command in, the reply is always ephemeral (visible only to you), so the raw content isn't posted publicly into a channel that may not have access to the target channel.

Permissions Needed

  • User: None.

Examples

/rawmessage message:123456789098765432
/rawmessage message:123456789098765432 channel:#rules
/rawmessage message:https://discord.com/channels/533372744130363392/534171951732752394/534751296847216642

/savechat

Command Syntax

/savechat [count:{# of messages}] [channel:{channel}]

Command Description

Dumps a certain number of messages from the given channel (defaults to the current channel) into a .csv file.

The file is sent to the author of the command via Direct Message. Instead of receiving the actual file as a Discord attachment, the author receives:

  • A URL to an encrypted .zip file containing the actual .csv.
  • The password to decrypt the archive.

Note

The archive password is known only to the author of the command, not even to the bot developer. The archive is available for 30 days, after which it is deleted.

If count is not specified, the default value of 150 messages is used. The maximum number of messages you can save is 2000.

Warning

Dumping a high number of messages can be very slow, or even fail.

Permissions Needed

  • User: Manage Messages. Re-checked in-code as well as by Discord's command-permissions picker (see Layer 3).

Examples

/savechat count:500

Note

Use Discord's native pin button (right-click a message -> Pin Message) to pin or unpin messages.

/emojify

Command Syntax

/emojify text:{word(s) to convert, or one emoji name} [verbose:{true/false}]

Command Description

Converts a sequence of words into a sequence of emojis, provided the bot has access to the emojis.

Emoji names are case-sensitive.

By default, this command only tries to fetch emojis from the current server.

By setting one or more servers as emojify source servers (see below), GiselleBot looks for emojis in those servers as well as the current server when /emojify runs.

Setting verbose to true looks up that one emoji name instead of converting text, and shows which server it was fetched from.

Permissions Needed

  • User: None.

Examples

/emojify text:BlobOwO BlobPats
/emojify text:BlobOwO verbose:true

Note

Setting one or more servers as emojify source servers, and excluding the current server's own emojis from being used elsewhere, are configured from your server's Settings page on the dashboard.

Note

Building an embed with JSON is done with /send embed, documented under the Send module. Only JSON is accepted; there is no tag-based shorthand.

Delete DM Message (context menu)

How to use it

Right-click one of the bot's messages in your DM with it -> Apps -> Delete DM Message.

Description

Note

This only works on messages the bot itself sent you, in your DM with it. No permissions apply.

Deletes that direct message. This is useful as a privacy/security measure for deleting previously sent passwords to encrypted archives, so they become completely unrecoverable.

Note

Non-sensitive direct messages (e.g. moderation actions) might still be logged into the owner-restricted bot console.

Note

/role get and /role drop (the other two /role subcommands) are documented under Self-Assignable Roles instead, alongside the rest of that sub-module.

/role members

Command Syntax

/role members role:{role} [format:{mention/id}]

Command Description

Prints the list of users that currently have the specified role. Users are printed by username by default; use the format option to print user IDs or mentions instead.

The list is always sorted in alphabetical order based on the users' usernames.

Permissions Needed

  • User: None.

Examples

/role members role:@Discord Moderator
/role members role:@Verified format:id

/role add

Command Syntax

/role add role:{role} [user1:{user}] [user2:{user}] [user3:{user}] [user4:{user}] [user5:{user}] [users:{user ids}] [everyone:{true/false}]

Command Description

Adds a role to up to 5 individual users, any number of users via the users option, or to everyone in the server (set everyone:true instead of picking users - this asks for confirmation before running, since it affects the whole server).

Note

user1-user5 pick up to 5 users individually. For more than 5, use users instead: a space-separated list of user IDs or @mentions (any number, e.g. users:123456789012345678 987654321098765432). Both can be combined in the same run - overlapping users are only affected once. Use everyone:true for the whole server.

A run that touches 25 or more members (an everyone:true run, or a users list that large) posts a public progress message in the channel. It keeps a running count and estimates how much time is left, and carries a Cancel button only you can use (anyone else who clicks it is told it is not theirs). The final report is posted on that same public message, so a long run stays visible rather than sitting on a private reply that stops updating after a few minutes. Smaller runs report on the private reply.

Discord only allows a server roughly one role change per second, so a large run takes a while (a few thousand members means hours), and nothing on this side can speed it up. A large run's report gives the totals and then names only the members that failed, rather than listing every success.

Permissions Needed

  • User: Manage Roles. Discord's command-permissions picker for /role itself is open to everyone; Manage Roles is enforced in-code for this subcommand (see Layer 3).
  • Bot: Manage Roles

Examples

/role add role:@Discord Moderator user1:@cycloptux user2:@NaviKing
/role add role:@Verified users:123456789012345678 987654321098765432 111111111111111111
/role add role:@Verified everyone:true

/role remove

Command Syntax

/role remove role:{role} [user1:{user}] [user2:{user}] [user3:{user}] [user4:{user}] [user5:{user}] [users:{user ids}] [everyone:{true/false}]

Command Description

Removes a role from up to 5 individual users, any number of users via the users option, or from everyone in the server (set everyone:true instead of picking users - this asks for confirmation before running, since it affects the whole server).

Note

user1-user5 pick up to 5 users individually. For more than 5, use users instead: a space-separated list of user IDs or @mentions (any number, e.g. users:123456789012345678 987654321098765432). Both can be combined in the same run - overlapping users are only affected once. Use everyone:true for the whole server.

A run that touches 25 or more members (an everyone:true run, or a users list that large) posts a public progress message in the channel. It keeps a running count and estimates how much time is left, and carries a Cancel button only you can use (anyone else who clicks it is told it is not theirs). The final report is posted on that same public message, so a long run stays visible rather than sitting on a private reply that stops updating after a few minutes. Smaller runs report on the private reply.

Discord only allows a server roughly one role change per second, so a large run takes a while (a few thousand members means hours), and nothing on this side can speed it up. A large run's report gives the totals and then names only the members that failed, rather than listing every success.

Permissions Needed

  • User: Manage Roles. Discord's command-permissions picker for /role itself is open to everyone; Manage Roles is enforced in-code for this subcommand (see Layer 3).
  • Bot: Manage Roles

Examples

/role remove role:@Discord Moderator user1:@cycloptux user2:@NaviKing
/role remove role:@Verified users:123456789012345678 987654321098765432 111111111111111111
/role remove role:@Verified everyone:true

Role Menus

/rolemenu posts a set of buttons in a channel that let members assign or remove one of your server's self-assignable roles by clicking.

Note

Role menus are buttons, not reactions - members click a button instead of adding a reaction emoji to pick a role. The role group data itself (which roles belong to a menu) lives on your server's Self-Assignable Roles page on the dashboard; see the Self-Assignable Roles guide for how to set up a role group before posting a menu for it.

/rolemenu create

Command Syntax

/rolemenu create group:{role group} [channel:{channel}]

Command Description

Posts a new self-assignable role menu for the given role group. Defaults to the current channel if channel is omitted.

Permissions Needed

  • User: Manage Roles

Examples

/rolemenu create group:Colors
/rolemenu create group:Colors channel:#roles

/rolemenu remove

Command Syntax

/rolemenu remove [message_id:{message id}] [channel:{channel}]

Command Description

Deactivates a role menu - its buttons stop working, but the message itself is not deleted. Defaults to the most recent role menu message in the given channel (or the current channel) if message_id is omitted.

Permissions Needed

  • User: Manage Roles

Examples

/rolemenu remove
/rolemenu remove message_id:123456789098765432

/rolemenu update

Command Syntax

/rolemenu update [message_id:{message id}] [channel:{channel}]

Command Description

Refreshes a role menu's buttons to match its role group's current roles (useful after adding/removing roles from the group). Defaults to the most recent role menu message in the given channel (or the current channel) if message_id is omitted.

Permissions Needed

  • User: Manage Roles

Examples

/rolemenu update
/rolemenu update message_id:123456789098765432

Other Tools

URL Shortener (dashboard)

Note

Shortening a URL is done from your server's Tools page on the dashboard, not from a Discord command - see Tools for details.

/snowflake

Command Syntax

/snowflake id:{Discord snowflake}

Command Description

Extracts the time from a valid Discord snowflake, showing it in multiple relative and absolute formats.

Permissions Needed

  • User: None.

Examples

/snowflake id:123456789098765432

Note

Clock and member-count channels are created, edited, and deleted entirely from the dashboard. See Tools.

See also

Full migration mapping for these commands: Migration Guide.