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

# ER:LC Server Logs

> Mirror in-game activity to Discord channels in real time.

Once [ER:LC is linked](/configuration/erlc-integration), Warden can forward player activity to Discord as it happens — no one needs to run a command for each event.

Need a snapshot on demand? Staff can still pull recent history with **`/erlc logs`**, **`/erlc joins`**, **`/erlc kills`**, and **`/erlc modcalls`**. See [Commands](/configuration/commands#erlc-server).

## Log categories

Each type is configured independently under **`/config`** → **ER:LC Server Logs** → **Edit configuration options...**

| Category         | Default message idea          |
| ---------------- | ----------------------------- |
| **Join Logs**    | Someone entered the server    |
| **Leave Logs**   | Someone left                  |
| **Kill Logs**    | Kill event between players    |
| **Modcall Logs** | Staff responded to a modcall  |
| **Command Logs** | Player ran an in-game command |

## Per-category options

<Steps>
  <Step title="Enable or pause">
    Toggle each log type without affecting the others.
  </Step>

  <Step title="Route to a channel">
    Pick the Discord text channel for that event stream.
  </Step>

  <Step title="Customize the line">
    Edit the message template and insert placeholders from **Variables**.
  </Step>

  <Step title="Save">
    Click **Save** — unsaved template edits are discarded if you navigate away.
  </Step>
</Steps>

## Placeholders

Join and leave templates commonly use `{player.name}`, `{player.id}`, and `{player.hyperlink}` plus any `{time…}` format from [Variables](/configuration/variables).

Kill, modcall, and command templates add context-specific tokens — `{killer}`, `{killed}`, `{moderator}`, `{caller}`, `{command}`, and others. The in-panel **Variables** button lists what each log type supports.