LFG System

The LFG system now provides a production-ready workflow for creating, hosting, and cleaning up group activities.

How it works

1. Staff configures the Command Container channel, Participant Destination channel, and per-user limits/voice rules in the dashboard.
2. Post the /post_lfg container message in the command channel. Members interact with this embed to propose new events.
3. When an event is created, the bot posts the session details to the Participant Destination channel, handles sign-ups, and tracks status changes.
4. At the scheduled end time—or earlier if voice requirements fail—the bot automatically closes the LFG entry and tidies up the thread/voice channel.

Active-only feeds

• The Participant Destination channel only shows live events; closed posts are removed or archived automatically.
• Hosts can cancel events manually, and the automation will clear the post immediately.

Voice participation enforcement

• When “Require voice participation” is on, the bot verifies that the host or any participant is already in the linked voice channel the moment the scheduled start time hits.
• If nobody is connected—or if everyone joins and immediately leaves—the LFG post closes and the related thread/voice channel is cleaned up.
• Voice channels can persist beyond the scheduled end while members remain; they disappear the instant the channel empties.
• These rules are perfect for events that rely on live comms, preventing empty or abandoned groups from lingering.

Voice Forge integration

• The LFG system plugs directly into Voice Forge so the same automation that manages temporary voice rooms applies to LFG events.
• Hosts still retain manual controls (lock, invite, rename) through Voice Forge while the LFG automation enforces attendance and cleanup.

Host and participant experience

• Hosts see real-time participant counts, voice status, and limit feedback right inside the container message.
• Participants join via buttons or menus and receive reminders about voice requirements when applicable.
• Per-configuration limits keep the feed healthy by preventing a single organizer from launching more concurrent events than allowed.