CommunityOne Discord Bot Changelog

Improvements:

- Adding save button to all the quests configuration
- Moving the language configuration to Spark on the config dashboard
- Adding "/check-configuration" on the server
- Only allow for spark advance settings when the bot is configured

Bugs:

- Remove unsubscribed email from the configuration dashboard 

Improvements:

- Making UI for the general pages to look prettier
- Now our analytics will have updated mods list per server once a day

Bugs:

- Update the way we fetch server roles so that people with our custom bots can get it as well. 
- Move operations of fetching mods id from front-end to back end workflow, so that larger servers wouldn't face this issues
- Enable/Disable spark!

Improvements:

Replaced third party discord oauth with our own auth and remove all unnecessary permission requirements

Fixes:

Found another bug on terms of letting large server setup analytics configuration, fixed now

Improvements:

Adding initial configuration for quest engine. If you have our alpha code, u can now set it up yourself

Fixes:

Adding more async operations on our analytics so that large servers (60k+) won't face timeout errors when setting up their analytics config

Improvements:

Now you can include annoucement and threads channels for our analytics!

Fixes:

Fixing the issues that sometimes your Discord server name is not updated on our server list

Fixes:

Adding fail safe measure to make sure analytics is enabled whenever you setup the analytics configuration on dashboard. We notice there are edge cases where dashboard is setup but the "enable" part disappeared due to caching issues

Fixes:

- Update the spark configuration message to alert users that all changes are updated via Discord
- For servers that do not have our bot, we've speed up the page loading and direct to "invite bot page"

Improvements:

- A bunch of backend changes for an upcoming feature Louisa doesn't want me to talk about in the logs.

Fixes:

- Fixes for... well, see above.
- [1] Fixed issue where chatbot configuration was not being properly reloaded in some cases.