# What is Builderman?
What does Builderman do in short?
Builderman is an extremely powerful, but simple and easy-to-use Discord bot designed to be the only tool one should need for managing submitted suggestions and/or bug reports from users within their Discord server. Aside from allowing users within a Discord server to submit bugs and/or suggestions of your various games (otherwise known as projects), Builderman makes the organization of those bug reports and suggestions a breeze!
From the ability to approve or deny submitted bug reports and/or suggestions, to being able to reserve them to begin development and more, Builderman is here to make it easy for both game (project) developers and users of those games (projects) to identify problems, fix problems and add new features within them.
### Contributors
👨💻 **Bot Developers**
* Reis#2109
🗣️ **Translators**
* Arashi#9639 (Dutch)
* Chisato#7401 (Swedish)
* JustRPR (German)
* Mr.Coco#1563 (Chinese Traditional)
🔎 **Bug Hunters**
* Sir Aaronology#5309
# Pre-Requirments
Before you can invite Builderman, please check for the following
* To invite Builderman you need either "Manage Server" or "Administrator" Permissions
* Please check that your Members can use slash-Commands
* Please also **do not remove** any permissions, when you invite Builderman. All listed permissions are required for Builderman to work correctly
* Manage Webhooks
* Read Messages
* Send Messages
* Manage Messages
* Embed Links
* Attach Files
* Read Message History
* Mention @here and all Roles
* Add Reactions
* Use Application Commands
# Channels & Permissions
After inviting the Builderman bot into your Discord server, you'll need to then configure some settings of Builderman to your needs.
## Discord Channels
You will need to create channels within your server that will aid in the functionality of Builderman. Create channels that correspond to the following commands listed below.
{% hint style="info" %}
*In the future, if you only want to check what you configured these to, just run the command without the channel variable attached to them.*
{% endhint %}
| Command | Description | Example |
| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :----------------------------------------------------------------------------------------------------------------------------------------: | :--------------------------------------------------------------------------------: |
| /holding-channel
channel:#text-channel
| Sets the default channel that will hold submitted bug reports and suggestions. *This can be both a public or private Channel.* | /holding-channel
channel:#awaiting-approval
|
| /todo-channel
channel:#text-channel
| Sets the default channel that will hold approved bug reports or suggestions to be worked on. *It is advised to make this Channel private.* | /todo-channel
channel:#developer-interal
|
| /poll-channel
channel:#text-channel
| Sets the default channel that will send submitted suggestions that are opened for public voting. | /poll-channel
channel:#polls
|
| /update-channel
channel:#text-channel
| Sets the default channel that Builderman will post all updates to. | /update-channel
channel:#change-log
|
## Administrative Roles
You will need to create roles within your server for users that will be used by Builderman to grant certain administrative permissions for your development team to interact with the bot. Create the roles in your Discord server that correspond to the following commands listed below.
{% hint style="info" %}
*In the future, if you only want to check what you configured these to, just run the command without the role variable attached to them.*
{% endhint %}
| Command | Description | Example |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------: | :--------------------------------------------------------------------------------------------------------------------------------: | :------------------------------------------------------------------: |
| /manager-role
role:@role
| Sets the role that Builderman will check if users possess to manage **ALL** aspects of the bot. | /manager-role
role:@Manager
|
| /dev-role
role:@role
| Sets the role that Builderman will check if users possess to work on approved bug reports or suggestions, as well as reserve them. | /dev-role
role:@ServerDev
|
| /approver-role
role:@role
| Sets the role that Builderman will check if users possess to approve/decline submitted bug reports and suggestions. | /approver-role
role:@Approver
|
# Custom Settings
Within Builderman, your projects are referred to as "Games" and are the topics in which members within your server can submit bug reports or suggestions that pertain to them.
To add a new Game to Builderman use: `/add-game game:YourProjectName`
You can also remove or add more scopes. The standard Scopes are *building*, *scripting* and *others*. To add or remove such Scopes you can use the `/scope` command.
With all these settings configured you are ready to receive your first suggestions and bug reports!\
Make sure to also check out our Commands Section to see all functions we currently offer.
# Default Users
"Default" Users have access to all so-called User Commands. Excluding those who either have a role that has been blacklisted with the [/blocked-role](/commands/owner-commands/blocked-role) command or users who have been manually blocked by a Server Manager, Server Administrator, or the Ravenhub Support Staff using the [/blacklist](/commands/manager-commands/blacklist) command.
# /suggest
### General Information
With the `/suggest` command, users can suggest new features for a specific project (game).
When executing the command, the user will receive a Direct Message from the Bot and fill out details about their suggestion. If the user has their Direct Messages disabled, the Bot will ask them to enable them.
### Requirments
* The User must not have a blacklisted role ([/blocked-role](/commands/owner-commands/blocked-role))
* The User must not be blacklisted by Server Managers/Administrators or Ravenhub ([/blacklist](/commands/manager-commands/blacklist))
* The User must have their Direct Messages enabled
* There must be at least one project (game) on the server ([/add-game](/commands/manager-commands/add-games))
* There must be a holding channel on the server ([/holding-channel](/commands/owner-commands/holding-channel))
### Command Details
Upon successfully executing the command the user will receive a Direct Message with further instructions from the Bot.
1. **Set the Title of the suggestion**\
The user is first asked for the title of the suggestions/feature request. This title will be included in the [project update](/commands/manager-commands/publish) containing this suggestion and in the [status-embed](/commands/manager-commands/status-embed).
2. **Selecting the Project (game)**\
The user can then select the project for which they would like to submit the suggestion. This can be done via text or the selection menu.
3. **General description**\
The user can then describe their proposal in depth. Due to Discord's limitations, the user can use a maximum of 1024 characters.
4. **Check the entered Information and add Files** \
The user then gets the opportunity to check his suggestion again. They can also add files like pictures, HTML files, etc., and then confirm the suggestion.
{% hint style="info" %}
#### **IMPORTANT!**
\
For the safety of our users, we block certain extensions. To check which file extensions we block please check: [My Files are not accepted](/faq/my-files-are-not-accepted)
{% endhint %}
# /report
### General Information
With the `/report` command, users can report bugs in a specific project (game).
When executing the command, the user will receive a Direct Message from the Bot and fill out details about their report. If the user has their Direct Messages disabled, the Bot will ask them to enable them.
### Requirments
* The User must not have a blacklisted role ([/blocked-role](/commands/owner-commands/blocked-role))
* The User must not be blacklisted by Server Managers/Administrators or Ravenhub ([/blacklist](/commands/manager-commands/blacklist))
* The User must have their Direct Messages enabled
* There must be at least one project (game) on the server ([/add-game](/commands/manager-commands/add-games))
* There must be a holding channel on the server ([/holding-channel](/commands/owner-commands/holding-channel))
### Command Details
Upon successfully executing the command the user will receive a Direct Message with further instructions from the Bot.
1. **Set the Title of the report**\
The user is first asked for the title of the bug report. This title will be included in the [project update](/commands/manager-commands/publish) containing this report and in the [status-embed](/commands/manager-commands/status-embed).
2. **Selecting a Scope**\
The user will be asked to enter a scope. If no changes have been done to the scopes yet, the user can choose between *scripting*, *building*, and *others*. This can be entered via text or via the selection menu.
3. **Selecting the Project (game)**\
The user can then select the project for which they would like to submit the report. This can be done via text or the selection menu.
4. **General description**\
The user can then describe their report in depth. Due to Discord's limitations, the user can use a maximum of 1024 characters.
5. **Check the entered Information and add Files** \
The user then gets the opportunity to check his report again. They can also add files like pictures, HTML files, etc., and then confirm the suggestion.
{% hint style="info" %}
#### **IMPORTANT!**
\
For the safety of our users, we block certain extensions. To check which file extensions we block please check: [My Files are not accepted](/faq/my-files-are-not-accepted)
{% endhint %}
# /help
### General Information
With the `/help` command, users can see all available commands with the role requirements needed to execute them.
### Requirments
None
# /invite
### General Information
With the `/invite` command, users can invite Builderman to other Discord Servers and get a link to the top.gg voting site.
### Requirments
None
# Approvers
Users who have been assigned the Approver Role or higher, have access to manage incoming suggestions and bug reports. The Approver Role is defined using the [/approver-role](/commands/owner-commands/approver-role) command.
# Incoming suggestions
### General Information
Once a suggestion has been sent by a User, it will be sent to the already configured holding-channel ([/holding-channel](/commands/owner-commands/holding-channel)). There an Approver or higher can review and process the suggestion.
### Requirments
* A ToDo-Channel has been configured ([/todo-channel](/commands/owner-commands/todo-channel))
* A Poll-Channel has been configured ([/poll-channel](/commands/owner-commands/poll-channel))
* The Reviewer must be an Approver or higher ([/approver-role](/commands/owner-commands/approver-role), [/dev-role](/commands/owner-commands/dev-role), [/manager-role](/commands/owner-commands/manager-role))
### How to use
Once a suggestion has arrived in the Channel it will look something like this:
1. **Accept the suggestion**\
You can accept a suggestion by pressing the "Accept" button. This will send the suggestion to the configured todo-channel. The User who sent the suggestion will also be informed by Builderman that their suggestion has been accepted.
2. **Create a Public Vote**\
Using the "Public Vote" button you can send the suggestion to a different Text-Channel. In there Users will have the ability to vote on the suggestions using buttons. The User who sent the suggestion will also be informed by Builderman via Direct Messages, that the suggestion has been opened for voting. Once the suggestion has either been accepted or denied, the Bot will automatically delete the vote from the Channel.
3. **Decline the suggestion**\
You can decline a suggestion by pressing the "Decline" button. This will remove the suggestion from the channel. The User who sent the suggestion will also be informed by Builderman via Direct Messages, that their suggestion has been declined.
4. **Report to Ravenhub Support**\
Should you feel like, the suggestion violates either Discord's or Ravenhub's TOS you can report the suggestion to our Support. Should our Staff confirm that the suggestion is against TOS, the suggester will be globally banned from using Builderman.
# Incoming bug reports
### General Information
Once a bug report has been sent by a User, it will be sent to the already configured holding-channel ([/holding-channel](/commands/owner-commands/holding-channel)). There an Approver or higher can review and process the suggestion.
### Requirments
* A ToDo-Channel has been configured ([/todo-channel](/commands/owner-commands/todo-channel))
* The Reviewer must be an Approver or higher ([/approver-role](/commands/owner-commands/approver-role), [/dev-role](/commands/owner-commands/dev-role), [/manager-role](/commands/owner-commands/manager-role))
### How to use
Once a bug report has arrived in the Channel it will look something like this:
1. **Accept bug reports with low severity**\
You can accept a bug report by pressing the "Low Severity" button. This will send the report to the configured todo-channel and rank the report as "Low Severity". The User who sent the report will also be informed by Builderman via Direct Messages, that their report has been accepted.
2. **Accept bug report with medium severity**\
You can accept a bug report by pressing the "Medium Severity" button. This will send the report to the configured todo-channel and rank the report as "Medium Severity". The User who sent the report will also be informed by Builderman via Direct Messages, that their report has been accepted.
3. **Accept bug report with high severity**\
You can accept a bug report by pressing the "High Severity" button. This will send the report to the configured todo-channel and rank the report as "High Severity". The User who sent the report will also be informed by Builderman via Direct Messages, that their report has been accepted.
4. **Decline bug reports**\
You can decline a bug report by pressing the "Decline" button. This will remove the report from the channel. The User who sent the report will also be informed by Builderman via Direct Messages, that their report has been declined.
5. **Report to Ravenhub Support**\
Should you feel like, the report violates either Discord's or Ravenhub's TOS you can report the bug report to our Support. Should our Staff confirm that the bug report is against TOS, the bug-reporter will be globally banned from using Builderman.
# Developers
Users who have been assigned the Developer Role or higher, have access to process approved suggestions and bug reports. The Developer Role is defined using the [/dev-role](/commands/owner-commands/dev-role) command.
# /queue
### General Information
With the `/queue` command, developers, managers, and administrators can see what feature requests and bug reports are currently in the publishment queue.
### Requirments
* There must be at least one project (game) on the server ([/add-game](/commands/manager-commands/add-games))
* The User must either have the Developer ([/dev-role](/commands/owner-commands/dev-role)) or Manager Role ([/manager-role](/commands/owner-commands/manager-role)), or be an Administrator
### Command Details
To execute the command, the requested project (game) must be specified. Example `/queue game:MyGame`
Upon successfully executing the command in a channel where Builderman is able to send messages, the bot will respond with a list of all completed bug reports and feature requests that are queued for publishment.
# Processing suggestions
### General Information
Once a suggestion has been approved by your Team, it will be sent to the already configured todo-channel ([/todo-channel](/commands/owner-commands/todo-channel)). There a Developer or higher can process the suggestion.
### Requirments
* The User must have either the Developer ([/dev-role](/commands/owner-commands/dev-role)) or Manager Role ([/manager-role](/commands/owner-commands/manager-role)), or be an Administrator
### How to use
Once a suggestion has been sent to the ToDo-Channel it will look something like this:
1. **Reserve the Ticket**\
Developers can reserve the suggestions. This is mainly for organizational purposes. In addition, when an update is published, the developer is credited for implementing the suggestion.
2. **Send it in the publishment Queue** \
As soon as a suggestion is implemented by a Developer, they can move it to the publishment queue. This deletes the suggestion from the channel and moves it to the final stage. As soon as a game update is now published, this suggestion is attached as implemented. This action can not be undone.
3. **Publish it immediately**\
Unlike the "Publish Queue" button, this is not intended for game updates but rather for game hotfixes. The suggestion is published directly as a single update.
4. **Delete the suggestion**\
If the developer decides that you do not want to implement the suggestion, you can delete it using the "Delete" button. **Important: The user will not be informed that the suggestion has been deleted.**
# Processing bug reports
### General Information
Once a bug report has been approved by your Team, it will be sent to the already configured todo-channel ([/todo-channel](/commands/owner-commands/todo-channel)). There a Developer or higher can process the suggestion.
### Requirments
* The User must have either the Developer ([/dev-role](/commands/owner-commands/dev-role)) or Manager Role ([/manager-role](/commands/owner-commands/manager-role)), or be an Administrator
### How to use
Once a bug report has been sent to the ToDo-Channel it will look something like this:
1. **Reserve the Ticket**\
Developers can reserve the bug report. This is mainly for organizational purposes. In addition, when an update is published, the developer is credited for fixing the bug report.
2. **Re-classify as Low Severity** \
This will allow Developer to re-classify their bug report to a Low Severity.
3. **Re-classify as Medium Severity** \
This will allow Developer to re-classify their bug report to a Medium Severity.
4. **Re-classify as High Severity**\
This will allow Developer to re-classify their bug report to a High Severity.
5. **Send it in the publishment Queue**\
As soon as a bug is fixed by a Developer, they can move it to the publishment queue. This deletes the suggestion from the channel and moves it to the final stage. As soon as a game update is now published, this bug report is attached as implemented. This action can not be undone.
6. **Publish it immediately**\
Unlike the "Publish Queue" button, this is not intended for game updates but rather for game hotfixes. The suggestion is published directly as a single update.
7. **Delete the suggestion**\
If the developer decides that you do not want to fix the bug, you can delete it using the "Delete" button. **Important: The user will not be informed that the bug report has been deleted.**
# Managers
Users who have been assigned the Manager Role or higher, have access to manage projects (games), make project (game) updates, and blacklist users from using the bot on the Server. The Manager Role is defined using the [/manager-role](/commands/owner-commands/manager-role) command.
# /list-games
### General Information
With the `/list-games` command, managers and administrators can see what projects (games) currently exist on the server.
### Requirments
* The User must either have the Manager Role ([/manager-role](/commands/owner-commands/manager-role)) or be an Administrator
### Command Details
Upon successfully executing the command in a channel where Builderman is able to send messages, the bot will respond with a list of all projects (games) that have been added to the Server.
# /add-game
### General Information
With the `/add-game` command, managers and administrators can add new projects (games) to the server.
### Requirments
* The User must either have the Manager Role ([/manager-role](/commands/owner-commands/manager-role)) or be an Administrator
### Command Details
To execute the command, the name of the new project (game) must be defined. Example `/add-game game:MyNewGame`
Upon successfully executing the command in a channel where Builderman is able to send messages, the bot will add the requested game to the database and respond with a confirmation.
# /delete-game
### General Information
With the `/add-game` command, managers and administrators can remove already existing projects (games) from the server.
### Requirments
* There must be at least one project (game) on the server ([/add-game](/commands/manager-commands/add-games))
* The User must either have the Manager Role ([/manager-role](/commands/owner-commands/manager-role)) or be an Administrator
### Command Details
To execute the command, the name of the project (game) must be defined. Example `/add-game game:MyNewGame`
Upon successfully executing the command in a channel where Builderman is able to send messages, the bot will remove the requested game to the database and respond with a confirmation.
# /publish
Should be the same like Developer and Approval
### General Information
With the `/publish` command, managers and administrators can publish project (game) updates with all new features, all bug fixes/changes, and all completed [suggestions](/commands/user-commands/suggest) and [bug-reports](/commands/user-commands/report) in the [publishment queue](/commands/developer-commands/queue).
### Requirments
* There must be at least one project (game) on the server ([/add-game](/commands/manager-commands/add-games))
* The User must either have the Manager Role ([/manager-role](/commands/owner-commands/manager-role)) or be an Administrator
### Command Details
To execute the command, the name of the project (game) and the version must be defined. Example `/add-game game:MyGame version:1.0`
Additionally, if no [default update-channel](/commands/owner-commands/update-channel) has been set, the channel where the update should be set has to be defined. Example `/add-game game:MyGame version:1.0 channel:#update-channel`
Upon successfully executing the command the user will receive a Direct Message from the bot asking for additional specifications.
First, the user is asked to state what has been added to the game, this can be done by simply sending it to the bot via Direct Messages. The bot will react to the message with a :white\_check\_mark: to confirm that it has been added, the feature will also be added to the embed in the initial message.
After the user is done with their inputs, they can click the "Done" button or write "done" to proceed. Upon doing so, the user is now asked to state what has been changed in the game, this can be done by simply sending it to the bot via Direct Messages. The bot will react to the message with a :white\_check\_mark: to confirm that it has been added, the feature will also be added to the embed in the initial message.
Once the user is satisfied with the list, they can press the "Done" button or write "done" again to publish the update. A message with all new features, changes, and completed [suggestions](/commands/user-commands/suggest) and [bug-reports](/commands/user-commands/report) in the [publishment queue](/commands/developer-commands/queue) will be sent in the defined text channel by the bot. Depending on the [settings](/commands/owner-commands/update-ping) a ping will be sent with the message.
Note that at any time, the user can revert the current input by pressing the "Revert Input" button, or cancel the entire update by clicking the "Cancel" button or writing "cancel".
# /blacklist
### General Information
With the `/blacklist` command, managers and administrators can view blacklisted users and blacklist users from using Builderman on the Discord Server.
### Requirments
* The User must either have the Manager Role ([/manager-role](/commands/owner-commands/manager-role)) or be an Administrator
### Command Details
To view a list of all currently blacklisted users, simply type `/blacklist`.
To permanently blacklist a user from using Builder on a Discord Server, you must specify the user and optionally the action.
Examples
`/blacklist user:@DiscordUser` and `/blacklist user:@DiscordUser action:ADD` *(Blacklists @DiscordUser)*
`/blacklist user:@DiscordUser action:REMOVE` *(Removes @DiscordUser's Blacklist)*
# /status-embed
### General Information
With the `/status-embed` command, managers and administrators can create a status-embed that displays the current status of all [suggestions](/commands/user-commands/suggest) and [bug-reports](/commands/user-commands/report).
### Requirments
* The User must either have the Manager Role ([/manager-role](/commands/owner-commands/manager-role)) or be an Administrator
### Command Details
To execute the command, the channel where the embed should be posted must be defined. Example `/status-embed channel:#status-channel`
Upon successfully executing the command the status embed will be posted, after that, the bot will handle everything for you. To disable the status-embed simply write `/status-embed` without defining a channel.
# Administrators
Server Administrators have access to set up required channels/roles and change the bot settings.
The Server Owner is also considered an Administrator.
# /holding-channel
### General Information
With the `/holding-channel` command, administrators can view or set the holding-channel.
### Requirments
* The User must be an Administrator
### Command Details
To view the current holding-channel, execute the `/holding-channel` command.
To set or change the holding-channel, the channel must be defined. The bot will then respond with a confirmation. Example `/holding-channel channel#holding-channel`
# /todo-channel
### General Information
With the `/todo-channel` command, administrators can view or set the holding-channel.
### Requirments
* The User must be an Administrator
### Command Details
To view the current todo-channel, execute the `/todo-channel` command.
To set or change the todo-channel, the channel must be defined. The bot will then respond with a confirmation. Example `/todo-channel channel#todo-channel`
# /poll-channel
### General Information
With the `/poll-channel` command, administrators can view or set the holding-channel.
### Requirments
* The User must be an Administrator
### Command Details
To view the current poll-channel, execute the `/poll-channel` command.
To set or change the poll-channel, the channel must be defined. The bot will then respond with a confirmation. Example `/poll-channel channel#poll-channel`
# /update-channel
### General Information
With the `/update-channel` command, administrators can view or set the holding-channel.
### Requirments
* The User must be an Administrator
### Command Details
To view the current update-channel, execute the `/update-channel` command.
To set or change the update-channel, the channel must be defined. The bot will then respond with a confirmation. Example `/update-channel channel#update-channel`
# /update-ping
### General Information
With the `/update-ping` command, administrators can enable, disable, and change the Role Ping for published updates.
### Requirments
* The User must be an Administrator
### Command Details
To enable or disable the update-ping, the state must be defined. Example `/update-ping toggle:Disabled`
To also change the role that should be pinged, the role must be defined additionally to the setting. Example `/update-ping toggle:Enabled role:@Update Ping`
# /manager-role
### General Information
With the `/manager-role` command, administrators can view or set the manager-role.
### Requirments
* The User must be an Administrator
### Command Details
To view the current manager-role, execute the `/manager-role` command.
To set or change the manager-role, the role must be defined. The bot will then respond with a confirmation. Example `/manager-role role:@Manager`
# /dev-role
### General Information
With the `/dev-role` command, administrators can view or set the dev-role.
### Requirments
* The User must be an Administrator
### Command Details
To view the current dev-role, execute the `/dev-role` command.
To set or change the dev-role, the role must be defined. The bot will then respond with a confirmation. Example `/dev-role role:@Developer`
# /approver-role
### General Information
With the `/approver-role` command, administrators can view or set the approver-role.
### Requirments
* The User must be an Administrator
### Command Details
To view the current approver-role, execute the `/approver-role` command.
To set or change the approver-role, the role must be defined. The bot will then respond with a confirmation. Example `/approver-role role:@Approver`
# /blocked-role
### General Information
With the `/blocked-role` command, administrators can view or set the blocked-role.
### Requirments
* The User must be an Administrator
### Command Details
To view the current blocked-role, execute the `/manager-role` command.
To set or change the blocked-role, the role must be defined. The bot will then respond with a confirmation. Example `/blocked-role role:@Blocked`
# /scope
### General Information
With the `/scope` command, administrators can view and set scopes. These can be selected when [making suggestions](/commands/user-commands/suggest) or [reporting bugs](/commands/user-commands/report).
### Requirments
* The User must be an Administrator
### Command Details
To view a list of all scopes, simply type `/scope`.
To add or remove a scope, the name and the requested action must be defined.
Examples
`/scope name:MyNewScope` and `/scope name:MyNewScope action:ADD` *(Adds "MyNewScope" to the scope list)*
`/scope name:MyScope action:REMOVE`*(Removes "MyScope" from the scope list)*
# /language
### General Information
With the `/language` command, administrators can view or set the server language.
### Requirments
* The User must be an Administrator
### Command Details
To view the current server language, execute the `/language` command.
To set or change the language, it must be defined. The bot will then respond with a confirmation. Example `/language language:German`
# Why does the bot not work after the migration?
To make the bot easier to use, we have migrated the bot to slash-commands. If you have invited the bot to your Discord server before December 11, 2021, you have to activate the slash-commands. For more information type `-help` on your server.
While we advise kicking and re-invite Builderman to ensure your Database Entry is on the latest version, a normal migration via the Command does also work.
{% hint style="danger" %}
**We will drop support of none-Button Embeds on March 30th**.
Should you until then still have not migrated, or have bug report/suggestion embeds that still use the old Functions, that will result in a loss of these tickets.
{% endhint %}
# Slash-Command don't appear
If you have migrated the bot or invited the bot but do not see any slash commands, this may be related to the permissions.
When inviting the bot, all permissions that are requested must also be given. Otherwise, the bot cannot function correctly. Also, make sure that you give (preferably) @everyone the right to use slash-commands.
If you have a general permission problem, please use the Button on Builderman to add him again to your Server. You don't need to kick him for that!
# What are "scopes"?
Scopes are the different choices of what exactly can be reported. You can think of them as bug categorisations.
You can add your own custom scopes via [`/scopes`](/commands/owner-commands/scope), when you add your own scopes the Bot will automatically delete all default scopes.
# What does the report Function?
Reporting suggestions/bug reports will result in a copy of it being sent to our Support Team.
They will check if Discord's or our ToS have been violated with this suggestions/bug report, and take then the appropriate Steps.
This means they can either warn the User via Builderman (see Image below), or can globally ban the user from using Builderman from any Server.
{% hint style="info" %}
Please note, you can also blacklist a User from only your Server via [`/blacklist`](/commands/manager-commands/blacklist)
{% endhint %}
# My Files are not accepted
When you create a bug report or a feature request, you can always upload a file, images or similar at the end to give the developers more information.
To protect our users as much as possible from threats from malicious users, we have decided to block some types of files that are often used to perform malicious activities. You can tell that Builderman blocks the file by the X emoji that Builderman adds to the file.
We block the following file types:
* .zip
* .rar
* .7z
* .exe
* .cmd
* .bat
* .msi
* .ps1
* .vbs
* .dll
* .docx
* .xlsx
* .xls
* .sh
* .rpm