A Discord bot with various utility & customization features. It is most suited for small to medium servers.
Roberto is licensed under the MIT license. Feel free to reuse it if you want!
If you find any issues, please report them in Issues. Additionally, feel free to dm me on Discord directly at iwao#8394 if you need any help!
When inviting Roberto to your server, you will be prompted to give them a set of permissions within it. The purpose for each of those asked permissions are explained in the next section.
Once Roberto has joined your server, a new Roberto role will have automatically been created and marked as "managed by an integration". This role is managed by Discord itself and is used to give Roberto their needed permissions. Note that if Roberto doesn't have more permissions than @everyone, no such role will be generated. It is highly recommended to put this role at the very top of your server's role list. This is required for several features to work properly.
If the Manage Roles permissions was given to Roberto, another role will be created on your server : Roberto Admin. This role is not automatically created or managed by Discord, and is used solely by Roberto : some commands will require their caller to have this role. Its permissions or position in the role list are of no importance.
When inviting Roberto to a server, the server owner will automatically receive a DM from Roberto explaining the basics of the bot's usage. If the View audit logs permission is granted, the user who invited Roberto will receive this DM as well.
The /config command is used to modify Roberto's behavior on the server. The last section explains those configurable options in more detail. This command can only be used by users with the Roberto Admin role, excepted the roles-repair subcommand, the purpose of which is to regenerate the Roberto Admin role, in case it was deleted or other roles with the same name were created (and you don't know which one is the real one).
The Roberto role managed by the integration will automatically be deleted when removing Roberto from your server. Other roles such as color roles or the Roberto Admin role, however, will remain: bots cannot clean up servers they are not in anymore.
When inviting Roberto, you will be asked to grant them 5 permissions:
- Read messages : this is mainly used to display Roberto in the right sidebar of Discord.
- Send messages : this is used for Roberto to send auto-greet messages on new member joins if the option is enabled (disabled by default).
- Note that neither Read messages or Send messages is needed for commands to be read and responded to by Roberto.
- Manage nicknames : this is obviously needed for the
/nicknamecommand. - Manage roles : this is needed for the following:
- Creating the Roberto Admin role (performed when Roberto joins your server - this role is needed to call some commands).
- Calling the
/config roles-repaircommand, which may create a new role and delete unused roles. - Using the
/colorcommand since name colors are given through roles. For the same reason, it is also needed for the auto-color feature to function.
- View audit logs: this is used for the following:
- Fetch the user who invited Roberto in the server to send them a DM.
- Fetch the user who removed needed permissions from Roberto (by editing a server role or Roberto's role list) and send them a DM (configurable with the permission-dm option).
Roberto currently has 10 commands, some of them having subcommands. All of them support Discord's slash command feature.
Changes the caller's name's color in the server using a dedicated role. When a user changes their color, the previous color role - if any - is automatically deleted if unused.
Roberto needs the permission to manage roles for this command to work. Additionally, Roberto's role should be placed above all color roles in order for this command to work properly.
Note that the created color role is placed at the very bottom of the role list. For this reason, any other role with a color placed above the color role created by this command will override it. This can be prevented by simply reordering roles.
/color hex <hex-code>: Applies the entered hex color code to the user./color random: gives the user a random color./color random-vibrant: gives the user a random vibrant color - that is, a color from the saturated color wheel./color dominant <type>: picks a dominant color from the user's profile picture - the user can choose between the main, dark or light dominant colors./color remove: removes the user's current color role.
Looks up the entered word or expression on Wiktionary and displays an embed with the found definitions. This command currently supports french & english.
/dictionary en <word-or-expression>: Looks up the word or expression in the english Wiktionary. Only english definitions will be displayed./dictionary fr <word-or-expression>: Looks up the word or expression in the french Wiktionary. Only french definitions will be displayed.
When you play Valorant, you sometimes need to send chat messages to your team - but in the heat of a round, it can be difficult to quickly type that british fire guy's name without errors. That's where this command comes handy: it generates alternative spellings for his name, that are guaranteed to be easier to write but still recognizable. Use its results to impress your teammates!
/px: Generates an alternative spelling for "Phoenix" - the "Again!" button can be pressed by the command caller to regenerate it as many times as needed.
Generates random values, such as dice rolls or draws from a pool of values.
/random dice <sides> <rolls>: Rolls a dice with a specific number of sides one or several times - the "Roll again" button can be pressed by the command caller to generate more rolls. Only the 10 most recent roll results will be displayed./random draw <total> <draws>: Draws a specific number of values (without duplicates) from a pool of possible numbers - the "Draw again" button can be pressed by the command caller to generate more draws. Only the 10 most recent draw results will be displayed.
Randomly chooses users from your voice channel - can be used to pick people or generate teams.
/random-channel teams <teams>: distributes all channel members in a specific number of teams - the "Generate again" button can be pressed by the command caller to regenerate the teams. This command can only be called when the caller is in a voice channel with at least 3 connected members./random-channel draw <draws>: randomly draws a specific number of users from the voice channel - the "Draw again" button can be pressed by the command caller to redraw channel members. This command can only be called when the caller is in a voice channel with at least 2 connected members.
Updates or removes the nickname of the chosen server member.
Roberto needs the permission to manage nicknames for this command to work. Additionally, Roberto's role should be placed above all roles of a given user in order to successfully give them a new nickname. For this reason, it is impossible to update the nickname of the server owner, as their owner status automatically counts as the highest role in the role list. It is recommended to put Roberto's role above all others, to ensure that everyone can be renamed apart from the server owner.
/nickname set <user> <nickname>: gives a nickname to the tagged server member./nickname remove <user>: removes a server member's nickname if they have one.
Fetches the weather for the entered location on OpenWeather and displays an embed with the found information.
/weather <location>: Fetches the weather for the given location.
Displays information about available commands and their usage.
/help: Displays a list of all available commands./help <command>: Displays information about a specific command.
This command is used to configure Roberto's behavior on your server.
Most of its subcommands can only be called by server members with the Roberto Admin role - the only exception is the roles-repair subcommand, which can be used by anyone.
Roberto needs the permission to manage roles for the roles-repair subcommand to work.
/config auto-color <action>: Enables, disables or shows the current value for the auto-color configuration option (enabled by default)./config auto-greet <action>: Enables, disables or shows the current value for the auto-greet configuration option (disabled by default)./config permission-dm <action>: Enables, disables or shows the current value for the permission-dm configuration option (enabled by default)./config roles-show: Shows the current Roberto admin role name and ID./config roles-repair: Regenerates the Roberto admin role if needed and deletes unused roles with the same name (a role is considered unused if it has no members).
Displays the changelog of the latest release of Roberto.
/changelog: Fetches the changelog from Roberto's latest release from GitHub and displays it.
Roberto's behavior on your server can be customized through 3 togglable options. Each of those options can be shown and edited through the corresponding subcommand of /config.
This option is enabled by default.
When this option is enabled, new members joining the server will automatically be given a color role - the chosen color will be the main dominant color from their profile picture (as if the member called the /color dominant main command upon joining) - this dominant color extraction has a small chance to fail, in which case a random color will be given instead.
The color role will not be created or applied if Roberto was offline when the new member joined.
This option is disabled by default.
When this option is enabled, Roberto will automatically send a greetings message when a new member joins the server. The message is randomly picked from a pool containing both Discord's old greetings message list (not used anymore) and new message list.
If this option is enabled, it is recommended to disable Discord's native greeting feature to avoid a double greeting.
The greeting message will not be sent if Roberto was offline when the new member joined.
This option is enabled by default.
When this option is enabled, whenever a role needed by Roberto is removed from them (this can happen when a role Roberto has is edited or removed from them), an alert DM is sent to the person who removed the permissions. If Roberto doesn't have the View audit logs permission or was offline when this was performed, the DM will be sent to the server owner instead (the next time Roberto starts up).