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

# Logging Settings

> Auto-log ER:LC kicks and bans, and let staff log punishments in game with the :log command.

***

## What are Logging Settings?

Logging Settings record moderation actions from your ER:LC server in Melonly. You can auto-log every kick and ban, and let staff log punishments in game with `:log`. These logs show up in the Mod Panel.

<Info>
  Requires a **Webhook Channel** in [Webhook Configuration](/Dashboard/erlcintegration/webhook/webhookconfig). Staff need a Roblox account [linked to Melonly](https://melonly.xyz/my/account) so Melonly knows who ran the action.
</Info>

***

## Configuration Options

Find **Logging Settings** on the **ER:LC Integration → Webhooks** page.

| Setting | Description |
| - | - |
| Auto Log Kicks/Bans | Logs every kick and ban run in your ER:LC server |
| :log punish command | Lets staff run `:log [type] [username] [reason]` in game. On by default. |

<Frame caption="Logging settings">
  <img className="block" src="https://mintcdn.com/melonly/lEOimPXEDE-NzFj7/images/Dashboard/ERLCIntegration/loggingsettingsimg.png?fit=max&auto=format&n=lEOimPXEDE-NzFj7&q=85&s=596e4f51448f636c930eef30cae52a3d" alt="" style={{ borderRadius: '0.75rem' }} width="1901" height="936" data-path="images/Dashboard/ERLCIntegration/loggingsettingsimg.png" />
</Frame>

***

## Auto Log Kicks and Bans

Every kick and ban is recorded, even if staff forget to log it. Add a reason later by editing the log in the Mod Panel.

***

## :log Punish Command

The `:log` command lets staff log punishments from in game without opening the dashboard. It works with your custom log types too, once you've set them up on the dashboard.

### :log Command Reference

| Command | Action |
| - | - |
| `:log note [username] [reason]` | Logs a note |
| `:log warn [username] [reason]` | Logs a warning |
| `:log kick [username] [reason]` | Logs a kick |
| `:log bolo [username] [reason]` | Logs a Ban BOLO |
| `:log ban [username] [reason]` | Logs a ban |
| `:log vehicle [user/plate]` | Looks up the player or vehicle |
| `:log chasing` | Tells you who you're chasing |
| `:log vc [abbreviation]` | Moves you to a voice channel |
| `:log vc [username] [abbreviation]` | Moves a player to a voice channel |

### :log vehicle

Run `:log vehicle` with a username, plate or vehicle name. Melonly finds the closest matching vehicle in the server and sends you an in-game PM saying who is driving it.

### :log chasing

Run `:log chasing` during a pursuit. Melonly watches where you and every other player move over the next few seconds and finds the player who stays close to you while heading the same way. You get an in-game PM like *It appears you are chasing ROBLOXUSER.*

* Players on your own team are never picked.
* The PM arrives within about 10 seconds, so keep driving after you run it.
* If nobody fits, you get *Could not determine who you are chasing.* instead of a guess.

### :log vc

Moves people between Discord voice channels using the abbreviations from [Voice Channel Configurations](/Dashboard/erlcintegration/api/voicechannelconfig). `:log vc s1` moves you, and `:log vc [username] s1` moves another player. You must already be in a voice channel.

<Note>
  `:log vehicle` and `:log chasing` need your ER:LC server linked with an API key so Melonly can read players and vehicles.
</Note>

***

## Example Use Cases

* Record every kick and ban automatically
* Let staff log punishments quickly in game
* Keep a complete moderation history
* Use custom log types for your own workflows

***

<Card title="Need help?" icon="headset" href="https://melonly.xyz/discord">
  Still have questions? Join our Discord server for support from the Melonly Team.
</Card>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.