The MyLMU Discord bot posts team alerts into channels you choose. Setup happens in Team Settings (no Discord slash commands required). Slash commands are optional shortcuts once the bot is linked.
Webhooks remain an optional fallback when a bot channel is not set for that alert type.
What you get
| Feature | Free | Pro (team owner) |
|---|---|---|
| Install bot + link server | ✓ | ✓ |
| Pick channels in Settings | ✓ | ✓ |
| Lap record posts | ✓ | ✓ |
| Session result posts | ✓ | ✓ |
| Weekly schedule digest | ✓ | ✓ |
| Next-race ping (optional) | ✓ | ✓ |
| Digest category filters & quiet hours | ✓ | ✓ |
| Team event / lineup / reminder posts | ✓ | |
| Talk announcements → Discord | ✓ | |
| Role ping on event reminders | ✓ | |
| Day-of event briefing | ✓ | |
/mylmu events (optional) | ✓ |
Personal race-schedule reminders still use a personal webhook — see Personal Discord reminders.
Install (Settings-first)
- Open Dashboard → Teams → [your team] → Settings.
- Under Discord Integration, open MyLMU Discord bot.
- Click Add to Discord and authorize the bot for your team’s server.
- Back in Settings, pick channels for lap records, session results, and digests.
- (Pro) Pick an events channel and optional ping role.
- Use Test next to a bound channel to verify delivery.
- Toggle digests, categories, quiet hours, and places-gained as needed.
Pause vs unlink
- Pause (switch) — keeps the server and channel bindings; stops all Discord delivery for the bot install (bot channels and webhook fallback) until you resume.
- Unlink & remove bot — deletes the MyLMU link and removes the bot from Discord. Webhook fallbacks keep working if configured (and the bot is gone).
Already added the bot?
Use Advanced: already in server → link token, then /mylmu link in Discord. Prefer Add to Discord when you can.
Optional slash commands
Configure everything in Settings when possible. In Discord (Manage Server for write commands):
| Command | What it does |
|---|---|
/mylmu help | Short usage |
/mylmu status | Link health and channels |
/mylmu set-channel / clear-channel | Bind or clear a channel |
/mylmu set-role | Event ping role (Pro) |
/mylmu config | Weekly / next-race digests |
/mylmu test | Test embed |
/mylmu upcoming | Official LMU races |
/mylmu events | Team calendar (Pro) |
/mylmu unlink confirm:true | Hard unlink + remove bot |
Slash commands need a public Interactions URL on the Discord app. Settings works without them.
Digests
- Weekly schedule digest — Mondays, into the digest channel
- Next-race ping — about two hours before the next official race
- Categories — limit digests to selected RaceControl categories
- Quiet hours (UTC) — suppress digests (not lap/results) during a window
Pro teams also get a day-of event briefing in the events channel when a calendar event is within about six hours.
Webhooks (fallback)
Under Advanced · Webhook fallback, you can still paste webhook URLs for lap records, session results, and events. MyLMU prefers the bot channel when one is set; otherwise it uses the webhook.
Privacy
Linking the bot stores your Discord server id and channel / role ids so MyLMU can post alerts. It does not read Discord message history. Personal Discord account ids are not required for team channel delivery.