ER:LC Integration

The ER:LC integration links Melonly to your private server for Virtual Server Management (VSM), member checks, in-game logs, automation and more. Each section below links to its full page.

Set Up the Integration

Get Your API Key

Join your ER:LC private server and open Private Server Settings → ER:LC API. Copy your unique key.

Add the Server in Melonly

On your dashboard’s ER:LC Integration page, click Manage linked servers. Paste your API key, enter a label and click Add Server. Server info appears next to the setup button.You can add several API keys and switch between linked servers. Each key keeps its own settings.

VSM and member checks become available as soon as a key is set.

ER:LC API

These settings are on the ER:LC Integration → API page.

Server Configuration

Setting	Description
API Configuration	Set or update your ER:LC API key
Server Name	The linked private server’s name
Players	Live player count. Can take up to 5 minutes to refresh.
Join Code	Your private server join code, or use Join Server

See Server Configuration.

Raid Rollback

Revert the commands a raider ran. Answer a few prompts and Melonly handles the rest. See Raid Rollback.

Event Logs

Forward ER:LC events to Discord channels. Requires Melonly Plus. See Event Logs.

Setting	Description
Join Logs Channel	ER:LC join events
Leave Logs Channel	ER:LC leave events
Kill Logs Channel	ER:LC kill events
Mod Call Logs Channel	ER:LC mod calls

AFK Inactivity Checks

Check that on-duty staff are actually moderating. Flagged staff get a PM with a code they must run in game. See AFK Inactivity Checks.

Setting	Description
Minutes Before Alert	Time before the first alert
Alert Channel	Where the first alert posts
Mention Roles on Alert	Roles pinged on the first alert
Escalation Grace Period	Time before escalation
Escalation Channel	Where the escalation posts
Mention Roles on Escalation	Roles pinged on escalation
Send ER:LC PM Confirmation	Sends the PM with the confirmation code
Confirmation Command	The `:log {code}` command staff must run

Restrictions

Team and vehicle restrictions don’t run on their own. Create a reminder on the Reminders page to run the checks.

Team Restrictions

Lock teams behind Discord roles or Melonly departments. See Team Restrictions.

Setting	Description
Role Requirement	The team requires a Discord role
Department Restriction	The team requires a Melonly department
Combined Requirement	Both the role and the department are required
Alert Message	The PM sent to a player before they’re kicked off the team
Minimum Playercount	The player count at which restrictions start

Vehicle Restrictions

Lock vehicles behind a Discord role. Players without the role are flagged in the panel or by reminders. See Vehicle Restrictions.

Safe Zone Enforcement

See Safe Zone Enforcement.

Setting	Description
Safe Zone Enforcement	Turns the feature on or off
Open Safe Zone Editor	Opens the safe zone editor. See Map Editor.
Warnings Before Action	Warnings given before action is taken
Action After Warnings	The punishment once the warning limit is reached
Create Moderation Record	Logs the punishment in moderation history

Team Jurisdictions

See Team Jurisdictions.

Setting	Description
Police Jurisdiction	The area assigned to Police
Sheriff Jurisdiction	The area assigned to Sheriff
Fire Department Jurisdiction	The area assigned to Fire
DOT Jurisdiction	The area assigned to DOT
Open Jurisdiction Editor	Opens the editor. See Map Editor.
Minutes Allowed Outside of Jurisdiction	Time before warnings start
Number of PM Warnings Before Action	PM warnings given before action is taken
Jurisdiction Enforcement Action	The action once the warning limit is reached
Exclude Moderators	Moderators aren’t affected

VC Server Status

Voice channels whose names update with live server data. Requires Plus. See VC Server Status.

Type	Displays
Playercount VC	The number of players in game
Queue VC	The number of players in the queue

Voice Channel Configurations

Give voice channels abbreviations for the in-game ;vc command. If s1 maps to the Scene 1 channel, running ;vc s1 moves you into Scene 1 (you must already be in a voice channel). Use ;vc [usernames] [abbreviation] to move other players. Anyone can use an abbreviation unless Staff Only is turned on for it. See Voice Channel Configurations.

Ban BOLO

See Ban BOLO.

Setting	Description
Manual Completion	Staff with the ER:LC Admin and Ban permissions can ban players when approving a Ban BOLO
Automatic Completion	Bans players with an active Ban BOLO when they join

Shift Automation

Requires Plus and a linked Roblox account. See Shift Automation.

Setting	Description
Automatic Shift Start	Starts a shift when staff join the ER:LC server
Automatic Shift End	Ends a shift when staff leave the ER:LC server

Punishment Controls

Requires Plus. See Punishment Controls.

Setting	Description
Punishment Rejoin Timer	If a kicked player rejoins within this time, Melonly punishes them again
Kick or Ban	The punishment for rejoining

Welcome Messages

See Welcome Messages.

Setting	Description
Welcome Message	A PM sent to players when they join

Permission Management

Requires Plus. See Permission Management.

Setting	Description
Automatic Permission Removal	Removes in-game permissions when a user leaves the linked Melonly server

Username Moderation

See Username Moderation.

Setting	Description
Kick “All/Others” Usernames	Kicks anyone whose username starts with `all` or `others`

Weather and Time Sync

Requires Plus. Turn off the in-game weather cycle in your ER:LC server settings first. See Weather and Time Sync.

Setting	Description
City Name	The city to sync with
Sync Weather	Matches in-game weather to the city
Sync Time	Matches in-game time to the city

Webhooks

These settings are on the ER:LC Integration → Webhooks page.

ER:LC Webhook Channel

Requires PRC command logs in your Discord server. See PRC’s setup video.

Setting	Description
Webhook Channel	The channel for command webhooks from PRC
Alternative Channel	The channel for punishment, kick and ban webhooks from PRC
Events Webhook Link	Copy this link into the Events Webhook setting of your PRC server

See Webhook Configuration and ER:LC Events Webhook.

Auto-Log Kicks and Bans

Logs every kick and ban in your ER:LC server. Add reasons later by editing the log in the Mod Panel. See Logging Settings.

`:log` Punish Command

The :log command lets staff log punishments from in game. It needs a linked Roblox account. Custom log types work too, once you set them up on the dashboard.

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`	PMs you who you appear to be chasing, based on recent player locations
`:log vc [abbreviation]`	Moves you to a voice channel
`:log vc [username] [abbreviation]`	Moves a player to a voice channel

Off-Duty Commands Alert

Catch staff using moderation commands while off duty. See Off-Duty Commands Alert.

Setting	Description
Enable Off-Duty Commands Alert	Turns the feature on or off
Alert Channel	The channel for alerts
Mention Roles in Alert	Roles pinged on alerts, up to 5
Allowed Commands	Commands allowed off duty
Allowed Roles	Roles that never trigger alerts

Mass Command Alerts

Flag server-wide commands like :ban all and post an alert. See Mass Command Alerts.

Setting	Description
Commands to Monitor	The commands tracked, such as `:unmod`, `:ban` or `:kick`
Targets That Trigger an Alert	`all`, `others` or both
Mention Roles on Alert	Roles pinged, up to 5
Alert Delivery Channel	Where alerts post. Leave it empty to post in your webhook channel.
Minimum Players Affected	Only alerts when at least this many players are affected
Alert Cooldown	Minimum time between alerts for the same command and target

Playtime Levels

These settings are on the ER:LC Integration → Playtime Levels page. See Playtime Levels.

Enable Playtime Levels

Setting	Description
Enable Playtime Levels	Turns Playtime Levels on or off

Manage Levels

You can create up to 15 levels, or up to 100 with Plus.

Field	Description
Level Name	1 to 100 characters, such as Bronze Player
Required Playtime	Minimum playtime for the level. Levels must be in ascending order. At least 1 minute, at most 1 year.
Discord Role	Optional role given at this level
Perks	Up to 20 perks per level, 300 characters each

Action	Description
Reorder Levels	Change the level order. It must stay ascending.
Remove Levels	Delete a level
Add Perks	Add perks to a level

Notifications

Setting	Description
Level Up Events Channel	The channel for level-up posts
Custom Level Up Message	The channel message. Supports `{robloxuser}`, `{user}`, `{mentionuser}`, `{level}` and `{playtime}`. Requires Plus.
DM Players on Level Up	DMs the player when they level up
Custom Level Up DM	The DM template, with the same variables. Requires Plus.

Need help?

Still have questions? Join our Discord server for support from the Melonly Team.

Setup & permissions

Staff operations

Modules & programs

Integrations & automation

Directory & visibility

Audit logs

ER:LC Integration

Set Up the Integration