Make a server event rule
In the server's Schedules, open When something happens and choose Add a rule.
Choose what triggers a rule
Use the When field to choose an event this server offers.
Say something in game chat
Choose Say it in chat as the rule's response and enter a message.
Send an alert when an event happens
Choose Send an alert to my channels and enter the message.
Post in Discord when an event happens
Choose Post in Discord where offered and select a channel.
Read what a rule did
Check Latest result or open What it did for earlier runs.
Check whether a chat rule works on the host
Look for Runs on the server's host on a chat rule. Alerts and Discord responses need RustSC's connection.
Read rules from a script
Use the customer API to list the rules you may read.
Schedule a temporary change
Choose a server, its start and end, and the files the change uses.
Choose temporary files or plugins
Add the files or plugin changes that should be in place for the chosen window.
Choose when a temporary change starts
Choose the start in the form. Now starts it on save.
Change when a temporary change ends
Edit the saved timing, or use Extend where offered for a change that is already on.
Extend a running temporary change
Choose Extend where offered and confirm the new end.
Copy a temporary change
A copy starts paused so you can review its timing before turning it on.
Tell players when a temporary change starts and ends
Add optional start and end messages under Tell players before saving.
Review a temporary change before saving
Check the selected files, plugins and timing on the form before you save.
Check files after a temporary change stops
Read the run result before retrying. If the change could not turn off yet, RustSC keeps trying to put files back.
Review or reverse a temporary-change run
Open Past and choose Roll back or Roll forward where the run offers it.
Check files for a temporary change
Open the files from the schedule and check what is ready before the change runs.
Read temporary-change history from a script
Use the customer API to see when a change ran and how it ended.