You are about to write a complete SER script. No variables, loops, or language theory yet—just a result you can see immediately.
Run serhelp start and open the script directory it prints. Create a file named
hello.ser and put this inside:
Reply "Hello from my first SER script!"
Reply is a method: an instruction that asks SER to do something.
Use the server console or Remote Admin:
serrun hello
Use the script name, not hello.ser and not its full path. You should see your
message followed by confirmation that hello was requested to run.
Remote Admin senders need the ser.run permission.
Add another method:
Reply "Sending a message to everyone..."
Broadcast @all 5s "This server can be scripted!"
Run serrun hello again. SER refreshes the file before executing it, so the new
broadcast should appear for every connected player.
Read the second line from left to right:
Broadcastis what SER should do;@allmeans every player;5sis how long the message stays visible;- the quoted text is what they see.
That pattern—method, then arguments—already covers a surprising amount of SER.
Change 5s to 10s, edit the message, and run the script again. If you want a
smaller on-screen message, ask SER how Hint works:
serhelp Hint
Run:
serstatus
It tells you whether the file was accepted, failed to compile, is disabled by a
leading #, lives inside a disabled folder, or conflicts with another file
using the same script name.