ZBot also allows you to retrieve information about the virtual world surrounding you. There you will find a single command that summarizes all the information about a channel/member/role/server/invitation/emoji, as well as a few other commands allowing you to study further.
This command sends a short presentation text of the bot, so that you know it a little better. It will also give you some links that may be useful to you (like the one to invite the bot, or to access its Discord server).
For this command, ZBot doesn’t need any specific permission! Good news, isn’t it?
Shorter than the ‘about’ command, this one only send an url to invite the bot. And this url will always be working, even if our web server crashes.
Allows you to know the list of all the orders currently available for you. The list is interactive, which means that you will only see the commands you are allowed to use.
You can specify a command (or subcommand) to get more details about it, or a cog (a code module) to see the list of commands related to that cog.
info [type] <object>
This command is probably the most powerful in the information module. It allows you to find information on any item on your server: members, roles, text and voice channels, categories, emojis, invitations, as well as the server itself. Oh and also raw snowflakes (Discord IDs). Some information is even available about users who are not on your server!
You can enter the name, the mention, or the identifier of the object to be searched, and if the type of object (member, user, role…) is not specified, the bot will search itself to identify it. Note however that you are obliged to inform the type if your search includes spaces.
Some fields may not appear under certain conditions. No need to worry, it’s just that Discord didn’t send the requested information to the bot. And there’s nothing we can do about it ¯\_(ツ)_/¯
The necessary permissions for the bot depend on the desired result: for example “Manage webhook” is required to get the list of webhooks of a channel.
With this command, you can get the number of members on your server, but also the number of bots, of humans, people connected, and probably other numbers that will be added later. This is a small basic command without much functionality, but it allows you to quickly keep up with these statistics.
Good news! The bot does not need any specific permissions for this command! Just keep in mind that the rendering is much prettier with “Embed Links” permission enabled.
perms [channel] [user|role] or
permissions [channel] [user|role]
This small command allows you to see the list of permissions assigned to a member/role in a particular channel. The channel can be either a text or a voice chat, but if you don’t provide any, the bot will select the general permissions as set in the Server Configuration. To inform a member or a role, it is only necessary to enter his exact name, his ID , or his mention. If no name is given the targeted member will be the one who enters the command.
The only permission needed to grant the bot is “Embed Links”.
ping [ip adress]
The ping command allows you to get the bot latency. It’s useful if you want to check why your command takes too long to be read. The number corresponds with the delay between the moment when your message reaches Discord and the moment when the bot’s response is received by the API.
If you give an ip address in the command, the bot will send a certain number of packets to this server to see if it is active, and know its latency. This may take a short time, depending on the server bandwidth and the number of packets to send.
prefix change <new prefix>
A nice shortcut to know the prefixes to which the bot responds. This is usually the prefix defined in the configuration, plus the mention of the bot.
Note that this result may differ from the
config see prefix command when the database is out of sync.
..note:: The subcommand
prefix change is an alias of
config change prefix
usernames <user> (aliases:
This command displays the history of all nickname changes of a member. The Discord API does not give this information, so Zbot records each change, therefore it is possible that some nicknames may not be displayed in the list.
If you don’t want your names changes to be recorded, you can opt-out by using the profile config usernames_log command.