Jellyn Lab
In-game commands
Start a system when a player types your own command in ER:LC, with arguments, aliases, who may use it and a wait between uses.
ER:LC takes a command typed with : or ; in front. A system started by Someone runs an in-game command can be written with either (:duty or ;duty) and hears both.
;report Sam_RP Random deathmatch at the bankArguments
A command can take up to 5 arguments: the words typed after it, in order, used in blocks as {arg.name}. The last one takes the rest of the line, so it can be a reason or a message.
| Typed | {arg.player} | {arg.reason} |
|---|---|---|
;report Sam_RP Random deathmatch at the bank | Sam_RP | Random deathmatch at the bank |
Required arguments come first. When one is missing the system doesn't run, and it can tell the player how to use it with a :pm:
Jellyn's words
Use it like this: :report <player> <reason>Your own words
Reports need a player and a reason. {usage}{usage} is where how to use it goes in your own words.
The other settings
Other commands that start itup to 4Aliases, like :r for :report. : and ; count as the same.
Who can use iteveryone · verified · staffEveryone in game, players who verified their Roblox account on Jellyn, or staff (players whose verified Discord account is on your server's staff).
Wait between uses0 to 3600 secondsEach player waits this long before it runs for them again.
Sending commands back
The Run an in-game command block sends any : command ER:LC runs (:h, :m, :pm, :kick, :tp, :weather and the rest): one line, with the command written out and values after it.
:pm {player} Thanks, your report is in. Staff will look at it soon.A system started by an in-game command can't send another in-game command. That stops two systems from setting each other off forever. And Lab never sends rank changes or commands on everyone at once.
Jellyn sends : commands only. ; commands are what players type, and reach Jellyn through your server's events webhook.