Understanding ERLC command logs and what they tell you
A deep dive into what ERLC records in its command log, how Dispatcher parses ban, kick, and warn commands, and how to use that data to spot patterns in your server.
ER:LC keeps a running command log of what staff do in-game. It's one of the most useful data sources your server produces — once you know how to read it.
What the command log records
Every time a moderator runs a command in-game — kicking a player, banning an exploiter, sending a message — ER:LC writes it to the command log with the moderator, the target, and a timestamp.
How Dispatcher uses it
Dispatcher reads this log and parses the moderation commands — :ban, :kick, and :warn — into a clean, searchable history. Instead of scrolling through raw text, you get a filterable record of every action with the moderator and reason attached.
What it tells you
- Which players keep coming up across multiple actions
- Which moderators are most active, and when
- Patterns in rule-breaking — peak times, repeat offenders, common reasons
Read well, your command log turns from a wall of text into a map of how your server actually runs.