Make sure that your bans module is enabled before configuring the bans module (
!module bans to enable, and
!module list to see if it's enabled).
Setting Up Bans Module
This is one of the most easiest features to set up because enabling the module means the feature has been set up. There are no configuration commands for this module. Its sole purpose is simply to ban rowdy people, raiders, or even spam accounts from your community.
The list below details the minimum needed permissions in order for the bans module to function:
- View Channels
- Send Messages
Manage Messages (If using
%das an argument at the end of the ban command)
- Ban Members
Make sure that Gaius' role is higher than your mod role(s) but below your admin role
It is possible to ban people by their role with the banrole command. This will result in the uninterruptable banning of everyone who has this role. This cannot be canceled because a processed command cannot be canceled.
Required Permissions (Staff)
Ban Members (Admin)
!ban member [#w #d #h #m #s] [%d0-7] [Reason]
!ban member member member [%d0-7] [Reason]
!ban role role [%d0-7] [Reason]
!unban user [Reason]
!unban user user user [Reason]
!ban @yeetmaster#3000 420s %d2 | Bans person, sends ban DM, deletes 2 days of their messages and sends ban log
!ban @yeetmaster#3000 @yeetmaster#3001 | Bans multiple people, sends ban DMs, and sends ban log
!banrole @Troll Role | Bans everyone who has the Troll Role role, sends ban DMs, and sends ban log
!unban @yeetmaster#3000 420s %d2 | Unbans person and sends a log in the ban log
!unban @yeetmaster#3000 @yeetmaster#3001 | Unbans multiple people and sends logs in the ban log
This is for permanently banned users, not users who were softbanned. Softban is in the kicks module because it doubles as a hard kick.
This is highly useful for servers that allow banned people to submit ban appeals.
Banmsg allows banned members the opportunity to see your community's customized ban message. Whether it's to allow a ban appeal opportunity, tell them to get yeeted on, or say who banned them, where, and why, banmsg makes these possibilities possible.
Required Permissions (Staff)
!banmsg [temp] message
!banmsg reqreason [off/on/true/false]
!banmsg requnreason [off/on/true/false]
!banmsg Get yeeted on, %user! :Dabalicious: | Sets the new ban message to be sent to banned people
!banmsg temp You're temporarily banned. | Sets the new ban message to be sent to temp-banned people
!banmsg reqreason on | Sets the requirement to say the reason in all bans, kicks, mutes, and vcmutes
!banmsg requnreason on | Sets the requirement to say the reason in all unbans, unmutes, and vcunmutes
These flags are useful tools available to you and will be replaced by whatever that flag is meant for (example: %server will be replaced by the name of your server). In the example, any time you change your server's name after the setup, the flag will also change to that server's current name.
|%server||Will be replaced with the server's name|
|%user||Will be replaced with the banned user's name|
|%reason||Will be replaced with the reason provided by the moderator|
Will be replaced with the name of the moderator who performed the ban
As the command name suggests, these commands allows you to see the list of permanently and temporarily banned users respectively...very easy to use and quite useful for auditing and reviewing purposes.
Required Permissions (Staff)
!allbans [noreason] [nodelete]
!allbans noreason | Lists all permanent bans that don't have a reason along with other details of each ban
!allbans nodelete | Lists all permanent bans of account that have not been deleted from Discord
!tempbanlist | Lists all temporary bans (softbans) that are currently active in the server
BanSync is NOT a part of the band module, so there is NOT a need to enable the band module.
This feature is reserved for Gaius Plus only. Learn more.
BanSync with a server will result in both bans and unbans linking between the servers.
- Displays the current BanSync settings
|!bansync add/rem [export/import] id||
!bansync add/rem export 270438133584232449
- Adds/removes the target server to/from the exporting list
This will tell Gaius to export, or send, all future bans to the target server that has been specified.
Be aware not to use the same server ID that you are doing the command in. It must be the target server that you want to send the bans to.
!bansync add/rem import 270438133584232449
- Adds/removes the target server to/from the importing list
This will tell Gaius to import, or receive or get, all future bans from the target server that has been specified.
Be aware not to use the same server ID that you are doing the command in. It must be the target server that you want to receive the bans from.
|!bansync approve/unapprove id||
!bansync approve 270438133584232449
- Approves the target server for BanSync
!bansync unapprove 270438133584232449
- Unapproves, or removes, the target server for BanSync
- Removes all bansync connections with all servers
This will still keep the bansync setting to remain enabled instead of disabled.
Only the listed servers in the current bansync sommands are removed from the list.
- Enables BanSync integration with other servers
- Disables BanSync integration with other servers
|!bansync recursive id||
!bansync recursive 270438133584232449
- Adds all previous bans from the specified ServerID to your own
Q. Will kicking Gaius reset the bot?
- No, kicking/banning Gaius will never reset your settings or prefix.
Q. Can I set the bans to not send a message to someone when they are banned?
- No, this is currently not a feature.
Q. How do I see all the commands?
- The help command is man's best friend (not dogs).
Not yet available
If you have or find a video on Gaius specifically for what is covered in this documentation page, you can send the info to Fairy 狐 紫#0001 via DM (You must be in the support server in order to make contact).
Points of Interest