Many SER methods begin with a player argument:
Broadcast @all 5s "Message"
Heal @sender 20
SetRole @classDPlayers Scientist
The @ value answers the most important question: which players?
SER keeps common groups ready for you:
| Value | Who it means |
|---|---|
@all |
every connected player |
@alivePlayers |
every living player |
@scpPlayers |
living SCP players |
@classDPlayers |
Class-D players |
@foundationForcePlayers |
Foundation forces |
@surfacePlayers |
players currently on Surface |
@sender |
the player who used a command |
@evPlayer |
the main player supplied by many events |
Run serhelp variables for the list provided by your installed version. There
are groups for roles, teams, zones, living players, spectators, NPCs, and more.
Create surfacewarning.ser:
!-- CustomCommand surfacewarning
-- availableFor RemoteAdmin Server
-- description "Warns and damages players camping on Surface"
Broadcast @surfacePlayers 8s "<b><color=red>Leave the Surface Zone!</color></b>"
Damage @surfacePlayers 20 "Surface camping"
An administrator now has one command which affects only players in that zone.
There is no need to look up names or player IDs. The value of
@surfacePlayers is resolved when the method runs.
This is why the same method can target one person or a whole group:
Heal @sender 20
Heal @classDPlayers 20
Heal @all 20
Be careful when reading a property such as a name or health value. Those questions normally make sense for exactly one player, not a group. We will select one player and inspect them in the next lesson.
Turn surfacewarning.ser into a zone-specific announcement. Replace
@surfacePlayers with another predefined zone group from serhelp variables,
remove the Damage line, and change the message.
You now have methods, triggers, and useful targets—the core of many SER scripts. Variables become worthwhile only when you need to remember a result.