Follow these tips for supplying parameters for commands that require them:
Command parameters surrounded by <> are required.
Command parameters surrounded by [] are optional.
Command parameters surrounded by "" are literal.
Grouped command parameters separated by / require only one of the parameters in the group.
Due to Discord's limit for the number of slash commands that can be
registered by a single bot, only a portion of
the bot's commands can be ported. For consistency, all commands will remain prefix-based.
There are a few reasons why this may be happening:
The command is disabled, either by the development team or a moderator of your server. The
category that the command is in
may also be disabled.
The bot has run into an error while executing the command. Please file a support ticket if this
happens.
The command does not exist, or the alias that you're using does not exist. If you think that
an alias should be added,
please file a support ticket.
There are a few reasons why this may be happening:
The bot is restarting with a new update/bugfix. It takes time for the bot to connect to
Discord every time it restarts,
so please be patient.
Discord's Gateway/API services may be degraded. To check, first try to use the ping command to check for Discord's
Gateway and message pings. For more information, go to Discord's status page.
You have run into a bug, or the bot has an internal error. You can file a support ticket
using the ticket command in the
case of a bug, or check the bot's status page for more information in the case of an
internal error.
The bot's host server is having a high latency. This usually will not happen, but please file a support ticket if this
issue occurs.
Please be patient. Usually, you will receive an initial response for your
support tickets 24 hours after they are filed.
(Note: This includes (but is not limited to) active minigames and
music playback.)
There may be a few reasons as to why this might be happening:
The bot is restarting with a new update/bugfix.
The bot has gone offline.
You have a poor connection to Discord.
Gradient Premium is only awarded to friendly and supportive users of the
bot and is NOT obtainable through monetary
transactions. There is no fixed criteria for acquiring Gradient Premium, and all awards are
decided on a case-to-case
basis by the development team.
The bot is written in JavaScript using a customized branch of Discord.js
and the stable version of Node.js.
Support Server
Have a question that isn't in the FAQ, or want to provide feedback? Join the
official support server for Gradient, a community where
users share usage knowledge with each other and suggest improvements to the developers.
Need to set up Gradient for the first time? This quick guide has got you covered.
❮
Section 1: Configure the bot's role hierarchy
1 / 4
ℹ️ If you do not need to use the bot's moderation features, skip to the next section.
Click the dropdown button next to the server name.
Section 1: Configure the bot's role hierarchy
2 / 4
ℹ️ If you do not need to use the bot's moderation features, skip to the next section.
Click the "Server Settings" button.
Section 1: Configure the bot's role hierarchy
3 / 4
ℹ️ If you do not need to use the bot's moderation features, skip to the next section.
Click the "Roles" button once you are in Server Settings.
Section 1: Configure the bot's role hierarchy
4 / 4
ℹ️ If you do not need to use the bot's moderation features, skip to the next section.
Order the roles so that the role called "Gradient" is above all roles that you want
it to be able to moderate.
In this example, moderation commands can be used for users with the Member and Subscriber roles, but
moderation commands cannot be used on anyone with a role that's higher than Gradient. Therefore, Gradient
cannot moderate users with the Bot, VIP, Admin, and Wozard roles.
Section 2: Configure the bot's permissions
1 / 4
ℹ️ Please ensure that the bot has the necessary permissions to perform its actions in all
channels you would like to use it.
Click the gear icon next to a channel in which you want to use the bot to open Channel Settings.
Section 2: Configure the bot's permissions
2 / 4
ℹ️ Please ensure that the bot has the necessary permissions to perform its actions in all
channels you would like to use it.
Click the "Permissions" button once you are in the Channel Settings.
Section 2: Configure the bot's permissions
3 / 4
ℹ️ Please ensure that the bot has the necessary permissions to perform its actions in all
channels you would like to use it.
Click the small plus icon and select the role called "Gradient".
Section 2: Configure the bot's permissions
4 / 4
ℹ️ Please ensure that the bot has the necessary permissions to perform its actions in all
channels you would like to use it.
Ensure that the green check mark is selected for all the permissions you want Gradient to have, then press the "Save
Changes" button.
Tip: Gradient requires the ability to read messages, send messages, and embed links at all times. Other permissions are
optional; enable them if you would like the bot to perform additional functionality, such as server moderation.
