dreset

{
  "id": 630397,
  "created_at": "2021-02-24T00:03:21.000Z",
  "tag_name": "dreset",
  "nsfw": false,
  "owner_id": "597040433096556544",
  "uses": 3,
  "description": null,
  "restricted": false,
  "shared": false,
  "deleted": false,
  "safe": "unrated",
  "hidden": false,
  "guild_id": "731054936132943883",
  "sharer": "597040433096556544",
  "content": "{=(COMMENT):─── COMMAND CONFIGURATION ───}\n{=(COMMENT):Daily reset time (24-hour clock). Format `HH:MM` MUST be respected.}\n{=(time.reset):00:00}\n{=(COMMENT):Timezone Management. Set \"timezone.offset\" to 0 if it should return UTC date.\nThis corresponds to the amount of hours there is between your personal timezone and UTC.}\n{=(timezone.offset):0}\n\n{=(COMMENT):This is the main prefix for Carl-bot on your server. It will be displayed in the embed's footer with the command usage.}\n{=(prefix):!}\n{=(COMMENT):Make sure you don't name your tag \"reset\", as it's already a built-in command. Possible alternatives are \"dreset\" or \"dres\" or \"res\", but can be anything else, as long as it doesn't conflict with an existing command.}\n{=(tag.name):dreset}\n\n{=(COMMENT):───────────────────────────────────\nThere should be nothing to touch below. Only do it if you know what you're doing.}\n\n{=(COMMENT):Returns the datetime values **in your own timezone** of today and of the reset, in case you want to display them somewhere.}\n{=(hour.in.second):3600}\n{=(timezone.today.unix):{m:trunc(({timezone.offset}*{hour.in.second})+{unix})}}\n{=(timezone.today.datetime):{strf({timezone.today.unix}):%F %T}}\n\n{=(COMMENT):Today's date and time.}\n{=(today.date):{strf({timezone.today.unix}):%F}}\n{=(today.time):{strf({timezone.today.unix}):%T}}\n{=(today.datetime):{today.date} {today.time}}\n{=(today.unix):{timezone.today.unix}}\n\n{=(COMMENT):Tomorrow's date and time.}\n{=(seconds.in.day):86400}\n{=(one.more.day):{strf({m:trunc({seconds.in.day}+{today.unix})}):%F}}\n{=(tomorrow.date):{one.more.day}}\n{=(tomorrow.datetime):{tomorrow.date} {today.time}}\n\n{=(COMMENT):Checking the sign (positive or negative) of the difference between today's date and the reset date.}\n{=(unix.reset):{strf({today.date} {time.reset}:00):%s}}\n{=(unix.diff):{m:trunc({today.unix}-{unix.reset})}}\n{=(diff.sgn):{m:sgn({unix.diff})}}\n\n{=(COMMENT):If it is positive, it means the reset has already happened today and it should take tomorrow's datetime; otherwise today's datetime.}\n{=(reset.to.take):{if({diff.sgn}==1):{tomorrow.date}|{today.date}} {time.reset}:00}\n{=(reset.datetime):{reset.to.take}}\n{=(reset.unix):{strf({reset.datetime}):%s}}\n\n\n{=(COMMENT):Actual time remaining between now and the next daily reset!}\n{=(time.remaining):{td({timezone.today.datetime}):{reset.datetime}}}\n\n{=(COMMENT):Output Management.}\n{=(em.title):Time Until SoS Server Reset}\n{=(em.description):**{time.remaining}**}\n{=(em.footer):{prefix}{tag.name} • Daily Reset Time: {time.reset}}\n{=(em.color):2f3136}\n{embed(color):#{replace(#,):{em.color}}}\n\n{=(COMMENT):Debug variable, in which I call almost all the variables in that code to know which value they return and troubleshoot the command. I very much recommend you do this when debugging your code.}\n{=(debug):__Debug:__\ntoday.datetime `{today.datetime}`\ntoday.unix `{unix}`\ntomorrow.date `{tomorrow.date}`\ntomorrow.datetime `{tomorrow.datetime}`\n\nunix.reset `{unix.reset}`\nunix.diff `{unix.diff}`\ndiff.sgn `{diff.sgn}`\n\nreset.to.take `{reset.to.take}`\nreset.datetime `{reset.datetime}`\nreset.unix `{reset.unix}`\n\nTimezone Management:\ntimezone.today.unix `{timezone.today.unix}`\ntimezone.today.datetime `{timezone.today.datetime}`\n\ntime.remaining `{time.remaining}`\n}",
  "embed": "{\"color\": 5198940, \"author\": {\"name\": \"{em.title}\"}, \"description\": \"{em.description}\"}",
  "last_fetched": "2026-10-21T00:26:02.672Z"
}