Server Administration

The Administration module contains tools used to manage a Discord server and its members.

See also

NaviKing#3820 wrote a very good guide about a few real use cases of using the administration module. You can find it here: Step 1: Configuring the Administration Module


Bot Prefix

!prefix

Command Syntax

!prefix [new prefix]

Command Description

Sets the bot prefix for all bot commands within the current server.

Using the command without any argument will show the current prefix.

Warning

The prefix cannot contain spaces. If spaces are used, only the first “word” will be considered.

Note

Generally speaking, there will never be a space in between the prefix and the command itself. A common prefix being used is a mention of the bot. If the bot mention is used, a space will be automatically added after the mention. This only applies if the bot mention is used, while any other mention will be considered as a normal character string.

Note

If you happen to forget the prefix for GiselleBot, try using “@GiselleBot hprefix”. This reaction will only work if the Custom Reactions module is enabled.

Permissions Needed

User: Manage Server

Examples

!prefix
!prefix b?

Server Activity Logging

!log

Command Syntax

!log [type(s)]

Command Description

Toggles one or more logger types in the current channel. Available loggers are:

  • Members: User joined/left the server.

  • Users: Username change, nickname change, avatar change.

  • Roles: Role added to user, role removed from user, role created, role edited, role deleted.

  • Channels: Channel created, channel edited*, channel deleted.

  • Server: Server info updated*, emoji created, emoji deleted, emoji updated.

  • Messages: Message deleted, message edited, message pinned, message unpinned.

  • Voice: User connected to/disconnected from/switched voice channel.

  • Moderation: Auto-moderation actions, administrators/moderators using a sensitive command, user struck by a moderation action (warn/kick/ban/mute/…), user evaded from a moderation action**.

  • Warning: This one is a more verbose version the moderation log, focused on moderation actions. Activating this logger enables the case/scoring system.

  • ALL: Activates all available loggers in the current channel.

You can also print the list of available loggers within Discord by using !log without any additional argument.

Premium

The Members, Messages, Roles, Channels, Moderation and Warning loggers are publicly available. If you want to enable Users, Server and Voice loggers, you can unlock them as a Premium feature (see: Premium Perks).

*: Due to the high amount of info that can be edited, these commands are limited to monitoring the main parameters.
**: Evasion is intended as leaving and re-joining a server while a permanent or time-based mute/ban action is taken on the user, in an attempt to clear the moderation roles. The roles will be reapplied and the administrators/moderators will be notified.

Examples

!log members
!log voice messages
!log ALL

!logstatus

Command Syntax

!logstatus

Command Description

Prints a summary of the enabled loggers, showing which logger(s) are enabled in which channel(s).


!logignore

Command Syntax

!logignore (logger type) [entity id/mention/q_name]

Command Description

Premium

This feature is only available to Premium-enabled servers (see: Premium Perks).

Add a filter to skip logging certain events. Any action that comes from a user/channel/role that is added to the filter won’t generate a logging entry. Please refer to the list below for a list of supported filters:

  • Members: Users.

  • Users: Users.

  • Roles: Roles.

  • Channels: Channels.

  • Server: N/A.

  • Messages: Users, Channels.

  • Voice: Users, Channels.

  • Moderation: Users.

  • Warning: Users.

You can also print the list of currently set filters by using !logignore (logger type) without any additional argument.

Examples

!logignore members @cycloptux#1543
!logignore channels #admin-chat

!logmatt

Command Syntax

!logmatt

Command Description

Opens an interactive menu to configure the message attachments logging feature on deleted messages.

By default, deleting a message that contains an image as attachment will trigger an automatic reupload of said image into the Messages logging channel.

Within the configuration menu, users will be able to enable or disable this feature, and to limit the feature to certain channels (whitelist mode) or exclude certain channels from this extra logging feature (blacklist mode).


Greet Messages

The Greet Messages submodule lets server managers configure automatic and configurable messages that GiselleBot sill send when a user joins/leaves your server, or obtains a specific role.

All use cases (minus the “goodbye” messages) can be configured to send greet messages to a channel or to the user through a Direct Message.

!greet

Command Description

Toggles announcements on the current channel when someone joins the server.

Permissions Needed

User: Manage Server

!greetdm

Command Description

Toggles announcements via Direct Message when someone joins the server (this is separate from greet - you can have both, any, or neither enabled).

Permissions Needed

User: Manage Server

!greetmsg

Command Syntax

!greetmsg [message content]

Command Description

Sets a new join announcement message which will be shown in the server’s channel. Using it with no message will show the current greet message.

You can use one (or more) of these placeholders in your message:

  • %user%: This will be replaced with a mention of the user.

  • %username%: This will be replaced with the username of the user, without the discriminator (e.g. cycloptux).

  • %discriminator%: This will be replaced with the discriminator of the user, without the # character (e.g. 1543).

  • %fullusername%: This will be replaced with the username of the user, including the discriminator (e.g. cycloptux#1543).

  • %user_avatar_url%: This will be replaced with the current user avatar URL (in WebP or GIF format).

  • %bot%: This will be replaced with a mention of the bot.

  • %botname%: This will be replaced with the username of the bot, without the discriminator.

  • %botdiscriminator%: This will be replaced with the discriminator of the bot, without the # character.

  • %fullbotname%: This will be replaced with the username of the bot, including the discriminator.

  • %bot_avatar_url%: This will be replaced with the current bot avatar URL (in WebP or GIF format).

  • %server%: This will be replaced with the server name.

  • %now%: This will be replaced with the current time, with format YYYY-MM-DD HH:mm:ss (UTC).

  • %server_time%: This will be replaced with the current time, with format HH:mm UTC.

  • %server_icon_url%: This will be replaced with the current server icon URL (in WebP or GIF format).

  • %server_banner_url%: This will be replaced with the current server icon URL (in WebP format).

  • %server_splash_url%: This will be replaced with the current server icon URL (in WebP format).

  • %boost_level%: This will be replaced with the current Nitro Server Boost level for the server.

  • %boost_number%: This will be replaced with the current number of Nitro Server Boosts that the server received.

You can use embed json from https://eb.nadeko.bot/ instead of a regular text, if you want the message to be embedded.

Permissions Needed

User: Manage Server

Examples

!greetmsg Welcome, %user%.

!greetdmmsg

Command Syntax

!greetdmmsg [message content]

Command Description

Sets a new join announcement message which will be sent to the user who joined. Using it with no message will show the current DM greet message.

You can use one (or more) of these placeholders in your message:

  • %user%: This will be replaced with a mention of the user.

  • %username%: This will be replaced with the username of the user, without the discriminator (e.g. cycloptux).

  • %discriminator%: This will be replaced with the discriminator of the user, without the # character (e.g. 1543).

  • %fullusername%: This will be replaced with the username of the user, including the discriminator (e.g. cycloptux#1543).

  • %user_avatar_url%: This will be replaced with the current user avatar URL (in WebP or GIF format).

  • %bot%: This will be replaced with a mention of the bot.

  • %botname%: This will be replaced with the username of the bot, without the discriminator.

  • %botdiscriminator%: This will be replaced with the discriminator of the bot, without the # character.

  • %fullbotname%: This will be replaced with the username of the bot, including the discriminator.

  • %bot_avatar_url%: This will be replaced with the current bot avatar URL (in WebP or GIF format).

  • %server%: This will be replaced with the server name.

  • %now%: This will be replaced with the current time, with format YYYY-MM-DD HH:mm:ss (UTC).

  • %server_time%: This will be replaced with the current time, with format HH:mm UTC.

  • %server_icon_url%: This will be replaced with the current server icon URL (in WebP or GIF format).

  • %server_banner_url%: This will be replaced with the current server icon URL (in WebP format).

  • %server_splash_url%: This will be replaced with the current server icon URL (in WebP format).

  • %boost_level%: This will be replaced with the current Nitro Server Boost level for the server.

  • %boost_number%: This will be replaced with the current number of Nitro Server Boosts that the server received.

You can use embed json from https://eb.nadeko.bot/ instead of a regular text, if you want the message to be embedded.

Permissions Needed

User: Manage Server

Examples

!greetdmmsg Welcome to %server%, %user%.

!greetdel

Command Syntax

!greetdel (seconds)

Command Description

Sets the time it takes (in seconds) for in-server greet messages to be auto-deleted. Set it to 0 to disable automatic deletion. The maximum time you can set is 300 (5 minutes).

Note

This setting does not apply to DM greet messages.

Permissions Needed

User: Manage Server

Examples

!greetdel 0
!greetdel 30

!goodbye

Command Description

Toggles announcements on the current channel when someone leaves the server.

Note

Due to Discord’s caching system, some or all of the information needed to correctly fill the goodbye message might be missing at the time of leaving of a user. GiselleBot will still attempt to create the message with the info that can be fetched from the cache, but the information might be incomplete or incorrect. This is not a bug.

Permissions Needed

User: Manage Server

!goodbyemsg

Command Syntax

!goodbyemsg [message content]

Command Description

Sets a new leave announcement message which will be shown in the server’s channel. Using it with no message will show the current goodbye message.

You can use one (or more) of these placeholders in your message:

  • %user%: This will be replaced with a mention of the user.

  • %username%: This will be replaced with the username of the user, without the discriminator (e.g. cycloptux).

  • %discriminator%: This will be replaced with the discriminator of the user, without the # character (e.g. 1543).

  • %fullusername%: This will be replaced with the username of the user, including the discriminator (e.g. cycloptux#1543).

  • %user_avatar_url%: This will be replaced with the current user avatar URL (in WebP or GIF format).

  • %bot%: This will be replaced with a mention of the bot.

  • %botname%: This will be replaced with the username of the bot, without the discriminator.

  • %botdiscriminator%: This will be replaced with the discriminator of the bot, without the # character.

  • %fullbotname%: This will be replaced with the username of the bot, including the discriminator.

  • %bot_avatar_url%: This will be replaced with the current bot avatar URL (in WebP or GIF format).

  • %server%: This will be replaced with the server name.

  • %now%: This will be replaced with the current time, with format YYYY-MM-DD HH:mm:ss (UTC).

  • %server_time%: This will be replaced with the current time, with format HH:mm UTC.

  • %server_icon_url%: This will be replaced with the current server icon URL (in WebP or GIF format).

  • %server_banner_url%: This will be replaced with the current server icon URL (in WebP format).

  • %server_splash_url%: This will be replaced with the current server icon URL (in WebP format).

  • %boost_level%: This will be replaced with the current Nitro Server Boost level for the server.

  • %boost_number%: This will be replaced with the current number of Nitro Server Boosts that the server received.

You can use embed json from https://eb.nadeko.bot/ instead of a regular text, if you want the message to be embedded.

Permissions Needed

User: Manage Server

Examples

!goodbyemsg See you soon, %fullusername%!

!goodbyedel

Command Syntax

!goodbyedel (seconds)

Command Description

Sets the time it takes (in seconds) for in-server goodbye messages to be auto-deleted. Set it to 0 to disable automatic deletion. The maximum time you can set is 300 (5 minutes).

Permissions Needed

User: Manage Server

Examples

!goodbyedel 0
!goodbyedel 30

!greetrole

Command Syntax

!greetrole (role id/mention/q_name)

Command Description

Toggles announcements on the current channel when someone obtains a certain role.

Permissions Needed

User: Manage Server

Examples

!greetrole @Beta Tester
!greetrole 123456789098765432
!greetrole "Top Secret Pass"

!greetroledm

Command Syntax

!greetroledm (role id/mention/q_name)

Command Description

Toggles announcements via Direct Message when someone obtains a certain role (this is separate from greetrole - you can have both, any, or neither enabled).

Permissions Needed

User: Manage Server

Examples

!greetroledm @Beta Tester
!greetroledm 123456789098765432
!greetroledm "Top Secret Pass"

!greetrolemsg

Command Syntax

!greetrolemsg (role id/mention/q_name) [message content]

Command Description

Sets a new role greeting message which will be shown in the server’s channel. Using it with no message will show the current greet message.

You can use one (or more) of these placeholders in your message:

  • %role%: This will be replaced with the name (in plain text) of the obtained role.

  • %role_mention%: This will be replaced with the mention of the obtained role.

  • %user%: This will be replaced with a mention of the user.

  • %username%: This will be replaced with the username of the user, without the discriminator (e.g. cycloptux).

  • %discriminator%: This will be replaced with the discriminator of the user, without the # character (e.g. 1543).

  • %fullusername%: This will be replaced with the username of the user, including the discriminator (e.g. cycloptux#1543).

  • %user_avatar_url%: This will be replaced with the current user avatar URL (in WebP or GIF format).

  • %bot%: This will be replaced with a mention of the bot.

  • %botname%: This will be replaced with the username of the bot, without the discriminator.

  • %botdiscriminator%: This will be replaced with the discriminator of the bot, without the # character.

  • %fullbotname%: This will be replaced with the username of the bot, including the discriminator.

  • %bot_avatar_url%: This will be replaced with the current bot avatar URL (in WebP or GIF format).

  • %server%: This will be replaced with the server name.

  • %now%: This will be replaced with the current time, with format YYYY-MM-DD HH:mm:ss (UTC).

  • %server_time%: This will be replaced with the current time, with format HH:mm UTC.

  • %server_icon_url%: This will be replaced with the current server icon URL (in WebP or GIF format).

  • %server_banner_url%: This will be replaced with the current server icon URL (in WebP format).

  • %server_splash_url%: This will be replaced with the current server icon URL (in WebP format).

  • %boost_level%: This will be replaced with the current Nitro Server Boost level for the server.

  • %boost_number%: This will be replaced with the current number of Nitro Server Boosts that the server received.

You can use embed json from https://eb.nadeko.bot/ instead of a regular text, if you want the message to be embedded.

Permissions Needed

User: Manage Server

Examples

!greetrolemsg Congratulations for obtaining the %role% role, %user%! With great power comes great responsibility...

!greetroledmmsg

Command Syntax

!greetroledmmsg (role id/mention/q_name) [message content]

Command Description

Sets a new role greeting message which will be sent to the user who obtained the role. Using it with no message will show the current DM greet message.

You can use one (or more) of these placeholders in your message:

  • %role%: This will be replaced with the name (in plain text) of the obtained role.

  • %role_mention%: This will be replaced with the mention of the obtained role.

  • %user%: This will be replaced with a mention of the user.

  • %username%: This will be replaced with the username of the user, without the discriminator (e.g. cycloptux).

  • %discriminator%: This will be replaced with the discriminator of the user, without the # character (e.g. 1543).

  • %fullusername%: This will be replaced with the username of the user, including the discriminator (e.g. cycloptux#1543).

  • %user_avatar_url%: This will be replaced with the current user avatar URL (in WebP or GIF format).

  • %bot%: This will be replaced with a mention of the bot.

  • %botname%: This will be replaced with the username of the bot, without the discriminator.

  • %botdiscriminator%: This will be replaced with the discriminator of the bot, without the # character.

  • %fullbotname%: This will be replaced with the username of the bot, including the discriminator.

  • %bot_avatar_url%: This will be replaced with the current bot avatar URL (in WebP or GIF format).

  • %server%: This will be replaced with the server name.

  • %now%: This will be replaced with the current time, with format YYYY-MM-DD HH:mm:ss (UTC).

  • %server_time%: This will be replaced with the current time, with format HH:mm UTC.

  • %server_icon_url%: This will be replaced with the current server icon URL (in WebP or GIF format).

  • %server_banner_url%: This will be replaced with the current server icon URL (in WebP format).

  • %server_splash_url%: This will be replaced with the current server icon URL (in WebP format).

  • %boost_level%: This will be replaced with the current Nitro Server Boost level for the server.

  • %boost_number%: This will be replaced with the current number of Nitro Server Boosts that the server received.

You can use embed json from https://eb.nadeko.bot/ instead of a regular text, if you want the message to be embedded.

Permissions Needed

User: Manage Server

Examples

!greetroledmmsg Congratulations for obtaining the %role% role in %server%, %user%! With great power comes great responsibility...

!greetroledel

Command Syntax

!greetroledel (role id/mention/q_name) (seconds)

Command Description

Sets the time it takes (in seconds) for in-server role greet messages to be auto-deleted. Set it to 0 to disable automatic deletion. The maximum time you can set is 300 (5 minutes).

Note

This setting does not apply to DM greet messages.

Permissions Needed

User: Manage Server

Examples

!greetroledel @Beta Tester 0
!greetroledel "Top Secret Pass" 30

Automated Roles Assignment/Removal

!autoassignrole

Command Syntax

!autoassignrole [role id(s)/mention(s)/q_name(s)]

Command Description

Automaticaly assigns one or more specified roles to every user who joins the server.

Providing one or more role identifiers will toggle whether or not users will receive that role upon joining the server, for each role.

Note

In other words, after activating a role, use the same command on that role to disable the auto assignment on join.

Provide no parameters to show the current settings.

Permissions Needed

User: Manage Roles
Bot: Manage Roles

Examples

!aar
!aar RoleName1 RoleName2

!autoremoverole

Command Syntax

!arr [time code] [role id(s)/mention(s)/q_name(s)]

Command Description

Automaticaly removes one or more specified roles from any user after the specified amount of time, no matter how that role was gained.

Providing one or more role identifiers and a time code will set the expiration time of those roles.

Providing one or more role identifiers without a time code will disable the expiration of those roles.

Provide no parameters to show the current settings.

Permissions Needed

User: Manage Roles
Bot: Manage Roles

Examples

!arr
!arr 1h RoleName1 RoleName2
!arr RoleName2

!vcrole

Command Syntax

!vcrole [role id/mention/q_name]

Command Description

Automaticaly assigns a role to users who join the voice channel you’re in when you run this command. Provide no role identifier to disable.

Provide no parameters to disable this feature.

Warning

You must be in a voice channel to run this command.

Permissions Needed

User: Manage Roles
Bot: Manage Roles

Examples

!vcrole
!vcrole VoiceRoleName

!vcrolelist

Command Syntax

!vcrolelist

Command Description

Shows a list of currently set voice channel roles.


Self-Assignable Roles

IMPORTANT NOTE: The bot will be able to assign a role only if it has both “Manage Roles” permissions AND if the role it’s trying to assign is lower than the highest role the bot has. Please arrange your roles accordingly.

Before we delve into the actual self-assignable roles, it’s very important that you become familiar with role groups.

A role group is a group of Discord roles that will share the same set of assignment rules.

Each role group can be configured by editing the following settings:

  • Name: Custom name for the group.

  • Mode: Given a group of Discord roles, the assignment mode defines how roles will be assigned to users:

    • Single Mode: Users can only have 1 role within this group.

    • Multiple Mode: Users can have a minimum and a maximum number of roles within this group.

    • None: No specific rules are applied. Required and ignored roles (see below) still apply.

  • Required Roles: This setting requires users to have at least one of the specified roles to be able to self-assign one role within this group.

  • Ignored Roles: This setting requires users not to have any of the specified roles to be able to self-assign one role within this group. Or, in other words, users with at least one of the specified roles won’t have access to this group.

  • Prerequisites Check: Toggles the periodic monitoring of role requirements for self-assigned roles.

    • The configuration of self-assignable roles allows for preventing users with certain roles from receiving roles from a certain group, or to only receive roles from a group if they already have (one or more) different, particular role(s).

    • By default, the monitoring feature is disabled and prerequisite checks only happen upon the assignment (or removal) of the role.

    • Upon activating the periodic monitoring feature, self-assignable roles within the selected group are re-checked automatically so that if a user fails the prerequisite checks (e.g. by either having an ignored role, or losing a required role, or having multiple roles from a group in “Single” mode), they will lose the previously acquired role.

Note

Prerequisites checks only happen every 15-30 minutes.

In Single or Multiple mode, you’ll also have access to additional, optional settings:

Single Mode Settings

  • Require 1 role in group at all times (after initial assignment): Whether the role is assigned by a 3rd party or self-assigned, users won’t be able to self-remove all of the roles in the group.

  • Remove existing role when assigning another role in group: Self-assigning a role within this group will remove any other group role from the user.

Multiple Mode Settings

  • Minimum number of roles: Users won’t be able to self-remove a role if the removal would bring them under this threshold of group roles.

  • Maximum number of roles: Users won’t be able to self-assign a role if the assignment would bring them over this threshold of group roles.

Warning

One role can be assigned to more than one group. While technically possible, this is generally not recommended unless you know what you are doing. In such cases, you must design your settings to avoid conflicts between the different group settings. Conflicting settings will cause unpredictable behaviors.

Once a role group is configured, two ways of self-assigning a group will be available to users:

  • Role Menus: Interactive menus using Discord emoji reactions to assign and remove roles. Role menus can be created from scratch using bot commands (see below) or “attached” to an existing user message.

  • Manual Commands: The !iam and !iamnot commands will always be available to anyone. Specific permissions will need to be handled by using the “Required Roles” and “Ignored Roles” settings.

Here’s the full list of available commands for this sub-module:

!sargs

Command Description

Opens the self-assignable roles (i.e. role groups) interactive setup menu. Use the menu items to configure the above settings.

Note

Mode-specific settings will only work if the corresponding mode is currently set as active.


!asar

Command Syntax

!asar [group id] (role id(s)/mention(s)/q_name(s))

Command Description

Adds one or more roles to the specified group. If the group ID is omitted, group 0 will be used as target role group.

Permissions Needed

User: Manage Roles
Bot: Manage Roles

Examples

!asar "Group 1"
!asar 2 @Testing123
!asar 12 123456789098765432

!rsar

Command Syntax

!rsar [group id] (role id(s)/mention(s)/q_name(s))

Command Description

Removes one or more roles from the specified group. If the group ID is omitted, the role(s) will be removed from all role groups.

Permissions Needed

User: Manage Roles
Bot: Manage Roles

Examples

!rsar "Group 1"
!rsar 2 @Testing123
!rsar 12 123456789098765432

!lsar

Command Description

Prints a list of all role groups and the relative self-assignable groups.

Note

This command is always available to everyone.


!adsarm

Command Description

Toggles the automatic deletion of the “public” self-assignable roles-related messages upon using the !iam and !iamnot commands.

Only successful messages will be deleted.

The user-sent message will be deleted immediately. The confirmation message will be deleted after 5 seconds.

Permissions Needed

User: Manage Messages
Bot: Manage Messages

!iam

Command Syntax

!iam (role id/mention/name)

Command Description

Assings one role among those that are flagged as self-assignable, provided the requirements are met.

Note

This command is always available to everyone.

Examples

!iam Group 1
!iam @Testing123
!iam 123456789098765432

!iamnot

Command Syntax

!iamnot (role id/mention/name)

Command Description

Removes one role among those that are flagged as self-assignable, provided the requirements are met.

Note

This command is always available to everyone.

Examples

!iamnot Group 1
!iamnot @Testing123
!iamnot 123456789098765432

!rmcreate

Command Syntax

!rmcreate [group id] [--m {message id}]

Command Description

Starts an interactive process to build a role menu (i.e. a message whose reactions will assign or remove the roles in the specified role group). The bot will guide you through the process of creating the role menu, follow the in-Discord instructions.

If a valid message ID is specified through the dedicated parameter, the role menu will be created on the target message.

If the group ID is omitted, group 0 will be used as source role group.

Permissions Needed

User: Manage Roles
Bot: Manage Roles

Examples

!rmcreate
!rmcreate 1 --m 123456789098765432

!rmremove

Command Syntax

!rmremove [message id]

Command Description

Removes a role menu from an existing message. The message itself won’t be deleted, nor the existing reactions will be removed, but the bot will now not do anything with reactions on that message.

If the message ID is omitted (or is invalid), the bot will attempt to pick the latest role menu in the current channel.

Permissions Needed

User: Manage Roles
Bot: Manage Roles

Examples

!rmremove 123456789098765432

!rmupdate

Command Syntax

!rmupdate [message id]

Command Description

Updates a role menu with a new reaction if a role was added to the particular role group.

Note

In order to remove a role from a role menu, you’ll need to delete the role menu and create a new one.

If the message ID is omitted (or is invalid), the bot will attempt to pick the latest role menu in the current channel.

Permissions Needed

User: Manage Roles
Bot: Manage Roles

Examples

!rmupdate 123456789098765432

Nitro Server Boost Notifications

With Server Boosts, Discord added a way for you and your community to work together to unlock fresh new and improved collective perks for a server of your choice, each month, and share those epic perks to the rest of the server community.

See also

You can find everything about Server Boosts at this link: https://support.discordapp.com/hc/en-us/articles/360028038352

With GiselleBot, Server Boosts can now be tracked efficiently, and your members can be greeted through a custom message when they gift your server with a Boost!

Note

Due to technical issues (specifically, the lack of a real “event” in case of a Server Boost), GiselleBot will do its best to keep track of the Boosts that are gifted to your server. That said, users gifting more than 1 Boost to your server will not trigger the Boost event, and the removal of a Boost won’t always be able to track down who removed the Boost.

Here’s the full list of available commands for this sub-module:

!nsbaddnotif

Command Syntax

!nsbaddnotif [channel id(s)/mention(s)/q_name(s)]

Command Description

Toggles Nitro Server Boost announcements, on the selected channel(s), when someone Boosts the server.

If used without any (valid) argument, the command will show which channels are currently enabled for these announcements.

Examples

!nsbaddnotif
!nsbaddnotif 123456789098765432 234567890987654321

!nsbaddtemplate

Command Syntax

!nsbaddtemplate [message content]

Command Description

Sets a new Nitro Server Boost announcement message which will be shown in the selected server’s channel(s) when someone Boosts the server. Using it with no message will show the current template.

You can use one (or more) of these placeholders in your message:

  • %user%: This will be replaced with a mention of the user.

  • %username%: This will be replaced with the username of the user, without the discriminator (e.g. cycloptux).

  • %discriminator%: This will be replaced with the discriminator of the user, without the # character (e.g. 1543).

  • %fullusername%: This will be replaced with the username of the user, including the discriminator (e.g. cycloptux#1543).

  • %user_avatar_url%: This will be replaced with the current user avatar URL (in WebP or GIF format).

  • %bot%: This will be replaced with a mention of the bot.

  • %botname%: This will be replaced with the username of the bot, without the discriminator.

  • %botdiscriminator%: This will be replaced with the discriminator of the bot, without the # character.

  • %fullbotname%: This will be replaced with the username of the bot, including the discriminator.

  • %bot_avatar_url%: This will be replaced with the current bot avatar URL (in WebP or GIF format).

  • %server%: This will be replaced with the server name.

  • %now%: This will be replaced with the current time, with format YYYY-MM-DD HH:mm:ss (UTC).

  • %server_time%: This will be replaced with the current time, with format HH:mm UTC.

  • %server_icon_url%: This will be replaced with the current server icon URL (in WebP or GIF format).

  • %server_banner_url%: This will be replaced with the current server icon URL (in WebP format).

  • %server_splash_url%: This will be replaced with the current server icon URL (in WebP format).

  • %boost_level%: This will be replaced with the current Nitro Server Boost level for the server.

  • %boost_number%: This will be replaced with the current number of Nitro Server Boosts that the server received.

You can use embed json from https://eb.nadeko.bot/ instead of a regular text, if you want the message to be embedded.

Examples

!nsbaddtemplate
!nsbaddtemplate %user% just boosted the server! Thanks a bunch!nThe total Boost count for %server% is now %boost_number%.

!nsbremnotif

Command Syntax

!nsbremnotif [channel id(s)/mention(s)/q_name(s)]

Command Description

Toggles Nitro Server Boost announcements, on the selected channel(s), when someone removes a Boost for the server.

If used without any (valid) argument, the command will show which channels are currently enabled for these announcements.

Examples

!nsbremnotif
!nsbremnotif 123456789098765432 234567890987654321

!nsbremtemplate

Command Syntax

!nsbremtemplate [message content]

Command Description

Sets a new Nitro Server Boost announcement message which will be shown in the selected server’s channel(s) when someone removes a Boost for the server. Using it with no message will show the current template.

You can use one (or more) of these placeholders in your message:

  • %user%: This will be replaced with a mention of the user.

  • %username%: This will be replaced with the username of the user, without the discriminator (e.g. cycloptux).

  • %discriminator%: This will be replaced with the discriminator of the user, without the # character (e.g. 1543).

  • %fullusername%: This will be replaced with the username of the user, including the discriminator (e.g. cycloptux#1543).

  • %user_avatar_url%: This will be replaced with the current user avatar URL (in WebP or GIF format).

  • %bot%: This will be replaced with a mention of the bot.

  • %botname%: This will be replaced with the username of the bot, without the discriminator.

  • %botdiscriminator%: This will be replaced with the discriminator of the bot, without the # character.

  • %fullbotname%: This will be replaced with the username of the bot, including the discriminator.

  • %bot_avatar_url%: This will be replaced with the current bot avatar URL (in WebP or GIF format).

  • %server%: This will be replaced with the server name.

  • %now%: This will be replaced with the current time, with format YYYY-MM-DD HH:mm:ss (UTC).

  • %server_time%: This will be replaced with the current time, with format HH:mm UTC.

  • %server_icon_url%: This will be replaced with the current server icon URL (in WebP or GIF format).

  • %server_banner_url%: This will be replaced with the current server icon URL (in WebP format).

  • %server_splash_url%: This will be replaced with the current server icon URL (in WebP format).

  • %boost_level%: This will be replaced with the current Nitro Server Boost level for the server.

  • %boost_number%: This will be replaced with the current number of Nitro Server Boosts that the server received.

You can use embed json from https://eb.nadeko.bot/ instead of a regular text, if you want the message to be embedded.

Examples

!nsbremtemplate
!nsbremtemplate Oh no! %user% has just withdrawn a boost!nThe total Boost count for %server% is now %boost_number%.

!nsbdmnotif

Command Syntax

!nsbdmnotif

Command Description

Toggles Nitro Server Boost “thank you” messages, sent to the users who Boost the server, via Direct Message.


!nsbdmtemplate

Command Syntax

!nsbdmtemplate [message content]

Command Description

Sets a new Nitro Server Boost “thank you” message which will be sent to the user who boost the server. Using it with no message will show the current template.

You can use one (or more) of these placeholders in your message:

  • %user%: This will be replaced with a mention of the user.

  • %username%: This will be replaced with the username of the user, without the discriminator (e.g. cycloptux).

  • %discriminator%: This will be replaced with the discriminator of the user, without the # character (e.g. 1543).

  • %fullusername%: This will be replaced with the username of the user, including the discriminator (e.g. cycloptux#1543).

  • %user_avatar_url%: This will be replaced with the current user avatar URL (in WebP or GIF format).

  • %bot%: This will be replaced with a mention of the bot.

  • %botname%: This will be replaced with the username of the bot, without the discriminator.

  • %botdiscriminator%: This will be replaced with the discriminator of the bot, without the # character.

  • %fullbotname%: This will be replaced with the username of the bot, including the discriminator.

  • %bot_avatar_url%: This will be replaced with the current bot avatar URL (in WebP or GIF format).

  • %server%: This will be replaced with the server name.

  • %now%: This will be replaced with the current time, with format YYYY-MM-DD HH:mm:ss (UTC).

  • %server_time%: This will be replaced with the current time, with format HH:mm UTC.

  • %server_icon_url%: This will be replaced with the current server icon URL (in WebP or GIF format).

  • %server_banner_url%: This will be replaced with the current server icon URL (in WebP format).

  • %server_splash_url%: This will be replaced with the current server icon URL (in WebP format).

  • %boost_level%: This will be replaced with the current Nitro Server Boost level for the server.

  • %boost_number%: This will be replaced with the current number of Nitro Server Boosts that the server received.

You can use embed json from https://eb.nadeko.bot/ instead of a regular text, if you want the message to be embedded.

Examples

!nsbdmtemplate
!nsbdmtemplate Thanks for boosting %server%! Our total Boost count is now %boost_number%.

!nsblist

Command Syntax

!nsblist

Command Description

Lists all members that contributed with at least one Server Boost in the current server.


Emoji Submissions

Through the “Emoji Submissions” sub-module, you can let your members submit new emojis to be used your server.

You can configure one or more roles that will be allowed to submit new emojis. If a user tries to submit an emoji while having more than one role up, only the highest role will be considered in order to avoid unpredictable conflicts.

For each role, you will be able to configure:

  • Whether the role will be allowed to submit emojis without further verification.

    • By setting a verification channel, authorized users (more on that below) will be able to accept or reject an emoji submission before it’s actually uploaded.

    • By disabling the verification channel, the emoji will be immediately uploaded without further verification.

    • By default, the additional verification step is disabled.

  • Which roles will be able to accept or reject an emoji submission, provided you enabled the verification channel.

    • These roles will also be mentioned within the verification channel when a submission is received.

    • Users that are enabled to use the administration module using the Permissions System will always be authorized to accept or reject any emoji submission.

    • By default, no additional roles are enabled to accept or reject emoji submissions.

  • How many emojis (submitted through this system) the role will be allowed to have up at any given time.

    • If the verification step is active, users are virtually allowed to submit any number of emojis. By setting a maximum number of emojis through the dedicated setting, you are locking the maximum number of accepted emojis.

    • By default, there is no limit to how many active emojis a user can have.

  • Whether the periodic monitoring of prerequisites is active for this role.

    • If this option is active, the emojis will be deleted if the user leaves the server and/or if the user loses the role that they “used” to submit the emoji. For example, you can have Nitro Boosters submit one or more emojis, and then have their emoji removed if they stop boosting the server (hence losing the Nitro Boost role).

    • Even if this option is disabled, emojis that are manually deleted will also be removed from this system.

    • By default, this option is disabled.

Note

Prerequisites checks only happen every 15-30 minutes.

Here’s the full list of available commands for this sub-module:

!esubrole

Command Syntax

!esubrole [role id(s)/mention(s)/q_name(s)]

Command Description

Toggles the “emoji submitter” status of the selected role(s).

If used without any (valid) argument, the command will show which roles are currently enabled to submit new emojis.

Note

If you want to add the “everyone” role as a submitter role, you must either use the mention (which will obviously ping everyone) or the server ID.

Permissions Needed

User: Manage Emojis
Bot: Manage Emojis

Examples

!esubrole
!esubrole 123456789098765432 234567890987654321

!esubsetup

Command Syntax

!esubset (role id/mention/q_name)

Command Description

Opens the interactive setup menu for the selected role. Use the menu items to configure the settings shown in Emoji Submissions.

Permissions Needed

User: Manage Emojis
Bot: Manage Emojis

!esublist

Command Syntax

!esublist [user id/mention/name]

Command Description

Lists all active/accepted submitted emojis that users submitted through this system.

If this command is used with a user identifier, it will filter the output on emojis submitted by the specified user.


!esubpending

Command Syntax

!esubpending [user id/mention/name]

Command Description

Lists all pending submitted emojis that users submitted through this system, with a quick link to jump to the verification channel message.

If this command is used with a user identifier, it will filter the output on emojis submitted by the specified user.


!emojisubmit

Command Syntax

!emojisubmit [existing emoji, or image URL] (valid emoji name)

Command Description

Lets users submit a new emoji, provided they have at least one of the “emoji submitter” roles.

Note

This command is always available to everyone. A proper configuration of the emoji submitter roles will avoid an improper use of this command.

Users won’t need “Manage Emojis” permissions to run this command, but GiselleBot will still check for its own “Manage Emojis” permissions to be sure it can (eventually) upload the emoji upon a successful verification, if any.

By default, no role is set as emoji submitter role (before a proper configuration) and this command will not have any effect.

The emoji image can be provided by using an existing emoji (this will only work if the bot has access to the emoji from another server), or a valid image URL, or an image provided in forms of an attachment to the submit message. Emoji images must be under 256 KB in size and one of these formats: .jpg, .jpeg, .png, .gif.

Emoji names must be at least 2 characters long (and no more than 32 characters long) and can only contain alphanumeric characters and underscores. You must not include the colon (:) characters in the emoji name. Users are also not allowed to submit an emoji that has the same name of an existing server emoji.

GiselleBot will attempt to limit the amount of duplicate emoji submissions by checking, wherever possible, the ID of the submitted emoji with the IDs of already active server emojis.

In order to avoid unpredictable conflicts, if a user tries to submit an emoji while having more than one “emoji submitter” role up, only the highest role will be considered for the optional limits/configurations.

Permissions Needed

Bot: Manage Emojis