-
Notifications
You must be signed in to change notification settings - Fork 11
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
Move recital roles to p!stats card #78
Comments
Ill make some card designs in the next few days in between piano practice. God smite me if I don't. |
Having thought about this for a bit, I'm convinced that the right thing to do is to convert the stats card to an embed. Several reasons:
|
So here's a first stab at badges and the graphics we'll need:
I think that's a good start for now. Looking at the old list of achievements we floated around I do like the idea of "focused" as well, but we can worry about that later. Note that we'll need to upload the emojis first before the bot changes, because the bot requires the IDs of the emojis. |
I believe this is a bad idea and were better off simply listing out the recitals parcipated and then give a badge based on total recitals played like 1 5 10 15 20, bad idea because this is going to just increase work for the recital managers and theyre already so unmotivated to do half of the things we ask of them. |
I still disagree regarding the recitals. First, it shouldn't be any more work for the RMs than what is currently happening. In fact it should make it easier, if the bot can batch process an entire role into a recital code (i.e. everybody with role "Performer" gets recital code 36 - that could be one command). The second reason is that early recital badges are a point of pride for our members with more lengthy tenures and I'd rather keep that by not reducing recital participation to "number of recitals played". It's possible that they don't need to be badges but a plain-text list seems like it'd be rather unaesthetic... |
I'm just unsure how to make these recital badges work. |
Quick triage comment: this is still a good idea, it's just probably more work than it's worth right now. |
No description provided.
The text was updated successfully, but these errors were encountered: