You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+21-7Lines changed: 21 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -6,12 +6,26 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
6
6
7
7
# [Unreleased]
8
8
9
+
### Added
10
+
- You will no longer need to view your bot debug logs from Heroku. `debug` will show you the you the recent logs within 24h through a series of embeds.
11
+
- If you don't mind your data (may or may not be limited to: user ID, guild ID, bot name) be on the internet, `debug hastebin` will upload a formatted logs file to https://hastebin.com.
12
+
-`debug clear` will clear the locally cached logs.
13
+
- Local logs are automatically cleared at least once every 27h.
14
+
9
15
### Fixed
16
+
- Will no longer show `Unclosed client session` and `Task was destroyed but it is pending!` when the bot terminates.
10
17
-`thread.create` is now synchronous so that the first message sent can be queued to be sent as soon as a thread is created.
11
18
- This fixes a problem where if multiple messages are sent in quick succession, the first message sent (which triggers the thread creation) is not sent in order.
12
-
13
19
- Trying to reply to someone who has DMs disabled or has blocked the bot is now handled and the bot will send a message saying so.
14
20
21
+
### Changed
22
+
-`print` is replaced by logging.
23
+
- New environment variable introduced: `LOG_LEVEL`.
24
+
- This influences the amount of messages received in Heroku logs.
25
+
- Possible options, from least to most severe, are: `INFO`, `DEBUG`, `WARNING`, `ERROR`, `CRITICAL`.
26
+
- In most cases, you can ignore this change.
27
+
-`on_error` and `CommandNotFound` are now logged.
28
+
15
29
# v2.13.4
16
30
17
31
### Changed
@@ -20,7 +34,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
20
34
# v2.13.3
21
35
22
36
### Fixed
23
-
- a typo in the config options.
37
+
-Fixed a typo in the config options.
24
38
25
39
# v2.13.2
26
40
@@ -53,22 +67,22 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
53
67
54
68
### Added
55
69
- Named colors are now supported! Over 900 different common color names are recognized. A list of color names can be found in [core/_color_data.py](https://github.com/kyb3r/modmail/blob/master/core/_color_data.py).
56
-
- Named colors can be set the same way as hex. But this can only be done through `?config set`, which means database modifications will not work.
57
-
- For example: `?config set main_color yellowish green`.
70
+
- Named colors can be set the same way as hex. But this can only be done through `config set`, which means database modifications will not work.
71
+
- For example: `config set main_color yellowish green`.
58
72
- New config var `main_color` allows you to customize the main Modmail color (as requested by many). Defaults to Discord `blurple`.
59
73
60
74
# v2.12.3
61
75
62
76
### Fixed
63
-
- Patched a bug where `?logs` sub-commands were accessible by anyone.
77
+
- Patched a bug where `logs` sub-commands were accessible by anyone.
64
78
- Patched a bug where an error was raised if there was an open thread where the recipient had left the server.
65
79
66
80
Huge thanks to Sasiko for reporting these issues.
67
81
68
82
# v2.12.2
69
83
70
84
### Fixed
71
-
- Fixed a bug in self-hosted `?update` command.
85
+
- Fixed a bug in self-hosted `update` command.
72
86
73
87
# v2.12.1
74
88
@@ -97,7 +111,7 @@ In the future, the Modmail API (https://modmail.tk) will be deprecated. This is
97
111
-`logs closed-by [user]` this returns all logs closed by a certain user
98
112
99
113
### Fixed
100
-
-`?activity listening to music` no longer result in two "to"s ("listening to to music").
114
+
-`activity listening to music` no longer result in two "to"s ("listening to to music").
101
115
- This may require you to change your activity message to accommodate this fix.
102
116
- A problem where `main_category_id` and `log_channel_id` weren't updated when their corresponding channel or category get deleted.
0 commit comments