The overarching goal of BetaHub’s development is to create a solution that connects game creators with their community, without necessitating additional education on either side. One of the first pieces of feedback we received was that few people use the BetaHub Discord Bot to report errors.

The Problem

We see where the problem lies - community testers need to know that they should enter the /report command to report an error. However, they prefer to simply leave a message on the #bugs channel and forget about it. In this case, we decided to do something crazy, namely trying to identify all messages from the error reporting channel as errors!

Everything is an error!

Here too, we can’t do without the help of GPT. The generative artificial intelligence manages pretty well with text classification, but the real challenge is doing it well.

The new version of the bot (already working and online!) searches your server for a channel that could be the error reporting channel. How? It has a list of potential names and if any match, it determines that this is the bug channel, for example #bugs, #bug-reports, #issues, etc.

Then it reads each message dropped on this channel. It is sent through a classification endpoint and if the message is classified as a bug, an error report is created.

Note on Privacy

It’s important to mention that no information directly identifying the project or the user is shared with OpenAI. According to OpenAI’s privacy policy, the endpoint we base our service on does not store the content of the request. This means that whatever is typed by your users on the bug channel is not stored anywhere, only tested in search of a proper error report.

The Process in Practice!

This is what a Discord conversation looks like when the bot catches an error. (The red BetaHub bot visible on the screen is the developer’s bot)

The report appears on the project page like any other report, but in addition (if classified as a bug) it will contain the original Discord message and a link to that message:

Furthermore, if the message contains attachments in the form of screenshots, videos or log files, they will be attached to the report!

Keep in mind, after writing a message, the bot may need a few minutes before it even responds to it. This is due to factors such as response time from OpenAI servers and temporary failures. BetaHub will retry the classification query multiple times, but may postpone it if necessary.

Configuration

You can check if your bot has automatically picked up your bug reporting channel by typing /info. If not, go to the bug reporting channel and type /set bugs_channel true. The text channel you are currently on will be picked up as the bug reporting channel.

On the other hand, if you want to completely disable the automatic error reporting feature, call /set bugs_channel false on any channel. From then on, the bot will completely ignore what happens on the bug reporting channel.

And if you don’t have your BetaHub Bot integrated yet, don’t hesitate and set it up now!

Encountered a Bug in BetaHub?

Join our discord channel and report it! You can do it here: https://app.betahub.io/feedback