-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FR: Add discord role to member with specific event ticket #18
Comments
AIUI, I don't think this is something we can do from the oauth2 flow we're using for authentication. The better option is a discord bot that has appropriate permissions on the server, and it can then manage the groups for people. Would be appropriate work for anyone with skills at writing Discord bots. |
Was hoping it would be easy enough to hook into the existing work to just add a different discord integration to push the role change :( Looks possible but i've not fully read yet> https://gist.github.com/RikoDEV/e6a35ce7cb7fb9880537c0b6e19b35db |
Interesting, didn't know about that. Notes for self:
|
Turns out role connections is the wrong way to do it. It's easier to just connect the app to the server as a bot and then use the API to manage roles on members.
You will now have an option in Settings to Connect to Discord Server. Once done, you will be able to allocate a role to a ticket type. Anytime a ticket type's discord role is changed, or a ticket is created/user changed - roles will be updated. They will also be updated every 15 minutes. Control will only update roles for users that it knows about. If the user isn't in Control's DB, the roles will not be modified. Control WILL remove roles from users it knows about if that user no-longer has a ticket with that role assigned to it. |
Automatically link a discord server & role to an event, then for each user with a valid (or transferred ticket) automatically grant them that role.
Bonus points> Allow the role to be ticket type specific (EG: BYOC gets one role, indoor sleeping another)
The text was updated successfully, but these errors were encountered: