Describe the bug
When using webhooks, the server uptime is a large negative value. E.g., "-18 day(s), 0 hour(s), -13 minute(s) and -24 second(s)"
Reproduction steps
Set a webhook URL in fdlink.json.
Make sure the botActivities in messages.json to ["Uptime: %uptime_D day(s), %uptime_H hour(s), %uptime_M minute(s) and %uptime_S second(s)"].
Start the server.
Check the bot activity for uptime.
Expected behaviour
The correct, positive uptime should be displayed. E.g., shortly after starting the server, it could look like "0 day(s), 0 hour(s), 0 minute(s) and 40 second(s)"
Describe the bug When using webhooks, the server uptime is a large negative value. E.g., "-18 day(s), 0 hour(s), -13 minute(s) and -24 second(s)"
Reproduction steps
fdlink.json
.botActivities
inmessages.json
to["Uptime: %uptime_D day(s), %uptime_H hour(s), %uptime_M minute(s) and %uptime_S second(s)"]
.Expected behaviour The correct, positive uptime should be displayed. E.g., shortly after starting the server, it could look like "0 day(s), 0 hour(s), 0 minute(s) and 40 second(s)"
Additional context
fdlink.json