How to Set Up a Discord Reminder Bot (and When Not to Use One)

Most servers ask for "reminders" and mean one of three different things:

• A one-off nudge. "Remind me about this in two hours." Personal, usually a DM.
• A recurring announcement. Raid night every Tuesday, a weekly check-in, a monthly event.
• A countdown to a fixed moment. A launch, a tournament, a deadline.

They fail for different reasons, so it is worth knowing which one you are solving before you install anything. The first is a scheduling problem. The second is a scheduling problem plus a permissions problem. The third is not really a reminder at all — it is a display problem, and it has a much better answer than a bot.

Here is the failure almost every server hits at least once. A moderator posts:

Raid night starts at 8pm!

Half the server shows up at the wrong hour, and a few show up on the wrong day.

Discord solves this natively and almost nobody uses it. A timestamp written as `<t:1798204500:F>` renders in each reader's own timezone, automatically. The person in Berlin sees their time; the person in Los Angeles sees theirs. Nobody converts anything, and nobody gets it wrong.

The catch is that you need the Unix number, which is not something you can work out in your head. That is what our Discord time converter is for — pick the date, pick the timezone you are scheduling in, and copy the code.

The timezone selector matters more than it sounds. If you are organising an event at 8pm Eastern while sitting in London, entering "8pm" in a tool locked to your own zone produces a timestamp five hours wrong. Setting the zone explicitly is what stops that.

For personal nudges, the lightest option is a bot with a `/remind` command that accepts natural language: `/remind me in 2 hours to post the results`.

Things to check before you commit to one:

• Does it survive a restart? Plenty of small reminder bots keep pending reminders in memory. A deploy or a crash silently drops every scheduled reminder, and nobody finds out until the reminder does not arrive.
• Does it DM or post in channel? DMs are unreliable — a large share of Discord users have DMs from server members disabled, so a DM-only reminder quietly fails for them with no error anyone sees.
• What is the maximum delay? Some cap at 24 hours or a week.

If you are building your own, the durable pattern is to write the reminder to a database with a due timestamp and have a scheduled job sweep for due rows, rather than holding a timer in process.

This is where most setups get messy. Two decent routes:

Discord's built-in Scheduled Events. These support weekly, biweekly and monthly recurrence natively, show every member the time in their own timezone, and let people mark themselves interested. For "every Tuesday at 8pm" this is genuinely the best answer and it needs no bot at all. The limits: a recurring event runs until you delete it, and the intervals on offer are fixed — there is no "every four weeks".

A bot posting on a schedule. More flexible, and necessary if you want the reminder to ping a role, include a link, or change its text. The thing to get right is that the message should contain a freshly generated timestamp each time, not a hardcoded "8pm" — otherwise you are back to the timezone problem.

A recurring timestamp is not a thing, incidentally. `<t:>` encodes one specific second, so a code you wrote for last Tuesday keeps pointing at last Tuesday forever. Recurrence has to come from whatever posts the message.

If what you actually want is "3 days until launch", you do not need a reminder bot at all. Discord's relative timestamp format does it natively:

`<t:1798204500:R>` renders as "in 3 days" and updates itself as the date approaches, without anyone editing the message. Pin it and forget it.

We wrote up the details — including why channel-name countdowns look broken — in how to add a countdown timer to Discord.

The reason most servers end up with three bots is that each one does 80% of what they wanted. If your reminder needs to ping a specific role, post to a specific channel, skip weeks when there is no event, and include a timestamp that renders correctly for everyone — that combination is usually not on offer as a preset.

With VibeBot you describe it instead: "every Tuesday at 6pm Eastern, post in #raids, ping @Raiders, and include a countdown to 8pm." The bot runs under your own Discord application, so it carries your name and avatar rather than appearing as one more shared bot in the member list.