- Added 2 new fields to creds.yml -> TwitchClientId and TwitchClientSecret
- Users now have to provide them in order to use twitch stream notifications as Twitch is shutting down old api on 18th of February 2022
- Possibly fixed some issues with streams randomly getting cleared
- Added an incomplete trovo stream notification provider
- Some renamings and code cleanups
- Chained method calls, binary expressions and binary patterns will now break into newlines
- Type param constraints and base constructor calls will be on the new line
- Added credentials.json -> creds.yml migration
- Migrated credentials.json fields are:
- Token
- OwnerIds
- GoogleApiKey
- OsuApiKey
- CleverbotApiKey
- TotalShards (although you should set this from Coordinator's coord.yml TotalShards, so this setting will usually have no effect)
- PatreonAccessToken and PatreonCampaignId
- VotesUrl and VotesToken
- BotListToken
- RedisOptions
- LocationIqApiKey and TimezoneDbApiKey
- CoinmarketcapApiKey
- Sharding with coordinator now works properly
- Documented creds.yml RestartCommand - it has no effect when coordinator is starting the bot
- Regenerated creds_example.yml
- Removed all db migrators as the v3 requires the user to have updated 2.x all the way
- TotalShards in creds.yml gets overriden by coord.yml's TotalShards if the bot is ran through coordinator (more precisely, by the command line argument to the bot)
- Coordinator now runs on http://localhost:3442 by default, you can change this in appsettings.json
- This is done because of macos https issues
- Primarily because https for regular users is a massive hassle. Coordinator shouldn't be exposed anyway
- Minor cleanup
- creds.yml now loads and reloads properly (from the current directory, like credentials.json)
- added empty creds.yml to repo, and added it to .gitignore