# 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.

## 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.

- **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.

- [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/index.html.md)
- [Schedule a message or command](https://rustsc.com/support/guides/schedule-messages-commands/index.html.md)

## 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.

- **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.

- [Build an event rule](https://rustsc.com/support/guides/make-a-server-event-rule/index.html.md)
- [Schedule a temporary change](https://rustsc.com/support/guides/temporary-changes/index.html.md)

## 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.

- **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.

- [Read server performance charts](https://rustsc.com/support/guides/reference-performance/index.html.md)
- [Check host load and logs](https://rustsc.com/support/guides/host-performance-and-logs/index.html.md)

## Know which server needs attention

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

- **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.

- [Set up alerts](https://rustsc.com/support/guides/resource-alerts/index.html.md)
- [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/index.html.md)

## 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.

- **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.

- [Explore player management](https://rustsc.com/support/guides/reference-players/index.html.md)
- [See in-game player actions](https://rustsc.com/support/guides/player-actions/index.html.md)

## 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.

- **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.

- [See how permission sync works](https://rustsc.com/support/guides/sync-player-permissions/index.html.md)

## 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.

- **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.

- [See how plugin updates and rollback work](https://rustsc.com/support/guides/plugin-update-source-and-recovery/index.html.md)

## 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.

- **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.

- [Link your players to Discord](https://rustsc.com/support/guides/discord-link/index.html.md)
- [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/index.html.md)

## 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.

- **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.
- **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.
- **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.
- **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.
- **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.
- **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.

- [Read the wipe plan guide](https://rustsc.com/support/guides/wipe-plans/index.html.md)

## 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.

- **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.

- [See all portal roles](https://rustsc.com/support/guides/workspace-roles/index.html.md)
- [Limit access to selected servers](https://rustsc.com/support/guides/limited-access/index.html.md)

## 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.

- **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.

## Choose how to connect your server

A host you control, a rented panel and a file login give you different controls. Check which connection fits the server you already run.


- [See supported hosts](https://rustsc.com/compatibility/index.html.md)
- [See setup steps](https://rustsc.com/get-started/index.html.md)

---

HTML version: https://rustsc.com/features/

RustSC helps you manage your Rust dedicated server from your browser.
