F.A.Q.

A list of frequently asked questions

How do I get started with RTByte?

To get started with RTByte, simply click the Add RTByte button in the upper right corner of this page. Once RTByte has been invited to your server, it will automatically set up the following items.

  • An administrator role
  • A moderator role
  • A server log channel

The server owner will be granted the Administrator role automatically. All of these things can be reconfigured using the conf command.

For a full list of commands, please see the Commands page, or run the help command.

I already have moderator and/or admin roles set up! Can I remove the ones the bot created?

Yes you can! Make sure you've reconfigured the bot to use your already existing roles using the conf command first, however. For instructions on how to use the conf command, please see the Configuration category.

RTByte isn't responding to any commands, what do I do?

This can be due to a couple of different things. Please check the following:

  1. Check if RTByte has the Read and Send Messages permission either on the whole server or in the channel you're in.
  2. Type @RTByte prefix, and make sure you're using the correct one.

If neither of these work, please join our support server for further assistance.

Is RTByte open-source?

Yes. RTByte has always, and will always, be open-source. You can view or contribute to the source code for any of our projects over on our GitHub page.

How can I contribute to the project?

Of course! We'd love it if you were able to contribute to the project in any way you'd like - whether that's through helping with development, design, testing, translating, or even just helping others in our support server.

Even if you can't contribute in any of the ways listed above, you can still help out by giving us suggestions for new features, or by donating to the project.

Every single contribution to the project is greatly appreciated.

How do I use the configuration command?

While the conf command looks complicated at first, it's actually pretty easy to use. Every configuration is stored as a key, and that key has a value. Keys can also be stored in folders, and those folders can have subfolders.

To view the configuration, you can run the following command.

-conf show

This will show you the root folder of the configuration. You'll see a list of folders, as well as a couple of keys. To view one of those folders, simply type in the folder name. To view a subfolder of a folder, simply type in the folder name, followed by .subfolder

-conf show channels
-conf show logs.events

Setting a value for a configuration key follows the same structure of viewing the configuration, but is slightly different.

-conf set logs.events.channelUpdate true
🠕 🠕 🠕 🠕
folder subfolder key value

In this example, we're first telling the command that we want to set a configuration instead of showing one. After that, we're defining the folder (and optionally any subfolders), then the actual key itself. The key, much like a folder, is accessed by typing its name. If it's in a folder, you'd need to add .key after the folder name. If the key isn't in a folder, you can simply type in the name of the key.

Why are configuration options named the way they are?

The configuration keys are named the way they are due to our coding guidelines. The same way you access a configuration key when running the conf command, we do in the code. We're currently working on a server dashboard for this website, which will let you configure all your server settings via your browser (with the command as a backup).

We try to name the configuration options as clearly as possible, but in some cases it doesn't come across as clearly as we intended.

What event and moderation logs are enabled by default?

All moderation logs are enabled by default. The event logs that are enabled by default are as follows:

  • Server settings change
  • Member joins
  • Member leaves
  • Message is deleted
  • Message is edited