How to organize raids and LFG on Discord

Organizing a raid in chat usually ends with a messy list of “+1 healer” replies and three people missing at pull time. On Discord you can do better: a sign-up post with fixed role slots, an automatic bench, a reminder before start and an attendance check from voice. This guide shows how to organize raids on Discord with BotGG’s Parties module, and how to handle quick pick-up groups with /lfg from Games.

Use each tool for what it does best:

• Parties (/party) — planned events with roles and a start time: raids, dungeons, clan wars, scrims, tournaments. Up to 50 roles, each with its own capacity.
• LFG (/lfg) — “need 3 for ranked right now” posts with a player count, an expiry time and an optional temporary voice channel.

What you need

• Manage Server permission, and BotGG on the server (https://discord.com/oauth2/authorize?client_id=1553367772451446804&scope=bot%20applications.commands&permissions=282969912110295).
• A text channel for raid posts, e.g. #raid-signups. The bot needs Send Messages, Embed Links, Create Public Threads, Manage Threads and Send Messages in Threads there.
• Optional: a voice channel where raids happen (for voice checks and attendance) and a category for temporary LFG voice channels.

Everything is configured in the console at https://console.botgg.app; the daily work happens in Discord. All subcommands are listed on the commands page.

Step 1: Configure Parties in the console

Enable Parties and open the Settings tab:

1. Channels — limit where parties can be created (empty = any channel).
2. Creator roles — who may create parties (empty = everyone). Add Raid Leader here on bigger servers.
3. Manager roles — who may edit, ping, lock and close any party (the creator and admins always can).
4. Ping role on create — for example Raiders, so the whole roster sees new events.
5. Sign-up rules — one role per member (default) or several; send members to the bench when a role is full (default on).
6. Automation — reminder before start (15 minutes by default, optionally also by DM), automatic attendance after start (10 minutes), a late window (15 minutes) and auto-close (6 hours after start).

Step 2: Build role templates

Templates save you from typing the roster every week. Open Templates and add rows with emoji, role name and capacity — no free-text parsing needed. The free plan includes 3 templates and 3 open parties at a time; Pro raises that to 25 and 50 (pricing).

Some starting points:

Step 3: Create a raid in Discord

Run /party create template:20-player raid. A form opens with the title, description, roles (prefilled from the template), footer and start time. The start time understands 2026-09-27 20:00, 27/09 20:00, 20:00 (next occurrence) or in 2h, in your server’s timezone, and everyone sees it in their own local time.

Without a template you type roles one per line: 🛡️ Tank 4 means four tank slots, a line without a number is one slot.

The bot posts the roster and opens a thread for questions and the sign-up log. Members click a role button to sign up, Leave to drop out or Join bench to wait as a backup. When a role is full, new sign-ups go to the bench, and when a spot frees up the first person waiting for that role is promoted automatically and pinged in the thread.

With more roles than buttons fit (20 by default), the post switches to numbers mode: members sign up in the thread by mentioning the bot with the role number, e.g. @BotGG 3.

Step 4: Raid night — voice check, ping, attendance

• /party voice channel:#Raid links the voice channel. The roster shows 🔊 next to everyone already connected, and the reply lists who signed up but isn’t in voice, and who is in voice without signing up. The Voice check button repeats that check at any time.
• /party ping who:missing mentions only the people missing from voice; who:role pings one role (for example all healers).
• /party add and /party remove fix the roster by hand; /party lock stops sign-ups before the pull.
• Attendance is taken automatically after the start when a voice channel is linked — present, absent, and late for those who join within the grace window. Use /party attendance take to snapshot it yourself, /party attendance show to see it, and /party attendance set to mark someone excused.
• /party close finishes the event; /party disband cancels it and tells everyone in the thread.

/party stats shows a member’s attendance rate, and the console Attendance tab ranks all members and exports a CSV — handy for loot rules or roster decisions.

Step 5: Quick groups with /lfg

For spontaneous games, enable Games and open Game list: add your games with an emoji, default group size and an optional notify role per game. In the LFG tab pick the LFG channel, a voice category for temporary channels and whether those channels are private, the default expiry, how many active LFGs a member may have and a cooldown.

Members opt in to pings with /lfg notify (or /games play). Then:

1. /lfg create game:Valorant voice:true opens a short form: mode, description, players needed, rank requirement and expiry (30m, 2h).
2. The card appears with Join / Leave / Close buttons and live slots; the game’s notify role is pinged.
3. With voice:true the bot creates a temporary voice channel sized for the group. It disappears when it empties or when the LFG ends.

/lfg list shows open groups and /lfg close ends yours early. For permanent “create your own channel” voice, use Lobbies — see the temporary voice channels guide.

Recommended settings

• Create parties from templates only, and restrict creators to raid leaders on big servers.
• Keep the bench on — backups are promoted automatically and nobody has to watch the post.
• Set the reminder to 15–30 minutes and turn on DM reminders for raids with a fixed start.
• Link the raid voice channel early so attendance is taken automatically.
• For LFG, keep one active LFG per member and a short expiry (60 minutes by default) so the channel stays fresh.

Common mistakes and troubleshooting

“Parties can’t be created in this channel.” The channel isn’t in the allowed list — or, with a different error, the member lacks a creator role. Check Settings in the console. Parties are posted in text or announcement channels, not inside threads.

No thread appears. Threads may be off in Settings, or the bot is missing Create Public Threads in that channel. The bot also needs Manage Threads and Send Messages in Threads.

The start time is rejected. Use one of the formats above; times in the past or more than a year ahead are refused.

Attendance is empty. Automatic attendance needs a linked voice channel and a start time. Link it with /party voice or take it manually.

The temporary LFG voice channel isn’t created. No voice category is set in the LFG tab, or the bot can’t manage channels in that category.

The notify role isn’t pinged. The game has no notify role, pings are turned off in the LFG tab, or members haven’t opted in with /lfg notify.

Want XP and rewards for raiders too? See how to add a leveling system.

FAQ

How many roles can a raid have?

Up to 50 roles with 1–99 slots each. Up to 20 roles get their own buttons; bigger rosters use numbers mode in the thread.

Can a member sign up for two roles?

Only if you enable multiple roles in Settings. By default, clicking another role switches the member.

Does the start time work across timezones?

Yes. You enter it in the server’s timezone and Discord shows it to every member in their local time, with a countdown.

What is the difference between a party and an LFG?

A party is a planned event with a role roster, reminders and attendance. An LFG is a quick “need players now” post with a player count, expiry and optional temporary voice.