-
Notifications
You must be signed in to change notification settings - Fork 20
/
info.json
12 lines (12 loc) · 2.38 KB
/
info.json
1
2
3
4
5
6
7
8
9
10
11
12
{
"$schema": "https://raw.githubusercontent.com/Cog-Creators/Red-DiscordBot/V3/develop/schema/red_cog.schema.json",
"author": ["Vexed (Vexed#3211)"],
"name": "BetterUptime",
"install_msg": "Thanks for installing! This cog will replace the default `uptime` command. The difference from Core's uptime command is that is shows the uptime percentage of the bot running and the percentage connected to Discord.\nThis cog writes to config every 60 seconds to prevent data loss. It is also very storage efficient, using under 150 bytes each day the cog runs.\n\n**Please carefully read the information bellow about some of the cog's inner workings.**\n\nWhen you first load the cog, the `uptime` command will say **data may be inaccurate** for first 15 minutes. The cog does try to correct for this as much as possible, so uptime percentages will 'snap' to 100.0% if downtime is only a few seconds. As well as this, the cog will not show the total downtime in minutes if it's under a couple minutes.\n\nWhilst the cog will start showing data from first load, it will ignore all data collected on the UTC date of first load from tomorrow.\n\nOnce the cog's been running for a while, data over 30 days old will no longer be counted in the `uptime` command.\n\nPlease avoid excessively reloading the cog. Whilst it tries to clean up to prevent data loss, there will still be a second or so of downtime added. As well as this, sometimes it can't clean up properly so there could be up to a minute's worth of data loss.\n\nThis cog has docs! Check them out at <https://cogdocs.vexcodes.com/en/latest/cogs/betteruptime.html>",
"requirements": ["pandas", "matplotlib","vex-cog-utils==1.5.9"],
"description": "Replace the uptime command with a rich embed that shows the bot's percentage uptime (both time of the bot being on and time connected to Discord). There is also a new `downtime` command which shows when downtime happened. This cog writes to config every 60 seconds to prevent data loss. It is also very storage efficient, using under 150 bytes each day the cog runs.",
"short": "A better uptime command that tracks the bot's uptime as a percentage over the last 30 days, and has a new `downtime` command that shows when downtime happened.",
"tags": ["utility", "uptime", "meta"],
"end_user_data_statement": "This cog does not persistently store data or metadata about users.",
"min_bot_version": "3.4.0"
}