1 |
# Changelog |
2 |
|
3 |
### development |
4 |
* Added new and improved pagination system |
5 |
* Upgraded the queue management system |
6 |
* Fixed AFK systems not working properly (#84) |
7 |
* Updated config schema |
8 |
|
9 |
### v4.0.0-alpha1 |
10 |
* Fixed typo in a welcome message |
11 |
|
12 |
### v4.0.0-alpha |
13 |
* Performance Improvements |
14 |
* Now Using MongoDB as Database instead of SQLite **[BREAKING CHANGE]** |
15 |
* A full refactor of the API |
16 |
* Dockerized the project |
17 |
* Customizable data directory path |
18 |
* Fixed autocomplete interaction issues |
19 |
* Add license notices and other details to the about command |
20 |
* Minor bug fixes |
21 |
* Added profile filter for checking banned words/tokens in user profiles |
22 |
|
23 |
### v3.0.0-alpha |
24 |
* Improved channel locking system |
25 |
* Added welcomer with random welcome messages support |
26 |
* Added permission based command system [BREAKING CHANGE] |
27 |
* Added config management command |
28 |
* Added embed builder command |
29 |
* Snippets, and some other commands now support embed schemas |
30 |
* Improved automod system |
31 |
* Added AntiJoin system |
32 |
* Auto mute user if they were muted before and left the server |
33 |
* Added debug logger for better error investigation |
34 |
* Improve the strategy of loading services |
35 |
* Added repeated text filter channel exclution, spam filter exclusions will now also apply to this filter |
36 |
* Added mention input parser |
37 |
* Integrate with PM2 process manager |
38 |
* Performance enhancements |
39 |
|
40 |
##### Breaking Changes!!! |
41 |
Some commands will now require specific permissions. Users without those permissions will not be able to run those commands. |
42 |
The required permissions are given below: |
43 |
|
44 |
Command |Permission(s) |
45 |
------------------------------|------------- |
46 |
Ban |`BAN_MEMBERS` |
47 |
Kick |`KICK_MEMBERS` |
48 |
Mute |`MODERATE_MEMBERS` (Timeout Members) |
49 |
Clearing messages |`MANAGE_MESSAGES` |
50 |
Setting Channel Permissions |`MANAGE_CHANNELS` |
51 |
|
52 |
Users having the `ADMINISTRATOR` permission will be able to bypass these requirements. Commands not listed here are not affected in this change. |