Skip to main content

Rust server management, from plugins to performance

Find out why your server slowed down, give VIPs the same perks on two worlds or schedule a weekend plugin rotation. See how each job works in RustSC.

Inside the web portal

Find the world that needs attention

See which servers are running, then open the one your players reported. Each world has its own console, player list and activity.

Servers list showing Community server stopped and EU Main running.

Find a recovery point

The Backups page shows the latest copy on your host. Choose Restore to preview which files it will replace.

The portal shows the newest available backup, its time and the Restore action.

See which jobs finished

Open Activity to check whether a backup succeeded or a new map was planned. Select an entry to see its details.

The Activity page shows successful jobs, including a map plan and a cleanup check, for Community server.

Schedule the work that repeats

See the next restart, wipe, backup or update for each Rust server. Set a routine that suits your players and check how each run went.

All feature topics
A backup routine across two servers
  1. Choose both servers

    Weekly and Monthly

  2. Set the backup time

    Run on each server’s clock

  3. Check each result

    Read both runs in History

  • Run on each server’s clock

    Set a restart for quiet mornings on the days you choose. Preview the next runs in the server’s time zone and give players a countdown in game chat.

  • Set the same routine for several servers

    Add the same backup schedule or wipe reminder to several servers at once. Each server runs it by its own clock and gets its own schedule, so you can change one later.

  • See what ran and what got skipped

    Use Week to see whether a restart and wipe are due together. On a host you control, History explains when a run was skipped because another job was already running.

  • Keep routine jobs running during a connection loss

    Once a Windows or Linux host receives a local schedule, it can still run a scheduled restart or backup if it loses contact with RustSC. Check the result when it reconnects.

Let the server trigger the next step

A clock can tell you when maintenance should end. A server event tells you when the game has actually finished starting. Use either one to trigger the work that follows.

All feature topics
Weekend plugin rotation
  1. Friday evening

    Put the event’s plugin files in place

  2. During the event

    Use the temporary files

  3. Sunday evening

    Put the regular files back

  • Announce when the world is ready

    Choose the event for a server finishing startup, then choose an available response. Post in Discord so players know when they can reconnect.

  • Run a weekend event

    Set a start and end for a temporary change. Put the event’s files or plugins in place for the weekend and restore the previous setup when it ends.

  • Check what a rule did

    Read the latest result or open earlier runs. Pause the rule when you want to handle the job yourself.

See what changed when players felt lag

If players report a slowdown from last night, open the game’s performance history. Compare server FPS with player count and world entities at the time they noticed it.

All feature topics
Hourly averages from one server
Server frame rate
79 FPS to 122 FPS
Relative player activity
15% to 100%

Player activity is relative to the busiest hour’s average player count.

Compare hourly readings
HourServer FPSPlayer activity
179100%
27955%
310025%
411125%
511025%
69425%
712015%
812020%
912235%
109565%
117965%
129580%
  • Read the game alongside the host

    Check the game’s processor and memory use. On a host you manage, compare those readings with the whole host to see whether other servers were busy too.

  • Put a dip in context

    Line up the change with a restart or wipe. Select a point for exact readings, or open the figures as a table. Gaps show when a reading was missing.

  • Compare worlds at a glance

    View player counts and frame rates across a group of servers, then open the affected world to look closer.

Know which server needs attention

Open Alerts to see what happened, which server or host was affected and what to do next.

All feature topics
  • Watch for crashes and failed jobs

    Choose which servers to watch for crashes, failed backups and failed wipes. Add low disk warnings for your host and choose reminders for ongoing problems.

  • Send each alert where it belongs

    Send failed backups to a private staff channel in Discord. Choose your own alerts for a browser with notifications enabled. Use a webhook to send alerts to a tool you run.

  • Let staff know who’s handling a problem

    Acknowledge a low disk space alert and leave a note saying you’re clearing old backups. Repeat notifications stop while the problem stays visible in Alerts.

  • Keep a maintenance window quiet

    When you take a server down for planned work, set a quiet time for selected alerts. Staff can still find those alerts in the portal.

Follow a player across names and servers

A moderator gets a report after the player has logged out and changed names. Search their earlier name or Steam ID to find the same person and see where else they’ve played.

All feature topics
  • Pick up where the last moderator left off

    See visits across your servers, read private staff notes and add a label the next moderator will recognise.

  • Help someone without joining the game

    With the RustSC plugin, staff can inspect what a player is carrying, move a stuck player or give them an item from the browser.

  • Manage several players together

    Select the players you want to label, add to a group, kick or ban. Review who the action reached before following up.

Give players the right perks across servers

A VIP can claim a kit on Weekly but gets denied on Monthly. Look up the player in RustSC to see which permission they have and which Oxide or Carbon group grants it.

All feature topics
Give Cedar VIP on two servers

Cedar has played on both servers. You’ve chosen Weekly and Monthly, reviewed the changes and turned on permission sync.

  1. WeeklyAdd Cedar to VIP
  2. MonthlyCedar joins VIP here too

Test server stays separate.

  • Trace a missing permission

    See what the player received directly, through a group or through that group’s parent. Change the shared group when the fix should apply to everyone in it.

  • Preview changes on each server

    Choose which servers should share permissions and review the additions for each one before turning sync on. Leave your test server out.

  • Keep staff access local

    In-game owner and moderator status stays with each server. For a one-off setup, save a group list and review it before applying it on another server.

Know which plugins actually loaded

A plugin can be in the right folder and still fail to load. Check what Oxide or Carbon is running before replacing files or asking players to test again.

All feature topics
Installed plugins with their versions and load status
  • Find the plugin that needs attention

    Filter your installed plugins by load status or available updates. Open a plugin to check its settings and the permissions it adds.

  • Choose what updates at wipe

    Update selected uMod plugins while the game is stopped. Hold a plugin at its current version or mark a file you maintain as your own version.

  • Recover from a bad update

    Check the source and version before updating. If the new release causes trouble, use Roll back where offered to put the previous plugin file back and reload it.

Connect your Rust community to Discord

Add the RustSC bot to the Discord server you already use. Set up each Rust server’s channels and choose what linking gives your players access to.

All feature topics
When a backup fails
WeeklyScheduled backup failed
#staff-alertsPrivate Discord channel
Backup failedWeekly. There was not enough disk space.

Choose the staff channel for failed backups in Alert settings.

  • Show server status and public chat

    Choose a channel for each server’s status board. To share public game chat, turn on recording and set up Chat relay for the channel you want.

  • Let players link Steam and Discord

    With the RustSC plugin on Oxide or Carbon, players get a code in the game and enter it in your Discord link channel. Staff can find a player’s link from RustSC.

  • Connect Discord roles with Rust groups

    Give linked players a Discord role so they can follow wipe announcements. On an Oxide or Carbon server, choose which Rust group and Discord role stay in sync for linked players, and which way changes go.

Prepare for wipe day

A map wipe can keep blueprints or clear them. Choose the scope ahead of time, take a backup before the wipe and check the next run in your schedule.

All feature topics

Back up and restore

Keep a copy of the world on your host before wipe day. If the wrong map loads or a save is damaged, select the earlier backup and review what it contains.

  • Preview which files a restore will replace.
  • RustSC takes a backup before replacing files, so you can undo the restore.
Backups on your host
  1. Before wipe
  2. Last scheduled
  3. Manual backup
Pine Valley · Local backup

Before wipe

Preview what restoring this backup will replace.

See how restore works
  1. Before wipe
  2. Last scheduled
  3. Manual backup
Pine Valley · Local backup

Last scheduled

Preview what restoring this backup will replace.

See how restore works
  1. Before wipe
  2. Last scheduled
  3. Manual backup
Pine Valley · Local backup

Manual backup

Preview what restoring this backup will replace.

See how restore works

Plan a wipe

Pick the date and review what the wipe will reset. Choose the next map and whether to reset blueprints or selected plugin data.

  • Warn players before the wipe starts.
  • Pick a map seed or paste a custom map link.
Choose what to reset

Map only

Start on a new map and keep blueprints.

See how wipes work

Map and blueprints

Start on a new map and reset learned blueprints.

See how wipes work

Map and plugin data

Start on a new map and reset the plugin data you select.

See how wipes work

Schedule routine work

Put regular backups and planned wipes on the calendar. See the next run and the result of the previous one before changing the schedule.

  • Set the time zone and the warning players will see.
  • Pause, resume or run a supported job when you need it.
Jobs on a schedule
  1. Restarts
  2. Backups
  3. Wipes
Read the server controls guide

Manage Oxide and Carbon plugins

See installed plugins, change their settings and manage groups and permissions from the portal.

  • Find plugins and install supported uMod plugins from RustSC.
  • Check the result after you reload or replace a plugin.
Your plugin framework
Rust
Oxide
Carbon
  1. Installed plugins
  2. Configuration
  3. Permissions
Check compatibility

Install and update

Install a new server or bring in one you already run. See the installed game and framework versions and choose when to update.

  • Update Rust and reinstall Oxide or Carbon in the same restart.
  • Check or repair the game's files while keeping your world and settings.
Your server setup
Rust
Oxide
Carbon
  1. Install or add
  2. Update
  3. Verify files
Check compatibility

Start, stop and restart

Warn players in chat before a restart and check when the server is back online. Turn on crash recovery to bring it back when it crashes.

  • Save the world before a normal stop or restart.
Restart with a warning
  1. Warn players
  2. Restart
  3. Back online
Read the server controls guide
Read the wipe plan guide

Choose what each staff member can do in the portal

RustSC uses role-based access control (RBAC). As the owner, invite each person under their own sign-in and choose their role. You can change or remove their portal access later. In-game staff status is set separately.

All feature topics

Administrator

Give your lead admin access to manage servers and team members across the whole community. Ownership stays with you.

Moderator

Assign a moderator to Weekly, Monthly or both. They can look up players, leave private notes and manage bans on the servers you choose.

Operator

Let someone run updates, change settings and take backups on their assigned servers. Managing the team and handling bans stay with other roles.

Viewer

Give a helper a read-only view of the servers and hosts you choose. They can check players, status and backups while you retain control of changes.

Review reports from your browser

With the RustSC plugin on Oxide or Carbon, a moderator can review in-game F7 reports and leave private notes for the next member of staff.

  1. F7Player report
  2. Staff review
  3. Private staff notes
Players and reports
Player details

Nova

Connected

Private staff note

Helped welcome a new player.

Player details

Rook

Connected

Private staff note

Asked about the next wipe.

Player details

Ash

Previously played

Private staff note

Joined the community recently.

In-game F7 report

Chat report

Repeated messages in global chat.

F7 reports use the RustSC plugin on Oxide or Carbon.

Reported by Nova
Read the moderation guide

Manage servers across hosts

Manage your main world and test server together, even when they run on different hosts. Check each one’s status and review which servers a change will affect.

All feature topics
Your servers
Pine Valley
  • Console
  • Players
  • Backups
Frostline
  • Console
  • Players
  • Backups
Red Mesa
  • Console
  • Players
  • Backups

Manage servers together

See which servers are online at a glance.

The portal lists servers and their hosts alongside active alerts and work in progress.

What works on your host

PortalConnected
Command lineLocal control
PortalUnavailable
Command lineLocal control

Use the command line on your host.

Several servers

Organise servers into groups, even when they run on different hosts.

  • See which servers are online at a glance.
  • Preview supported changes across selected servers and check the outcome for each.

Monitoring and alerts

Check server performance and host resources. Choose which alerts you receive, such as a server crash or a backup failure.

Local control

Use the Windows app or the command line on your host. Saved local schedules and core controls can still run when the portal is out of reach.

iPhone and Android

Preview how to check your server, read the console and look up players on your phone.

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details