🚧 Help center article under construction! 🚧
How to submit a bug
To submit a bug you need to give us information on what the bug is and how it happens. You have to write a command that is formatted correctly for the bot. This command is made up of different sections. The sections are listed below with a short explanation of what each section is:
A short description of the bug in one sentence.
Step by step how to make the bug happen
What should happen
What actually happens
The discord build, host, and version you are using
Operating system, for a phone the device + os version, for a pc the os version
To indicate which section you are giving information on you have to use - in combination with a letter. There is also a longer version which is -- in combination with a word. Each section has its own letter and words listed below:
- Title: -t or --title
- Reproduction Steps: -r or --repro-steps
- Expected Result: -e or --expected
- Actual Result: -a or --actual
- Client settings: -c or --client
- System settings: -s or --system
Note: on iOS -- will automatically convert —, which is unsupported.
The order of the sections is the order they are in for the submit command. You start off the command with !submit and then you fill in each section and add after each other. For the reproduction steps you start with `-r` write down the first step, add a - and a space before each following step. It is important to have space before and after the - for each step. If you don’t do that the submit command will not be accepted. A correct example of reproduction steps are:
The left underlined part is the start of the reproduction steps section with the first step. The right underlined part are steps that follow after. Each - tells the bot there is another step. When you are done with the reproduction steps move on to the next sections and fill those out.
Don't know how and where to find your client and/or system settings? Check out How do I find my client info?
Example of a complete bug report:
!submit -t This is a title -r Submitting from - The HC - Gets you - Banned -e This is what is supposed to happen -a This is what actually happens -c Canary 75056 (ead3483) -s Windows 10 Pro x64 v20H2 (OS Build 19042.746)
Finally to actually submit the report you need to send the submit in the reports channel of the platform you have a bug for. When it’s submitted your bug report will show up in the approval queue.
Can’t see any platform channels? Please read the Bug Hunter FAQ on how to get those.
Editing a bug
If you notice you have made an error in your bug submission you can edit it. You will need the bug submission ID for it. This ID can be found at the bottom left of the embed in the approval queue.
The edit command is similar to the submit command. You start with !edit and then specify the section of the report that you want to edit. Each of these sections is the same as the submit command. You can update one or more sections if needed in the edit command.
You can add a section with the shorthands posted below in front of the section and add the new information. For repro-steps it looks the same as explained in the submit command above. Each section is listed below:
- Title: -t
- Reproduction Steps: -r
- Expected Result: -e
- Actual Result: -a
- Client settings: -c
- System settings: -s
The edit command can be used in the reports channel or as a direct message to DBug.
Your command should look like this: