I am running! I mean, rolling!
It's long been a request that Dot get more admin-oriented or role-management abilities, so this update is dedicated to just that. 3.4 adds some nifty new role-granting abilities, as well as refurbishes existing admin menus to make interfacing with Dot's settings easier than navigating a command line. I'm pretty happy with these changes, so I hope you will be too.
First thing's first: For CalRef-only, the I am rolling system has been retired. It was difficult to use at times, since you needed to type things very specifically, and still relied on an on_message structure, with hard-coded roles in Dot's main launcher. Not ideal with how the rest of Dot works. Now there's a new way of doing things which you can access with I cast determination, to bring up a new role menu.
The menu has two drop downs, the first for which role colour you'd like to select (you can only pick one) and the second drop down is for all other self-assigned roles, and you can select as many of those as you want. When you're done, close those dropdowns and hit the Add Roles or Remove Roles buttons, depending on what you want. Alternatively, you can use the Clear All button to remove all your colour and opt-in roles in one click.
For this and other command demonstrations, check the demonstrations on the sidebar, linked to the commands' section in the docs, which has demo videos for everything.
Magical New Admin Abilities: Autoroles
If your server lifestyle finds it prudent to automatically role members upon their arrival, Dot can now help you out with this. Use the new autorole(s) function to summon a menu of roles. Select between one and ten roles that members should receive upon their arrival, close the menu, and click the Set Active or Set Inactive buttons to toggle the feature on or off. If you'd like to delete the set entries, simply bypass the dropdown and click Clear All.
If you need more than ten roles applied to a member on their arrival, probably reconsider your server structure at that point, or let me run your WAA ministry.
Dot's generic invite link does not ask for Manage Role permissions, so if you want to set up autoroles, she will need that permission to actually apply them. Dot will mention this if you try to set them up when she doesn't have the right permissions in your server. You can either grant them to her bot role, or give her another role which has the permissions.
Magical New Admin Abilities: Reaction Roles
Admins now have the ability to set up reaction roles in their server. These are typically static messages in locked channels where members can click certain reactions and receive whatever roles you say they go to. The set reactions command allows you to add, drop, or end reaction role messages.
Establish or add to a reaction message with I cast set reacts add [message url], [emoji], [role ID or ping]
Drop a reaction role from a reaction message with I cast set reacts drop [message url], [emoji]
Terminate a reaction message setting with I cast set reacts end [message url]
For example: I cast set reacts add https://discord.com/channels/869038758299861064/954649444391993395/991133353929609296, :heppy:, @9
You can use set reacts add on the same message link to keep adding react settings to it. If you forget what messages you've set up or wish there were some kind of overview command, well have I got some sweet news for you -- there is.
You can use the new reacts command to show everything you've set up so far, with links to all messages, and what emotes go with what roles. You can use this menu to terminate individual reaction role messages, or to terminate all of them. So reacts to overview, set reacts to add or edit. Hopefully that's pretty straight forward.
If you're picking up a trend between the autoroles and reacts admin commands, you're quite onto something. Going forward, as many admin commands as possible are going to try to follow this interface template: a simple title reminding you what you're looking at, a colour-coded sidebar and light bulb at the bottom corner of the embed that lets you know if it's active or not, and simple buttons or dropdowns allowing you to control all the settings with ease. To this end, I've revised a couple of the existing admin commands, and improve how Dot handles their data internally.
This means that set autopins is being moved to autopins, and set recruiter is being moved to recruiter. Making settings using those should now be super incredibly unbelievably easy.
The rest will take a bit, but we'll get there.
Minor Changes and Bug Fixes
- Fixed an issue in rotato where an image may have repeated.
- Added region banners to the region command (if a region has one set)
- Fixed an issue in bouncer where CalRef re-roles would give up if a role could not be added (such as nitro).
- Added an error handler to report issues with commands that require permissions Dot has not been granted in the local server.
- CalRef-only commands now report as "command not found" when used in other servers.
- Errors triggered through repeaters now present the same error content as through the error handler.
- Fixed an error in eyebeast where bulk deletions would break on logging.
- The sidebar of embeds in colour will now present as the requested colour, in addition to the embedded colour image.
- Fixed an issue in recruit where manually running the command without a set template would disrupt the output.
- Docs now show what update a command was added.
- New footer banner in the command menu.