Create a role
Last updated
Last updated
Create a new Role in the server. You can choose various modifications to enhance the role or leave some fields blank to be default.
The bot must have the Manage Roles permission in order to create a role.
This field will set the name of the role that the bot will create. Variables can be used in this field.
This field is an optional reason for creating the new role. This reason will show in the audit log of the server that the command / event was executed in. Variables can be used as well.
This field is optional and changes the position of the new role in your server. Leave this blank for default positioning. Positions are all arranged from bottom (default) to top. This field only accepts integers and variables can be used.
This field is optional and changes the color of the role the bot is creating. This field only accepts a HEX format. Server members use the color of the highest position role they have. Variables can be used. Leaving this field blank will make it a default grey color.
Hex format example: #af5555
This switch controls whether the role is hoisted or not.
This switch will allow anyone to mention / @ this role, even if they don't possess the mention @everyone / @here permission.
Click the "+" to attach certain permissions to the role the bot is creating. Leave this field blank to have no permissions. Visit this link to learn more about permissions.
Enable Success / Error Handles to detect success and errors inside of the action block. This allows you to run different actions if something goes wrong with your action. Inside of the handle, there are 2 different paths which are used to detect the outcome of the action. The green path on the bottom left side of the block indicates success, while the red path on the bottom right side of the block indicates error. You may attach action blocks to each side of the handle to get the outcome of your action block.
The Success/Error Handles feature includes 3 different error variables you can use to get information on why the action block encountered an error. Check them out here.
