CommunityOne Discord Bot Changelog

Improvements:

- We now allow for @username placeholder for auto-onboarding greeting!
- Spark auto-onboarding is now off by default.
- ConfigDashboard: Support enabling/disabling disclaimer without deleting the text.
- Backend: We now sync guild active status with db on bot initialization.

Fixes:

- Bot: Fixed edge case where /check-configuration wouldn't work.
- Bot: Fixed issue where /onboard command would be slow to respond.
- ConfigDashboard: Removed empty space at the end of section pages.
- ConfigDashboard: Fixed background color for premium tab.

Improvements:

- The following configurations from the config dashboard are being synced/used with the bot:
    - Disclaimers, Smart Listening Period, Auto-onboarding Greeting.
- Improved /check-configuration output for spark channel (additional permissions being checked and more info displayed).
- We now sync member invite data on analytics configuration changes and on on-demand historical data recording.
- Backend: Reworked the entire syncing mechanism between configuration dashboard and bot.
- Backend: More efficient member invite data recording.

Fixes:

-  Fixed an edge case bug where the bot wouldn't answer when trying the chatbot with /spark test.

Current research:

- Looking into an even more sophisticated bot detection algorithm.

Improvements:

- Added check status button on main menu.
- Renamed /communityone-setup command to /get-started.
- Added warning indicators on configuration status when features enabled but have issues.
- Bot back-end refactor.
- Added deprecation notice on configuration /slash-commands

Fixes:

- Fix issue on /check-configuration when user has a lot of tracked channels.
- Fix issue where guilds with problematic permission configurations with huge influx spikes of new members would make us hit rate limits.

change UI for analytics and make the buttom much bigger

added un-subsrbe feature on the email!

adding checking permissions when loading historical data

Feature push: We've updated Spark so that it will be live on your server when you initially set it up on Dashboard, vs previously that we require you to give us a document or a CP to start

debug: fixing caching issues on dashboard