You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Koala extension does this refer to (if applicable)
Verify
Is your feature request related to a problem? Please describe.
When setting up large, or tournament scale servers there is no easy way to easily make one react for role per university
Describe the solution you'd like
When using a command such as k!Verify addUni * would create a role for each university and set up
k!Verify addUni Southampton would create the 'Uni of Southampton' role and create a verify with that new role and @soton.ac.uk
Both of these would first require confirmation that x roles and x verify thingies will be set up, requiring the user to reply 'Y/N'
Possibly check current roles to see if one with 'Southampton' or similar already exists and use that (if the user wants) so previous infrastructure doesn't need to be torn down
Alternative Solution:
Allow users to input a json file with role names and email suffixes and either use roles with those names or make them
Describe alternatives you've considered
N/A (other than just manually doing it)
Additional context
Contact me for a list of the emails, check if making public is a good idea
The text was updated successfully, but these errors were encountered:
What Koala extension does this refer to (if applicable)
Verify
Is your feature request related to a problem? Please describe.
When setting up large, or tournament scale servers there is no easy way to easily make one react for role per university
Describe the solution you'd like
k!Verify addUni *
would create a role for each university and set upk!Verify addUni Southampton
would create the 'Uni of Southampton' role and create averify
with that new role and@soton.ac.uk
Alternative Solution:
Allow users to input a json file with role names and email suffixes and either use roles with those names or make them
Describe alternatives you've considered
N/A (other than just manually doing it)
Additional context
Contact me for a list of the emails, check if making public is a good idea
The text was updated successfully, but these errors were encountered: