Skip to content

ER:LC Alerts and Automation

Live player counts, kill-spree detection, ban-list changes, and knowing the instant nobody's moderating.

· 2 min read
Table of contents

Beyond the session hub, ER:LC integration includes a set of quieter automated alerts — things that happen in the background once they're configured, without anyone needing to be watching.

Live player count, on a voice channel

Pick a voice channel (one nobody actually needs to join — it's a label, not a room) and a name template using the player count and max count, and Varko keeps it renamed to the live number. Discord only allows a channel to be renamed about twice every ten minutes, so this updates on roughly a six-minute cadence rather than instantly — close enough to live for a rough indicator, not meant to be a second-by-second scoreboard.

"Filling up" and "server's empty"

Set a channel and a player threshold, and Varko posts once when the server crosses that number going up — not every poll while it sits above it, just the moment it crosses. Turn on the companion "server's empty" alert and it'll also say so the moment the server goes from having people in it to having nobody, which only fires after it's actually had people — a server that's never had anyone in it yet doesn't need announcing as empty.

Nobody's moderating

The single most useful alert here, arguably: set a channel, a role to ping, and a minimum player count, and Varko watches whether anyone with in-game staff permissions is actually in the server once it's busy enough to matter. No staff present past that threshold, and it pings — once, with a cooldown so it's not re-pinging every thirty seconds for the same gap, and it resets the moment staff coverage shows back up.

Kill sprees

Set a threshold and a time window, and a player racking up that many kills inside the window gets flagged — not banned, not kicked, just surfaced as "worth a look." A real firefight trips this too; it's a prompt to go check, not a verdict.

Ban list changes

ER:LC's own API doesn't keep a ban log — it only ever hands back the current full list — so Varko diffs it against the previous poll and posts what actually changed: who got banned, who got unbanned. The very first poll after you turn this on posts nothing, since there's no "previous" list yet to diff against; every ban already on the list at that point would otherwise read as brand new.

Watched commands

List specific in-game commands and a channel, and Varko relays it the moment one of them gets run — matched on the actual command word, so watching a ban command doesn't also fire on an unban command.

Queue alerts

Shares the same channel as the player-count alerts, since it's the same underlying conversation — "the server's busy." Set a threshold and get told when the queue reaches it.