You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature:
it would be nice if you could compare more users with each other and use a player as base for example:
time compare @userbase@user1@user2
User1 is 3 hours ahead of userBase, User2 is 1 hour behind of userBase (preferably printed out in a list in order of time (and an override would be cool to sort on order of mentioned)
Feature:
it would be nice if you could compare to a timezone so for example
time compare UTC @user1
Feature:
list of all timezones which are used in the current discord server
time listTZ
Feature:
a method of calculating a time where most people or all people are likely be to awake in a certain timezone format. you could call this by using a @ROLE, @user@user@user or #channel (all the players who got acces to that channel) Example:
time calculate UTC @user1@user2 (user1 utc -4 user2 utc +4)
recommended time: UTC 12:00 - 16:00
The text was updated successfully, but these errors were encountered:
Feature:
it would be nice if you could compare more users with each other and use a player as base for
example:
time compare @userbase @user1 @user2
User1 is 3 hours ahead of userBase, User2 is 1 hour behind of userBase (preferably printed out in a list in order of time (and an override would be cool to sort on order of mentioned)
Feature:
it would be nice if you could compare to a timezone so for example
time compare UTC @user1
Feature:
list of all timezones which are used in the current discord server
time listTZ
Feature:
a method of calculating a time where most people or all people are likely be to awake in a certain timezone format. you could call this by using a @ROLE, @user @user @user or #channel (all the players who got acces to that channel)
Example:
time calculate UTC @user1 @user2 (user1 utc -4 user2 utc +4)
recommended time: UTC 12:00 - 16:00
The text was updated successfully, but these errors were encountered: