> ## Documentation Index
> Fetch the complete documentation index at: https://docs.seshy.lol/llms.txt
> Use this file to discover all available pages before exploring further.

# ER:LC Integration: Connect Your Private Server to Discord

> Connect Seshy to your ER:LC Private Server for live player counts, command logs, kill logs, vehicle tracking, ban management, and real-time server status.

Running an ERLC community without a live feed into your Private Server means constantly context-switching — tabbing into the game to check player counts, pulling up the ban list manually, or waiting for staff to relay what's happening in-game. Seshy's ER:LC Integration eliminates that entirely. By connecting directly to the ER:LC Private Server API, Seshy pulls live data from your server and surfaces it in Discord: who's online, what commands are being run, every kill logged with full context, every vehicle spawned, and a self-updating server status dashboard your whole community can see.

## Overview

The ER:LC Integration module creates a persistent, real-time bridge between your ER:LC Private Server and your Discord server. Once connected, Seshy continuously syncs data from the game into dedicated Discord channels — no manual updates, no polling commands. Your staff team gets everything they need for moderation and session management without ever leaving Discord, and your community gets live visibility into server health and activity.

<Note>
  Your Private Server API key is encrypted before being stored by Seshy. It is never exposed in Discord, logs, or error messages.
</Note>

## Setup

<Steps>
  <Step title="Get your Private Server API key">
    Open ER:LC and navigate to your Private Server settings. Under the **API** section, copy your Private Server API key. This key is unique to your server and authorizes Seshy to read your live game data.
  </Step>

  <Step title="Open Seshy's ER:LC settings">
    In your Discord server, run `/settings` and navigate to the **ER:LC Integration** section.
  </Step>

  <Step title="Paste your API key and test the connection">
    Enter your API key in the designated field and click **Test Connection**. Seshy will make a live call to the ER:LC API to verify the key is valid and your server is reachable.
  </Step>

  <Step title="Confirm and begin syncing">
    Once the connection test passes, Seshy confirms the integration is live and begins syncing data immediately. Player counts, logs, and status information will start populating your configured channels within seconds.
  </Step>
</Steps>

## Features

<CardGroup cols={2}>
  <Card title="Player List & Tracking" icon="users" href="/modules/erlc-integration">
    View every player currently in your ER:LC server with live counts, join and leave tracking, and full player detail views including team, rank, and in-game permissions.
  </Card>

  <Card title="Command Logs" icon="terminal" href="/modules/erlc-integration">
    See every in-game command executed, with the user who ran it, the exact command, and a timestamp — essential for auditing admin actions and moderation consistency.
  </Card>

  <Card title="Kill Logs" icon="skull" href="/modules/erlc-integration">
    Monitor every kill in your server with killer name, victim name, weapon used, and timestamp. Indispensable for RDM investigations and enforcement decisions.
  </Card>

  <Card title="Vehicle Tracking" icon="car" href="/modules/erlc-integration">
    Track every spawned vehicle with its owner, spawn location, and vehicle history. Spot suspicious patterns like repeated high-speed spawns near populated areas before they become incidents.
  </Card>

  <Card title="Ban Management" icon="ban" href="/modules/erlc-integration">
    View and manage your full ER:LC ban list directly in Discord, including the reason, the moderator who issued the ban, and the timestamp — cross-referenced with Discord moderation history.
  </Card>

  <Card title="Mod Call Tracking" icon="headset" href="/modules/erlc-integration">
    See every in-game moderation call with caller details, the responding staff member, response time, and resolution status. Hold your team accountable to fast, consistent response.
  </Card>

  <Card title="Queue Monitor" icon="list-ol" href="/modules/erlc-integration">
    Check your server's join queue in real time — current queue length, estimated wait times, and priority player status. Manage capacity confidently during peak hours.
  </Card>

  <Card title="Server Status Dashboard" icon="gauge-high" href="/modules/erlc-integration">
    A single Discord message displaying live player count, server uptime, and overall health. Updates itself continuously so it never goes stale.
  </Card>
</CardGroup>

<Tip>
  Pin the Server Status Dashboard message in a public channel so your community can check live server health at any time without asking staff. Because it self-updates, it stays accurate around the clock with no maintenance required.
</Tip>

## Voice Channel Commands

Seshy supports in-game ER:LC commands that interact with Discord voice channels, making it easy to coordinate staff and event scenes without leaving the game. These commands require the Events Webhook to be configured in `/settings` → **ER:LC Integration** → **Events Webhook**.

| Command              | Description                                                                                                           |
| -------------------- | --------------------------------------------------------------------------------------------------------------------- |
| `;vc <abbreviation>` | Teleports all nearby in-game players to the Discord voice channel matching the given abbreviation                     |
| `;ss`                | Staff Scene — instantly moves all nearby in-game members to a designated staff voice channel for private coordination |

Configure the abbreviation-to-channel mappings in `/settings` → **ER:LC Integration** → **Voice Channels** so each abbreviation resolves to the right VC in your server.

## Configuring Data Channels

Each type of ER:LC data can be routed to its own dedicated Discord channel, keeping command logs, kill logs, and player tracking separate and easy to navigate.

Set up your channel routing in `/settings` → **ER:LC Integration** → **Channels**:

<AccordionGroup>
  <Accordion title="Command Log Channel" icon="terminal">
    All in-game command usage posts here. Designate a private staff channel so your leadership team can audit admin actions without the logs cluttering public spaces.
  </Accordion>

  <Accordion title="Kill Log Channel" icon="skull">
    Every kill event posts here in real time. Use a staff-only moderation channel so the team can review and act on RDM reports immediately.
  </Accordion>

  <Accordion title="Player Tracking Channel" icon="users">
    Join and leave events post here, giving you a live record of who entered and exited your server throughout each session.
  </Accordion>

  <Accordion title="Mod Call Channel" icon="headset">
    In-game moderation calls post here with full context. Staff monitoring this channel can respond to calls without switching into the game.
  </Accordion>

  <Accordion title="Server Status Channel" icon="gauge-high">
    The self-updating server status dashboard lives here. Pin the message and point your community to this channel for live server health.
  </Accordion>
</AccordionGroup>

## Per-Role Permissions

Not every staff member needs access to every ER:LC data feed. Seshy lets you configure exactly which Discord roles can use each ER:LC command and see each data channel.

Set per-role permissions in `/settings` → **ER:LC Integration** → **Role Permissions**. Assign command access by rank — for example, only Senior Moderators and above can use ban management commands, while Patrol Officers can view the player list but not issue bans. This gives your community precise control over who can act on in-game data through Discord, matching your existing staff hierarchy without any compromise.