Integrations
Placeholders
Every {word} Jellyn fills in, feature by feature. Session posts, staff requests, warnings, alerts and punishment commands.
Wherever you write your own words for Jellyn, words in braces are filled in when it posts. Each feature has its own set: a word from another feature stays as you wrote it.
For Jellyn Lab systems, see Values: Lab has the most of all, and checks them when you save.
Session posts Jellyn+
On the Sessions page, under your own posts.
| Word | Becomes |
|---|---|
{user} | Who ran it |
{players} | Players in game |
{maxplayers} | The most the server takes |
{queue} | Players waiting to join |
{servername} | The ER:LC server's name |
{code} | Its join code |
{joinlink} | A link to join |
{aop} | The area of play |
{votes}, {votesrequired} | Votes so far, and votes needed |
{time} | Now, as a Discord timestamp |
{scheduledtime} | When a planned session starts |
Put a style after {time} or {scheduledtime}: t and T for the time, d and D for the date, f and F for both, R for relative (in 2 hours). Each reader sees it in their own time zone.
Staff requests Jellyn+
On the Sessions page, under Staff requests.
| Word | Becomes |
|---|---|
{user} | Who asked |
{reason} | Their reason |
{staff} | How many staff are on shift |
{players} | Players in game |
{ingame} | Staff in game |
Safe zone warnings
On the Map editor, beside safe zones. Up to 170 characters.
| Word | Becomes |
|---|---|
{player} | The player |
{area} | The safe zone |
{next} | What the next one brings: a warning, a kick or a ban |
{warning}, {warnings} | Which warning this is, and how many there are: Warning 2 of 3 |
Command alerts Jellyn+
On Game features, for commands run off shift.
| Word | Becomes |
|---|---|
{staff} | The staff member, as a Discord mention (or their Roblox name, when they haven't verified) |
{player} | Their Roblox name |
{commands} | The commands they ran |
Punishment types
On Types and rules, a punishment type's in-game command.
| Word | Becomes |
|---|---|
{player} | The player being punished |
{reason} | The reason logged |
:kick {player} {reason}AFK checks
On Automations, the private message for an AFK check. Put {{token}} in it, with two braces: it becomes the code staff answer with, :log CODE.