# Bot Commands *** ## GENERAL ### rec.help Displays this help message.

{% hint style="info" %} `rec.` is the bot prefix, everyone has a different prefix. Your bot will have a unique prefix upon request, a custom prefix for sure ! {% endhint %} *** ### rec.servers Lists all servers the bot is connected to.

*** ### rec.resource Shows the bot's memory usage.

*** ### rec.guildroles Displays all available roles on a specific guild server (default = all servers).

Unveil Guild Server Roles: Explore the Roster!

**Usage** ``` rec.guildroles ``` **Parameters** * **``** (required): The Guild ID can be found by right-clicking on the server icon in Discord and selecting **"Copy Server ID"**. **Examples** ``` rec.guildroles 123412341234 ```

This command is useful for finding the role ID of the server your bot is on, for 'rec.add' purposes *** ### rec.invite Shows the bot's invite link.

Your bot must be invited manually by the server / client owner, they will usually ask for an invite link and you just have to give the link to them. *** ### rec.leaveguild Instructs the bot to leave a specified server.

Instruct the Bot to Leave a Server

**Usage** ``` rec.leaveguild ``` **Parameters** * **``** (required): The Guild ID can be found by right-clicking on the server icon in Discord and selecting **"Copy Server ID"**. **Example** ``` rec.leaveguild 123412341234 ```

*** ## BROADCASTING & GROUP ### rec.recall Deletes the last broadcasted message.

when you realize there is an error in calls / broadcast messages that have been sent to all client servers, recall is the right solution to delete them all automatically. {% hint style="warning" %} Please note, the deleted messages will be in order from the last one you sent, if you do the `rec.recall` command 2x, then your 2 broadcasts will be deleted. {% endhint %} *** ### rec.add \ \[channel] \[role] Adds a channel and role.

Add or Link a Client Channel to a Broadcast Group

**Usage** ``` rec.add [role] ``` **Parameters** * **``** (required): The specific broadcast group to add the channel to. Available groups: bc0, bc1, bc3 ... bc99. * **``** (required): The channel to link to the bot's configuration. You can mention the channel or provide its ID. * **`[role]`** (optional): The role to associate with the channel. You can mention the role or provide its ID. If not provided, the role will be set to **@everyone**. **Examples** ``` rec.add bc0 #announcements @MentionableRole rec.add bc69 986153785342722208 987654321098765432 rec.add bc77 1067772861026152580 @Moderators ```

*** ### **rec.setrole \ \[channel] \[new\_role]** Updates the role for a specific channel.

Change the Ping Role for a Registered Channel in a Broadcast Group

**Usage** ``` rec.setrole [new_role] ``` **Parameters** * **``** (required): The broadcast group where the channel is registered. Available groups: bc0, bc1, bc3 ... bc99. * **``** (required): The channel for which you want to change the role. You can mention the channel or provide its ID. * **`[new_role]`** (optional): The new role to associate with the channel. You can mention the role or provide its ID. If not provided, the existing role will remain unchanged. **Examples** ``` rec.setrole bc0 #announcements @MentionableRole rec.setrole bc69 986153785342722208 987654321098765432 rec.setrole bc77 1067772861026152580 @Moderators ```

*** ### r**ec.remove \ \[channel]** Removes a channel and role.

Remove a Channel from a Broadcast Group

**Usage** ``` rec.remove ``` **Parameters** * **``** (required): The broadcast group from which the channel will be removed. Available groups: bc0, bc1, bc3 ... bc99. * **``** (required): The channel to remove from the bot's configuration. You can mention the channel or provide its ID. **Examples** ``` rec.remove bc0 #announcements rec.remove bc69 986153785342722208 rec.remove bc77 1067772861026152580 ```

*** ### **rec.show \** Displays information for a specific group.

Display All Channels Integrated with the Bot in a Broadcast Group

**Usage** ``` rec.show ``` **Parameters** * **``** (required): The broadcast group to display. Available groups: bc0, bc1, bc3 ... bc99. **Examples** ``` rec.show bc0 rec.show bc1 rec.show bc69 rec.show bc77 ```

bot displays all channels affiliated with broadcast group 'bc1' *** ### **rec.addgroup** Adds a new broadcast group.

If you do not enter the CAPTCHA for 15 seconds then everything will return to normal, there is no need for you to take any steps. {% hint style="danger" %} It is highly not recommended to use this command if you do not understand, you should contact me to do it. {% endhint %} *** ### **rec.removegroup** Removes an existing broadcast group. If you have previously added a group and want to delete it, please use this command.

same as `addgroup`, If you do not enter the CAPTCHA for 15 seconds then everything will return to normal, there is no need for you to take any steps.

*** ### **rec.showgroup** Shows your current broadcast groups. By default you get 2 broadcast groups, bc0 and bc1. bc0 is a group that is intended as a testing group and bc1 is intended for the real broadcast group. you can add broadcast groups as you wish.

{% hint style="success" %} As you can see here, I have 9 broadcast groups, each of which has its own purpose. {% endhint %} *** ### **rec.setsource** Sets up a source channel for each group. This command is intended to set the source channel, the channel that has been set as the source will be where you make calls / analysis, and then the bot will forward (broadcast) the message to all servers from the affiliated group. {% hint style="danger" %} It is not recommended to use this command, you should contact me to do the initial setup of your bot. {% endhint %}

Change the Channel ID of the Current Source Channel

**Usage** ``` rec.setsource ``` **Parameters** * **``** (required): The broadcast group to modify. Available groups: bc0, bc1, bc3 ... bc99. * **``** (required): The type of message format to apply. * `enp`: Embed without Ping Role * `ep`: Embed with Ping Role * `np`: Normal with Ping Role * `nnp`: Normal without Ping Role * **``** (required): The source channel to add to the bot's configuration. You can either mention the channel or provide its ID. **Examples** ``` rec.setsource bc0 ep #say-ep rec.setsource bc69 enp 123456789012345678 rec.setsource bc77 nnp 123456789012345678 ```

*** ### rec.setlog Sets up a log channel for all bot activities.

Change the Channel ID for Log Information

**Usage** ``` rec.setlog ``` **Parameters** * **``** (required): The channel where the bot will send its log information. You can either mention the channel or provide its ID. **Examples** ``` rec.setlog #bot-logs rec.setlog 123456789012345678 ```

*** ## CUSTOMIZATION ### rec.setpfp Changes the bot's profile picture.

{% hint style="info" %} It is recommended to use .jpeg / .jpg / .png image files {% endhint %}

Replace the Bot's Profile Picture (PFP)

**Usage** ``` rec.setpfp + Attach your image file! ``` **Instructions** Simply use the `rec.setpfp` command and attach the image file you want to use as the new profile picture for the bot.

*** ### rec.setgroupname Renames a broadcast group. In order for the bot to respond to the changes you make, after using this command it is mandatory to run the `rec.reload` command so that the bot refreshes itself automatically and the name of your broadcast group changes.

Set a Custom Name for Your Broadcast Group

**Usage** ``` rec.setgroupname ``` **Parameters** * **``** (required): The broadcast group number. Available group numbers: 0 to 6. * **``** (required): The new name for the broadcast group. It is recommended to use **ALL CAPITAL LETTERS** for better visibility. If the group name has more than one word, enclose it in quotation marks. **Examples** ``` rec.setgroupname bc0 CRYPTO rec.setgroupname bc69 "CRYPTO CALLS" rec.setgroupname bc77 "TEST CALLS" ```

*** ### rec.setusername Updates the bot's username. Your bot username will change according to what you give, use characters that are still acceptable by the rules that discord has.

{% hint style="warning" %} Attention: do not use this command often, because discord has a rule not to change your bot username often, if possible if you have changed your bot username today, give it 24 hours to change the next username. {% endhint %}

Replace the Bot's Username

**Usage** ``` rec.setusername ``` **Parameters** * **``** (required): The new username for the bot. You can use special characters, and the more unique the better. Note that Discord only allows changing the username every 2 hours. **Examples** ``` rec.setusername Thę Rēct◎r (GPA4.0🎓) rec.setusername Crypto Alert rec.setusername ANALYST rec.setusername Callers ```

*** ### **rec.setprefix** Changes your personal command prefix. prefix is a specific and special command prefix for your bot, each Rector Alert Bot user will have a different prefix from one another. It is recommended that the prefix is no more than 4 characters. {% hint style="warning" %} Attention: after changing the prefix, immediately contact me to do a hard restart of your bot, because the new prefix will not work if you only do a reload code command such as using the `rec.reload` command. {% endhint %}

Change Your Personal Command Prefix

**Usage** ``` rec.setprefix ``` **Parameters** * **``** (required): The new prefix for your commands. It is recommended not to use special characters. A prefix of 3 letters followed by a dot (.) is ideal. **Examples** ``` rec.setprefix rec. rec.setprefix crypto. rec.setprefix ? rec.setprefix - rec.setprefix ! ```

*** ### **rec.setfooter** Updates the footer text for the bot's embedded messages.

Replace the Footer Text of the Bot's Embedded Message

**Usage** ``` rec.setfooter ``` **Parameters** * **``** (required): The new footer text for the bot's embedded message. It is recommended to keep the character length to **30 characters or fewer**, including spaces. **Examples** ``` rec.setfooter Powered By ★ RZMetaversity.com rec.setfooter linktr.ee/rzmetaversity ```

*** ### rec.setwebsite Changes the website link in the bot's status message.

Replace the Website Text in the Bot's Status Message

**Usage** ``` rec.setwebsite ``` **Parameters** * **``** (required): The new website text for the bot's status message. The recommended character length is **25 characters or fewer**, including spaces. **Examples** ``` rec.setwebsite RZMetaversity.com rec.setwebsite linktr.ee/rzmetaversity ```

*** ### rec.seticon Updates the icon in the footer of the bot's embedded messages.

Replace the Icon in the Footer of the Bot's Embedded Message

**Usage** ``` rec.seticon / + upload an image ``` **Parameters** * **``** (required): Make sure the URL you provide is a direct link to an image. **Examples** ``` rec.seticon https://link_to_image.png rec.seticon https://link_to_image.jpg rec.seticon + Upload an Image ```

*** ### rec.setembedcolor Customizes the default embed color for messages.

Change the Embed Color of the Bot's Embedded Message

**Usage** ``` rec.setembedcolor ``` **Parameters** * **``** (required): The HEX color code (a 6-character combination) without the `#` sign. You can visit [color-hex.com](https://www.color-hex.com/) to find your desired color. **Examples** ``` rec.setembedcolor fcb708 ```

*** ## MAINTENANCE ### rec.reload Reloads the bot’s code.

*** ### rec.botstatus Displays your current subscription status with RZ Alert Bot.

*** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.rectorspace.com/rector-bot-alert/bot-commands.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.