Part 1: Kill log
Every time a player is killed in ERLC, this automation posts a line to your#kill-log channel showing who did it, who died, and when.
1
Add the player-killed trigger
Drag an
erlc_when_event block onto the canvas and set EVENT to player_killed. This fires once per kill event in your ERLC server.2
Read kill event data
Attach three
erlc_event_value blocks to pull the relevant fields:KillerName— the display name of the player who scored the kill.KilledName— the display name of the player who was eliminated.Timestamp— the time the kill occurred (ISO 8601 string).
3
Build the log message
Use nested
erlc_join_values blocks to concatenate the fields into a readable log line:4
Send to the kill-log channel
Attach an
erlc_bot_send_message block:- Set CHANNEL_ID to your
#kill-logchannel ID (replace<resource-id>). - Wire your completed
erlc_join_valueschain into the MESSAGE input.
Part 1 block JSON
Part 2: Join/leave log
This automation handles both player joins and leaves using a single trigger and anerlc_if_else block to branch the message based on the Join field.
1
Add the player-joined trigger
Drag an
erlc_when_event block onto the canvas and set EVENT to player_joined. This event fires for both joins and leaves — the Join field tells you which one it is.2
Read event fields
Attach three
erlc_event_value blocks:PlayerName— the display name of the player.Join— a boolean (truewhen joining,falsewhen leaving).Timestamp— the time of the event.
3
Branch on the Join field
Attach an
erlc_if_else block and wire the Join erlc_event_value output into its CONDITION input.THEN branch (join): Attach an erlc_bot_send_message block with a message like:
"✅ " + PlayerName + " joined the server at " + TimestampELSE branch (leave): Attach another erlc_bot_send_message block with a message like:
"👋 " + PlayerName + " left the server at " + TimestampSet the CHANNEL_ID on both send blocks to your #join-log channel ID (<resource-id>).If you want join and leave events in separate channels, use two different
<resource-id> channel IDs — one in the THEN branch and one in the ELSE branch.Part 3: Rich embed kill log (bonus)
Plain text logs are functional, but an embedded message with a red color, labeled fields, and a timestamp looks much sharper in Discord. This bonus section upgrades your kill log to a rich embed.1
Swap the send block for an embed block
Replace
erlc_bot_send_message with an erlc_embed_send block. This block accepts a CHANNEL_ID and an EMBED input that you build from embed component blocks.2
Set the embed title
Attach an
erlc_embed_title block to the EMBED input and set its text to "Player Killed".3
Add killer and killed fields
Chain two
erlc_embed_field blocks:- First: NAME =
"Killer", VALUE = output oferlc_event_value(FIELD:KillerName). - Second: NAME =
"Killed", VALUE = output oferlc_event_value(FIELD:KilledName).
4
Set a red color
Attach an
erlc_embed_color block and wire an erlc_discord_rgb block into it. Set the RGB values to R: 255, G: 0, B: 0 for a bold red sidebar on your embed.5
Add a timestamp
Attach an
erlc_embed_timestamp block to automatically stamp the embed with the current time. This shows up as a relative timestamp (e.g. “just now”) in Discord.6
Set the channel and save
On the
erlc_embed_send block, set CHANNEL_ID to your #kill-log channel ID (<resource-id>). Save and enable the automation.Logging system overview
Moderation Automation
Auto-timeout high-wanted players and respond to AutoMod.
Slash Commands
Build interactive slash commands for your Discord server.