7 posts tagged with "updates"

We're only halfway into the summer, but there have already been a lot of changes to Countr! We're excited to share these changes with you and hope that they enhance your counting experience.

At Promise Solutions, we're always looking for ways to improve Countr. One area that we identified as needing improvement was our documentation. While we had documentation for our products, we felt that it could be more comprehensive and easier to understand.

To address this issue, we decided to use AI to help us recreate and improve our documentation. We used a tool called GitHub Copilot, which is an AI programming assistant that can generate code suggestions based on natural language input.

We're proud to announce that Countr is now counting in 100,000 guilds! We've come a long way since we first launched Countr back in July 2018, and we're excited to see what the future holds. We'd like to thank everyone who has been using Countr, and we hope you continue to enjoy Countr for years to come!

It's been requested for a while now, and we're finally ready to release it. Position roles are a new type of role that is given to someone based on their position on the leaderboard. For example, if you have a role called "Top Counter" then this can be given to the person in first place on the leaderboard.

It's still in BETA so let us know if you have any issues!

We've gotten multiple reports about "removing all users from a role" being quite buggy and not working as expected. Users that want this feature usually want to remove the previous user from a role to give it to the new user, so ... we just made it its own action.

To cut the long story short, we've added a new action called "Unique role" that will remove the previous user from the role, and add it to the new user. It's a lot more reliable than the "Remove all users from role" action, and it's a lot less reliant on cache (which is why it was buggy in the first place).

There's currently some issues with interactions, we're working to identify the problem and solve it. It doesn't happen in our test environment though, it's quite rare and happens after some time, so we've increased our logging capabilities on the bot and, hopefully, we'll be able to identify it as soon as possible.

Thanks for being patient, we'll keep you posted! If you haven't seen yet, check out this blog post for more details on our big upgrade we did last week!

This is a follow-up to our previous blog post, we're just announcing that the rewrite is here! Check out the previous blog post for more details about the changes.

There's a lot of changes, which also means a lot of things might've been missed or broken in the update, so please let us know in the support server if you see anything!