Releases: MJHeijster/StatBot
v1.6.0
v1.6.0 release
IMPORTANT
Run the StatBotConfiguration application, review the new settings (or ignore them to use the defaults) and press save. Else you will miss some settings. It should work without doing so, but make sure to do this to get the new features.
Also, make sure not to overwrite the appsettings.json when installing a new version, making a backup is always a good idea as well.
Changes:
- Dead chat detection. After a disconnect and dead chat detection is on, it will wait for a while to see if messages are being received. If not, a message will be sent through logging that something might be wrong.
- Admin user commands added:
-
- Link an old username to a current user
-
- Override someone's username
-
- Remove the username override
-
- Linking a userid to a username (in case the user left)
You can also set the admin userid and if server admins can use the admin commands.
pre-release-237
v1.5.0
pre-release-220
v1.4.1
v1.4.0
Changes:
- Names are now stored in a SQLite database, tracking username changes and avatar URIs. If turned on, it will also generate the nicks.txt file filling in all the information.
pre-release-187
Pre-release-187
The nicks.txt file is generated every time the stats are being generated OR every half hour if you don't let StatBot handle it. Make sure you create/set the new settings in appsettings.
Changes:
- 18fefcc Log users with name changes and create the nicks file automatically.
This list of changes was auto generated.
v1.3.1
Feel free to skip this release if you have 1.3.0 installed.
Changes:
- 3894f6a Moved the logic to determine if it should trigger the stats generation to the BotSettings.
If you're upgrading from a version earlier than v1.2.0, make sure to read the changelog for v1.2.0.
v1.3.0
Changes:
- 0d31d07 Added ability to start the generation of the stats through the bot.
If you're upgrading from a version earlier than v1.2.0, make sure to read the changelog for v1.2.0.
v1.2.1
Changes:
- e83b371 Ensure vital configuration is filled.
If you're upgrading from a version earlier than v1.2.0, make sure to read the changelog for v1.2.0.