Skip to content
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

Determine what tables are needed for the Music features #20

Open
tgoins opened this issue Jul 28, 2018 · 1 comment
Open

Determine what tables are needed for the Music features #20

tgoins opened this issue Jul 28, 2018 · 1 comment
Assignees

Comments

@tgoins
Copy link
Member

tgoins commented Jul 28, 2018

No description provided.

@tgoins tgoins self-assigned this Jul 28, 2018
@brandonbothell
Copy link
Member

We'll probably need to have a role ID in the guild settings for DJs, and a way to set that with the bot. We'll also need to have a boolean that determines whether or not the guild has the option enabled to only let DJs skip music and clear the queue. Not sure we'll need anything else, because if we want the queue to persist through bot restarts we can just use Redis.

Actually, we may also need a boolean for whether or not a guild is banned from using music features. Same thing for users.

@tgoins tgoins transferred this issue from Nightwatch/-DEPRECATED-db Nov 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants