34 |
|
|
35 |
## Installation |
## Installation |
36 |
|
|
37 |
To install SudoBot, you need to clone the repository first, if you have Git installed. Run the following command in your terminal: |
To install SudoBot, you need to clone the [git](https://git-scm.com) repository or checkout the [svn](https://subversion.apache.org/) repository first, if you have git installed. Run the following command in your terminal: |
38 |
|
|
39 |
```bash |
```bash |
40 |
git clone https://github.com/onesoft-sudo/sudobot |
git clone https://github.com/onesoft-sudo/sudobot |
41 |
``` |
``` |
42 |
|
|
43 |
If you don't have Git installed, you can download the repository as a zipball/tarball from the [GitHub Releases Page](https://github.com/onesoft-sudo/sudobot/releases/latest). |
You can also checkout the [svn](https://subversion.apache.org/) repository: |
44 |
|
|
45 |
|
```bash |
46 |
|
svn checkout https://svn.onesoftnet.eu.org/svn/sudobot sudobot |
47 |
|
``` |
48 |
|
|
49 |
|
If you don't have git or svn installed, you can download the repository as a zipball/tarball from the [GitHub Releases Page](https://github.com/onesoft-sudo/sudobot/releases/latest). |
50 |
Then, extract the downloaded file to a directory of your choice. |
Then, extract the downloaded file to a directory of your choice. |
51 |
|
|
52 |
Next, navigate to the directory where you have cloned the repository using Git, or extracted the zipball/tarball, by running the following command in your terminal: |
Next, navigate to the directory where you have cloned the repository using Git, or extracted the zipball/tarball, by running the following command in your terminal: |
164 |
By default, BlazeBuild will use [Bun](https://bun.sh) to run the bot. If you want to use Node.js instead, you can run the following command: |
By default, BlazeBuild will use [Bun](https://bun.sh) to run the bot. If you want to use Node.js instead, you can run the following command: |
165 |
|
|
166 |
```bash |
```bash |
167 |
./blazew run -- --node |
./blazew run --node |
168 |
``` |
``` |
169 |
|
|
170 |
This will start the bot, and you should see the bot online in your Discord server. |
This will start the bot, and you should see the bot online in your Discord server. |
178 |
To register the application commands to the Discord API, you can run the following command: |
To register the application commands to the Discord API, you can run the following command: |
179 |
|
|
180 |
```bash |
```bash |
181 |
./blazew run -- -- -u |
./blazew run -- -u |
182 |
``` |
``` |
183 |
|
|
184 |
If you have debug mode enabled and have `HOME_GUILD_ID` set in the `.env` file, the bot will register the commands in the development guild. |
If you have debug mode enabled and have `HOME_GUILD_ID` set in the `.env` file, the bot will register the commands in the development guild. |
187 |
If you want to force the bot to register the commands globally, you can run the following command: |
If you want to force the bot to register the commands globally, you can run the following command: |
188 |
|
|
189 |
```bash |
```bash |
190 |
./blazew run -- -- -u -g |
./blazew run -- -u -g |
191 |
``` |
``` |
192 |
|
|
193 |
To clear the registered commands, you can run the following command: |
To clear the registered commands, you can run the following command: |
194 |
|
|
195 |
```bash |
```bash |
196 |
./blazew run -- -- -c |
./blazew run -- -c |
197 |
``` |
``` |
198 |
|
|
199 |
Once again, if you have debug mode enabled, the bot will clear the commands in the development guild. Otherwise, it will clear the commands globally. |
Once again, if you have debug mode enabled, the bot will clear the commands in the development guild. Otherwise, it will clear the commands globally. |
200 |
To force the bot to clear the commands globally, you can run the following command: |
To force the bot to clear the commands globally, you can run the following command: |
201 |
|
|
202 |
```bash |
```bash |
203 |
./blazew run -- -- -c -g |
./blazew run -- -c -g |
204 |
``` |
``` |
205 |
|
|
206 |
## Emojis |
## Emojis |