Recording Mode

Recording mode applies your join and chat restrictions for a take. Set the options first, turn the session on when you're ready, and turn it off when normal play should resume.

Session mode (/recsession)

commands

/recsession on
/recsession off
/recsession status

Depending on your recording settings, a session can apply these restrictions:

nobody new can join
chat's locked
join messages are hidden
the MOTD switches to your recording message
/me is blocked
private messages are blocked for non-ops
admin broadcasts about teleports, gamemode, items, time, weather and op changes are dropped

Which of those apply is the recording block in Content & chat settings. allow-chat opens chat to everyone, allow-ops-chat to ops only, and scriptedessentials.recording.chat.bypass lets one person talk regardless.

Don't lock yourself out

With allow-ops-join: false, a crash and reconnect leaves you outside your own session. Turn it on before you start if you're the only admin.

Fake messages (Premium)

commands

/fakejoin <player>
/fakeleave <player>
/fakedeath <victim> <killer>

A join, leave or death that didn't happen. Same formatting as the real thing.

Flooding the chat (/cycle)

Premium

Part of ScriptedEssentials Premium. See what's in each edition.

commands

/cycle <spawn|join|leave|death> <seconds> <amount>
/cycle stop

Fires fake join, leave or death messages, or NPCs spawning near you, one at a time on a randomised gap around the seconds you give (roughly a quarter to one and three quarter times that value), until it's fired amount times. /cycle stop cancels whatever you've got running.

commands

/cycle join 2 20      # about 20 fake joins over roughly 40 seconds
/cycle spawn 5 10      # 10 NPCs wandering in near you, spread out

Each type uses the matching feature's own permission: spawn needs NPC access, join/leave/death need the matching fake-message feature.

Recording borders (/recordingborder)

Premium

Part of ScriptedEssentials Premium. See what's in each edition.

Recording borders are named borders sent to individual players. You can move and resize them, restrict which world they apply in, and choose who bypasses them. They aren't team-specific enclosures.

commands

/recordingborder create <name>       # where you're standing
/recordingborder delete <name>
/recordingborder list
/recordingborder info <name>
/recordingborder on <name>
/recordingborder off <name>
/recordingborder size <name> <blocks>
/recordingborder center <name> <x> <z>
/recordingborder here <name>         # move the centre to you
/recordingborder world <name> <world|all>
/recordingborder warning <name> <blocks>
/recordingborder bypassops <name> <true|false>
/recordingborder team <name> <team|none>
/recordingborder bypass <name> [player]
/recordingborder reapply

Aliases /recborder, /rborder. Saved in recording-borders.yml.

Subcommand	Notes
`size`	Diameter in blocks
`warning`	How close before the red edge shows
`bypassops`	Ops ignore this border
`team`	Members of that team bypass this border
`bypass`	Toggle a player's manual bypass of recording borders
`reapply`	Push borders out to everyone again

These are client-side

These are per-player borders with border damage set to zero. They don't replace the world's real border or stop the world outside from running. Don't rely on them as a server-side security boundary.

If more than one enabled border matches a player, the first applicable border is used. A manual bypass applies across recording borders, even though the command includes a border name.

Queues

A queue lines players up on an NPC and lets them in one at a time. See Queues.

Fake tab players (Premium)

commands

/npc tab count <number>

Pads the player list. See Fake tab players.