Skip to main content
Before your staff can start launching session votes or posting session images, Burger Bot needs to know where to send everything and how your sessions are structured. This guide walks you through every session-related configuration option so you can get your ERLC workflow running exactly the way you want it.

​
Overview

Burger Bot’s session features are powered by a handful of key configuration settings. These settings control where votes are posted, how many votes are needed to start a session, where session images land, and which session types are available to your team. All of these options are managed through the /config command.
All session configuration is handled under /config. Navigate to the session-specific settings within that command to access the options described on this page. Changes take effect immediately after saving.

​
Configuration Options

​
Session Vote Channel

The channel where /sessionvote posts vote embeds. This should be a dedicated channel your community monitors so they can participate in votes quickly. Without this set, /sessionvote will not function. Setting: session_vote_channel Configured via: /config channels

​
Vote Threshold

The number of votes required for Burger Bot to consider a session approved and trigger the session start notification. Set this based on your community size — a threshold that’s too high can make sessions hard to start, while one that’s too low may not represent genuine community interest. Setting: vote_threshold Configured via: /config session Default: 5

​
Session Images Channel

The channel where /sessionimages submissions are posted. Keep this separate from your vote channel to maintain a clean, browsable archive of session screenshots. Setting: session_images_channel Configured via: /config channels

​
Session Types

The list of valid session types available when using /sessionvote and /sessionimages. Burger Bot includes common defaults (Patrol, Raid, Tryout, Training, SSU), but you can customize this list to match your server’s specific structure. Setting: session_types Configured via: /config session

​
How It All Works Together

Here’s the full flow once your session configuration is in place:
  1. A staff member runs /sessionvote Patrol — Burger Bot posts a vote embed to your session vote channel.
  2. Community members react to cast votes — Burger Bot tracks progress toward your vote threshold in real time.
  3. When the threshold is reached — Burger Bot sends a session start notification automatically.
  4. Staff post screenshots during or after the session using /sessionimages — embeds land in your session images channel.
Keep your session vote channel and session images channel separate. Mixing them makes it harder for your community to track active votes, and harder for you to browse your image archive later.
If either the session vote channel or the session images channel is deleted or becomes inaccessible to Burger Bot, the related commands will stop working. Make sure Burger Bot has Send Messages and Embed Links permissions in both channels.

Session Vote

Launch a community vote to start an ERLC session with real-time threshold tracking.

Session Images

Post official ERLC session screenshots to your configured session images channel.

Configuration Reference

Full reference for all /config session settings and accepted values.

Staff Management

Manage staff promotions and infractions alongside your session workflow.