| 1 |
<p align="center"> |
<p align="center"> |
| 2 |
<img src="https://res.cloudinary.com/rakinar2/image/upload/v1651761676/sudobot4_r257uw.png" height="200px" width="200px"> |
<img src="https://res.cloudinary.com/rakinar2/image/upload/v1659628446/SudoBot-new_cvwphw.png" height="200px" width="200px"> |
| 3 |
</p> |
</p> |
| 4 |
|
|
| 5 |
<h1 align="center">SudoBot</h1> |
<h1 align="center">SudoBot</h1> |
| 14 |
<p align="center"> |
<p align="center"> |
| 15 |
A Discord bot for moderation purposes. |
A Discord bot for moderation purposes. |
| 16 |
</p> |
</p> |
| 17 |
|
|
| 18 |
|
### Features |
| 19 |
|
|
| 20 |
|
- Strong automoderation system with tools like anti-spam and anti-raid |
| 21 |
|
- Useful moderation tools |
| 22 |
|
- Secure |
| 23 |
|
- Fun commands |
| 24 |
|
|
| 25 |
|
### Getting started |
| 26 |
|
|
| 27 |
|
You can request an invite for SudoBot [here](https://sudobot.everything-server.ml/). |
| 28 |
|
Alternatively, you can create your own Discord API application and then host SudoBot. |
| 29 |
|
|
| 30 |
|
### Setup for Custom Hosting |
| 31 |
|
|
| 32 |
|
First, download the latest release or clone the repo by running: |
| 33 |
|
|
| 34 |
|
``` |
| 35 |
|
git clone https://github.com/onesoft-sudo/sudobot |
| 36 |
|
``` |
| 37 |
|
|
| 38 |
|
Then go inside the project directory, and run the following commands: |
| 39 |
|
|
| 40 |
|
``` |
| 41 |
|
mkdir config tmp storage logs |
| 42 |
|
touch logs/join-leave.log |
| 43 |
|
echo "{}" > config/snippets.json |
| 44 |
|
cp sample-config.json config/config.json |
| 45 |
|
npm install |
| 46 |
|
npm install -D |
| 47 |
|
``` |
| 48 |
|
|
| 49 |
|
Then open up the `config/config.json` file and change at least the following: |
| 50 |
|
|
| 51 |
|
```json |
| 52 |
|
{ |
| 53 |
|
"global": { |
| 54 |
|
"id": "set your home guild id", |
| 55 |
|
"owners": ["set owner user ids here"], |
| 56 |
|
... |
| 57 |
|
}, |
| 58 |
|
"guild id here": { |
| 59 |
|
"prefix": "-", |
| 60 |
|
"mod_role": "the mod role, users having it will be able to use the bot", |
| 61 |
|
"gen_role": "general role id, which all users have", |
| 62 |
|
"mute_role": "the muted role id", |
| 63 |
|
"admin": "the admin role id. users having it will be immune to sudobot.", |
| 64 |
|
... |
| 65 |
|
} |
| 66 |
|
} |
| 67 |
|
``` |
| 68 |
|
|
| 69 |
|
**Note**: `...` means other options that exist in the config, you can edit them to customize the settings, but not required. |
| 70 |
|
|
| 71 |
|
Build the project: |
| 72 |
|
|
| 73 |
|
``` |
| 74 |
|
npm run build |
| 75 |
|
``` |
| 76 |
|
|
| 77 |
|
Deploy slash commands globally: |
| 78 |
|
|
| 79 |
|
``` |
| 80 |
|
node deploy-commands.js |
| 81 |
|
``` |
| 82 |
|
|
| 83 |
|
Start the bot: |
| 84 |
|
|
| 85 |
|
``` |
| 86 |
|
npm start |
| 87 |
|
``` |
| 88 |
|
|
| 89 |
|
And if everything was configured correctly, you should not see an error and the bot should say `Logged in as [tag]!`. |
| 90 |
|
Then you can run the following command in Discord to make sure everything is working: |
| 91 |
|
|
| 92 |
|
``` |
| 93 |
|
-about |
| 94 |
|
``` |
| 95 |
|
|
| 96 |
|
That should show the bot information. |
| 97 |
|
Congratulations! You've successfully set up your own instance of SudoBot! |
| 98 |
|
|
| 99 |
|
### Support |
| 100 |
|
|
| 101 |
|
- **Email**: [email protected] |
| 102 |
|
- **Discord Server**: [Support Server Invite](https://discord.gg/892GWhTzgs) |
Parent Directory
| 
Revision Log
| 
Patch