-
-
Notifications
You must be signed in to change notification settings - Fork 255
AoC countdown #81
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
AoC countdown #81
Conversation
jerbob
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
sco1
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only general caveat I can see is to be cognizant of the rate limits with the regular presence change. Discord's Rich Presence Payload supports an end timestamp for "time remaining" which may be better suited in the long run.
Looks great for now, but there's some more fun tinkering with Rich Presence that can still be done.
|
I think the ratelimit for presence changes is pretty low (iirc once every 15 seconds, I will check). Bots cannot make use of rich presence at this time because it is something controlled via a local websocket which bots don't have. |
This adds a few features regarding countdowns and notifications.
I've added a couple config things but they default to things already in the server so no environment changes are required.