-
Notifications
You must be signed in to change notification settings - Fork 17
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
[Feat] Add a countdown for the shutdown command. #191
Comments
Lezetho on Discord: we could do discord timestamps as it's a good solution and it's already built into discord however they can get unreliable sometimes. what i propose is that we do like it'll say "60 seconds" then "30 seconds" and in the last 10 seconds it'll then use a timestamp to finish it off, making it probably more reliable |
Me on Discord: yeah but if the client's internal rtc is off itll still be unreliable, you want it or not, so, i still think its good way to do it, and it shows that "its actually restarting", for example people usually lile more ubuntu's poweroff screen, because the seconds count down while zorin's doesnt |
Lezetho on Discord: hmm fair point |
Sorry green, the template auto assigned you. |
HOW AM I STILL BEING NOTIFIED FOR EVERY COMMENT YOU MAKE |
Checklist
Problem
When shutting the bot down it tells you that if you don't do anything it'll be shut down in 60 seconds, a countdown could be useful and look better.
Proposed solution
Use discord timestamps
![image](https://private-user-images.githubusercontent.com/140397732/400854246-cfc4b222-c780-4ea3-b592-ff39306edbe7.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg5Njg3NzEsIm5iZiI6MTczODk2ODQ3MSwicGF0aCI6Ii8xNDAzOTc3MzIvNDAwODU0MjQ2LWNmYzRiMjIyLWM3ODAtNGVhMy1iNTkyLWZmMzkzMDZlZGJlNy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjA3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIwN1QyMjQ3NTFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1kNjA3NmQxMDI1Y2QxYTM3MjQwOWYwMzQ1MWIyZDY2M2MwNDZiNjc0MmJmZWQ3YWQ5MDQzZjk1NjZlYzM4MzJhJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.lFFWtt8awhte07uekoKK-kr_mdOgY9JL3nmg9TtrbgA)
Also adding a "If the timestamp shows incorrectly, your time or the servers is not right."
Alternatives considered
Editing the message but its too API intensive and not practical.
Additional context
This is a valid code to get the rich timestamp, apply a 60 sec delay and send it
(One shown in the screenshots)
The text was updated successfully, but these errors were encountered: