Bot Meta Commands

Bot Information Commands

Bot status and meta information.

Command Information

The /help command displays information on the bot's commands themselves.

Wiki link command usage: /help wiki

Specific command wiki link: /help command <COMMAND NAME>

Command information provided:

• A link to the command's wiki page
• All usable aliases for this command
• A link to the command's source code

Ping

The /ping command displays the bot's ping to Discord and has nothing to do with your ping. The command is used to test basic bot responsiveness.

The command response time will likely be a higher number than you may see on other bots. This is the time between what Discord reports for your command message being sent, and the bot's response being sent. This may spike for many reasons including Discord API lag spikes.

Bot Info Command

The /botinfo command displays basic bot information:

• Support Discord invite
• Bot uptime
• Guild count
• Current version number.

Data Transfer between Bot Instances

You can transfer your data using /transferdata if you are switching to a different instance of FBK.

This is generally not recommended unless you really know what you are doing, but some reasons you may want to do this include:

• You are on FBK#1 or the verified FBK and use the Starboard feature. Thees bots do not have access to the message content and the starboard posts accordingly are blank, only FBK 2-7 have the Starboard feature functioning.
• You do not use the starboard or music player and would like to switch to the verified bot.

Most things will transfer over completely using this command, but the following considerations must be made first:

• The new bot must have the same permissions as the old bot. For example, you are likely to run into trackers failing to post if the old bot had channel-specific permissions granted to allow it to post. The "View Server as Role" feature in Discord is useful for troubleshooting such permissions issues. If you can't see it, the bot can't either.

• The new bot would need to be re-added to any threads that the old bot was a part of, if trackers were used there. Discord enables this by @mentioning the bot in the thread to force it into the thread.

• "Button roles" are not transferable and will need to be re-configured. The configuration will transfer, and they may seem to work on the new bot, but the new bot will not be able to edit the message posted by the old bot, so you will not be able to make changes to the embed. This may result in an error.

If you want to continue, the process for transferring to a different FBK instance is as follows:

1. Invite the verified bot to your server where you already use a different one. You will need both versions of the bot in the same server for a bit. Do not kick the old bot yet.
2. Make sure the new bot has the same or more permissions, especially permission to send messages in every channel you are using trackers etc in. Transferring data will not check for any of the permission warnings that happen when using /track, so you could end up with trackers that can not send messages and will not work.
3. Run /transferdata. It does not matter which bot you run the command from.
4. Follow the embed instructions to select the OLD bot and the NEW bot to transfer all data.
5. Kick the old bot from your server.

Data Deletion

Use /datadeletionrequest. See the Privacy Policy for details.