Command reference

Every slash command GatorSys registers, grouped by the area it belongs to. Commands only appear in your server when their module is enabled, and many are additionally gated by your permission setup.

General

Staff management

Game logs written by hand

Game Logs routes everything the ER:LC API reports — joins, leaves, kills, in-game commands — on its own. These three are the ones nothing can generate for you, because they record a decision rather than an event. Each posts to its own channel under Game Logs, falling back to the shared fallback channel.

/staff request calls for backup from in game. It has three limits, all configurable, all of them there for a reason: a cooldown so it cannot be pressed eleven times, a minimum staff on shift so it cannot ping at 3am for an empty server, and a maximum so it cannot ping the whole team when eight people are already on.

ER:LC server tools

/prc and /erlc are the same commands under two names. ER:LC has been called both, staff teams migrating from other bots have one of them in their fingers, and typing the other and getting nothing reads like a missing feature. They share one implementation — there is no way for the two to behave differently.

Player punishments

/punish files a case against an ER:LC player. The target field searches Roblox itself: players currently in your linked server are listed first and marked 🟢, then everyone else, shown as Display Name (@username) so the two names are never confused. Whatever you pick is resolved against Roblox before anything is written — a case filed against a username with a typo in it is a case nobody finds again.

The same search is on every field in the bot that names a player: /prc check, /prc pm, /prc refresh, /prc playerlogs, /prc command, /erlc check, /erlc refresh, /search, /userid, /tempban and /punishment issue.

Name several players, separated by commas or spaces, to punish a group in one command. You get one summary listing every case filed and, separately, anybody it could not be filed against.

Who may issue what

Permission is per punishment type, not per command. Warnings, notes and kicks are staff; bans, temporary bans and BOLOs are management. One blanket check on the whole command meant a server either let its moderators ban or stopped them warning, and neither is what anybody wants.

A punishment type you add yourself can name its own tier. One that runs an in-game command and does not name a tier defaults to management — the safe answer to "somebody added a type and did not say who may use it".

What the confirmation, the log and the DM show

All three carry the player's avatar headshot and read top to bottom in one column rather than as a row of inline fields, which reflow into an unreadable grid on a phone.

The confirmation you get back shows the whole record you just wrote — moderator, case id, reason, time, and the player's username, Roblox id, profile link, type and points. The point of a confirmation is to let you catch a mistake in the second after you make it, and you cannot catch the wrong Builderman from a case id alone. If the player has an active BOLO, it says so prominently.

The log adds one thing ERM's does not: how much history the player already had at the moment the case was filed. That is the first thing anybody reading the channel wants to know — is this their first, or their ninth — and it saves a lookup at exactly the moment somebody is deciding whether the punishment was proportionate.

The DM to a linked player names the punishment type, the reason and the case id. It deliberately does not name the moderator or include the staff notes: the person being told cannot reply to a bot DM, so naming who filed it only invites them to go and find that person, and the notes are where staff write what they would not say to the player's face.

Departments

/department is the whole department surface in Discord. Setup still reads better on the Departments tab — the dashboard has pickers and side-by-side views a slash command cannot give you — but everything a department does day to day is here.

Every subcommand takes a department argument with autocomplete over the departments this server has actually configured.

Department shifts

These run against the department's own settings — its on-duty and break roles, its shift log channel, its headcount limit, its named shift types, its nickname prefix — and fall back to the server's settings for anything the department has not set.

They are not a second shift system. A department shift is an ordinary shift with a department on it, written to the same records /shift and /duty use, so every existing report stays correct.

Working a shift is one command with buttons, not three. Nobody thinks "I will now run the break command" — they think "I am stepping away" — and the panel is where that lands. Buttons that cannot apply are disabled rather than left to fail: a panel offering "End shift" to somebody off duty is a panel that produces confusing errors.

Department infractions

issue runs the real infraction engine — escalation chains, the approval queue, the configured log channel, the DM and the confirmation embed all behave exactly as they do for /infraction issue. The only difference is that the record it writes carries the department, which is what makes /department infraction list and the per-department reports possible.

Shifts and activity

/shift works for the whole server by default. Pass department and it runs under that department's settings instead: its on-duty and break roles, its shift log channel, its limit on how many people may be on at once, its named shift types, and its on-duty nickname prefix. Anything the department has not set falls back to the server's setting rather than being blank.

You are only asked which department when the answer is genuinely ambiguous — a member of exactly one department that runs shifts gets it picked for them.

Leave

Leave of Absence and Reduced Activity are one record with a type on it, not two systems. They are the same thing with a different promise attached: one says "I am away", the other says "I am here but less". Building them separately would have meant a second set of requests, approvals, extensions, expiry sweeps and reports — five things that drift apart the first time one gets a bug fix.

So there is one command, and it asks which. /loa and /ra still work as message-prefix aliases.

Automations

An automation is "when this happens, do these things". Build one in the Automations tab — it needs role and channel pickers — and manage it from here.

Applications, forms & training

Tickets, AI support & modmail

Submissions & workflow

Sessions

Community

Connection roles

Operations suite

Custom commands & AI tooling

Owner-only