CommunityOne Discord Bot Changelog

Improvement:

- Updated our pricing pages
- Added waitlist for the upcoming new features
- Revamped how members submit their Steam name to reduce error rate
- Now you can vote for the game of the month and refer ur friends to vote

Improvement:

- Added a web3 buying.staking quests (final testing)
- Added better error logging for debugging
- Added a email onboarding process
- Tracked voice channel text data

Fixes:

- Fixed analytics moderators and verification role issues

Improvement:

- Added better logger for bug detection
- Integrated better onboarding emails
- Allowed users to download their .txt git file

Fixes:

- Fixed the issues regarding manual quests

Improvement:

- Added git integration for Spark. 

Improvement:

- Improved the save bar on mobile so that it is not easily missed
- Decoupled Hype Engine from Analytics so that you can add and remove any channels on the dashboard. 
- Changed UI for hype engine and let people know that we create two channels for them. 

Fixed:

- Fixed the issue of analytical channels were not properly recorded
-Fixed a couple UI issue on the save bar

Improvement:

- Added a connection page where members can connect with walllet or email address. 
- Improved explanations on the difference between steam account name and display name. 
- Allowed players to update their steam display name after submitting a claim request.
- Created redirect URLs so that we can track whether a user visits the custom quests URLs. 

- Added use cases for preTGE, post TGE
- Added tutorial on how to read your analytics

NEW:
- We are making available our TypeScript/Javascript SDK: https://www.npmjs.com/package/communityone
Improvements:

- Our API now returns required role id as string (for improved compatibility with JS and languages with limited integer bit sizes).

Improvements:

- Improved reliability when creating private channels.
- We now ensure allowed member/roles get read_message_history permission on any private channel created by the bot.

Fixes:

- [1] Fixed an issue that prevented proper configuration of required/issued role data for custom quests.
- Removed Testing Role setting.

Improvements::

- Improved visual presentation of testing mode description text.

NEW:

- We now support testing mode for custom quests in the API/SDK.
- We now include a testing_mode parameter in custom quest related endpoints. Make sure to update your SDK!