Become Legend.

This simple yet powerful message that Bungie launched into the universe that drove us to start resurrecting the warmind Charlemagne. What better way to answer Bungie's call, than to bring guardians and communities together. Five years, 1.5 million registered guardians, and over 100,000 Discord servers later, we have watched as you all embraced her into your clans, into your Discord servers, and into your hearts.

We are so grateful to you all, and we aren't done yet.

However...

This last year, Discord has made a concerted effort to improve privacy and visibility of bots (and warminds) on their service. With that effort, they have completely overhauled their API to support slash ( / ) commands, and are eliminating the ability to see message content without rare and special approval. More info here. Charlemagne's legacy command system uses message content to determine if you sending a command or not by looking for the prefix (!). After August 31st, 2022, Charlemagne will no longer have access to message content.

We weighed the pros and cons of applying for message content permission from Discord and attempting to maintain this legacy system past August 31st versus embracing the new slash commands and upgrading her systems from the ground up. We decided that it was time to upgrade and have spent the last few months converting her commonly used commands over to slash commands. This will allow us to focus on adding new features that we have been forced to put off in order to maintain her legacy system. What does this mean for legacy commands?

After August 31st, her legacy system will no longer be able to detect any new command requests and those commands will be added to the Charlemagne Vault. (This includes D1 commands as they are based on her legacy system.)

Does this mean [insert command here] is gone forever? Like Bungie's Vault, Charlemagne's is also not forever.

---

As of writing this article, there are 2 remaining legacy commands that need to be migrated: !server and !lfg

Server

Server configuration has remained a pain point for many admins. What is the right keyword, how do I disable XYZ, or even just what features are available? Because of that, we are taking this opportunity to move server configuration over to the web. Most features are already supported, but we ask your patience while we finish up adding support for her more complex feature sets such as automated roles.

Are all my settings going to be migrated? While we are able to migrate most settings, her more complicated settings may need to reconfigured. We will announce which settings fall into this category in the coming weeks.

Here's a sneak peak of the upcoming web UI.

Note: Final UI actively being developed

LFG / Events

Lfg and event scheduling is not getting vaulted. It will become /event starting on Sept 1st. Because the systems are completely different, old LFG events and their settings will not be migrated to the new system. At the launch of /event, she will support setting an event channel, alert times, event life times, and discussion categories. We plan to add support for channel filters and access to public events shortly after, and appreciate your patience.

There's so much more to come. Eyes up Guardian.