# Your all-in-one Rust server manager Whether you run one server or several across different hosts, RustSC puts them in one web portal. Manage players and plugins, schedule wipes and backups, and check server performance from anywhere. Open beta is coming in early 2027 - [Get an email when open beta launches](https://rustsc.com/sign-up/) - [Explore features](https://rustsc.com/features/index.html.md) ## Vanilla or modded - **Rust.** - **Oxide.** - **Carbon.** - [Check compatibility](https://rustsc.com/compatibility/index.html.md) ## What do you need to do on your server? Track down a missing perk, find out why the game slowed down or set up a job you can leave to run. Open a tool to see how it works. - [Scheduling · Set the same routine across servers](https://rustsc.com/features/index.html.md) - [Automation · Run a weekend event and put the files back](https://rustsc.com/features/index.html.md) - [Performance · Investigate last night’s lag](https://rustsc.com/features/index.html.md) - [Alerts · Route a failed backup to the right staff](https://rustsc.com/features/index.html.md) - [Player management · Find a player who changed names](https://rustsc.com/features/index.html.md) - [Player permissions · Keep VIP perks in sync](https://rustsc.com/features/index.html.md) - [Plugins · Check what loaded after an update](https://rustsc.com/features/index.html.md) - [Discord · Connect game groups and Discord roles](https://rustsc.com/features/index.html.md) ## Decide what wipe day changes On a host you control, pick the date, next map and what to reset. Review it all before the wipe runs. - **Pick the map.** Choose a seed or use a custom map. - **Choose what resets.** Keep blueprints or clear them. Choose which plugin data goes with the old world. - **Keep a way back.** Keep a local backup before a wipe and preview what a restore will replace. - [See wipes and backups](https://rustsc.com/features/index.html.md) ## Check in from wherever you are When someone reports a problem, open your browser to see who’s online, read the console and check alerts. Switch to another world or check the host it runs on. - **Follow up from your phone.** Check a server alert, look up a player or read the latest console messages while you’re away from your desk. - [See the app in action](https://rustsc.com/mobile-apps/index.html.md) ## Invite your admins and moderators into the portal Give each person their own sign-in and a role that fits their job. When someone makes a change, you can see who did it in Activity. - **Administrator.** Let your lead admin manage the team and look after all your servers. - **Moderator.** Give a moderator access to handle players and bans on your weekly server while you look after the others. - [Compare portal staff roles](https://rustsc.com/features/index.html.md) ## Keep your servers where they run Bring in a server you already run with its map, saves and settings in place. You choose when RustSC takes over each job. - **A host you control.** Connect a Windows or Linux host with one command. Saved schedules run on that host, even if it loses its internet connection. - **A rented Rust server.** Check your provider and what access you’ll need to connect through its hosting panel when the open beta starts. - [See how setup works](https://rustsc.com/how-it-works/index.html.md) - [Check my provider](https://rustsc.com/compatibility/index.html.md) ## Try RustSC when the beta opens - [Notify me](https://rustsc.com/sign-up/index.html.md) - [Compare Rust server tools](https://rustsc.com/compare/index.html.md) --- HTML version: https://rustsc.com/ RustSC helps you manage your Rust dedicated server from your browser. --- # 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. --- # Your host runs the game. Manage it from anywhere. Install RustSC on the machine that runs your game, then add your existing world in the portal. You choose which jobs to run from your browser. ## Connect your server and pick your first job Start with the host and world you already use. You decide which jobs RustSC takes on. 1. **Connect your host.** On a computer you control, install the Windows or Linux host app. For a rented server, choose your provider to see the connection options. 2. **Add your existing world.** On your own host, select the server folder. RustSC reads the settings so you can keep the map and files your players know. 3. **Choose the first job.** Set up a local backup or plan a wipe. If an existing script handles that job, turn off its schedule when you move it to RustSC. - [Preview the setup](https://rustsc.com/get-started/index.html.md) - [Check your host](https://rustsc.com/compatibility/index.html.md) ## When players say the server is lagging A player tells your moderator the game stuttered last night. Even if it’s running smoothly now, you can look back at what the server and its host were doing. - **Start with the world and the time.** Ask which server they were on and roughly when it happened. Open that server in your browser and compare its frame rate with the player count around the time they gave you. - **Check the machine behind the game.** On a host you control, look at processor and memory use over the same period. If several Rust worlds share that machine, check whether another world was busy too. - **Give the moderator an answer.** Your moderator can follow up with players on the server they cover. You and your admins can check the other worlds and the host, each with your own portal sign-in. - [Explore server performance](https://rustsc.com/features/index.html.md) - [See staff roles](https://rustsc.com/features/index.html.md) ## When your host loses its connection - **On your host.** Local start, stop and backup controls remain available. A wipe schedule already saved on a connected Windows or Linux host can run there even if it loses contact with RustSC. - **Back in the browser.** Remote controls need the connection. Once the host reconnects, open the server and check what ran before making another change. - [Troubleshoot a disconnected host](https://rustsc.com/status/index.html.md) - [Choose your setup](https://rustsc.com/get-started/index.html.md) --- HTML version: https://rustsc.com/how-it-works/ RustSC helps you manage your Rust dedicated server from your browser. --- # Will RustSC work with my server? Keep the host you already use for Rust on PC. Whether you run the whole machine or rent a single game server, start with the access you have today. ## Install on your host Manage game updates, scheduled wipes and local backups. - **Before you connect.** Install RustSC on the machine that runs the game. Use Windows 11, Ubuntu 24.04 LTS, Debian 12 or Debian 13. - **What you can manage.** Add the folder your server already uses to keep your map and player saves in place. In the portal you can schedule wipes, update the game, and take or restore local backups. - [See Windows and Linux setup](https://rustsc.com/get-started/index.html.md) ## Connect through a hosting panel Check which power, console and file controls your host offers. - **Before you connect.** Choose Rented server when adding a server in RustSC. Pick your host and enter the server details and the key from your panel. - **What you can manage.** Depending on the access your host gives you, you can use the console, manage files, and start, stop or restart the game. Choose Check to see what works before you connect. - [Find your hosting provider](https://rustsc.com/hosting/index.html.md) ## Connect with a file login Browse server files and add the console if your host offers one. - **Before you connect.** Have the file address, username and password from your host. Choose Another host if your provider isn’t listed. - **What you can manage.** Browse the folders your login can reach. Edit files when your login can write and you allow changes in RustSC. Add your server’s console password if your host offers a remote console. Use your host’s panel to start a stopped server. - [See file login setup](https://rustsc.com/hosting/any-host/index.html.md) ## Who hosts your server? Look up your provider or panel for a guide to the login details you need and the controls you can use. - [Browse all hosting guides](https://rustsc.com/hosting/index.html.md) - [My provider isn’t listed](https://rustsc.com/hosting/any-host/index.html.md) ## Does your server use mods? - **Vanilla Rust.** On a host you control, the core management tools work with the base game. You can use them without installing a plugin framework. - **Oxide and Carbon.** On a host you control, manage plugins and permissions for either framework. Add the optional RustSC plugin for features such as player reports and the live map. ## Keep your current world Connect the server where it runs today. Check it from your phone or laptop and choose when to hand over jobs like backups and wipes. - [See setup steps](https://rustsc.com/get-started/index.html.md) - [Notify me](https://rustsc.com/sign-up/index.html.md) - [Preview the mobile app](https://rustsc.com/mobile-apps/index.html.md) --- HTML version: https://rustsc.com/compatibility/ RustSC helps you manage your Rust dedicated server from your browser. --- # Connect your first Rust server Keep your existing world. Choose the kind of access you have to the machine that runs it. ## Open beta notification Open beta is coming in early 2027 - [Notify me](https://rustsc.com/sign-up/index.html.md) ## Choose your setup - **A host you control.** You can install the RustSC host app on your Windows or Linux machine. - **A hosting control panel.** You manage the game through a hosting panel that gives you a server key. - **A file login.** Your provider gave you a file address, username and password. - [See host setup](https://rustsc.com/get-started/index.html.md) - [Find your hosting panel](https://rustsc.com/hosting/index.html.md) - [Connect with a file login](https://rustsc.com/hosting/any-host/index.html.md) ## Setup on a host you control Follow these steps for your Windows or Linux host when sign-up opens. 1. **Sign in to RustSC.** Sign in with Discord. From the portal, you can add the host that runs your server and invite staff when you’re ready. 2. **Connect your host.** In the setup guide on Home, copy the install command for your system. Paste it into PowerShell on Windows or a terminal on Linux to install and connect. 3. **Add your server.** Choose Add existing server for your current world, or Install new for a fresh one. Your existing server keeps running until you switch it over. 4. **Protect the world.** Choose where to keep local backups in Backup settings, then schedule them if you want regular copies. Your host can keep running saved schedules when its internet connection drops. 5. **Invite staff if you need them.** Open Settings, then Members, and choose Invite someone. Give each person access to the servers they help run. ## Install on Windows - **Paste one command into PowerShell.** Run it on the host that will run your server and choose Yes when Windows asks. Add host in the web portal shows the same command with your code in it, so the host connects as it installs. ```powershell $f="$env:TEMP\rustsc-install.ps1"; [Net.ServicePointManager]::SecurityProtocol=[Net.ServicePointManager]::SecurityProtocol -bor 3072; iwr https://get.rustsc.com/install.ps1 -UseBasicParsing -OutFile $f; powershell -NoProfile -ExecutionPolicy Bypass -File $f ``` ## Install on Linux - **Paste one command into the terminal.** Run it on the host that will run your server. Add host in the web portal shows the same command with your code in it, so the host connects as it installs. ```bash curl -fsSL https://get.rustsc.com/install.sh | sudo bash ``` ## Prepare for your first session Follow the first-server guide to connect your host, add your world and check that it appears in the portal. - [Read the first-server guide](https://rustsc.com/support/guides/first-server/index.html.md) - [See how RustSC works](https://rustsc.com/how-it-works/index.html.md) --- HTML version: https://rustsc.com/get-started/ RustSC helps you manage your Rust dedicated server from your browser. --- # About RustSC RustSC is a web-based Rust server manager for owners who run a single community or several servers across different hosts. ## For Rust server owners and moderators - **Run your server from the web portal.** When someone says the server is down, open its console to see the last messages and check whether it is still running. From the same server page you can restart the game, see who is online or check the next scheduled job. - **Share the work.** Invite staff and give them access to the servers they help run. - **Keep your setup.** On a host you control, add your server in its existing folder. The open beta will also connect to servers on compatible hosting panels. - [Explore features](https://rustsc.com/features/index.html.md) - [See how setup works](https://rustsc.com/get-started/index.html.md) - [Compare Rust server tools](https://rustsc.com/compare/index.html.md) ## Who manages what? - **If you run a server for friends.** Start with the jobs you already do yourself. Set a regular restart with a chat warning and keep a backup before the next wipe. You choose the schedule and what the wipe resets. - **If you run a community.** Give moderators access to players and reports on the servers they cover. Your admins can handle plugins and wipes, and you can look up who changed what in Activity. - **If you run several servers.** See your main world, modded server and test server side by side in RustSC. Before doing maintenance on a host, open its page to see which servers run there. - [See how server management works](https://rustsc.com/how-it-works/index.html.md) --- HTML version: https://rustsc.com/about/ RustSC helps you manage your Rust dedicated server from your browser. --- # Your Rust servers on your phone Check a server after a restart, look into a player complaint or pick up an alert away from your desk. Preview the iPhone and Android apps. The web portal also works in your phone’s browser. ## What you can do away from your desk Open the affected server, check what happened and act with the access your role gives you. - **Check whether a server came back.** After a restart, open Overview to see if the server is running and players are returning. - Read the player count and recent frame rate together. - Open recent work to see how the restart ended. Use the server controls to save or restart if your role allows it. - **Look into a problem in the console.** A player reports an error after wipe. Open that server’s Console and search the recent output for the message. - Pause the live feed to read a line in full and copy it for another admin. - Jump back to the latest output. If you can run commands, open a saved command or enter one yourself. - **Find a player and decide what to do.** Open Players on the affected server. Search by name or Steam ID to make sure you have the right person. - Check their ping and session time, or show offline players if they’ve left. - Open their details. If you have moderation access, you can kick or ban from your phone. - **Pick up an alert and follow through.** Open Alerts to see which server stopped responding, which host disconnected, or where a backup did not run. - Open the affected server or host. Acknowledge an alert if you have permission so staff can see it’s been picked up. - If the server has the RustSC plugin, open F7 reports in Alerts to read a player’s report, pick it up and leave a note for staff. ## Start with the servers you already run Connect a server once in the portal and it appears when you sign in to the app. Use the portal for tasks such as installing plugins, setting up a wipe or restoring a backup. 1. **Set up in the web portal.** Connect your existing server in the web portal. Its world, player saves and plugins stay on your host. 2. **Bring your own account.** Sign in with the same account you use in the portal. Invite staff to use their own accounts so they can work without sharing a console password. 3. **Give staff access to the right servers.** Choose which servers each staff member can see and what they can do. They can switch between the servers you’ve shared with them. - [See setup steps](https://rustsc.com/get-started/index.html.md) - [Sign in to the web portal](https://app.rustsc.com/sign-in) ## App availability - **App Store.** iPhone · Coming soon - **Google Play.** Android · Coming soon --- HTML version: https://rustsc.com/mobile-apps/ RustSC helps you manage your Rust dedicated server from your browser. --- # Install RustSC Install RustSC on the Windows or Linux host that runs your server. Use the command from the web portal to install and connect in one step. ## Connect your host to RustSC ### Connect a new host In the portal, open Hosts and choose Add host. Select Windows or Linux, then choose Copy install command. ### Reconnect a host If you’ve already connected a host to RustSC, open its page under Hosts and choose Reconnect. - [See setup steps](https://rustsc.com/get-started/) - [Sign in to your account](https://app.rustsc.com/sign-in) ## Install on Windows ### Paste one command into PowerShell Run it on the host that will run your server and choose Yes when Windows asks. Add host in the web portal shows the same command with your code in it, so the host connects as it installs. ```powershell $f="$env:TEMP\rustsc-install.ps1"; [Net.ServicePointManager]::SecurityProtocol=[Net.ServicePointManager]::SecurityProtocol -bor 3072; iwr https://get.rustsc.com/install.ps1 -UseBasicParsing -OutFile $f; powershell -NoProfile -ExecutionPolicy Bypass -File $f ``` ## Install on Linux ### Paste one command into the terminal Run it on the host that will run your server. Add host in the web portal shows the same command with your code in it, so the host connects as it installs. ```bash curl -fsSL https://get.rustsc.com/install.sh | sudo bash ``` ## Mobile apps ### App Store iPhone · Coming soon ### Google Play Android · Coming soon - [Explore the mobile app](https://rustsc.com/mobile-apps/) ## Release notes ### No host release notes yet HTML version: https://rustsc.com/downloads/ --- # Developer documentation Connect tools to RustSC with the customer API. ## Developer guides - [Which permission each API action needs](https://rustsc.com/help/v1/permissions/index.html.md): Look up a workspace permission to see which API actions use it. - [Use the customer API](https://rustsc.com/help/v1/api/index.html.md): Sign in, find your workspace and make your first request. - [Follow actions and recover safely](https://rustsc.com/help/v1/operations/index.html.md): Avoid duplicate requests, handle changes and cancellations, and recover when the result is unclear. ## Reference and downloads - [Customer API reference](https://rustsc.com/help/v1/reference/index.html.md) - [OpenAPI](https://rustsc.com/help/v1/openapi.json) - [JSON Schemas](https://rustsc.com/help/v1/schemas.json) HTML version: https://rustsc.com/support/developers/ --- # Guides Set up, run and fix your Rust server. ## Set up RustSC - [Your first server in RustSC](https://rustsc.com/support/guides/first-server/index.html.md): Sign in, connect your host, start a server and restart it with a warning. - [Move a server you already run into RustSC](https://rustsc.com/support/guides/move-existing-server/index.html.md): Add a Rust server that is already installed, even while another tool is running it. - [Install RustSC on Linux](https://rustsc.com/support/guides/install-linux/index.html.md): One command installs RustSC on a Linux host and connects it. - [Install RustSC on Windows](https://rustsc.com/support/guides/install-windows/index.html.md): Paste one command into PowerShell and your Windows host is installed and connected. - [Add your first server](https://rustsc.com/support/guides/add-server/index.html.md): Install Rust on a connected host and start your server. - [Choose a server folder](https://rustsc.com/support/guides/server-folder/index.html.md): Choose the folder where RustSC installs your Rust server and keeps its game files, before you start the install. - [Add an existing server](https://rustsc.com/support/guides/add-existing-server/index.html.md): Bring a Rust server you already run into RustSC. Nothing about your server changes until you switch a function on. - [Add a host to your workspace](https://rustsc.com/support/guides/add-host/index.html.md): A host is where your servers run. Connect it once and manage its servers from the portal. - [Reconnect a host](https://rustsc.com/support/guides/reconnect-computer/index.html.md): Restore a host’s connection without reinstalling your servers. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/index.html.md): Connect your hosting company, check what works and fix a connection. - [Remove a host from RustSC](https://rustsc.com/support/guides/remove-host/index.html.md): Disconnect a host and choose what happens to the servers listed in your workspace. ## Run your server - [Start, stop or restart a server](https://rustsc.com/support/guides/start-stop-restart/index.html.md): Start, stop or restart your Rust server from RustSC, and check when it is ready for players to join. - [Messages, restarts and wipes: what players see](https://rustsc.com/support/guides/player-messages/index.html.md): The countdown players read in chat before a restart, a stop or a wipe, and how to change its words. - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/index.html.md): Find game messages, run commands and check server FPS. - [Change server settings](https://rustsc.com/support/guides/server-settings/index.html.md): Change your Rust server's settings in RustSC, save them and apply them to the running server. - [Update Rust](https://rustsc.com/support/guides/update-rust/index.html.md): Install the latest game build and choose automatic updates. - [Change Oxide or Carbon](https://rustsc.com/support/guides/change-framework/index.html.md): Install, update, switch or remove your server’s plugin framework. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/index.html.md): Restart your server at the same time every day, or on the days you choose. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/index.html.md): Search the plugin marketplaces, install a plugin and keep it up to date. - [Remove a server from RustSC](https://rustsc.com/support/guides/remove-server/index.html.md): Remove a server from RustSC and stop managing it there, while the server's files stay where they are. - [Move a server to a new host](https://rustsc.com/support/guides/move-to-new-host/index.html.md): Point a server at a new host after a rebuild or a loss. It keeps its name, history, schedules, rules and backups. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/index.html.md): Find local and cloud commands and their installed help. - [Control a server on its host](https://rustsc.com/support/guides/offline-server-control/index.html.md): Use the Windows app or Linux terminal when you are at your host. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/index.html.md): Check game files and updates, or use the Windows maintenance controls. - [Schedules and activity on the host](https://rustsc.com/support/guides/host-schedules-activity/index.html.md): See local schedules and follow work from a terminal. - [Find more host commands](https://rustsc.com/support/guides/host-command-line/index.html.md): Find the command for console, players, backups and other host tasks. - [Install or update the RustSC plugin](https://rustsc.com/support/guides/rustsc-plugin/index.html.md): Add the RustSC plugin to a server and keep it current. - [Set a quiet time for alerts](https://rustsc.com/support/guides/quiet-alerts/index.html.md): Pause selected alerts for a chosen time, then let them resume. - [Schedule a message or command](https://rustsc.com/support/guides/schedule-messages-commands/index.html.md): Send a message, run a command or post to Discord on a schedule. - [Find and save console lines and commands](https://rustsc.com/support/guides/console-tools/index.html.md): Search the console, save a command and watch for words. - [Schedule a host restart](https://rustsc.com/support/guides/schedule-host-restart/index.html.md): Choose when your host and its servers restart on a schedule. - [Schedule a temporary change](https://rustsc.com/support/guides/temporary-changes/index.html.md): Put files or plugins in place for a while and choose when the change ends. - [Use the live map](https://rustsc.com/support/guides/live-map/index.html.md): See players and events on your server's map and choose what it shows. - [Read server events and chat](https://rustsc.com/support/guides/server-events/index.html.md): Find a recorded server event, search public chat or download a copy. - [Work with server files](https://rustsc.com/support/guides/manage-files/index.html.md): Find, upload and change files for a server from the Files tab. - [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/index.html.md): Choose the alerts you need and where you receive them. - [Manage several servers at once](https://rustsc.com/support/guides/bulk-actions/index.html.md): Send a message, change access or copy settings to a group of servers. - [Find and select servers in a workspace](https://rustsc.com/support/guides/find-a-server-in-your-workspace/index.html.md): Use Home or the Servers list to find the servers you manage. - [Announce or recover a temporary change](https://rustsc.com/support/guides/temporary-change-messages-and-recovery/index.html.md): Tell players when a change starts or ends and check what happened to its files. - [Review startup and performance settings](https://rustsc.com/support/guides/advanced-game-settings/index.html.md): Check what starts your server or change how it uses the host's processors. - [Get alerts for words in chat or console](https://rustsc.com/support/guides/watch-chat-and-console-words/index.html.md): Watch for a word or phrase on the servers you choose. - [Install a plugin from a link or a file](https://rustsc.com/support/guides/install-plugin-from-a-link/index.html.md): Check a plugin link before installing it, or upload a plugin file you already have. - [Choose a plugin update source and go back if needed](https://rustsc.com/support/guides/plugin-update-source-and-recovery/index.html.md): Check which version you are installing and put the previous plugin file back when needed. - [Edit a plugin's settings and messages](https://rustsc.com/support/guides/edit-plugin-settings-and-language/index.html.md): Open a plugin's files, review a change and see when it takes effect. - [Import or download server settings](https://rustsc.com/support/guides/import-server-settings/index.html.md): Review settings from a file before applying them to a server. - [Review settings changed outside RustSC](https://rustsc.com/support/guides/review-server-setting-changes/index.html.md): Decide whether to keep the server's setting or the value you saved in RustSC. - [Change the ports players use to join](https://rustsc.com/support/guides/change-server-ports/index.html.md): Change a server's ports and check which ones are in use. - [Save Nexus network settings for a server](https://rustsc.com/support/guides/save-nexus-network-settings/index.html.md): Use a Nexus key you already have to set up a server's next start. - [Find and inspect things on the live map](https://rustsc.com/support/guides/find-things-on-the-map/index.html.md): Find entities by name, owner or location, then inspect or count them. - [Make a rule that responds to a server event](https://rustsc.com/support/guides/make-a-server-event-rule/index.html.md): Send a message or alert automatically when something happens on a server. ## Backups and wipes - [Backups on your host](https://rustsc.com/support/guides/backups-local-and-offsite/index.html.md): Make a backup, make them regular and see where they are kept. - [Back up a server](https://rustsc.com/support/guides/back-up-server/index.html.md): Choose where backups go, make one, decide how many to keep and restore one. - [Free disk space](https://rustsc.com/support/guides/free-disk-space/index.html.md): Remove older backups and files while keeping your current world. - [Restore a backup](https://rustsc.com/support/guides/restore-backup/index.html.md): Choose a backup in RustSC and return your Rust server to the way it was when that backup was taken. - [Recover a damaged save](https://rustsc.com/support/guides/recover-save/index.html.md): Use a previous save when Rust cannot load the current one. - [Wipe your server](https://rustsc.com/support/guides/wipe-server/index.html.md): Start a new map and choose which player data to reset. - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/index.html.md): Choose the day and time your Rust server gets a new map, so each wipe happens on its own. - [Wipe plans in plain words](https://rustsc.com/support/guides/wipe-plans/index.html.md): A wipe plan is everything one wipe does, saved so you can run it again. - [Preview your map](https://rustsc.com/support/guides/preview-map/index.html.md): See a map before the server runs it, whether you pick a size and seed or use your own map file. - [Back up or restore on the host](https://rustsc.com/support/guides/host-backups/index.html.md): Make a local backup or restore one without the portal. - [Copy a backup as a new server](https://rustsc.com/support/guides/copy-backup/index.html.md): Make a separate server from a backup and start it when you are ready. - [Use a link to a custom map](https://rustsc.com/support/guides/use-a-custom-map-link/index.html.md): Give Rust and your players an address that downloads the map file. - [Plan a map rotation for wipes](https://rustsc.com/support/guides/plan-a-map-rotation/index.html.md): Choose the maps a saved wipe uses and what happens at the end of the list. ## Players and access - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/index.html.md): Find a player on your Rust server, kick or ban them from RustSC, and lift a ban when you change your mind. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/index.html.md): Give a player or a group the permissions of your plugins, and make staff. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/index.html.md): Players link their Steam and Discord accounts with a code. Staff look links up with /link search. - [Move existing Discord links](https://rustsc.com/support/guides/move-discord-links/index.html.md): Keep your players’ links when moving from another Discord service. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/index.html.md): Get told when a server goes offline, a backup or wipe fails, or a host runs low on space. - [Understand workspace roles](https://rustsc.com/support/guides/workspace-roles/index.html.md): See what each role in your RustSC workspace can do, so you know what you and your team can change. - [Let a moderator run a few commands](https://rustsc.com/support/guides/mod-commands/index.html.md): Write a command with blanks once. A moderator fills in the blanks and presses Run, without the console. - [Give someone access to only some servers or hosts](https://rustsc.com/support/guides/limited-access/index.html.md): Invite a helper to the servers and hosts you choose, and nothing else. - [See what your team did](https://rustsc.com/support/guides/team-activity/index.html.md): Find who started a restart, a backup or a wipe, and what came of it. - [Choose who can join](https://rustsc.com/support/guides/join-rules/index.html.md): Set join rules and ban lists, then review the decisions made for players. - [Import or download bans](https://rustsc.com/support/guides/import-bans/index.html.md): Bring in a list of bans or save a copy of the list. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/index.html.md): Choose how your server shares chat and linked player roles with Discord. - [Help a player in game](https://rustsc.com/support/guides/player-actions/index.html.md): Use the player menu to heal, move, message or give items. - [See player and server stats](https://rustsc.com/support/guides/player-stats/index.html.md): See who played and how busy your server has been over a chosen period. - [View a player and take action](https://rustsc.com/support/guides/player-details/index.html.md): Open a player's history, notes and available actions. - [Review F7 reports and find events](https://rustsc.com/support/guides/review-player-reports/index.html.md): Find a player's report, check what happened and record your team's decision. - [Keep player permissions the same across servers](https://rustsc.com/support/guides/sync-player-permissions/index.html.md): Preview and share permissions between the servers you choose. ## Fix a problem - [Get help](https://rustsc.com/support/guides/get-help/index.html.md): Send a support request from the portal and attach a file if it helps. - [If something is not working](https://rustsc.com/support/guides/not-working/index.html.md): What to check first, how to make a support file and how to ask for help. - [Host offline](https://rustsc.com/support/guides/computer-offline/index.html.md): Restore a connection while keeping your game server running. - [Server will not start](https://rustsc.com/support/guides/server-will-not-start/index.html.md): Find out why your Rust server did not start, read what RustSC reports and choose the next step. - [An action failed or stopped](https://rustsc.com/support/guides/action-failed/index.html.md): Check what happened when an action failed or stopped, so you know whether it is safe to try again. - [What a message means and what to do](https://rustsc.com/support/guides/fix-common-problems/index.html.md): Plain answers behind the short notices in RustSC: what each check proved and the one next step. - [Check a host’s performance and logs](https://rustsc.com/support/guides/host-performance-and-logs/index.html.md): Find a busy host, investigate a game exit or save the log lines you need. ## Account - [Manage workspace access](https://rustsc.com/support/guides/workspace-access/index.html.md): Find your workspace or ask for the access you need. - [Manage your sign-in and security](https://rustsc.com/support/guides/account-sign-in-security/index.html.md): Add or remove a sign-in method, see where you are signed in and end a sign-in. - [Download your data or delete your account](https://rustsc.com/support/guides/account-data/index.html.md): Export your account data and review what happens to workspaces before deleting your account. - [Choose how people sign in to a workspace](https://rustsc.com/support/guides/workspace-sign-in-rule/index.html.md): Set allowed sign-in methods and decide how often members sign in again. - [Make, limit or revoke an API key](https://rustsc.com/support/guides/make-api-key/index.html.md): Give a script access to the right workspace and servers, then replace or revoke its key. - [Download, hand over or close a workspace](https://rustsc.com/support/guides/workspace-data-closing/index.html.md): Download workspace data, make another member the owner or review closing the workspace. - [Set up a workspace integration](https://rustsc.com/support/guides/workspace-integrations/index.html.md): Set up, check or remove the workspace's Steam, Codefling and RustHQ connections. ## Feature reference - [Alerts reference](https://rustsc.com/support/guides/reference-alerts/index.html.md): Find a specific action or setting for alerts and open the related instructions in RustSC. - [API access and assistants reference](https://rustsc.com/support/guides/reference-api-access-and-assistants/index.html.md): Find a specific action or setting for api access and assistants and open the related instructions in RustSC. - [Automation reference](https://rustsc.com/support/guides/reference-automation/index.html.md): Find a specific action or setting for automation and open the related instructions in RustSC. - [Bans and join rules reference](https://rustsc.com/support/guides/reference-bans-and-join-rules/index.html.md): Find a specific action or setting for bans and join rules and open the related instructions in RustSC. - [Backups reference](https://rustsc.com/support/guides/reference-backups/index.html.md): Find a specific action or setting for backups and open the related instructions in RustSC. - [Console and chat reference](https://rustsc.com/support/guides/reference-console-and-chat/index.html.md): Find a specific action or setting for console and chat and open the related instructions in RustSC. - [Server configuration reference](https://rustsc.com/support/guides/reference-server-configuration/index.html.md): Find a specific action or setting for server configuration and open the related instructions in RustSC. - [Discord community reference](https://rustsc.com/support/guides/reference-discord-community/index.html.md): Find a specific action or setting for discord community and open the related instructions in RustSC. - [Discord server updates reference](https://rustsc.com/support/guides/reference-discord-server-updates/index.html.md): Find a specific action or setting for discord server updates and open the related instructions in RustSC. - [Reports and evidence reference](https://rustsc.com/support/guides/reference-reports-and-evidence/index.html.md): Find a specific action or setting for reports and evidence and open the related instructions in RustSC. - [Server files reference](https://rustsc.com/support/guides/reference-server-files/index.html.md): Find a specific action or setting for server files and open the related instructions in RustSC. - [Server groups reference](https://rustsc.com/support/guides/reference-server-groups/index.html.md): Find a specific action or setting for server groups and open the related instructions in RustSC. - [Community features reference](https://rustsc.com/support/guides/reference-community-features/index.html.md): Find a specific action or setting for community features and open the related instructions in RustSC. - [Getting started reference](https://rustsc.com/support/guides/reference-getting-started/index.html.md): Find a specific action or setting for getting started and open the related instructions in RustSC. - [Help and feedback reference](https://rustsc.com/support/guides/reference-help-and-feedback/index.html.md): Find a specific action or setting for help and feedback and open the related instructions in RustSC. - [Host maintenance reference](https://rustsc.com/support/guides/reference-host-maintenance/index.html.md): Find a specific action or setting for host maintenance and open the related instructions in RustSC. - [Hosts reference](https://rustsc.com/support/guides/reference-hosts/index.html.md): Find a specific action or setting for hosts and open the related instructions in RustSC. - [Server lifecycle reference](https://rustsc.com/support/guides/reference-server-lifecycle/index.html.md): Find a specific action or setting for server lifecycle and open the related instructions in RustSC. - [Live maps reference](https://rustsc.com/support/guides/reference-live-maps/index.html.md): Find a specific action or setting for live maps and open the related instructions in RustSC. - [Maps and worlds reference](https://rustsc.com/support/guides/reference-maps-and-worlds/index.html.md): Find a specific action or setting for maps and worlds and open the related instructions in RustSC. - [Portal on a phone reference](https://rustsc.com/support/guides/reference-portal-on-a-phone/index.html.md): Find a specific action or setting for portal on a phone and open the related instructions in RustSC. - [Performance reference](https://rustsc.com/support/guides/reference-performance/index.html.md): Find a specific action or setting for performance and open the related instructions in RustSC. - [Player permissions reference](https://rustsc.com/support/guides/reference-player-permissions/index.html.md): Find a specific action or setting for player permissions and open the related instructions in RustSC. - [Players reference](https://rustsc.com/support/guides/reference-players/index.html.md): Find a specific action or setting for players and open the related instructions in RustSC. - [Plugins reference](https://rustsc.com/support/guides/reference-plugins/index.html.md): Find a specific action or setting for plugins and open the related instructions in RustSC. - [Rented servers reference](https://rustsc.com/support/guides/reference-rented-servers/index.html.md): Find a specific action or setting for rented servers and open the related instructions in RustSC. - [Schedules reference](https://rustsc.com/support/guides/reference-schedules/index.html.md): Find a specific action or setting for schedules and open the related instructions in RustSC. - [Members and accounts reference](https://rustsc.com/support/guides/reference-members-and-accounts/index.html.md): Find a specific action or setting for members and accounts and open the related instructions in RustSC. - [Access and privacy reference](https://rustsc.com/support/guides/reference-access-and-privacy/index.html.md): Find a specific action or setting for access and privacy and open the related instructions in RustSC. - [Software updates reference](https://rustsc.com/support/guides/reference-software-updates/index.html.md): Find a specific action or setting for software updates and open the related instructions in RustSC. - [Wipes reference](https://rustsc.com/support/guides/reference-wipes/index.html.md): Find a specific action or setting for wipes and open the related instructions in RustSC. HTML version: https://rustsc.com/support/guides/ --- # Support Find an answer or get help with your server. ## Set up RustSC - [Your first server in RustSC](https://rustsc.com/support/guides/first-server/index.html.md): Sign in, connect your host, start a server and restart it with a warning. - [Move a server you already run into RustSC](https://rustsc.com/support/guides/move-existing-server/index.html.md): Add a Rust server that is already installed, even while another tool is running it. - [Install RustSC on Linux](https://rustsc.com/support/guides/install-linux/index.html.md): One command installs RustSC on a Linux host and connects it. - [Install RustSC on Windows](https://rustsc.com/support/guides/install-windows/index.html.md): Paste one command into PowerShell and your Windows host is installed and connected. - [Add your first server](https://rustsc.com/support/guides/add-server/index.html.md): Install Rust on a connected host and start your server. - [Choose a server folder](https://rustsc.com/support/guides/server-folder/index.html.md): Choose the folder where RustSC installs your Rust server and keeps its game files, before you start the install. - [Add an existing server](https://rustsc.com/support/guides/add-existing-server/index.html.md): Bring a Rust server you already run into RustSC. Nothing about your server changes until you switch a function on. - [Add a host to your workspace](https://rustsc.com/support/guides/add-host/index.html.md): A host is where your servers run. Connect it once and manage its servers from the portal. - [Reconnect a host](https://rustsc.com/support/guides/reconnect-computer/index.html.md): Restore a host’s connection without reinstalling your servers. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/index.html.md): Connect your hosting company, check what works and fix a connection. - [Remove a host from RustSC](https://rustsc.com/support/guides/remove-host/index.html.md): Disconnect a host and choose what happens to the servers listed in your workspace. ## Run your server - [Start, stop or restart a server](https://rustsc.com/support/guides/start-stop-restart/index.html.md): Start, stop or restart your Rust server from RustSC, and check when it is ready for players to join. - [Messages, restarts and wipes: what players see](https://rustsc.com/support/guides/player-messages/index.html.md): The countdown players read in chat before a restart, a stop or a wipe, and how to change its words. - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/index.html.md): Find game messages, run commands and check server FPS. - [Change server settings](https://rustsc.com/support/guides/server-settings/index.html.md): Change your Rust server's settings in RustSC, save them and apply them to the running server. - [Update Rust](https://rustsc.com/support/guides/update-rust/index.html.md): Install the latest game build and choose automatic updates. - [Change Oxide or Carbon](https://rustsc.com/support/guides/change-framework/index.html.md): Install, update, switch or remove your server’s plugin framework. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/index.html.md): Restart your server at the same time every day, or on the days you choose. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/index.html.md): Search the plugin marketplaces, install a plugin and keep it up to date. - [Remove a server from RustSC](https://rustsc.com/support/guides/remove-server/index.html.md): Remove a server from RustSC and stop managing it there, while the server's files stay where they are. - [Move a server to a new host](https://rustsc.com/support/guides/move-to-new-host/index.html.md): Point a server at a new host after a rebuild or a loss. It keeps its name, history, schedules, rules and backups. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/index.html.md): Find local and cloud commands and their installed help. - [Control a server on its host](https://rustsc.com/support/guides/offline-server-control/index.html.md): Use the Windows app or Linux terminal when you are at your host. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/index.html.md): Check game files and updates, or use the Windows maintenance controls. - [Schedules and activity on the host](https://rustsc.com/support/guides/host-schedules-activity/index.html.md): See local schedules and follow work from a terminal. - [Find more host commands](https://rustsc.com/support/guides/host-command-line/index.html.md): Find the command for console, players, backups and other host tasks. - [Install or update the RustSC plugin](https://rustsc.com/support/guides/rustsc-plugin/index.html.md): Add the RustSC plugin to a server and keep it current. - [Set a quiet time for alerts](https://rustsc.com/support/guides/quiet-alerts/index.html.md): Pause selected alerts for a chosen time, then let them resume. - [Schedule a message or command](https://rustsc.com/support/guides/schedule-messages-commands/index.html.md): Send a message, run a command or post to Discord on a schedule. - [Find and save console lines and commands](https://rustsc.com/support/guides/console-tools/index.html.md): Search the console, save a command and watch for words. - [Schedule a host restart](https://rustsc.com/support/guides/schedule-host-restart/index.html.md): Choose when your host and its servers restart on a schedule. - [Schedule a temporary change](https://rustsc.com/support/guides/temporary-changes/index.html.md): Put files or plugins in place for a while and choose when the change ends. - [Use the live map](https://rustsc.com/support/guides/live-map/index.html.md): See players and events on your server's map and choose what it shows. - [Read server events and chat](https://rustsc.com/support/guides/server-events/index.html.md): Find a recorded server event, search public chat or download a copy. - [Work with server files](https://rustsc.com/support/guides/manage-files/index.html.md): Find, upload and change files for a server from the Files tab. - [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/index.html.md): Choose the alerts you need and where you receive them. - [Manage several servers at once](https://rustsc.com/support/guides/bulk-actions/index.html.md): Send a message, change access or copy settings to a group of servers. - [Find and select servers in a workspace](https://rustsc.com/support/guides/find-a-server-in-your-workspace/index.html.md): Use Home or the Servers list to find the servers you manage. - [Announce or recover a temporary change](https://rustsc.com/support/guides/temporary-change-messages-and-recovery/index.html.md): Tell players when a change starts or ends and check what happened to its files. - [Review startup and performance settings](https://rustsc.com/support/guides/advanced-game-settings/index.html.md): Check what starts your server or change how it uses the host's processors. - [Get alerts for words in chat or console](https://rustsc.com/support/guides/watch-chat-and-console-words/index.html.md): Watch for a word or phrase on the servers you choose. - [Install a plugin from a link or a file](https://rustsc.com/support/guides/install-plugin-from-a-link/index.html.md): Check a plugin link before installing it, or upload a plugin file you already have. - [Choose a plugin update source and go back if needed](https://rustsc.com/support/guides/plugin-update-source-and-recovery/index.html.md): Check which version you are installing and put the previous plugin file back when needed. - [Edit a plugin's settings and messages](https://rustsc.com/support/guides/edit-plugin-settings-and-language/index.html.md): Open a plugin's files, review a change and see when it takes effect. - [Import or download server settings](https://rustsc.com/support/guides/import-server-settings/index.html.md): Review settings from a file before applying them to a server. - [Review settings changed outside RustSC](https://rustsc.com/support/guides/review-server-setting-changes/index.html.md): Decide whether to keep the server's setting or the value you saved in RustSC. - [Change the ports players use to join](https://rustsc.com/support/guides/change-server-ports/index.html.md): Change a server's ports and check which ones are in use. - [Save Nexus network settings for a server](https://rustsc.com/support/guides/save-nexus-network-settings/index.html.md): Use a Nexus key you already have to set up a server's next start. - [Find and inspect things on the live map](https://rustsc.com/support/guides/find-things-on-the-map/index.html.md): Find entities by name, owner or location, then inspect or count them. - [Make a rule that responds to a server event](https://rustsc.com/support/guides/make-a-server-event-rule/index.html.md): Send a message or alert automatically when something happens on a server. ## Backups and wipes - [Backups on your host](https://rustsc.com/support/guides/backups-local-and-offsite/index.html.md): Make a backup, make them regular and see where they are kept. - [Back up a server](https://rustsc.com/support/guides/back-up-server/index.html.md): Choose where backups go, make one, decide how many to keep and restore one. - [Free disk space](https://rustsc.com/support/guides/free-disk-space/index.html.md): Remove older backups and files while keeping your current world. - [Restore a backup](https://rustsc.com/support/guides/restore-backup/index.html.md): Choose a backup in RustSC and return your Rust server to the way it was when that backup was taken. - [Recover a damaged save](https://rustsc.com/support/guides/recover-save/index.html.md): Use a previous save when Rust cannot load the current one. - [Wipe your server](https://rustsc.com/support/guides/wipe-server/index.html.md): Start a new map and choose which player data to reset. - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/index.html.md): Choose the day and time your Rust server gets a new map, so each wipe happens on its own. - [Wipe plans in plain words](https://rustsc.com/support/guides/wipe-plans/index.html.md): A wipe plan is everything one wipe does, saved so you can run it again. - [Preview your map](https://rustsc.com/support/guides/preview-map/index.html.md): See a map before the server runs it, whether you pick a size and seed or use your own map file. - [Back up or restore on the host](https://rustsc.com/support/guides/host-backups/index.html.md): Make a local backup or restore one without the portal. - [Copy a backup as a new server](https://rustsc.com/support/guides/copy-backup/index.html.md): Make a separate server from a backup and start it when you are ready. - [Use a link to a custom map](https://rustsc.com/support/guides/use-a-custom-map-link/index.html.md): Give Rust and your players an address that downloads the map file. - [Plan a map rotation for wipes](https://rustsc.com/support/guides/plan-a-map-rotation/index.html.md): Choose the maps a saved wipe uses and what happens at the end of the list. ## Players and access - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/index.html.md): Find a player on your Rust server, kick or ban them from RustSC, and lift a ban when you change your mind. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/index.html.md): Give a player or a group the permissions of your plugins, and make staff. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/index.html.md): Players link their Steam and Discord accounts with a code. Staff look links up with /link search. - [Move existing Discord links](https://rustsc.com/support/guides/move-discord-links/index.html.md): Keep your players’ links when moving from another Discord service. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/index.html.md): Get told when a server goes offline, a backup or wipe fails, or a host runs low on space. - [Understand workspace roles](https://rustsc.com/support/guides/workspace-roles/index.html.md): See what each role in your RustSC workspace can do, so you know what you and your team can change. - [Let a moderator run a few commands](https://rustsc.com/support/guides/mod-commands/index.html.md): Write a command with blanks once. A moderator fills in the blanks and presses Run, without the console. - [Give someone access to only some servers or hosts](https://rustsc.com/support/guides/limited-access/index.html.md): Invite a helper to the servers and hosts you choose, and nothing else. - [See what your team did](https://rustsc.com/support/guides/team-activity/index.html.md): Find who started a restart, a backup or a wipe, and what came of it. - [Choose who can join](https://rustsc.com/support/guides/join-rules/index.html.md): Set join rules and ban lists, then review the decisions made for players. - [Import or download bans](https://rustsc.com/support/guides/import-bans/index.html.md): Bring in a list of bans or save a copy of the list. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/index.html.md): Choose how your server shares chat and linked player roles with Discord. - [Help a player in game](https://rustsc.com/support/guides/player-actions/index.html.md): Use the player menu to heal, move, message or give items. - [See player and server stats](https://rustsc.com/support/guides/player-stats/index.html.md): See who played and how busy your server has been over a chosen period. - [View a player and take action](https://rustsc.com/support/guides/player-details/index.html.md): Open a player's history, notes and available actions. - [Review F7 reports and find events](https://rustsc.com/support/guides/review-player-reports/index.html.md): Find a player's report, check what happened and record your team's decision. - [Keep player permissions the same across servers](https://rustsc.com/support/guides/sync-player-permissions/index.html.md): Preview and share permissions between the servers you choose. ## Fix a problem - [Get help](https://rustsc.com/support/guides/get-help/index.html.md): Send a support request from the portal and attach a file if it helps. - [If something is not working](https://rustsc.com/support/guides/not-working/index.html.md): What to check first, how to make a support file and how to ask for help. - [Host offline](https://rustsc.com/support/guides/computer-offline/index.html.md): Restore a connection while keeping your game server running. - [Server will not start](https://rustsc.com/support/guides/server-will-not-start/index.html.md): Find out why your Rust server did not start, read what RustSC reports and choose the next step. - [An action failed or stopped](https://rustsc.com/support/guides/action-failed/index.html.md): Check what happened when an action failed or stopped, so you know whether it is safe to try again. - [What a message means and what to do](https://rustsc.com/support/guides/fix-common-problems/index.html.md): Plain answers behind the short notices in RustSC: what each check proved and the one next step. - [Check a host’s performance and logs](https://rustsc.com/support/guides/host-performance-and-logs/index.html.md): Find a busy host, investigate a game exit or save the log lines you need. ## Account - [Manage workspace access](https://rustsc.com/support/guides/workspace-access/index.html.md): Find your workspace or ask for the access you need. - [Manage your sign-in and security](https://rustsc.com/support/guides/account-sign-in-security/index.html.md): Add or remove a sign-in method, see where you are signed in and end a sign-in. - [Download your data or delete your account](https://rustsc.com/support/guides/account-data/index.html.md): Export your account data and review what happens to workspaces before deleting your account. - [Choose how people sign in to a workspace](https://rustsc.com/support/guides/workspace-sign-in-rule/index.html.md): Set allowed sign-in methods and decide how often members sign in again. - [Make, limit or revoke an API key](https://rustsc.com/support/guides/make-api-key/index.html.md): Give a script access to the right workspace and servers, then replace or revoke its key. - [Download, hand over or close a workspace](https://rustsc.com/support/guides/workspace-data-closing/index.html.md): Download workspace data, make another member the owner or review closing the workspace. - [Set up a workspace integration](https://rustsc.com/support/guides/workspace-integrations/index.html.md): Set up, check or remove the workspace's Steam, Codefling and RustHQ connections. ## Feature reference - [Alerts reference](https://rustsc.com/support/guides/reference-alerts/index.html.md): Find a specific action or setting for alerts and open the related instructions in RustSC. - [API access and assistants reference](https://rustsc.com/support/guides/reference-api-access-and-assistants/index.html.md): Find a specific action or setting for api access and assistants and open the related instructions in RustSC. - [Automation reference](https://rustsc.com/support/guides/reference-automation/index.html.md): Find a specific action or setting for automation and open the related instructions in RustSC. - [Bans and join rules reference](https://rustsc.com/support/guides/reference-bans-and-join-rules/index.html.md): Find a specific action or setting for bans and join rules and open the related instructions in RustSC. - [Backups reference](https://rustsc.com/support/guides/reference-backups/index.html.md): Find a specific action or setting for backups and open the related instructions in RustSC. - [Console and chat reference](https://rustsc.com/support/guides/reference-console-and-chat/index.html.md): Find a specific action or setting for console and chat and open the related instructions in RustSC. - [Server configuration reference](https://rustsc.com/support/guides/reference-server-configuration/index.html.md): Find a specific action or setting for server configuration and open the related instructions in RustSC. - [Discord community reference](https://rustsc.com/support/guides/reference-discord-community/index.html.md): Find a specific action or setting for discord community and open the related instructions in RustSC. - [Discord server updates reference](https://rustsc.com/support/guides/reference-discord-server-updates/index.html.md): Find a specific action or setting for discord server updates and open the related instructions in RustSC. - [Reports and evidence reference](https://rustsc.com/support/guides/reference-reports-and-evidence/index.html.md): Find a specific action or setting for reports and evidence and open the related instructions in RustSC. - [Server files reference](https://rustsc.com/support/guides/reference-server-files/index.html.md): Find a specific action or setting for server files and open the related instructions in RustSC. - [Server groups reference](https://rustsc.com/support/guides/reference-server-groups/index.html.md): Find a specific action or setting for server groups and open the related instructions in RustSC. - [Community features reference](https://rustsc.com/support/guides/reference-community-features/index.html.md): Find a specific action or setting for community features and open the related instructions in RustSC. - [Getting started reference](https://rustsc.com/support/guides/reference-getting-started/index.html.md): Find a specific action or setting for getting started and open the related instructions in RustSC. - [Help and feedback reference](https://rustsc.com/support/guides/reference-help-and-feedback/index.html.md): Find a specific action or setting for help and feedback and open the related instructions in RustSC. - [Host maintenance reference](https://rustsc.com/support/guides/reference-host-maintenance/index.html.md): Find a specific action or setting for host maintenance and open the related instructions in RustSC. - [Hosts reference](https://rustsc.com/support/guides/reference-hosts/index.html.md): Find a specific action or setting for hosts and open the related instructions in RustSC. - [Server lifecycle reference](https://rustsc.com/support/guides/reference-server-lifecycle/index.html.md): Find a specific action or setting for server lifecycle and open the related instructions in RustSC. - [Live maps reference](https://rustsc.com/support/guides/reference-live-maps/index.html.md): Find a specific action or setting for live maps and open the related instructions in RustSC. - [Maps and worlds reference](https://rustsc.com/support/guides/reference-maps-and-worlds/index.html.md): Find a specific action or setting for maps and worlds and open the related instructions in RustSC. - [Portal on a phone reference](https://rustsc.com/support/guides/reference-portal-on-a-phone/index.html.md): Find a specific action or setting for portal on a phone and open the related instructions in RustSC. - [Performance reference](https://rustsc.com/support/guides/reference-performance/index.html.md): Find a specific action or setting for performance and open the related instructions in RustSC. - [Player permissions reference](https://rustsc.com/support/guides/reference-player-permissions/index.html.md): Find a specific action or setting for player permissions and open the related instructions in RustSC. - [Players reference](https://rustsc.com/support/guides/reference-players/index.html.md): Find a specific action or setting for players and open the related instructions in RustSC. - [Plugins reference](https://rustsc.com/support/guides/reference-plugins/index.html.md): Find a specific action or setting for plugins and open the related instructions in RustSC. - [Rented servers reference](https://rustsc.com/support/guides/reference-rented-servers/index.html.md): Find a specific action or setting for rented servers and open the related instructions in RustSC. - [Schedules reference](https://rustsc.com/support/guides/reference-schedules/index.html.md): Find a specific action or setting for schedules and open the related instructions in RustSC. - [Members and accounts reference](https://rustsc.com/support/guides/reference-members-and-accounts/index.html.md): Find a specific action or setting for members and accounts and open the related instructions in RustSC. - [Access and privacy reference](https://rustsc.com/support/guides/reference-access-and-privacy/index.html.md): Find a specific action or setting for access and privacy and open the related instructions in RustSC. - [Software updates reference](https://rustsc.com/support/guides/reference-software-updates/index.html.md): Find a specific action or setting for software updates and open the related instructions in RustSC. - [Wipes reference](https://rustsc.com/support/guides/reference-wipes/index.html.md): Find a specific action or setting for wipes and open the related instructions in RustSC. ## More support - [Contact support](https://app.rustsc.com/support) - [Contact RustSC](https://rustsc.com/support/contact/) - [Install RustSC](https://rustsc.com/downloads/) - [Release notes](https://rustsc.com/release-notes/) - [Common questions](https://rustsc.com/support/faq/) - [Developer documentation](https://rustsc.com/support/developers/) - [Connection problems](https://rustsc.com/status/) - [Account access](https://rustsc.com/account-recovery/) - [Accessibility](https://rustsc.com/accessibility/) - [Server support](https://rustsc.com/support/technical/) - [Sign in for support](https://app.rustsc.com/support) HTML version: https://rustsc.com/support/ --- # Server support Sign in and choose Contact support for help with your server or workspace. ## Get server help - [Contact support](https://app.rustsc.com/support?topic=technical) - [Get sign-in help](https://rustsc.com/support/account/) HTML version: https://rustsc.com/support/technical/ --- # RustSC open beta Open beta is coming in early 2027 - [Get an email when open beta launches](https://rustsc.com/sign-up/) --- HTML version: https://rustsc.com/sign-up/ RustSC helps you manage your Rust dedicated server from your browser. --- # Sign-in help Sign in with Discord, or with a passkey that you added to your account. ## Fix a sign-in problem ### You lost your Discord account Get back into your Discord account first, then continue with Discord. If you added a passkey, sign in with that and link your new Discord account. ### You cannot sign in any way Use the sign-in help form with the email address on your account. Tell us which Discord account you normally use. - [Sign in](https://app.rustsc.com/sign-in) - [Get sign-in help](https://rustsc.com/support/account/) HTML version: https://rustsc.com/account-recovery/ --- # Connection problems Choose what is not connecting. ## What is not working? ### The portal will not load Check that other websites load, then reload the portal. If it still will not open, contact support. ### Your host is offline Check that the host is on and connected to the internet. Your game may still be running. Open RustSC on that host to check it. ### A server action failed Open the result and follow its next step. If the result is unknown, check the server before trying again. - [Troubleshooting guide](https://rustsc.com/help/v1/troubleshooting/) - [Report a problem](https://app.rustsc.com/support) - [Server support](https://rustsc.com/support/technical/) HTML version: https://rustsc.com/status/ --- # Accessibility Read guides and contact support with a keyboard, touch screen or assistive technology. ## Use the site your way ### Keyboard and enlarged text Use Skip to main content to reach the page. You can zoom in with your browser and use Tab to move between links and controls. ### Motion and scripts Guides and the support form work without JavaScript. Search needs JavaScript; you can browse topics instead. ### Tell us about a barrier Tell us which page is difficult to use and what you were trying to do. - [Report an accessibility problem](https://rustsc.com/support/accessibility/) HTML version: https://rustsc.com/accessibility/ --- # Rust hosting providers RustSC supports Keep your existing Rust host. Choose your provider to see which details to copy from its panel, what you can manage in RustSC and which jobs you will still do with the provider. ## How RustSC connects - **Through the host's panel.** Where RustSC has a panel connection, you paste a key for your server. RustSC then offers the console, files, schedules, wipes and the power controls your key allows. - **Through the console and file login.** On any other Rust host, you pick Another host and enter the server's file login (SFTP, FTPS or FTP) and its remote console (RCON) password. RustSC then offers the console, files and plugins, schedules and wipes. - **If you have the whole machine.** If you can install software on the Windows or Linux machine that runs the game, use the host app instead. This gives RustSC local controls for starting the game, installing updates and backing up your saves. ## Hosting providers and panels - [AMP panel](https://rustsc.com/hosting/amp/index.html.md) - [Apex Hosting](https://rustsc.com/hosting/apex-hosting/index.html.md) - [BisectHosting](https://rustsc.com/hosting/bisecthosting/index.html.md) - [Bloom.host](https://rustsc.com/hosting/bloom-host/index.html.md) - [Citadel Servers](https://rustsc.com/hosting/citadel-servers/index.html.md) - [CreeperHost](https://rustsc.com/hosting/creeperhost/index.html.md) - [Cybrancee](https://rustsc.com/hosting/cybrancee/index.html.md) - [Freak Hosting](https://rustsc.com/hosting/freak-hosting/index.html.md) - [GameHostBros](https://rustsc.com/hosting/gamehostbros/index.html.md) - [GameServerKings](https://rustsc.com/hosting/gameserverkings/index.html.md) - [Godlike](https://rustsc.com/hosting/godlike/index.html.md) - [GPortal](https://rustsc.com/hosting/gportal/index.html.md) - [GTX Gaming](https://rustsc.com/hosting/gtx-gaming/index.html.md) - [Host Havoc](https://rustsc.com/hosting/host-havoc/index.html.md) - [Hostinger](https://rustsc.com/hosting/hostinger/index.html.md) - [Iceline Hosting](https://rustsc.com/hosting/iceline-hosting/index.html.md) - [Loafhosts](https://rustsc.com/hosting/loafhosts/index.html.md) - [LOW.MS](https://rustsc.com/hosting/low-ms/index.html.md) - [Nitrado](https://rustsc.com/hosting/nitrado/index.html.md) - [Nodecraft](https://rustsc.com/hosting/nodecraft/index.html.md) - [Pelican panel](https://rustsc.com/hosting/pelican/index.html.md) - [Physgun](https://rustsc.com/hosting/physgun/index.html.md) - [Pine Hosting](https://rustsc.com/hosting/pine-hosting/index.html.md) - [PingPerfect](https://rustsc.com/hosting/pingperfect/index.html.md) - [Pterodactyl panel](https://rustsc.com/hosting/pterodactyl/index.html.md) - [ScalaCube](https://rustsc.com/hosting/scalacube/index.html.md) - [Shockbyte](https://rustsc.com/hosting/shockbyte/index.html.md) - [Sparked Host](https://rustsc.com/hosting/sparked-host/index.html.md) - [Starbase panel](https://rustsc.com/hosting/starbase/index.html.md) - [Supercraft](https://rustsc.com/hosting/supercraft/index.html.md) - [Survival Servers](https://rustsc.com/hosting/survival-servers/index.html.md) - [TCAdmin panel](https://rustsc.com/hosting/tcadmin/index.html.md) - [Terabit](https://rustsc.com/hosting/terabit/index.html.md) - [Vastrox](https://rustsc.com/hosting/vastrox/index.html.md) - [Wabbanode](https://rustsc.com/hosting/wabbanode/index.html.md) - [WinterNode](https://rustsc.com/hosting/winternode/index.html.md) - [WISP panel](https://rustsc.com/hosting/wisp/index.html.md) - [XGamingServer](https://rustsc.com/hosting/xgamingserver/index.html.md) - [ZAP-Hosting](https://rustsc.com/hosting/zap-hosting/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) --- HTML version: https://rustsc.com/hosting/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Rust servers on the AMP panel AMP, from CubeCoders, is game server panel software that server owners install on a host they rent. Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for AMP panel servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in the panel. - **What stays with the panel.** Game updates, backups and the panel's own restart times stay with the panel. ## Connect your AMP panel server 1. **Find the console and file details.** In your panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Apex Hosting](https://rustsc.com/hosting/apex-hosting/index.html.md) - [Bloom.host](https://rustsc.com/hosting/bloom-host/index.html.md) - [Citadel Servers](https://rustsc.com/hosting/citadel-servers/index.html.md) - [CreeperHost](https://rustsc.com/hosting/creeperhost/index.html.md) - [Cybrancee](https://rustsc.com/hosting/cybrancee/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit AMP panel](https://cubecoders.com/AMP) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/amp/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Apex Hosting hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for Apex Hosting servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in Apex Hosting's own panel. - **What stays with Apex Hosting.** Game updates, backups and Apex Hosting's own restart times stay with Apex Hosting. ## Connect your Apex Hosting server 1. **Find the console and file details.** In Apex Hosting's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Bloom.host](https://rustsc.com/hosting/bloom-host/index.html.md) - [Citadel Servers](https://rustsc.com/hosting/citadel-servers/index.html.md) - [CreeperHost](https://rustsc.com/hosting/creeperhost/index.html.md) - [Cybrancee](https://rustsc.com/hosting/cybrancee/index.html.md) - [Freak Hosting](https://rustsc.com/hosting/freak-hosting/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit Apex Hosting](https://apexminecrafthosting.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/apex-hosting/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports BisectHosting hosted Rust servers BisectHosting's game panel is called Starbase. Add the server with a key from your account, then manage the console, files and plugins, schedules, wipes and power controls from RustSC. ## What RustSC does for BisectHosting servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC. - **Power, schedules and wipes.** Use the power controls, schedule restarts and wipes, and run a wipe. - **What stays with BisectHosting.** Game updates, backups and BisectHosting's own restart times stay with BisectHosting. ## Connect your BisectHosting server 1. **Create a key.** In BisectHosting's panel, open your account and create a key for the server. 2. **Add the server in RustSC.** Choose BisectHosting when you add a server, then paste the server's page address and the key. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Nitrado](https://rustsc.com/hosting/nitrado/index.html.md) - [Pelican panel](https://rustsc.com/hosting/pelican/index.html.md) - [Pine Hosting](https://rustsc.com/hosting/pine-hosting/index.html.md) - [Pterodactyl panel](https://rustsc.com/hosting/pterodactyl/index.html.md) - [Starbase panel](https://rustsc.com/hosting/starbase/index.html.md) ## More - [Visit BisectHosting](https://games.bisecthosting.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/bisecthosting/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Bloom.host hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for Bloom.host servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in Bloom.host's own panel. - **What stays with Bloom.host.** Game updates, backups and Bloom.host's own restart times stay with Bloom.host. ## Connect your Bloom.host server 1. **Find the console and file details.** In Bloom.host's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. 4. **If your panel is Pterodactyl.** Bloom.host's own help pages describe a Pterodactyl panel. If yours is one, choose Pterodactyl panel when you add the server and connect with a key from your account. ## Other hosts - [Citadel Servers](https://rustsc.com/hosting/citadel-servers/index.html.md) - [CreeperHost](https://rustsc.com/hosting/creeperhost/index.html.md) - [Cybrancee](https://rustsc.com/hosting/cybrancee/index.html.md) - [Freak Hosting](https://rustsc.com/hosting/freak-hosting/index.html.md) - [GameHostBros](https://rustsc.com/hosting/gamehostbros/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit Bloom.host](https://bloom.host) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/bloom-host/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Citadel Servers hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for Citadel Servers servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in Citadel Servers's own panel. - **What stays with Citadel Servers.** Game updates, backups and Citadel Servers's own restart times stay with Citadel Servers. ## Connect your Citadel Servers server 1. **Find the console and file details.** In Citadel Servers's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [CreeperHost](https://rustsc.com/hosting/creeperhost/index.html.md) - [Cybrancee](https://rustsc.com/hosting/cybrancee/index.html.md) - [Freak Hosting](https://rustsc.com/hosting/freak-hosting/index.html.md) - [GameHostBros](https://rustsc.com/hosting/gamehostbros/index.html.md) - [GameServerKings](https://rustsc.com/hosting/gameserverkings/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit Citadel Servers](https://citadelservers.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/citadel-servers/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports CreeperHost hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for CreeperHost servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in CreeperHost's own panel. - **What stays with CreeperHost.** Game updates, backups and CreeperHost's own restart times stay with CreeperHost. ## Connect your CreeperHost server 1. **Find the console and file details.** In CreeperHost's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. 4. **If your panel is Pterodactyl.** CreeperHost's own help pages describe a Pterodactyl panel. If yours is one, choose Pterodactyl panel when you add the server and connect with a key from your account. ## Other hosts - [Cybrancee](https://rustsc.com/hosting/cybrancee/index.html.md) - [Freak Hosting](https://rustsc.com/hosting/freak-hosting/index.html.md) - [GameHostBros](https://rustsc.com/hosting/gamehostbros/index.html.md) - [GameServerKings](https://rustsc.com/hosting/gameserverkings/index.html.md) - [Godlike](https://rustsc.com/hosting/godlike/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit CreeperHost](https://creeperhost.net) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/creeperhost/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Cybrancee hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for Cybrancee servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in Cybrancee's own panel. - **What stays with Cybrancee.** Game updates, backups and Cybrancee's own restart times stay with Cybrancee. ## Connect your Cybrancee server 1. **Find the console and file details.** In Cybrancee's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Freak Hosting](https://rustsc.com/hosting/freak-hosting/index.html.md) - [GameHostBros](https://rustsc.com/hosting/gamehostbros/index.html.md) - [GameServerKings](https://rustsc.com/hosting/gameserverkings/index.html.md) - [Godlike](https://rustsc.com/hosting/godlike/index.html.md) - [GPortal](https://rustsc.com/hosting/gportal/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit Cybrancee](https://cybrancee.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/cybrancee/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Freak Hosting hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for Freak Hosting servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in Freak Hosting's own panel. - **What stays with Freak Hosting.** Game updates, backups and Freak Hosting's own restart times stay with Freak Hosting. ## Connect your Freak Hosting server 1. **Find the console and file details.** In Freak Hosting's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. 4. **If your panel is Pterodactyl.** Freak Hosting's own help pages describe a Pterodactyl panel. If yours is one, choose Pterodactyl panel when you add the server and connect with a key from your account. ## Other hosts - [GameHostBros](https://rustsc.com/hosting/gamehostbros/index.html.md) - [GameServerKings](https://rustsc.com/hosting/gameserverkings/index.html.md) - [Godlike](https://rustsc.com/hosting/godlike/index.html.md) - [GPortal](https://rustsc.com/hosting/gportal/index.html.md) - [GTX Gaming](https://rustsc.com/hosting/gtx-gaming/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit Freak Hosting](https://freakhosting.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/freak-hosting/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports GameHostBros hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for GameHostBros servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in GameHostBros's own panel. - **What stays with GameHostBros.** Game updates, backups and GameHostBros's own restart times stay with GameHostBros. ## Connect your GameHostBros server 1. **Find the console and file details.** In GameHostBros's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [GameServerKings](https://rustsc.com/hosting/gameserverkings/index.html.md) - [Godlike](https://rustsc.com/hosting/godlike/index.html.md) - [GPortal](https://rustsc.com/hosting/gportal/index.html.md) - [GTX Gaming](https://rustsc.com/hosting/gtx-gaming/index.html.md) - [Host Havoc](https://rustsc.com/hosting/host-havoc/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit GameHostBros](https://gamehostbros.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/gamehostbros/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports GameServerKings hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for GameServerKings servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in GameServerKings's own panel. - **What stays with GameServerKings.** Game updates, backups and GameServerKings's own restart times stay with GameServerKings. ## Connect your GameServerKings server 1. **Find the console and file details.** In GameServerKings's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Godlike](https://rustsc.com/hosting/godlike/index.html.md) - [GPortal](https://rustsc.com/hosting/gportal/index.html.md) - [GTX Gaming](https://rustsc.com/hosting/gtx-gaming/index.html.md) - [Host Havoc](https://rustsc.com/hosting/host-havoc/index.html.md) - [Hostinger](https://rustsc.com/hosting/hostinger/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit GameServerKings](https://www.gameserverkings.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/gameserverkings/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Godlike hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for Godlike servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in Godlike's own panel. - **What stays with Godlike.** Game updates, backups and Godlike's own restart times stay with Godlike. ## Connect your Godlike server 1. **Find the console and file details.** In Godlike's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [GPortal](https://rustsc.com/hosting/gportal/index.html.md) - [GTX Gaming](https://rustsc.com/hosting/gtx-gaming/index.html.md) - [Host Havoc](https://rustsc.com/hosting/host-havoc/index.html.md) - [Hostinger](https://rustsc.com/hosting/hostinger/index.html.md) - [Iceline Hosting](https://rustsc.com/hosting/iceline-hosting/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit Godlike](https://godlike.host) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/godlike/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports GPortal hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for GPortal servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in GPortal's own panel. - **What stays with GPortal.** Game updates, backups and GPortal's own restart times stay with GPortal. ## Connect your GPortal server 1. **Find the console and file details.** In GPortal's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [GTX Gaming](https://rustsc.com/hosting/gtx-gaming/index.html.md) - [Host Havoc](https://rustsc.com/hosting/host-havoc/index.html.md) - [Hostinger](https://rustsc.com/hosting/hostinger/index.html.md) - [Iceline Hosting](https://rustsc.com/hosting/iceline-hosting/index.html.md) - [Loafhosts](https://rustsc.com/hosting/loafhosts/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit GPortal](https://www.g-portal.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/gportal/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports GTX Gaming hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for GTX Gaming servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in GTX Gaming's own panel. - **What stays with GTX Gaming.** Game updates, backups and GTX Gaming's own restart times stay with GTX Gaming. ## Connect your GTX Gaming server 1. **Find the console and file details.** In GTX Gaming's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Host Havoc](https://rustsc.com/hosting/host-havoc/index.html.md) - [Hostinger](https://rustsc.com/hosting/hostinger/index.html.md) - [Iceline Hosting](https://rustsc.com/hosting/iceline-hosting/index.html.md) - [Loafhosts](https://rustsc.com/hosting/loafhosts/index.html.md) - [LOW.MS](https://rustsc.com/hosting/low-ms/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit GTX Gaming](https://www.gtxgaming.co.uk) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/gtx-gaming/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Host Havoc hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for Host Havoc servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in Host Havoc's own panel. - **What stays with Host Havoc.** Game updates, backups and Host Havoc's own restart times stay with Host Havoc. ## Connect your Host Havoc server 1. **Find the console and file details.** In Host Havoc's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Hostinger](https://rustsc.com/hosting/hostinger/index.html.md) - [Iceline Hosting](https://rustsc.com/hosting/iceline-hosting/index.html.md) - [Loafhosts](https://rustsc.com/hosting/loafhosts/index.html.md) - [LOW.MS](https://rustsc.com/hosting/low-ms/index.html.md) - [Nodecraft](https://rustsc.com/hosting/nodecraft/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit Host Havoc](https://hosthavoc.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/host-havoc/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Hostinger hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for Hostinger servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in Hostinger's own panel. - **What stays with Hostinger.** Game updates, backups and Hostinger's own restart times stay with Hostinger. ## Connect your Hostinger server 1. **Find the console and file details.** In Hostinger's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Iceline Hosting](https://rustsc.com/hosting/iceline-hosting/index.html.md) - [Loafhosts](https://rustsc.com/hosting/loafhosts/index.html.md) - [LOW.MS](https://rustsc.com/hosting/low-ms/index.html.md) - [Nodecraft](https://rustsc.com/hosting/nodecraft/index.html.md) - [Physgun](https://rustsc.com/hosting/physgun/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit Hostinger](https://www.hostinger.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/hostinger/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Iceline Hosting hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for Iceline Hosting servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in Iceline Hosting's own panel. - **What stays with Iceline Hosting.** Game updates, backups and Iceline Hosting's own restart times stay with Iceline Hosting. ## Connect your Iceline Hosting server 1. **Find the console and file details.** In Iceline Hosting's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Loafhosts](https://rustsc.com/hosting/loafhosts/index.html.md) - [LOW.MS](https://rustsc.com/hosting/low-ms/index.html.md) - [Nodecraft](https://rustsc.com/hosting/nodecraft/index.html.md) - [Physgun](https://rustsc.com/hosting/physgun/index.html.md) - [PingPerfect](https://rustsc.com/hosting/pingperfect/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit Iceline Hosting](https://iceline-hosting.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/iceline-hosting/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Loafhosts hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for Loafhosts servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in Loafhosts's own panel. - **What stays with Loafhosts.** Game updates, backups and Loafhosts's own restart times stay with Loafhosts. ## Connect your Loafhosts server 1. **Find the console and file details.** In Loafhosts's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [LOW.MS](https://rustsc.com/hosting/low-ms/index.html.md) - [Nodecraft](https://rustsc.com/hosting/nodecraft/index.html.md) - [Physgun](https://rustsc.com/hosting/physgun/index.html.md) - [PingPerfect](https://rustsc.com/hosting/pingperfect/index.html.md) - [ScalaCube](https://rustsc.com/hosting/scalacube/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit Loafhosts](https://loafhosts.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/loafhosts/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports LOW.MS hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for LOW.MS servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in LOW.MS's own panel. - **What stays with LOW.MS.** Game updates, backups and LOW.MS's own restart times stay with LOW.MS. ## Connect your LOW.MS server 1. **Find the console and file details.** In LOW.MS's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Nodecraft](https://rustsc.com/hosting/nodecraft/index.html.md) - [Physgun](https://rustsc.com/hosting/physgun/index.html.md) - [PingPerfect](https://rustsc.com/hosting/pingperfect/index.html.md) - [ScalaCube](https://rustsc.com/hosting/scalacube/index.html.md) - [Shockbyte](https://rustsc.com/hosting/shockbyte/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit LOW.MS](https://low.ms) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/low-ms/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Nitrado hosted Rust servers Add the server with a key from your account, then manage the console, files and plugins, schedules, wipes and power controls from RustSC. ## What RustSC does for Nitrado servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC. - **Power, schedules and wipes.** Use the power controls, schedule restarts and wipes, and run a wipe. - **What stays with Nitrado.** Game updates, backups and Nitrado's own restart times stay with Nitrado. ## Connect your Nitrado server 1. **Create a key.** In your Nitrado account, create a key for the server's service. 2. **Add the server in RustSC.** Choose Nitrado when you add a server, then enter the service number and the key. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Pelican panel](https://rustsc.com/hosting/pelican/index.html.md) - [Pine Hosting](https://rustsc.com/hosting/pine-hosting/index.html.md) - [Pterodactyl panel](https://rustsc.com/hosting/pterodactyl/index.html.md) - [Starbase panel](https://rustsc.com/hosting/starbase/index.html.md) - [BisectHosting](https://rustsc.com/hosting/bisecthosting/index.html.md) ## More - [Visit Nitrado](https://server.nitrado.net) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/nitrado/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Nodecraft hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for Nodecraft servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in Nodecraft's own panel. - **What stays with Nodecraft.** Game updates, backups and Nodecraft's own restart times stay with Nodecraft. ## Connect your Nodecraft server 1. **Find the console and file details.** In Nodecraft's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Physgun](https://rustsc.com/hosting/physgun/index.html.md) - [PingPerfect](https://rustsc.com/hosting/pingperfect/index.html.md) - [ScalaCube](https://rustsc.com/hosting/scalacube/index.html.md) - [Shockbyte](https://rustsc.com/hosting/shockbyte/index.html.md) - [Sparked Host](https://rustsc.com/hosting/sparked-host/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit Nodecraft](https://nodecraft.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/nodecraft/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Rust servers on the Pelican panel Pelican is an open source game server panel and the successor to Pterodactyl. Add the server with a key from your account, then manage the console, files and plugins, schedules, wipes and power controls from RustSC. ## What RustSC does for Pelican panel servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC. - **Power, schedules and wipes.** Use the power controls, schedule restarts and wipes, and run a wipe. - **What stays with the panel.** Game updates, backups and the panel's own restart times stay with the panel. ## Connect your Pelican panel server 1. **Create a key.** In your Pelican panel, open your account and create a key for the server. 2. **Add the server in RustSC.** Choose Pelican panel when you add a server, then paste the server's page address and the key. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Pine Hosting](https://rustsc.com/hosting/pine-hosting/index.html.md) - [Pterodactyl panel](https://rustsc.com/hosting/pterodactyl/index.html.md) - [Starbase panel](https://rustsc.com/hosting/starbase/index.html.md) - [BisectHosting](https://rustsc.com/hosting/bisecthosting/index.html.md) - [Nitrado](https://rustsc.com/hosting/nitrado/index.html.md) ## More - [Visit Pelican panel](https://pelican.dev) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/pelican/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Physgun hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for Physgun servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in Physgun's own panel. - **What stays with Physgun.** Game updates, backups and Physgun's own restart times stay with Physgun. ## Connect your Physgun server 1. **Find the console and file details.** In Physgun's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [PingPerfect](https://rustsc.com/hosting/pingperfect/index.html.md) - [ScalaCube](https://rustsc.com/hosting/scalacube/index.html.md) - [Shockbyte](https://rustsc.com/hosting/shockbyte/index.html.md) - [Sparked Host](https://rustsc.com/hosting/sparked-host/index.html.md) - [Supercraft](https://rustsc.com/hosting/supercraft/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit Physgun](https://physgun.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/physgun/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Pine Hosting hosted Rust servers Add the server with a key from your account, then manage the console, files and plugins, schedules, wipes and power controls from RustSC. ## What RustSC does for Pine Hosting servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC. - **Power, schedules and wipes.** Use the power controls, schedule restarts and wipes, and run a wipe. - **What stays with Pine Hosting.** Game updates, backups and Pine Hosting's own restart times stay with Pine Hosting. ## Connect your Pine Hosting server 1. **Create a key.** In Pine Hosting's panel, open your account and create a key for the server. 2. **Add the server in RustSC.** Choose Pine Hosting when you add a server, then paste the server's page address and the key. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Pterodactyl panel](https://rustsc.com/hosting/pterodactyl/index.html.md) - [Starbase panel](https://rustsc.com/hosting/starbase/index.html.md) - [BisectHosting](https://rustsc.com/hosting/bisecthosting/index.html.md) - [Nitrado](https://rustsc.com/hosting/nitrado/index.html.md) - [Pelican panel](https://rustsc.com/hosting/pelican/index.html.md) ## More - [Visit Pine Hosting](https://pinehosting.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/pine-hosting/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports PingPerfect hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for PingPerfect servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in PingPerfect's own panel. - **What stays with PingPerfect.** Game updates, backups and PingPerfect's own restart times stay with PingPerfect. ## Connect your PingPerfect server 1. **Find the console and file details.** In PingPerfect's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [ScalaCube](https://rustsc.com/hosting/scalacube/index.html.md) - [Shockbyte](https://rustsc.com/hosting/shockbyte/index.html.md) - [Sparked Host](https://rustsc.com/hosting/sparked-host/index.html.md) - [Supercraft](https://rustsc.com/hosting/supercraft/index.html.md) - [Survival Servers](https://rustsc.com/hosting/survival-servers/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit PingPerfect](https://pingperfect.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/pingperfect/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Rust servers on the Pterodactyl panel Pterodactyl is an open source game server panel that runs Rust servers among other games. Add the server with a key from your account, then manage the console, files and plugins, schedules, wipes and power controls from RustSC. ## What RustSC does for Pterodactyl panel servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC. - **Power, schedules and wipes.** Use the power controls, schedule restarts and wipes, and run a wipe. - **What stays with the panel.** Game updates, backups and the panel's own restart times stay with the panel. ## Connect your Pterodactyl panel server 1. **Create a key.** In your Pterodactyl panel, open your account and create a key for the server. 2. **Add the server in RustSC.** Choose Pterodactyl panel when you add a server, then paste the server's page address and the key. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Starbase panel](https://rustsc.com/hosting/starbase/index.html.md) - [BisectHosting](https://rustsc.com/hosting/bisecthosting/index.html.md) - [Nitrado](https://rustsc.com/hosting/nitrado/index.html.md) - [Pelican panel](https://rustsc.com/hosting/pelican/index.html.md) - [Pine Hosting](https://rustsc.com/hosting/pine-hosting/index.html.md) ## More - [Visit Pterodactyl panel](https://pterodactyl.io) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/pterodactyl/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports ScalaCube hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for ScalaCube servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in ScalaCube's own panel. - **What stays with ScalaCube.** Game updates, backups and ScalaCube's own restart times stay with ScalaCube. ## Connect your ScalaCube server 1. **Find the console and file details.** In ScalaCube's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Shockbyte](https://rustsc.com/hosting/shockbyte/index.html.md) - [Sparked Host](https://rustsc.com/hosting/sparked-host/index.html.md) - [Supercraft](https://rustsc.com/hosting/supercraft/index.html.md) - [Survival Servers](https://rustsc.com/hosting/survival-servers/index.html.md) - [TCAdmin panel](https://rustsc.com/hosting/tcadmin/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit ScalaCube](https://scalacube.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/scalacube/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Shockbyte hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for Shockbyte servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in Shockbyte's own panel. - **What stays with Shockbyte.** Game updates, backups and Shockbyte's own restart times stay with Shockbyte. ## Connect your Shockbyte server 1. **Find the console and file details.** In Shockbyte's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Sparked Host](https://rustsc.com/hosting/sparked-host/index.html.md) - [Supercraft](https://rustsc.com/hosting/supercraft/index.html.md) - [Survival Servers](https://rustsc.com/hosting/survival-servers/index.html.md) - [TCAdmin panel](https://rustsc.com/hosting/tcadmin/index.html.md) - [Terabit](https://rustsc.com/hosting/terabit/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit Shockbyte](https://shockbyte.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/shockbyte/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Sparked Host hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for Sparked Host servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in Sparked Host's own panel. - **What stays with Sparked Host.** Game updates, backups and Sparked Host's own restart times stay with Sparked Host. ## Connect your Sparked Host server 1. **Find the console and file details.** In Sparked Host's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. 4. **If your panel is Pterodactyl.** Sparked Host's own help pages describe a Pterodactyl panel. If yours is one, choose Pterodactyl panel when you add the server and connect with a key from your account. ## Other hosts - [Supercraft](https://rustsc.com/hosting/supercraft/index.html.md) - [Survival Servers](https://rustsc.com/hosting/survival-servers/index.html.md) - [TCAdmin panel](https://rustsc.com/hosting/tcadmin/index.html.md) - [Terabit](https://rustsc.com/hosting/terabit/index.html.md) - [Vastrox](https://rustsc.com/hosting/vastrox/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit Sparked Host](https://sparkedhost.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/sparked-host/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Rust servers on the Starbase panel Starbase is the game panel that BisectHosting provides. Add the server with a key from your account, then manage the console, files and plugins, schedules, wipes and power controls from RustSC. ## What RustSC does for Starbase panel servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC. - **Power, schedules and wipes.** Use the power controls, schedule restarts and wipes, and run a wipe. - **What stays with the panel.** Game updates, backups and the panel's own restart times stay with the panel. ## Connect your Starbase panel server 1. **Create a key.** In the panel, open your account and create a key for the server. 2. **Add the server in RustSC.** Choose Starbase panel when you add a server, then paste the server's page address and the key. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [BisectHosting](https://rustsc.com/hosting/bisecthosting/index.html.md) - [Nitrado](https://rustsc.com/hosting/nitrado/index.html.md) - [Pelican panel](https://rustsc.com/hosting/pelican/index.html.md) - [Pine Hosting](https://rustsc.com/hosting/pine-hosting/index.html.md) - [Pterodactyl panel](https://rustsc.com/hosting/pterodactyl/index.html.md) ## More - [Visit Starbase panel](https://games.bisecthosting.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/starbase/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Supercraft hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for Supercraft servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in Supercraft's own panel. - **What stays with Supercraft.** Game updates, backups and Supercraft's own restart times stay with Supercraft. ## Connect your Supercraft server 1. **Find the console and file details.** In Supercraft's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Survival Servers](https://rustsc.com/hosting/survival-servers/index.html.md) - [TCAdmin panel](https://rustsc.com/hosting/tcadmin/index.html.md) - [Terabit](https://rustsc.com/hosting/terabit/index.html.md) - [Vastrox](https://rustsc.com/hosting/vastrox/index.html.md) - [Wabbanode](https://rustsc.com/hosting/wabbanode/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit Supercraft](https://supercraft.host) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/supercraft/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Survival Servers hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for Survival Servers servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in Survival Servers's own panel. - **What stays with Survival Servers.** Game updates, backups and Survival Servers's own restart times stay with Survival Servers. ## Connect your Survival Servers server 1. **Find the console and file details.** In Survival Servers's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [TCAdmin panel](https://rustsc.com/hosting/tcadmin/index.html.md) - [Terabit](https://rustsc.com/hosting/terabit/index.html.md) - [Vastrox](https://rustsc.com/hosting/vastrox/index.html.md) - [Wabbanode](https://rustsc.com/hosting/wabbanode/index.html.md) - [WinterNode](https://rustsc.com/hosting/winternode/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit Survival Servers](https://www.survivalservers.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/survival-servers/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Rust servers on the TCAdmin panel TCAdmin is game server panel software that some Rust hosts run. Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for TCAdmin panel servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in the panel. - **What stays with the panel.** Game updates, backups and the panel's own restart times stay with the panel. ## Connect your TCAdmin panel server 1. **Find the console and file details.** In your panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Terabit](https://rustsc.com/hosting/terabit/index.html.md) - [Vastrox](https://rustsc.com/hosting/vastrox/index.html.md) - [Wabbanode](https://rustsc.com/hosting/wabbanode/index.html.md) - [WinterNode](https://rustsc.com/hosting/winternode/index.html.md) - [WISP panel](https://rustsc.com/hosting/wisp/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit TCAdmin panel](https://www.tcadmin.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/tcadmin/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Terabit hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for Terabit servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in Terabit's own panel. - **What stays with Terabit.** Game updates, backups and Terabit's own restart times stay with Terabit. ## Connect your Terabit server 1. **Find the console and file details.** In Terabit's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Vastrox](https://rustsc.com/hosting/vastrox/index.html.md) - [Wabbanode](https://rustsc.com/hosting/wabbanode/index.html.md) - [WinterNode](https://rustsc.com/hosting/winternode/index.html.md) - [WISP panel](https://rustsc.com/hosting/wisp/index.html.md) - [XGamingServer](https://rustsc.com/hosting/xgamingserver/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit Terabit](https://terabit.io) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/terabit/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Vastrox hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for Vastrox servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in Vastrox's own panel. - **What stays with Vastrox.** Game updates, backups and Vastrox's own restart times stay with Vastrox. ## Connect your Vastrox server 1. **Find the console and file details.** In Vastrox's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [Wabbanode](https://rustsc.com/hosting/wabbanode/index.html.md) - [WinterNode](https://rustsc.com/hosting/winternode/index.html.md) - [WISP panel](https://rustsc.com/hosting/wisp/index.html.md) - [XGamingServer](https://rustsc.com/hosting/xgamingserver/index.html.md) - [ZAP-Hosting](https://rustsc.com/hosting/zap-hosting/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit Vastrox](https://vastrox.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/vastrox/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Wabbanode hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for Wabbanode servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in Wabbanode's own panel. - **What stays with Wabbanode.** Game updates, backups and Wabbanode's own restart times stay with Wabbanode. ## Connect your Wabbanode server 1. **Find the console and file details.** In Wabbanode's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [WinterNode](https://rustsc.com/hosting/winternode/index.html.md) - [WISP panel](https://rustsc.com/hosting/wisp/index.html.md) - [XGamingServer](https://rustsc.com/hosting/xgamingserver/index.html.md) - [ZAP-Hosting](https://rustsc.com/hosting/zap-hosting/index.html.md) - [AMP panel](https://rustsc.com/hosting/amp/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit Wabbanode](https://wabbanode.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/wabbanode/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports WinterNode hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for WinterNode servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in WinterNode's own panel. - **What stays with WinterNode.** Game updates, backups and WinterNode's own restart times stay with WinterNode. ## Connect your WinterNode server 1. **Find the console and file details.** In WinterNode's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [WISP panel](https://rustsc.com/hosting/wisp/index.html.md) - [XGamingServer](https://rustsc.com/hosting/xgamingserver/index.html.md) - [ZAP-Hosting](https://rustsc.com/hosting/zap-hosting/index.html.md) - [AMP panel](https://rustsc.com/hosting/amp/index.html.md) - [Apex Hosting](https://rustsc.com/hosting/apex-hosting/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit WinterNode](https://winternode.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/winternode/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Rust servers on the WISP panel Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for WISP panel servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in the panel. - **What stays with the panel.** Game updates, backups and the panel's own restart times stay with the panel. ## Connect your WISP panel server 1. **Find the console and file details.** In your panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [XGamingServer](https://rustsc.com/hosting/xgamingserver/index.html.md) - [ZAP-Hosting](https://rustsc.com/hosting/zap-hosting/index.html.md) - [AMP panel](https://rustsc.com/hosting/amp/index.html.md) - [Apex Hosting](https://rustsc.com/hosting/apex-hosting/index.html.md) - [Bloom.host](https://rustsc.com/hosting/bloom-host/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit WISP panel](https://wisp.gg) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/wisp/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports XGamingServer hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for XGamingServer servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in XGamingServer's own panel. - **What stays with XGamingServer.** Game updates, backups and XGamingServer's own restart times stay with XGamingServer. ## Connect your XGamingServer server 1. **Find the console and file details.** In XGamingServer's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. 4. **If your panel is Pterodactyl.** XGamingServer's own help pages describe a Pterodactyl panel. If yours is one, choose Pterodactyl panel when you add the server and connect with a key from your account. ## Other hosts - [ZAP-Hosting](https://rustsc.com/hosting/zap-hosting/index.html.md) - [AMP panel](https://rustsc.com/hosting/amp/index.html.md) - [Apex Hosting](https://rustsc.com/hosting/apex-hosting/index.html.md) - [Bloom.host](https://rustsc.com/hosting/bloom-host/index.html.md) - [Citadel Servers](https://rustsc.com/hosting/citadel-servers/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit XGamingServer](https://xgamingserver.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/xgamingserver/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports ZAP-Hosting hosted Rust servers Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. ## What RustSC does for ZAP-Hosting servers - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in ZAP-Hosting's own panel. - **What stays with ZAP-Hosting.** Game updates, backups and ZAP-Hosting's own restart times stay with ZAP-Hosting. ## Connect your ZAP-Hosting server 1. **Find the console and file details.** In ZAP-Hosting's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## Other hosts - [AMP panel](https://rustsc.com/hosting/amp/index.html.md) - [Apex Hosting](https://rustsc.com/hosting/apex-hosting/index.html.md) - [Bloom.host](https://rustsc.com/hosting/bloom-host/index.html.md) - [Citadel Servers](https://rustsc.com/hosting/citadel-servers/index.html.md) - [CreeperHost](https://rustsc.com/hosting/creeperhost/index.html.md) - [Any other Rust host](https://rustsc.com/hosting/any-host/index.html.md) ## More - [Visit ZAP-Hosting](https://zap-hosting.com) - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/zap-hosting/ RustSC helps you manage your Rust dedicated server from your browser. --- # RustSC supports Rust servers on any Rust host Add the server with its RCON password and file login, then manage the console, files and plugins, schedules and wipes from RustSC. Starting a stopped server, game updates and backups stay in your host's own panel. SFTP and FTPS are encrypted. Pick FTP only if your host offers nothing else. ## What RustSC does on any host - **Console and files.** Send console commands and manage the server's files and plugin files from RustSC, using the server's own console and file login. - **Schedules and wipes.** Schedule console commands and file changes, and prepare wipes. Starting a stopped server stays in your host's own panel. - **What stays with your host.** Game updates, backups and your host's own restart times stay with your host. ## Connect your server 1. **Find the console and file details.** In your host's panel, find the server's file login (SFTP, FTPS or FTP) and, if there is one, its remote console (RCON) password. 2. **Add the server in RustSC.** Choose Another host when you add a server, pick the file login type, then enter the login and the RCON password. 3. **Check and connect.** Once connected, you can open the server in RustSC. What you can manage depends on the access your host gives you. ## More - [All hosting providers](https://rustsc.com/hosting/index.html.md) - [Check compatibility](https://rustsc.com/compatibility/index.html.md) - [Check or change a host connection](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/hosting/any-host/ RustSC helps you manage your Rust dedicated server from your browser. --- # Version 1 guides Guides for setting up and running your Rust server with RustSC, and the developer reference for its customer API. ## Set up RustSC - [Your first server in RustSC](https://rustsc.com/support/guides/first-server/index.html.md): Sign in, connect your host, start a server and restart it with a warning. - [Move a server you already run into RustSC](https://rustsc.com/support/guides/move-existing-server/index.html.md): Add a Rust server that is already installed, even while another tool is running it. - [Install RustSC on Linux](https://rustsc.com/support/guides/install-linux/index.html.md): One command installs RustSC on a Linux host and connects it. - [Install RustSC on Windows](https://rustsc.com/support/guides/install-windows/index.html.md): Paste one command into PowerShell and your Windows host is installed and connected. - [Add your first server](https://rustsc.com/support/guides/add-server/index.html.md): Install Rust on a connected host and start your server. - [Choose a server folder](https://rustsc.com/support/guides/server-folder/index.html.md): Choose the folder where RustSC installs your Rust server and keeps its game files, before you start the install. - [Add an existing server](https://rustsc.com/support/guides/add-existing-server/index.html.md): Bring a Rust server you already run into RustSC. Nothing about your server changes until you switch a function on. - [Add a host to your workspace](https://rustsc.com/support/guides/add-host/index.html.md): A host is where your servers run. Connect it once and manage its servers from the portal. - [Reconnect a host](https://rustsc.com/support/guides/reconnect-computer/index.html.md): Restore a host’s connection without reinstalling your servers. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/index.html.md): Connect your hosting company, check what works and fix a connection. - [Remove a host from RustSC](https://rustsc.com/support/guides/remove-host/index.html.md): Disconnect a host and choose what happens to the servers listed in your workspace. ## Run your server - [Start, stop or restart a server](https://rustsc.com/support/guides/start-stop-restart/index.html.md): Start, stop or restart your Rust server from RustSC, and check when it is ready for players to join. - [Messages, restarts and wipes: what players see](https://rustsc.com/support/guides/player-messages/index.html.md): The countdown players read in chat before a restart, a stop or a wipe, and how to change its words. - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/index.html.md): Find game messages, run commands and check server FPS. - [Change server settings](https://rustsc.com/support/guides/server-settings/index.html.md): Change your Rust server's settings in RustSC, save them and apply them to the running server. - [Update Rust](https://rustsc.com/support/guides/update-rust/index.html.md): Install the latest game build and choose automatic updates. - [Change Oxide or Carbon](https://rustsc.com/support/guides/change-framework/index.html.md): Install, update, switch or remove your server’s plugin framework. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/index.html.md): Restart your server at the same time every day, or on the days you choose. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/index.html.md): Search the plugin marketplaces, install a plugin and keep it up to date. - [Remove a server from RustSC](https://rustsc.com/support/guides/remove-server/index.html.md): Remove a server from RustSC and stop managing it there, while the server's files stay where they are. - [Move a server to a new host](https://rustsc.com/support/guides/move-to-new-host/index.html.md): Point a server at a new host after a rebuild or a loss. It keeps its name, history, schedules, rules and backups. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/index.html.md): Find local and cloud commands and their installed help. - [Control a server on its host](https://rustsc.com/support/guides/offline-server-control/index.html.md): Use the Windows app or Linux terminal when you are at your host. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/index.html.md): Check game files and updates, or use the Windows maintenance controls. - [Schedules and activity on the host](https://rustsc.com/support/guides/host-schedules-activity/index.html.md): See local schedules and follow work from a terminal. - [Find more host commands](https://rustsc.com/support/guides/host-command-line/index.html.md): Find the command for console, players, backups and other host tasks. - [Install or update the RustSC plugin](https://rustsc.com/support/guides/rustsc-plugin/index.html.md): Add the RustSC plugin to a server and keep it current. - [Set a quiet time for alerts](https://rustsc.com/support/guides/quiet-alerts/index.html.md): Pause selected alerts for a chosen time, then let them resume. - [Schedule a message or command](https://rustsc.com/support/guides/schedule-messages-commands/index.html.md): Send a message, run a command or post to Discord on a schedule. - [Find and save console lines and commands](https://rustsc.com/support/guides/console-tools/index.html.md): Search the console, save a command and watch for words. - [Schedule a host restart](https://rustsc.com/support/guides/schedule-host-restart/index.html.md): Choose when your host and its servers restart on a schedule. - [Schedule a temporary change](https://rustsc.com/support/guides/temporary-changes/index.html.md): Put files or plugins in place for a while and choose when the change ends. - [Use the live map](https://rustsc.com/support/guides/live-map/index.html.md): See players and events on your server's map and choose what it shows. - [Read server events and chat](https://rustsc.com/support/guides/server-events/index.html.md): Find a recorded server event, search public chat or download a copy. - [Work with server files](https://rustsc.com/support/guides/manage-files/index.html.md): Find, upload and change files for a server from the Files tab. - [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/index.html.md): Choose the alerts you need and where you receive them. - [Manage several servers at once](https://rustsc.com/support/guides/bulk-actions/index.html.md): Send a message, change access or copy settings to a group of servers. - [Find and select servers in a workspace](https://rustsc.com/support/guides/find-a-server-in-your-workspace/index.html.md): Use Home or the Servers list to find the servers you manage. - [Announce or recover a temporary change](https://rustsc.com/support/guides/temporary-change-messages-and-recovery/index.html.md): Tell players when a change starts or ends and check what happened to its files. - [Review startup and performance settings](https://rustsc.com/support/guides/advanced-game-settings/index.html.md): Check what starts your server or change how it uses the host's processors. - [Get alerts for words in chat or console](https://rustsc.com/support/guides/watch-chat-and-console-words/index.html.md): Watch for a word or phrase on the servers you choose. - [Install a plugin from a link or a file](https://rustsc.com/support/guides/install-plugin-from-a-link/index.html.md): Check a plugin link before installing it, or upload a plugin file you already have. - [Choose a plugin update source and go back if needed](https://rustsc.com/support/guides/plugin-update-source-and-recovery/index.html.md): Check which version you are installing and put the previous plugin file back when needed. - [Edit a plugin's settings and messages](https://rustsc.com/support/guides/edit-plugin-settings-and-language/index.html.md): Open a plugin's files, review a change and see when it takes effect. - [Import or download server settings](https://rustsc.com/support/guides/import-server-settings/index.html.md): Review settings from a file before applying them to a server. - [Review settings changed outside RustSC](https://rustsc.com/support/guides/review-server-setting-changes/index.html.md): Decide whether to keep the server's setting or the value you saved in RustSC. - [Change the ports players use to join](https://rustsc.com/support/guides/change-server-ports/index.html.md): Change a server's ports and check which ones are in use. - [Save Nexus network settings for a server](https://rustsc.com/support/guides/save-nexus-network-settings/index.html.md): Use a Nexus key you already have to set up a server's next start. - [Find and inspect things on the live map](https://rustsc.com/support/guides/find-things-on-the-map/index.html.md): Find entities by name, owner or location, then inspect or count them. - [Make a rule that responds to a server event](https://rustsc.com/support/guides/make-a-server-event-rule/index.html.md): Send a message or alert automatically when something happens on a server. ## Backups and wipes - [Backups on your host](https://rustsc.com/support/guides/backups-local-and-offsite/index.html.md): Make a backup, make them regular and see where they are kept. - [Back up a server](https://rustsc.com/support/guides/back-up-server/index.html.md): Choose where backups go, make one, decide how many to keep and restore one. - [Free disk space](https://rustsc.com/support/guides/free-disk-space/index.html.md): Remove older backups and files while keeping your current world. - [Restore a backup](https://rustsc.com/support/guides/restore-backup/index.html.md): Choose a backup in RustSC and return your Rust server to the way it was when that backup was taken. - [Recover a damaged save](https://rustsc.com/support/guides/recover-save/index.html.md): Use a previous save when Rust cannot load the current one. - [Wipe your server](https://rustsc.com/support/guides/wipe-server/index.html.md): Start a new map and choose which player data to reset. - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/index.html.md): Choose the day and time your Rust server gets a new map, so each wipe happens on its own. - [Wipe plans in plain words](https://rustsc.com/support/guides/wipe-plans/index.html.md): A wipe plan is everything one wipe does, saved so you can run it again. - [Preview your map](https://rustsc.com/support/guides/preview-map/index.html.md): See a map before the server runs it, whether you pick a size and seed or use your own map file. - [Back up or restore on the host](https://rustsc.com/support/guides/host-backups/index.html.md): Make a local backup or restore one without the portal. - [Copy a backup as a new server](https://rustsc.com/support/guides/copy-backup/index.html.md): Make a separate server from a backup and start it when you are ready. - [Use a link to a custom map](https://rustsc.com/support/guides/use-a-custom-map-link/index.html.md): Give Rust and your players an address that downloads the map file. - [Plan a map rotation for wipes](https://rustsc.com/support/guides/plan-a-map-rotation/index.html.md): Choose the maps a saved wipe uses and what happens at the end of the list. ## Players and access - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/index.html.md): Find a player on your Rust server, kick or ban them from RustSC, and lift a ban when you change your mind. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/index.html.md): Give a player or a group the permissions of your plugins, and make staff. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/index.html.md): Players link their Steam and Discord accounts with a code. Staff look links up with /link search. - [Move existing Discord links](https://rustsc.com/support/guides/move-discord-links/index.html.md): Keep your players’ links when moving from another Discord service. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/index.html.md): Get told when a server goes offline, a backup or wipe fails, or a host runs low on space. - [Understand workspace roles](https://rustsc.com/support/guides/workspace-roles/index.html.md): See what each role in your RustSC workspace can do, so you know what you and your team can change. - [Let a moderator run a few commands](https://rustsc.com/support/guides/mod-commands/index.html.md): Write a command with blanks once. A moderator fills in the blanks and presses Run, without the console. - [Give someone access to only some servers or hosts](https://rustsc.com/support/guides/limited-access/index.html.md): Invite a helper to the servers and hosts you choose, and nothing else. - [See what your team did](https://rustsc.com/support/guides/team-activity/index.html.md): Find who started a restart, a backup or a wipe, and what came of it. - [Choose who can join](https://rustsc.com/support/guides/join-rules/index.html.md): Set join rules and ban lists, then review the decisions made for players. - [Import or download bans](https://rustsc.com/support/guides/import-bans/index.html.md): Bring in a list of bans or save a copy of the list. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/index.html.md): Choose how your server shares chat and linked player roles with Discord. - [Help a player in game](https://rustsc.com/support/guides/player-actions/index.html.md): Use the player menu to heal, move, message or give items. - [See player and server stats](https://rustsc.com/support/guides/player-stats/index.html.md): See who played and how busy your server has been over a chosen period. - [View a player and take action](https://rustsc.com/support/guides/player-details/index.html.md): Open a player's history, notes and available actions. - [Review F7 reports and find events](https://rustsc.com/support/guides/review-player-reports/index.html.md): Find a player's report, check what happened and record your team's decision. - [Keep player permissions the same across servers](https://rustsc.com/support/guides/sync-player-permissions/index.html.md): Preview and share permissions between the servers you choose. ## Fix a problem - [Get help](https://rustsc.com/support/guides/get-help/index.html.md): Send a support request from the portal and attach a file if it helps. - [If something is not working](https://rustsc.com/support/guides/not-working/index.html.md): What to check first, how to make a support file and how to ask for help. - [Host offline](https://rustsc.com/support/guides/computer-offline/index.html.md): Restore a connection while keeping your game server running. - [Server will not start](https://rustsc.com/support/guides/server-will-not-start/index.html.md): Find out why your Rust server did not start, read what RustSC reports and choose the next step. - [An action failed or stopped](https://rustsc.com/support/guides/action-failed/index.html.md): Check what happened when an action failed or stopped, so you know whether it is safe to try again. - [What a message means and what to do](https://rustsc.com/support/guides/fix-common-problems/index.html.md): Plain answers behind the short notices in RustSC: what each check proved and the one next step. - [Check a host’s performance and logs](https://rustsc.com/support/guides/host-performance-and-logs/index.html.md): Find a busy host, investigate a game exit or save the log lines you need. ## Account - [Manage workspace access](https://rustsc.com/support/guides/workspace-access/index.html.md): Find your workspace or ask for the access you need. - [Manage your sign-in and security](https://rustsc.com/support/guides/account-sign-in-security/index.html.md): Add or remove a sign-in method, see where you are signed in and end a sign-in. - [Download your data or delete your account](https://rustsc.com/support/guides/account-data/index.html.md): Export your account data and review what happens to workspaces before deleting your account. - [Choose how people sign in to a workspace](https://rustsc.com/support/guides/workspace-sign-in-rule/index.html.md): Set allowed sign-in methods and decide how often members sign in again. - [Make, limit or revoke an API key](https://rustsc.com/support/guides/make-api-key/index.html.md): Give a script access to the right workspace and servers, then replace or revoke its key. - [Download, hand over or close a workspace](https://rustsc.com/support/guides/workspace-data-closing/index.html.md): Download workspace data, make another member the owner or review closing the workspace. - [Set up a workspace integration](https://rustsc.com/support/guides/workspace-integrations/index.html.md): Set up, check or remove the workspace's Steam, Codefling and RustHQ connections. ## Feature reference - [Alerts reference](https://rustsc.com/support/guides/reference-alerts/index.html.md): Find a specific action or setting for alerts and open the related instructions in RustSC. - [API access and assistants reference](https://rustsc.com/support/guides/reference-api-access-and-assistants/index.html.md): Find a specific action or setting for api access and assistants and open the related instructions in RustSC. - [Automation reference](https://rustsc.com/support/guides/reference-automation/index.html.md): Find a specific action or setting for automation and open the related instructions in RustSC. - [Bans and join rules reference](https://rustsc.com/support/guides/reference-bans-and-join-rules/index.html.md): Find a specific action or setting for bans and join rules and open the related instructions in RustSC. - [Backups reference](https://rustsc.com/support/guides/reference-backups/index.html.md): Find a specific action or setting for backups and open the related instructions in RustSC. - [Console and chat reference](https://rustsc.com/support/guides/reference-console-and-chat/index.html.md): Find a specific action or setting for console and chat and open the related instructions in RustSC. - [Server configuration reference](https://rustsc.com/support/guides/reference-server-configuration/index.html.md): Find a specific action or setting for server configuration and open the related instructions in RustSC. - [Discord community reference](https://rustsc.com/support/guides/reference-discord-community/index.html.md): Find a specific action or setting for discord community and open the related instructions in RustSC. - [Discord server updates reference](https://rustsc.com/support/guides/reference-discord-server-updates/index.html.md): Find a specific action or setting for discord server updates and open the related instructions in RustSC. - [Reports and evidence reference](https://rustsc.com/support/guides/reference-reports-and-evidence/index.html.md): Find a specific action or setting for reports and evidence and open the related instructions in RustSC. - [Server files reference](https://rustsc.com/support/guides/reference-server-files/index.html.md): Find a specific action or setting for server files and open the related instructions in RustSC. - [Server groups reference](https://rustsc.com/support/guides/reference-server-groups/index.html.md): Find a specific action or setting for server groups and open the related instructions in RustSC. - [Community features reference](https://rustsc.com/support/guides/reference-community-features/index.html.md): Find a specific action or setting for community features and open the related instructions in RustSC. - [Getting started reference](https://rustsc.com/support/guides/reference-getting-started/index.html.md): Find a specific action or setting for getting started and open the related instructions in RustSC. - [Help and feedback reference](https://rustsc.com/support/guides/reference-help-and-feedback/index.html.md): Find a specific action or setting for help and feedback and open the related instructions in RustSC. - [Host maintenance reference](https://rustsc.com/support/guides/reference-host-maintenance/index.html.md): Find a specific action or setting for host maintenance and open the related instructions in RustSC. - [Hosts reference](https://rustsc.com/support/guides/reference-hosts/index.html.md): Find a specific action or setting for hosts and open the related instructions in RustSC. - [Server lifecycle reference](https://rustsc.com/support/guides/reference-server-lifecycle/index.html.md): Find a specific action or setting for server lifecycle and open the related instructions in RustSC. - [Live maps reference](https://rustsc.com/support/guides/reference-live-maps/index.html.md): Find a specific action or setting for live maps and open the related instructions in RustSC. - [Maps and worlds reference](https://rustsc.com/support/guides/reference-maps-and-worlds/index.html.md): Find a specific action or setting for maps and worlds and open the related instructions in RustSC. - [Portal on a phone reference](https://rustsc.com/support/guides/reference-portal-on-a-phone/index.html.md): Find a specific action or setting for portal on a phone and open the related instructions in RustSC. - [Performance reference](https://rustsc.com/support/guides/reference-performance/index.html.md): Find a specific action or setting for performance and open the related instructions in RustSC. - [Player permissions reference](https://rustsc.com/support/guides/reference-player-permissions/index.html.md): Find a specific action or setting for player permissions and open the related instructions in RustSC. - [Players reference](https://rustsc.com/support/guides/reference-players/index.html.md): Find a specific action or setting for players and open the related instructions in RustSC. - [Plugins reference](https://rustsc.com/support/guides/reference-plugins/index.html.md): Find a specific action or setting for plugins and open the related instructions in RustSC. - [Rented servers reference](https://rustsc.com/support/guides/reference-rented-servers/index.html.md): Find a specific action or setting for rented servers and open the related instructions in RustSC. - [Schedules reference](https://rustsc.com/support/guides/reference-schedules/index.html.md): Find a specific action or setting for schedules and open the related instructions in RustSC. - [Members and accounts reference](https://rustsc.com/support/guides/reference-members-and-accounts/index.html.md): Find a specific action or setting for members and accounts and open the related instructions in RustSC. - [Access and privacy reference](https://rustsc.com/support/guides/reference-access-and-privacy/index.html.md): Find a specific action or setting for access and privacy and open the related instructions in RustSC. - [Software updates reference](https://rustsc.com/support/guides/reference-software-updates/index.html.md): Find a specific action or setting for software updates and open the related instructions in RustSC. - [Wipes reference](https://rustsc.com/support/guides/reference-wipes/index.html.md): Find a specific action or setting for wipes and open the related instructions in RustSC. HTML version: https://rustsc.com/help/v1/ --- # Connect your first server Install RustSC, add a server and connect an existing host. ## Start in your workspace - [Your first server in RustSC](https://rustsc.com/support/guides/first-server/index.html.md) - [Install RustSC on Linux](https://rustsc.com/support/guides/install-linux/index.html.md) - [Install RustSC on Windows](https://rustsc.com/support/guides/install-windows/index.html.md) - [Add a host to your workspace](https://rustsc.com/support/guides/add-host/index.html.md) - [Add your first server](https://rustsc.com/support/guides/add-server/index.html.md) ## If the command does not work - [Install RustSC on Linux](https://rustsc.com/support/guides/install-linux/index.html.md) ## Choose where the server goes - [Choose a server folder](https://rustsc.com/support/guides/server-folder/index.html.md) ## Already running a server? - [Move a server you already run into RustSC](https://rustsc.com/support/guides/move-existing-server/index.html.md) - [Add an existing server](https://rustsc.com/support/guides/add-existing-server/index.html.md) - [Move a server to a new host](https://rustsc.com/support/guides/move-to-new-host/index.html.md) ## Reconnect a host - [Reconnect a host](https://rustsc.com/support/guides/reconnect-computer/index.html.md) ## Choose a setup that fits - [Install RustSC on Linux](https://rustsc.com/support/guides/install-linux/index.html.md) - [Install RustSC on Windows](https://rustsc.com/support/guides/install-windows/index.html.md) HTML version: https://rustsc.com/help/v1/getting-started/ --- # Run and configure your server Start, configure, update and schedule your server. ## Start, stop and restart - [Start, stop or restart a server](https://rustsc.com/support/guides/start-stop-restart/index.html.md) ## Player warnings - [Messages, restarts and wipes: what players see](https://rustsc.com/support/guides/player-messages/index.html.md) - [Start, stop or restart a server](https://rustsc.com/support/guides/start-stop-restart/index.html.md) ## See how the server is running - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/index.html.md) ## Change settings - [Change server settings](https://rustsc.com/support/guides/server-settings/index.html.md) ## Keep the game and add-ons current - [Update Rust](https://rustsc.com/support/guides/update-rust/index.html.md) - [Change Oxide or Carbon](https://rustsc.com/support/guides/change-framework/index.html.md) - [Find and manage plugins](https://rustsc.com/support/guides/plugins/index.html.md) ## Schedule routine work - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/index.html.md) ## Stop managing a server - [Remove a server from RustSC](https://rustsc.com/support/guides/remove-server/index.html.md) HTML version: https://rustsc.com/help/v1/server-basics/ --- # Back up, restore and wipe Protect your server, restore a backup or start a new map. ## Back up a server - [Backups on your host](https://rustsc.com/support/guides/backups-local-and-offsite/index.html.md) - [Back up a server](https://rustsc.com/support/guides/back-up-server/index.html.md) ## Keep fewer backups and free space - [Free disk space](https://rustsc.com/support/guides/free-disk-space/index.html.md) ## Restore a backup - [Restore a backup](https://rustsc.com/support/guides/restore-backup/index.html.md) ## If the save is damaged - [Recover a damaged save](https://rustsc.com/support/guides/recover-save/index.html.md) ## Wipe - [Wipe your server](https://rustsc.com/support/guides/wipe-server/index.html.md) - [Wipe plans in plain words](https://rustsc.com/support/guides/wipe-plans/index.html.md) ## Wipe on a schedule - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/index.html.md) - [Preview your map](https://rustsc.com/support/guides/preview-map/index.html.md) HTML version: https://rustsc.com/help/v1/backups-and-wipes/ --- # Players, alerts and who can do what Manage players, move Discord links and check workspace access. ## Kick, ban and unban - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/index.html.md) - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/index.html.md) ## Move your Discord links to RustSC - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/index.html.md) - [Move existing Discord links](https://rustsc.com/support/guides/move-discord-links/index.html.md) ## Low disk space and resource alerts - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/index.html.md) ## What each role can do - [Understand workspace roles](https://rustsc.com/support/guides/workspace-roles/index.html.md) - [Give someone access to only some servers or hosts](https://rustsc.com/support/guides/limited-access/index.html.md) - [Let a moderator run a few commands](https://rustsc.com/support/guides/mod-commands/index.html.md) - [See what your team did](https://rustsc.com/support/guides/team-activity/index.html.md) HTML version: https://rustsc.com/help/v1/players-and-access/ --- # Get back to a working server Find the next step for an offline host or failed action. ## The host is offline - [If something is not working](https://rustsc.com/support/guides/not-working/index.html.md) - [Host offline](https://rustsc.com/support/guides/computer-offline/index.html.md) ## An action failed - [An action failed or stopped](https://rustsc.com/support/guides/action-failed/index.html.md) ## The server will not start - [Server will not start](https://rustsc.com/support/guides/server-will-not-start/index.html.md) ## Prepare a useful support request - [Contact support](https://app.rustsc.com/support) HTML version: https://rustsc.com/help/v1/troubleshooting/ --- # Which permission each API action needs Look up a workspace permission to see which API actions use it. Reference: v1 (open beta). ## How to read this page Find a permission below to see its actions. If an action accepts either of two permissions, it appears under both. For an action without a listed workspace permission, check its entry in the API reference for sign-in requirements. - [Browse the customer API reference](https://rustsc.com/help/v1/reference/index.html.md) ## Alerts - alerts.manage: Clear an acknowledgement; Acknowledge an alert. - alerts.read: Read the alert manager; Preview applying a template; List alert templates; List open resource alerts; List chat words; List console words; List quiet times. - alerts.settings.manage: Save alert settings; Apply a template; Send a test card of an alert to Discord; Save the current settings as a template; Remove a template; Rename a template or update it from the current settings; Add a chat word; Remove a chat word; Change a chat word; Add a console word; Remove a console word; Change a console word; Save a host's alert settings; Make a notification template; Remove a notification template; Rename or change a notification template; Save a server's alert settings. ## Apikeys - apikeys.manage: List integration keys; Make an integration key; Revoke an integration key; Choose what an agent key asks first; Choose the servers an agent key reaches; Pause all assistants; Resume all assistants. ## Audit - audit.read: List audit records; Download the audit trail. ## Automation - automation.manage: Send a broadcast; Save a timed chat line or console command for a rented server; Save a broadcast; Change a saved broadcast; Send a saved broadcast; Archive a saved broadcast. ## Backups - backups.create: Back up a server now. - backups.export: Read whether a backup export can be downloaded; Download a backup export; Make a download link for a backup export; Export a backup as a zip; Restore a backup to a folder. - backups.manage: Change backup protection; Change how many backups a server keeps; Free up space; Check what can be cleaned up; Delete a backup; Turn a server's cloud copy on or off. - backups.read: Read backup protection status; Read the host's backup protection setting; Read how many backups a server keeps; List a server's backups; Read a server's cloud copy; List a server's cloud copies; Read how well a server's backups are keeping up; Download a rented server's backup; Make a download link for a rented server's backup. - backups.restore: Check a backup for a copy; Preview restoring a backup; Restore a backup; Restore a backup over another server; Get a cloud backup back onto the host; Restore a server's cloud backup onto its new host; Use the previous save; Keep the server stopped. ## Evidence - evidence.delete: Delete every report about a player; Delete a report; Delete what a server captured. - evidence.export: Download the events of the servers you can export; Download the report inbox; Download the events a server recorded. - evidence.read: Read the events a server recorded; Read one recorded event with the events around it. ## Groups - groups.manage: Create a server group; Delete a server group; Rename a server group; Add servers to a group; Take servers out of a group. ## Hosts - hosts.enroll: Create an enrollment token; Revoke an enrollment token; Reconnect a host. - hosts.manage: Rename a host in RustSC; Remove an installation; Connect a rented server; Check what a key allows on a host; Disconnect a rented server; Ask a connected rented server to start, stop, restart, kill or run a command; Check a connected rented server again; Read the game console saved with a connected rented server; Change the game console saved with a connected rented server; Read the recent lines of a connected rented server's log file; List the other servers of the same account at the host; Connect more servers from the same account; Remove the plugin key of a connected rented server; Make or replace the plugin key of a connected rented server; Read a connected server's startup values; Change one startup value on the host. - hosts.read: List pending enrollment tokens; Read an enrollment token; List hosts; Read a host; Read a host's alert settings and open alerts; List what you can ask of a host now; List a host's log lines; Get the latest host measurements; Read a host's update settings; Get the performance history of a host; List host restart schedules; Read a host restart schedule; List occurrences; Read a host's restart with the server restart choice; List what a host did and how it ended; List the hosts a rented server can be connected through, and the connected servers; List the latest actions of a connected rented server; See whether a connected rented server has a plugin key; Read the workspace's own Steam key state. - hosts.reboot: Restart a host; Request operating system updates; Save a host's update settings; Run the host's updates now; Schedule a host restart; Change a host restart schedule; Remove a host restart schedule; Save a host's restart with the server restart choice. - hosts.remove: Remove a host from RustSC. - hosts.update: Check what an update of the host would do; Choose when the host gets updates; Turn the host's automatic updates on or off; Update the host. ## Integrations - integrations.manage: Send alerts to a Discord channel; Send a test alert to a picked channel; Remove an alert route; Change an alert route; Send a test alert to a saved route; Remove the workspace's Codefling key; Save the workspace's Codefling key; Check the workspace's Codefling key; Disconnect Discord; Create the link channel; Choose the link channel; List the text channels to choose the link channel from; Connect the Discord server the bot was added to; Choose who can search links in Discord; Get the address that adds the bot to Discord; Save the Discord invite link; Turn the nickname sync on or off; Try the players who could not be renamed again; List the channels to post alerts and status in; Save the words players see for the link; Remove an integration's key from one host; Give linked players a Discord role; List the Discord roles a rule can give; List the Rust groups linked players can be added to; Stop giving a Discord role; Give the roles staff took away again; Stop adding linked players to a Rust group; Also add linked players to a Rust group; Add the players who already linked to the Rust group; Remove the workspace's RustHQ key; Save the workspace's RustHQ key; Check the workspace's RustHQ key; Disconnect a server from Discord; Save a server's Discord settings; Turn off and forget a server's chat relay; Save a server's chat relay; Send a chat relay test line; Send a Discord test message; Remove the workspace's own Steam key; Save the workspace's own Steam key; Send a test with the workspace's Steam key; Add a webhook; Remove a webhook; Change a webhook; Make a new signing key; Send a test delivery. - integrations.read: List alert routes; Read the workspace's Codefling connection; Read the Discord link setup; Get a saved Discord look picture; List the workspace's integrations; List the hosts that hold an integration's key; List the roles linked players get; List the Discord role and Rust group syncs; Read the workspace's RustHQ connection; Read a server's Discord settings; Read a server's chat relay; List webhooks; Show what a webhook receives; Show a webhook's delivery log. ## Links - links.manage: List the uploaded link files; Upload the data of the old link service; Throw an uploaded file away; Make the links from an uploaded file; Search the linked players; Sync the links now; End a player's link. ## Members - members.manage: Invite someone; Withdraw an invitation; Send an invitation again; Set what a member can do; Set a member's chat name. - members.read: List pending invitations; List members; List permissions; List roles. ## Players - players.actions: Heal a player; Kill a player; Restore a player's blueprints; Change a player's health, hunger or thirst; Move a player; Unlock a player's blueprints. - players.admit: Stop allowing a player anyway from the workspace settings; Save the ban list choices of the workspace; Add a BattleMetrics ban list; Add a community ban list; Remove a community ban list; Remove a community ban list's key; Add a community ban list's key; Save the join rule defaults of the workspace; Stop allowing a player anyway; Allow a player anyway; Refuse listed players when they join a rented server, or stop; Save the join rules of a server; Use the workspace's setting for a join rule. - players.entities.remove: Look at everything a player owns; Remove everything a player owns. - players.gameroles.manage: Take an owner or moderator role away; Make a player an owner or moderator. - players.inventory.manage: Give items to a player; Save inventory changes; Remove items from a player; Get saved inventory change results; List the item sets of a server; Save an item set; Delete an item set; Change an item set; Give an item set to a player. - players.inventory.read: Look at what a player carries; Read items available in the game; Get the game's items from a read. - players.moderate: Check the global ban list again; Ban a player on all servers, now and later; Unban a player on all servers; Ban a player; Also ban a player from Discord; Also lift a player's Discord ban; Freeze a player; Import a list of bans; Kick a player; Send a private message to a player; Kick, ban, unban or mute several players of a rented server; Mute a player's chat through the game's console; Mute a player; Preview a list of bans; Release a player; Unban a player; Let a player chat again through the game's console; Check players against the ban lists again; Apply the global bans to a hosting panel server, or stop; Take a label off a player; List the labels on a server's players; Put a label on a player; List the private notes of a server; Write a private note about a player; Remove a private note; Change a private note; List the texts a note has had; Check whether a player can also be banned from Discord; Lift a server's own ban where a global ban also applies. - players.permissions.manage: Turn the permission sync on or off and choose its servers; Choose what the sync does for players a server has not seen yet; Keep items Only on this server, or sync them again; List the saved permission templates; Save a permission template; Delete a permission template; Apply changes to a server's groups and permissions at once. - players.permissions.temporary: Give temporary access; End what an order reference gave; List temporary access packs; Delete a temporary access pack; Save a temporary access pack; Read temporary access settings; Save temporary access settings; Add time to temporary access; Apply temporary access again; End temporary access now; Keep temporary access. - players.read: List the players allowed anyway; Read the ban list choices of the workspace; Read where the global ban list stands on each server; Read the join rule defaults of the workspace; List the servers a join rule default would newly apply to; List the workspace bans; List the names players were seen under; Read the player stats; List the players of the workspace; Read the ban facts of players; Read the ban lists of a server; Read whether a rented server refuses listed players when they join; List the bans of a server; Download the ban list; List the join checks of a server; Read the join rules of a server; Read where a hosting panel server's global bans stand; List the player history of a server; Read the players seen on a server; Read what RustSC knows about some players; List connected players; List the owners and moderators of a server. - players.read.sensitive: Read the permission sync of the workspace; Read the history of the permission sync; Read the groups the permission sync keeps the same; Read a server's groups, players' permissions and in-game staff. - players.structures.manage: Take items out of a container; Remove one thing from the world; Remove a whole building from the world; Unlock a hackable crate. ## Plugins - plugins.manage: Check a server's plugins for updates now; Check a plugin file at a web address; Install a plugin from a marketplace; Remove the RustSC plugin from a rented server; Enable, disable, reload, remove or update a plugin; Check one plugin for updates now; Grant or revoke a permission, or change a group; Roll a plugin update back or forward; Mark a plugin as Custom; Keep a plugin up to date; Choose the marketplace of a plugin; Give the marketplace page of a plugin. - plugins.read: List a server's plugins; Find plugins on the marketplaces; Recognise a pasted plugin address; Open a found plugin; Read whether a rented server can take the RustSC plugin and whether it has it; Which plugin updates can be rolled back; Which plugin updates RustSC can make. ## Profiles - profiles.manage: Save a settings profile; Delete a settings profile; Change a settings profile; Let a server keep its own value. ## Reports - reports.manage: Change a report. - reports.read: Read the report inbox; Read a report; Read what the server recorded around a report. ## Roles - roles.manage: Make a role; Delete a role; Change a role. - roles.sync.manage: Keep a Discord role and a Rust group in step; List what a sync can be made from; Stop a sync; Give again what staff took away; Compare one sync's players again now. ## Rules - rules.enable: Switch a rule on or off. - rules.manage: Delete a rule; Change a rule. ## Schedules - schedules.manage: Save the Discord announcement of a schedule or temporary change; Delete a timed chat line or console command of a rented server; Save a restart for a rented server; Delete a saved restart of a rented server; Change a saved restart of a rented server; Add dropped plugin files to the library; Add the plugin files in the inbox to the library; Look in the plugin inbox; Look for newer versions at the plugins' GitHub update sources; Put the previous version of a library plugin back; Check what dropped plugin files would do; Swap a running plugin to the newer version in the inbox and reload it; Update the library from the plugins folder; Take the newer version from the plugins' GitHub update sources into the library; Save the plugin library's choices; Create a schedule; Change a schedule; Revoke a schedule; Save a temporary change; Take a plugin from the library; Check a temporary change before saving it; Delete a temporary change; Change a temporary change; Copy a temporary change that reads its folder to another server; Duplicate a temporary change; End a temporary change now; Extend a temporary change; Create, fill or list-write a temporary change's folder; Keep a temporary change on anyway; Pause a temporary change; Receive a copied folder on the target host; Resume a temporary change; Run a finished temporary change again; Start a temporary change now; Update a plugin a temporary change places; Save a temporary change as one that reads its folder. ## Servers - servers.config.write: Save a Nexus network; Delete a Nexus network; Change a Nexus network; Save configuration changes; Apply the saved configuration; Check an image link; Save desired server ports; Apply saved server ports; Choose what a server records of its history; Add the Windows Firewall rule; Remove the Windows Firewall rule; Save the start settings of a server; Rename a server in RustSC; Save the public IPv4 address of the server; Change automatic recovery; Switch history on or off for a rented server; Save the query address of a rented server; Choose the time zone of a server's schedules; Save or switch off a server's Upkeep setting. - servers.console.execute: Run a console command; Hide repeated errors in a server's console for a while, or stop hiding them; Save a mod command; Change a mod command; Remove a mod command; Save a command; Change a saved command; Run a saved command; Archive a saved command. - servers.console.read: Read whether commands reach a rented server; Read whether a server's console hides repeated errors; List the times a server's console repeated the same line; Search older console lines; List the ends of a server's game; List mod commands; List saved commands; Read a saved command. - servers.create: Browse folders on a host; Create a folder on a host; Preview adopting a server folder; Read a folder on a host; Check a custom map link; Add a server; Adopt a server folder; Adopt a server again with what is there now; Copy a backup as a new server. - servers.delete: Remove a server. - servers.files.read: Look at the files in a server's Oxide or Carbon folder; Read the last listing kept for a server's Oxide or Carbon folder; Read the names of a plugin's files, its permissions or its commands. - servers.files.write: Keep files for a server until a person has looked at them; Get an address to send one large file to; Throw a staged attachment away; Read a staged attachment; Put a staged attachment on the server; Delete, rename, move, copy or create files and folders in a server's Oxide or Carbon folder; Save a file in a server's Oxide or Carbon folder; Keep the listing the Files area has just read; Save a temporary change for a rented server; Delete a temporary change of a rented server; Change a temporary change of a rented server; Take a temporary change of a rented server out now; Put a saved temporary change of a rented server in place now; Start uploading files to a server's host; Stop an upload; Read an upload; Send a finished upload to the server's host; Put a finished upload in a folder of the server. - servers.helpers.manage: Save a server's helpers. - servers.helpers.read: Read a server's helpers. - servers.lifecycle: Plan a quiet time; Restart a server; Start a server; Stop a server; Save a server's player warnings. - servers.modcommands.run: Run a mod command; List the commands a moderator can run. - servers.read: List the RustSC plugin's player commands on every server; Read linking in the game; Read a command result; Read a rule; Read a server; Read a server's alert settings and the alerts that concern it; Read RustSC's default Discord announcement; Read the Discord announcement of a schedule or temporary change; List what you can ask of a server now; Read a server's configuration; Read endpoints from the host; Read what a rented server's host says happened to the server; Read a server's map name; Get the latest server measurements; Preview a message template; Get the performance history of a server; Read the plugin library of a server; List quick actions; Preview a quick action; Read whether players can reach the server; Check that players can reach the server; Read the host's automatic recovery setting; Check a release channel again; Read the game and framework versions of a rented server; Read the status of a rented server; Read whether history is kept for a rented server; Read whether a server has a RustEdit map key; Read whether the next start is the start the game runs with now; List saved broadcasts; List schedules; List a server's temporary changes; List the temporary changes that are on; List the saved files of a server's temporary changes; Read a temporary change; Refresh the files of a temporary change that reads its folder; Read the next start times of a temporary change; Read a server's Upkeep setting; List a server's installed and latest versions; List a server's saved wipes; Read a saved wipe. - servers.save: Save a server. - servers.secrets.write: Read a server's RCON connection details; Set a server's RCON password or where its console listens; Show a server's RCON password. - servers.setup.read: List the saved Nexus networks; Read what a rule did; Inspect the server configuration; Read configuration inspection history; Read server network endpoints; Read what a server records of its history; Read the Windows Firewall rule of a server; Read what the host of a rented server allows; Read the launch arguments an adoption imported; Read the start settings saved for a server; Read who restarts a rented server; List the temporary changes, wipes and restarts saved for a rented server; List the timed chat lines and console commands saved for a rented server; Read automatic crash recovery status; List release channels; Read a saved broadcast; Read a schedule; List occurrences; List the starting points for a temporary change; Read what a temporary change did; Read the visible folder of a temporary change; Read a server's automatic update settings; Read a server's player warnings; Preview a player warning; List the extras of a server's wipes; List the runs of a saved wipe; Read a server's wipe settings; List a server's wipe templates; Read a wipe template. - servers.software.manage: Save linking in the game; Install, update or remove a supporting extension; Install, upgrade, switch or uninstall Oxide or Carbon; Change the Steam branch of the game; Check for a game update; Inspect a server's game files; Install again; Repair a server's game files; Replace a server; Switch Oxide, Carbon or no framework on a rented server; Update the game; Update Oxide or Carbon on a rented server; Choose a release channel; Check a replacement; Remove a server's RustEdit map key; Set a server's RustEdit 2 map key; Save a server's automatic update settings. ## Workspace - workspace.close: Keep a closing workspace; Read what closing a workspace does; Close a workspace. - workspace.export: Download a workspace's data. - workspace.manage: Rename a workspace; Replace the workspace's sign-in rule; Save the workspace's time zone. - workspace.read: Read the workspace's sign-in rule. ## Worlds - worlds.read: Count what the world holds; Count what each player owns; Find things in the world; Look at one thing in the world; Look inside a container; Look at the building a part belongs to; Read a player's cupboards and upkeep trail on a server. - worlds.reset: Check a custom map link; Plan a new map; Wipe the map; Save a server's map name; Save a wipe template for a rented server; Delete a wipe template of a rented server; Change a wipe template of a rented server; Save a wipe for a rented server; Preview a wipe of a rented server before it is saved; Delete a saved wipe of a rented server; Change a saved wipe of a rented server; Add an extra to a saved wipe; Check a plugin at a web address; Remove an extra; Change an extra; Put an extra in place now; Save an extra to its plan's template; Take an extra out now; Use an extra again; Save a new wipe plan; Delete a saved wipe; Change a saved wipe; Wipe again or schedule a saved wipe; Switch off a saved wipe; Switch on a saved wipe; Copy a saved wipe; See what a saved wipe will do; Save a server's wipe settings; Save a new wipe template; Delete a wipe template; Change a wipe template; Copy a wipe template. HTML version: https://rustsc.com/help/v1/permissions/ --- # Use the customer API Sign in, find your workspace and make your first request. Reference: v1 (open beta). ## Which interface can I use? This reference describes the RustSC customer API for open beta. You need an existing RustSC account to sign in through the portal and use a browser session. Use an API key only with routes that say they accept one. Send API requests to the RustSC address where you sign in. Where supplied, the OpenAPI operation lists its permission (x-rustsc-permission), rate class (x-rustsc-rate-class) and cost class (x-rustsc-cost-class). - [Download OpenAPI JSON](https://rustsc.com/help/v1/openapi.json) - [Download JSON Schemas](https://rustsc.com/help/v1/schemas.json) - [Browse every accepted operation](https://rustsc.com/help/v1/reference/index.html.md) ## Sign in and discover your workspace Every unsafe cookie-authenticated request needs X-CSRF-Token, including sign-in requests. A read-only permission does not permit creating resources, saving wipe plans or issuing credentials. 1. Read GET /api/v1/session with a cookie-aware client. Keep its cookies and csrfToken private. 2. Sign in through the portal. Use one of the options it shows, such as Discord, Google, Apple or a passkey already added to your account. The customer API has no password sign-in. 3. Read GET /api/v1/session again after that sign-in, with the browser's cookies, to obtain the current session and request token. 4. Read GET /api/v1/workspaces. Select a workspace returned for this account, then list that workspace's hosts and servers. Never infer IDs from names or use another workspace's IDs. ## Synthetic request bodies These are request bodies for the documented operations, not credentials or a ready-made customer session. Replace the sample values only in your own client. ```http POST /api/v1/workspaces {"name":"Example community"} POST /api/v1/workspaces/{workspaceId}/servers/{serverId}/actions/restart Idempotency-Key: example-restart {"force":false} POST /api/v1/workspaces/{workspaceId}/servers/{serverId}/backups Idempotency-Key: example-backup {} POST /api/v1/workspaces/{workspaceId}/servers/{serverId}/actions/plan-wipe Idempotency-Key: example-wipe-plan {"seed":12345,"worldSize":3500} ``` - [Follow work safely](https://rustsc.com/help/v1/operations/index.html.md) ## Versions and compatibility Use the v1 links when building a client. Ignore unknown response fields and treat unknown enum values as other. Read the operation's declared request and response schema before sending it. Keep a copy of the contract used to build your client and compare it before upgrading. HTML version: https://rustsc.com/help/v1/api/ --- # Follow actions and recover safely Avoid duplicate requests, handle changes and cancellations, and recover when the result is unclear. Reference: v1 (open beta). ## Follow the operation 1. Keep the operation ID returned by a work request. An accepted or queued result means work is recorded, not complete. 2. Read the operation through getOperation after a reconnect. Use If-None-Match with its ETag to avoid downloading an unchanged record. Prefer: wait may wait for a change within the server's returned limit. 3. Read the final state, stages, effects and partial flag. Report succeeded, failed or cancelled exactly as returned. Cancellation cannot undo effects that already happened. ## A request timed out Send each new work request with a new Idempotency-Key. If its response is lost, repeat the identical request with the same key. Changing the key can start new work. Keep the method, path, body and If-Match value unchanged on a retry. If the key was reused with different input, correct the client instead of retrying blindly. After the key has expired, inspect existing work before sending another request. ## The outcome is unknown outcome_unknown means RustSC could not prove what happened. It does not mean the action failed. Read the uncertainty and inspect the target. Do not send another restart, wipe, restore or console command just to get a clearer answer. The current API reference lists the recovery operations actually available. Do not invent a resolve or retry endpoint from a planned workflow. If the current interface offers no suitable recovery, keep the operation ID and seek support. ## Choose the next step from the error 1. unauthenticated: sign in again. csrf_token_invalid: reload the session and repeat with its new token. 2. forbidden or insufficient_scope: obtain the needed authority from a workspace owner or the integration consent flow when it exists. Never widen scope yourself. 3. not_found: check your selected workspace and use an ID from a resource you can read. 4. revision_conflict: read the current resource and compare it with the intended change before submitting again. 5. operation_conflict: follow the blocking operation or use the action's documented queue option. 6. capability_unavailable: read the reason and the server's available actions. Repeating a request cannot add a missing host or plugin capability. 7. rate_limited: wait for Retry-After. dependency_unavailable: follow the error's suggested wait. Retry a work request with the same key. 8. validation_failed: correct the listed field pointers. Keep the traceId for a support request; do not share credentials or full private responses. ## Lists, limits and stale information Use the documented cursor and filters for each list. A page of results is not the whole workspace. Do not assume every endpoint uses the same pagination fields. Respect rate-limit responses. Check when a status was last observed and ask for a refresh if you need a current reading. HTML version: https://rustsc.com/help/v1/operations/ --- # Your first server in RustSC Sign in, connect your host, start a server and restart it with a warning. ## From sign-in to a running server 1. Sign in to your RustSC account. 2. Your workspace opens on **Set up your server**: three steps, **Connect your host**, **Add your server** and **Start your server**. The page moves on by itself as each one is done. The first step shows the command. A host is where your server will run. 3. On Linux, choose the **Linux** tab and **Copy install command**. Paste it into a terminal on that host and press Enter. You need an account with sudo. 4. On Windows, choose the **Windows** tab and **Copy install command**. Open PowerShell on that host, paste the command and press Enter. Choose **Yes** when Windows asks. 5. Wait for the host to show **Connected**, then choose **Add server**. Enter a name and keep the suggested folder and ports. Choose **Add server and install**. 6. Wait for the Rust download to finish. It is several gigabytes and the page follows it by itself. The server then shows **Ready to start**. Choose **Start now**. 7. The first start makes the map, so it can take several minutes. Wait for the status to change from **Starting** to **Running**. 8. To try a restart, choose **Restart server** and confirm with **Restart server**. Players read a countdown in chat first. ## What you should see Ubuntu 24.04 on x86-64 is the Linux system RustSC is tested on with a running game. On Windows, use the PowerShell command your portal shows. Nothing starts until you choose **Start now**. When your server is running, Home shows **Your server is running** with optional next steps: back up, choose alerts, connect Discord and plan wipes. Choose **Done with setup** to hide them. **Hide setup** hides the steps earlier, and **Continue setup** brings them back. - The host shows **Connected** on the **Hosts** tab. On Linux the terminal ends by telling you to go back to the portal and add your server. - The install page shows Downloading Rust with a percentage, then the server shows **Ready to start**. - The first start shows **Starting**, with **Generating map** or **Loading** while it works, and then **Running**. - During a restart the server header counts down, for example Restarting in 3:42, and offers **Cancel countdown**. - [Sign in to RustSC](https://app.rustsc.com/sign-in) - [Move a server you already run into RustSC](https://rustsc.com/support/guides/move-existing-server/index.html.md) - [If something is not working](https://rustsc.com/support/guides/not-working/index.html.md) HTML version: https://rustsc.com/support/guides/first-server/ --- # Move a server you already run into RustSC Add a Rust server that is already installed, even while another tool is running it. ## Add the server 1. Connect the host the server is on first. See Your first server in RustSC. 2. Open **Servers** and choose **Add existing server**. 3. If the host found a server, choose it under **Rust server found** and the page checks it at once. Otherwise choose the **Host** and enter the **Server folder**. It is the full path of the folder that holds RustDedicated. 4. For a folder you typed, choose **Check folder**. Checking changes nothing. Read what it found, such as the game build and your Oxide or Carbon files. 5. If the server is running, the page says it is running under another tool. RustSC can watch it while that tool keeps it running. 6. If **Install the RustSC plugin** is offered, it is ticked. Untick it if you want to leave the server files unchanged. 7. Choose **Add server** when it shows **Ready to add**. 8. The server shows **Running**, run by another tool, within a few seconds. The server's **Settings** open next, with **Restarts and recovery** first. Every job is off until you turn it on, so leave a job off while your old tool does it. ## What you will see To run it from RustSC, stop it in your old tool, then choose **Start server**. If you choose Start while the other game still runs, RustSC does not start a second copy. - Nobody is disconnected. RustSC does not stop, restart or start a game that another tool runs, on Windows or Linux. - Your files are not copied or moved. If you leave the plugin option ticked, RustSC can install its plugin when you add the server. - Players and Performance can show live information when the server's console is available. The page says when information or an action is unavailable. - If both tools have restart schedules they can restart the server at the same time. Keep schedules in one of them. - A server that is not running is added without being started. ## Switching between RustSC and your old tool - Whichever one is running the server owns it. The other one only watches. - To run it from RustSC: stop it in your old tool, then choose **Start server**. The first time, RustSC may ask once to take over the folder. Choose **Take over and start**; your old tool can still use the files. - To go back: choose **Stop** in RustSC, then start it in your old tool the way you always did. RustSC shows **Running**, run by another tool, within a few seconds. - While your old tool runs it, RustSC has no Start, Stop or Restart for it. A schedule, a backup, an update, a wipe or a host restart that would touch it is refused with the reason, and it is not stopped. - You can switch again and again. Nothing is remembered between switches: RustSC looks at what is running now. ## If it does not work In each of these cases RustSC leaves your server running as it was. Nothing in your folder is deleted. - Adding failed: the page says what happened. Choose **Try again**, or **Remove** to start over. Removing works even when the host is off. - Another server answered where this one should, so RustSC left everything running. Check the RCON port, then try again. - The game running from this folder uses another game port. Enter the port it runs on. - [If something is not working](https://rustsc.com/support/guides/not-working/index.html.md) - [Add an existing server](https://rustsc.com/support/guides/add-existing-server/index.html.md) HTML version: https://rustsc.com/support/guides/move-existing-server/ --- # Install RustSC on Linux One command installs RustSC on a Linux host and connects it. ## Install and connect The command installs RustSC, starts it and connects the host to your workspace. Your own Rust server files are not touched. Ubuntu 24.04 on x86-64 is the Linux system RustSC is tested on. 1. In the portal, open **Hosts**, then **Add host**. 2. Choose the **Linux** tab, then **Copy install command**. 3. Open a terminal on the host that will run your servers. Paste the command and press Enter. You need an account that can use sudo. 4. Wait for the terminal to finish. The last line says: Connected. Go back to RustSC to add your server. 5. In the portal, wait for the host to show **Connected**, then choose **Add server**. ## If something goes wrong - The terminal says the command expired or was already used: copy the new command from **Add host**. A command works once. - The terminal shows only a line that starts with curl: check the host's internet connection and its date and time, then run the same command again. - The host does not show **Connected**: open **Not showing up?** on the Add host page. It lists what to check. - Running the same command again on its connected host leaves the connection as it is. To connect that host again, use **Reconnect** on its page. - [Add a host to your workspace](https://rustsc.com/support/guides/add-host/index.html.md) - [Add your first server](https://rustsc.com/support/guides/add-server/index.html.md) - [Reconnect a host](https://rustsc.com/support/guides/reconnect-computer/index.html.md) HTML version: https://rustsc.com/support/guides/install-linux/ --- # Install RustSC on Windows Paste one command into PowerShell and your Windows host is installed and connected. ## Install and connect Closing the RustSC window leaves it running in the notification area. Your servers keep running either way. 1. In the portal, open **Hosts**, then **Add host**, and choose the **Windows** tab. 2. Choose **Copy install command**. The command already holds your connection code. 3. On the host that will run your servers, open **PowerShell** from the Start menu. Paste the command and press Enter. 4. Choose **Yes** when Windows asks for permission. RustSC installs and connects by itself. 5. In the portal, wait for the host to show **Connected**, then choose **Add server**. ## If something goes wrong - PowerShell says the code was already used or has expired: copy the command again from **Add host**. It holds a new code. - PowerShell says it stopped: it says why and what to do. Run the same command again; it picks up where it left off. - RustSC is already installed: open it and paste the code under **Connect to your workspace**, then choose **Connect**. - The host does not show **Connected**: open RustSC on the host. It says whether it is connected. - No command is offered on the page: Windows installation is not available from this service yet. - [Add a host to your workspace](https://rustsc.com/support/guides/add-host/index.html.md) - [Add your first server](https://rustsc.com/support/guides/add-server/index.html.md) HTML version: https://rustsc.com/support/guides/install-windows/ --- # Add your first server Install Rust on a connected host and start your server. ## Add and start the server Already have a Rust server? Use **Add existing server** to keep its files. 1. Choose **Add server** and select your connected host. 2. Enter a server name. Keep the suggested folder and ports unless you need different ones. 3. Choose **Add server and install**. Follow the download on the server page. 4. When the server shows **Ready to start**, choose **Start now**. Wait for **Running** before inviting players. - [Add an existing server](https://rustsc.com/support/guides/add-existing-server/index.html.md) - [Choose a server folder](https://rustsc.com/support/guides/server-folder/index.html.md) - [Server with a hosting company? See the supported providers](https://rustsc.com/hosting/index.html.md) HTML version: https://rustsc.com/support/guides/add-server/ --- # Choose a server folder Choose the folder where RustSC installs your Rust server and keeps its game files, before you start the install. ## Choose the folder If installation fails, change the folder on the server page and install again. 1. On **Add server**, choose **Choose folder**. 2. Open a folder on the host. Choose **New folder** if you need one. 3. Choose **Select this folder**. Check the free space before installing. HTML version: https://rustsc.com/support/guides/server-folder/ --- # Add an existing server Bring a Rust server you already run into RustSC. Nothing about your server changes until you switch a function on. ## Add the server RustSC reads your settings when you add the server. If you leave the plugin option ticked, RustSC can install its plugin. Restarts, updates, backups and wipes happen only for a function you switch on. A server that is running is watched, not stopped or restarted. If it is stopped, it is added without being started. Do not install a new server over an existing server folder. 1. Connect the host the server is on first. See Add a host to your workspace. 2. Open **Servers** and choose **Add existing server**. 3. If the host found a server, it shows under **Rust server found**. Choose it and the page checks it at once. Otherwise choose the **Host** and the server folder, the one that holds RustDedicated. 4. For a folder you typed or browsed, choose **Check folder**. Read what it found, such as the game build and your Oxide or Carbon files. Checking changes nothing. 5. If **Install the RustSC plugin** is offered, it is ticked. Untick it if you want to leave the server files unchanged. Choose **Add server** when it shows **Ready to add**. 6. The server's **Settings** open next, with **Restarts and recovery** first. Every job is off. Switch on only the jobs you want RustSC to do: automatic updates are on **Software** and rules on **Schedules**. ## If something goes wrong - The check names a problem with the folder: the message says what to change. Fix it and choose **Check folder** again. - **Take over this folder** appears: stop any game still running from that folder first. It changes who can use the folder; it does not move or delete your files. - Adding failed: choose **Try again**, or **Remove** to start over. Nothing in your folder is deleted. - [Move a server you already run into RustSC](https://rustsc.com/support/guides/move-existing-server/index.html.md) - [Add a host to your workspace](https://rustsc.com/support/guides/add-host/index.html.md) - [Server with a hosting company? See the supported providers](https://rustsc.com/hosting/index.html.md) HTML version: https://rustsc.com/support/guides/add-existing-server/ --- # Add a host to your workspace A host is where your servers run. Connect it once and manage its servers from the portal. ## Connect a host A host can be a spare PC, a home server or a rented server you can install software on. Add a second host the same way. The host's row then shows its system, RustSC version and resources. Open a host and choose its **Servers** tab to see **Servers on this host**. Your servers keep running when a host is not connected to RustSC. Servers that are already on the host are added from **Add existing server**. 1. Open **Hosts** in the left menu, then choose **Add host**. 2. Choose the **Linux** or **Windows** tab for the system the host runs. 3. Follow the tab on that host. On Linux you paste one command into a terminal. On Windows you paste one command into PowerShell. 4. Keep the Add host page open. It says **Waiting for the host to connect** and follows by itself. 5. When the host shows **Connected**, choose **Add server**. ## If something goes wrong - The page says to ask a workspace owner to let you add hosts: your role cannot add one. - The page keeps waiting: open **Not showing up?** under the waiting line. - A code or command works once. If it was used or has expired, the page gives you a new one. - A host belongs to one workspace. A command from another workspace adds the host there as a new host, and its servers do not come with it. Use the command from the workspace you want. - A host that went offline: open it in **Hosts** and choose **Reconnect**. - [Install RustSC on Linux](https://rustsc.com/support/guides/install-linux/index.html.md) - [Install RustSC on Windows](https://rustsc.com/support/guides/install-windows/index.html.md) - [Reconnect a host](https://rustsc.com/support/guides/reconnect-computer/index.html.md) HTML version: https://rustsc.com/support/guides/add-host/ --- # Reconnect a host Restore a host’s connection without reinstalling your servers. ## Reconnect to your workspace Your server files stay in place. Use Reconnect in the workspace you want to keep. 1. Open **Hosts**, select the host and choose **Reconnect**. 2. On Linux, copy the command and run it on that host with sudo. 3. On Windows, copy the code. Open RustSC on the host and paste it under **Connect to your workspace**, then choose **Connect**. 4. Return to the portal and wait for the host to show **Connected**. - [Host offline](https://rustsc.com/support/guides/computer-offline/index.html.md) HTML version: https://rustsc.com/support/guides/reconnect-computer/ --- # Start, stop or restart a server Start, stop or restart your Rust server from RustSC, and check when it is ready for players to join. ## Start, stop or restart **Back up first** on a restart saves a backup while the server is stopped. The server starts again only if the backup succeeds. **Kill** and **Force restart** end the game without saving. Progress since the last save can be lost. **Kill** sits on the server page while the game runs and also ends a stop, restart, update or wipe that is still waiting. 1. Open the server. Choose **Start server**, **Stop server** or **Restart server**. 2. Confirm a stop or restart. A normal stop saves the world first. 3. Follow the result on the server page. Wait for **Running** after a start or restart. ## Player warnings Stop and Restart from the server page send players a countdown in chat first. Kill and Force restart warn nobody. Updates, wipes and changes that require a restart show their player warning before you confirm. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/index.html.md) ## If something goes wrong - The buttons are greyed out and the page says the host is not connected: they work again when it reconnects. The game keeps running meanwhile. - The page says another task is using the server: nothing was started. Try again when that task finishes. - The server shows **Failed to start**: read the reason under it. Usually the next step is **Restart server**. - The server page says **A different world started**: the server came back on another world than the one it stopped on. Choose **Put the world back** to restore the world it stopped on, or **Keep this world** to carry on with this one. Nothing changes until you choose. - The page says to ask a workspace owner to let you start or stop: your role cannot do it. - [Server will not start](https://rustsc.com/support/guides/server-will-not-start/index.html.md) HTML version: https://rustsc.com/support/guides/start-stop-restart/ --- # Messages, restarts and wipes: what players see The countdown players read in chat before a restart, a stop or a wipe, and how to change its words. ## What players read The warning is always sent, even when nobody seems to be online. RustSC does not guess who is there. The normal warning is 5 minutes. **Kill** and **Force restart** end the game at once without saving and warn nobody. - Before a restart: Restarting in 5 minutes. Then a line every minute, then at 30 seconds, 10 seconds and each second from 5 to 1. - Before a stop: Stopping in 5 minutes. Before a wipe: Wiping in 5 minutes. A game update and an Oxide or Carbon update have their own words. - Every message RustSC puts in chat starts with RustSC, so players know it came from the platform and not from another player. - At zero the server saves and stops, which ends the connections. RustSC does not kick anyone. ## Change the words or the time Write plain words, one line, at most 200 characters. Colour tags are not used: any angle brackets you type show as text. 1. Open the server and its settings. Find **Player warnings**. 2. Under **Before a restart**, **Before a stop**, **Before a game update**, **Before an Oxide or Carbon update** or **Before a wipe**, write your message. Write {time} where the time left goes. Leave it empty or choose **Use the standard message** to keep the standard one. 3. Choose **Show the countdown** to read the lines players will see. 4. Choose **Save messages**. The page says: Saved. The host has these messages. 5. For a wipe, set the time in **Warn players for (minutes)** on the **Wipe** tab. 0 stops the server at once. 6. To stop a countdown that has started, choose **Cancel countdown** in the server header. - [Start, stop or restart a server](https://rustsc.com/support/guides/start-stop-restart/index.html.md) - [Wipe a server](https://rustsc.com/support/guides/wipe-server/index.html.md) HTML version: https://rustsc.com/support/guides/player-messages/ --- # Read the console and check performance Find game messages, run commands and check server FPS. ## Read the console 1. Open the server’s **Console** tab to read recent game messages. 2. Use search and filters to find errors or a particular message. 3. To send a command, enter it under **Command** and choose **Run**. 4. The console follows the newest line. Scroll up to hold it where you are while new lines are counted. Scroll back to the bottom, or choose **Resume** or **Jump to latest**, to follow again. The Windows app works the same way. 5. Choose a long line that is cut short to open it in full. Choose it again to close it. - [Search, save and watch the console](https://rustsc.com/support/guides/console-tools/index.html.md) ## Check performance Server FPS shows how quickly the game is running. Check it on the server page or in the Servers list. Unknown means no current reading is available. Use the Players tab to see who is connected. Its **Stats** tab shows records and figures for a wipe, the last 7 or 30 days or all time: the most players at once, the busiest hour and day, the average frame rate and how long each wipe lasted. HTML version: https://rustsc.com/support/guides/console-performance/ --- # Change server settings Change your Rust server's settings in RustSC, save them and apply them to the running server. ## Change and apply settings If applying fails, follow the error. **Apply saved settings** tries the saved values again. A saved map or world change does not apply by itself, and a restart does not apply it. The top of **Configuration** says **Saved, not applied**, what the server is on and what is saved. Choose **Apply** to use the saved one. The server's **Overview** shows **Saved map change not applied** with **Open settings**. Changing **Game mode** on a server that already has a world resets players and their items. It takes effect at the next start. Read **This changes the game mode** before choosing **Save anyway**. For a setting that starts a new map, read **This starts a new map** before confirming. 1. Open the server’s **Configuration** tab. 2. Change the values you need. The info button beside a setting explains its default and whether a restart is required. 3. Choose **Save** to keep the changes, or **Save and apply** to send them to the server. 4. Restart the server if a changed setting requires it. ## Network ports Open **Network ports** on the **Configuration** tab. **Check again** reads the host’s current ports; **Open now** shows ports used by a running server. HTML version: https://rustsc.com/support/guides/server-settings/ --- # Update Rust Install the latest game build and choose automatic updates. ## Update the game 1. Open the server’s **Software** page. **Game** shows the installed and latest builds. 2. Open the menu on the **Rust** row and choose **Check updates** to look for a newer build. 3. When an update is waiting, **Update game** shows on the row. Choose it and review the player warning. 4. Follow the update until the server is running again. ## Automatic updates Both options start off. Choose what you want under **Automatic updates**. If you run Oxide or Carbon, a short wait before **Restart for updates** restarts the server gives it time to catch up with a new Rust build. - **Update Rust and framework on restart** installs a newer game build, and a newer Oxide or Carbon, at each restart. It never waits. - **Restart for updates** warns players when a newer build comes out, then updates and restarts the server. A stopped server stays stopped. HTML version: https://rustsc.com/support/guides/update-rust/ --- # Change Oxide or Carbon Install, update, switch or remove your server’s plugin framework. ## Change the framework 1. Open the server’s **Software** tab, then **Framework**. 2. Choose Oxide, Carbon or the available removal action. 3. Review the change and player warning, then confirm. 4. Wait for the work to finish before checking your plugins. ## Extensions Open **Extensions** and find RustEdit. Choose **Install**, **Update** or **Remove** when offered. HTML version: https://rustsc.com/support/guides/change-framework/ --- # Schedule a restart or update Restart your server at the same time every day, or on the days you choose. ## Create a schedule The time uses the server's own clock. Change its time zone in the server's **Settings**. Daylight saving is followed. Nothing is scheduled until you save. A game update schedule runs only when a newer build is out. Each schedule has an on and off switch. Off keeps it but stops it running. A server rented from a hosting company can have a restart in **Schedules**, once or repeating. A wipe is offered there only for hosts where RustSC can do it. If it is not offered, wipe from your provider's panel. 1. Open **Schedules** in the left menu and choose **Add schedule**. 2. Choose **Restart** under **Server**. For a game update, choose **Update the game**. The other choices are grouped as **Wipes**, **Messages and alerts** and **Host**. 3. Choose the **Server**, how often to **Repeat** (for example **Daily** or **Weekly** on the days you pick) and the **Time**. 4. Set **Warn players**, from 0 to 60 minutes. Players read a countdown in chat first. 0 means no warning. 5. Choose **Save**. Check the next run in the list. ## If something goes wrong - The schedule shows **Waiting for host**: the host has not received it yet. The older version may still run until the host reconnects. - A restart did not happen: open **History** on the Schedules page. Each run shows its result and, for a skipped or failed run, the reason. - You also restart the server from another tool: keep schedules in one of them, so the two do not restart it at the same time. - [Start, stop or restart a server](https://rustsc.com/support/guides/start-stop-restart/index.html.md) - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/index.html.md) HTML version: https://rustsc.com/support/guides/schedule-tasks/ --- # Find and manage plugins Search the plugin marketplaces, install a plugin and keep it up to date. ## Find and install a plugin Plugins you own on a marketplace you connected under **Integrations**, on the **Other** tab, also install here. Other plugins open on their marketplace. Download the file there, then add it under **Files**. If you have a plugin's page or a link to its .cs file, use **Add by address** and choose **Look up**. The page says what it will add and where it is from. Choose **Install** to add it. 1. Open the server and choose **Plugins**. If it says Oxide or Carbon is not installed, choose **Install Oxide or Carbon** first. 2. Choose **Add plugin**. This opens **Find plugins**. 3. Type a name or what it does, for example kits, and choose **Search**. Use **Filter** and **Sort** to narrow the results. 4. Choose **Install**. The page follows the install and says when the plugin is loaded. ## Update, disable or remove one Removing a plugin keeps the server running. - **Update** shows when a newer version is listed. RustSC keeps a copy of the current file and puts it back if the new version does not load. It also works on a plugin file stored in a subfolder; only that file changes. - **Disable** switches a plugin off and keeps it off after a restart. **Reload** loads it again. - **Remove** moves the file to a folder on the server. It is not deleted, and its settings and data stay. - **Roll back** puts the file from before an update back, for 48 hours after the update. **Roll forward** puts the updated file back again. Its settings and data stay. - **Keep this plugin up to date** saves your preference. Check the installed version after applying an update. - **My own version** keeps your file as it is. RustSC never updates or replaces it. Both options are in the menu on the plugin. - Use the filters, such as **Updates available** or **Failed to load**, to find the plugins that need you. ## If something goes wrong - Your host has not reported yet, or the list may be out of date: the page says so. It updates when the host is online. - An install says nothing was installed because the download could not be checked: try again later. - A plugin did not load after an update: RustSC put the old one back. Read the console for the reason. - A plugin says it cannot update itself: add its new file under **Files**. - A message says to update RustSC on the host: the host is too old to change plugins. Update it, then try again. - [Wipe plans in plain words](https://rustsc.com/support/guides/wipe-plans/index.html.md) HTML version: https://rustsc.com/support/guides/plugins/ --- # Remove a server from RustSC Remove a server from RustSC and stop managing it there, while the server's files stay where they are. ## Remove the server The server’s files stay on the host. Without that tick, a running server is not removed. 1. Open the server and choose its **Settings** tab. 2. Under **Remove server**, choose **Remove** and confirm. To stop a running game at the same time, tick **Stop the server first**. HTML version: https://rustsc.com/support/guides/remove-server/ --- # Move a server to a new host Point a server at a new host after a rebuild or a loss. It keeps its name, history, schedules, rules and backups. ## Modify the server for a new host 1. Add the new host first and wait for it to show **Connected**. 2. If the old host still runs this server, stop it there. Do not run the same server on both. 3. Open the server, choose **Settings**, and under **Manage** choose **Modify…** beside **Modify server**. 4. Under **Destination**, choose the new **Host**. Keep the **Game folder** or type the one you want on the new host. 5. Under **Also do**, tick what the new host needs: **Game**, **Framework**, **Plugins**, **RustSC plugin** and **Settings**. 6. Under **Backup**, tick **Restore backup** and pick the backup to bring back. It restores the world, plugin settings and permissions. 7. Read the **This will** list, then choose **Modify**. 8. Follow each step under **Activity**. The server stays stopped. Start it when you are ready. ## What to expect - The server keeps its name, history, schedules, rules and backups. The old server's files are kept where they are. - If it says to add the new host first, the new host is not connected yet. - If it says another server uses that folder, choose another **Game folder**. - [Add a host](https://rustsc.com/support/guides/add-host/index.html.md) - [Restore a backup](https://rustsc.com/support/guides/restore-backup/index.html.md) - [Copy a backup as a new server](https://rustsc.com/support/guides/copy-backup/index.html.md) HTML version: https://rustsc.com/support/guides/move-to-new-host/ --- # Backups on your host Make a backup, make them regular and see where they are kept. ## Back up your server 1. Open the server and choose **Backups**. If it says backups are off until you choose where they go, choose **Save** under **Backup folder** first. 2. Choose **Back up now**. The page says: Stored a backup of, with its size. 3. To make them regular, choose **Schedule local backups**. ## Local backups are yours Local backups stay on your host, in RustSC's backup folder. RustSC puts no size limit on them and never refuses one for its size. They leave out logs and old files by themselves. - [Back up a server](https://rustsc.com/support/guides/back-up-server/index.html.md) - [Free disk space](https://rustsc.com/support/guides/free-disk-space/index.html.md) HTML version: https://rustsc.com/support/guides/backups-local-and-offsite/ --- # Back up a server Choose where backups go, make one, decide how many to keep and restore one. ## Make your first backup Backups stay on the host that runs the server, in the backup folder. Keep that folder out of the game's save and plugin folders. A running server saves its world first and keeps running; that backup is marked **While running**. A backup is the server as it was at that moment, so changes made while it runs do not stop it from being complete. Each backup shows where it is kept: a host icon for the host, a cloud icon for cloud storage, or both. Point at the icon for its name. 1. Open the server and choose **Backups**. 2. If it says **Backups are off until you choose where they go**, leave **Backup folder** empty and choose **Save**. RustSC uses a backups folder in a RustSC folder next to your server folder and creates it. Or choose **Choose folder** for another place on the host. 3. Choose **Back up now** and wait for the backup to appear in the list. 4. To make them regular, choose **Schedule local backups**. ## How many to keep Under **Backup settings**, **Keep** is the most backups that stay. Every backup counts, whether you, a schedule or a start took it. Older ones are removed after each backup. The suggested number is 10. Saving a smaller number removes the extra ones at once. **Keep all backups** removes nothing, so watch the disk. A backup that did not finish is not a backup. It is not listed and does not count towards **Keep**. Turn on **Back up before every launch** to take a backup each time the server starts. If that backup fails, the server stays stopped. ## Restore one Choose **Restore** on a backup marked complete, read what will change and confirm. RustSC takes a **Before restore** backup first, so you can go back. - [Restore a backup](https://rustsc.com/support/guides/restore-backup/index.html.md) - [Backups on your host](https://rustsc.com/support/guides/backups-local-and-offsite/index.html.md) ## If something goes wrong - Nothing was stored and the page names the backup folder: choose a new backup folder in **Backup settings**. - The page says to choose a folder on this host, not a network share: pick a folder on a disk inside the host. - The page says the disk has too little free space: free space on the host or lower **Keep**, then back up again. - Backups on the host keep working while the host is not connected to RustSC. HTML version: https://rustsc.com/support/guides/back-up-server/ --- # Free disk space Remove older backups and files while keeping your current world. ## Keep fewer backups Under **Space**, **Make room when the disk is nearly full** removes older files when a backup needs room. 1. Open **Backups** and lower **Keep** under **Backup settings**. 2. Review the number before saving. Saving a smaller number removes extra backups immediately. ## Delete one backup Deleting the backup frees space on that host. If the deletion is not confirmed, check the backup list before trying again. 1. Open **Backups**, find the backup and choose **Delete** from its actions. 2. Read the confirmation, then choose **Delete backup**. It says if this is the only backup on the host that can be restored. ## Clean up old files The current world stays. If there is still too little space for a backup, its result shows how much space is needed. 1. If **Old files** appears, choose **Clean up old files**. 2. Review the files listed, then choose **Delete**. HTML version: https://rustsc.com/support/guides/free-disk-space/ --- # Restore a backup Choose a backup in RustSC and return your Rust server to the way it was when that backup was taken. ## Restore a server on your own host Restoring replaces current server files with the backup. RustSC first takes a **Before restore** backup, so you can return to the previous state. 1. Open **Backups**. Choose **Restore** on a backup marked complete. 2. Read what will change. **Show changed files** lists what will be replaced. 3. Choose the player warning and whether to start the server afterwards. Choose **Restore backup**. 4. Follow the result until the restore finishes. If you chose to start the server, check that it is **Running**. 5. With **Back up before every launch** on, you can undo the last start or restart. Under **Backups**, choose **Put back the backup from before the last restart**, under **Backup before the last restart**. It opens the same restore. If that backup did not finish, the page says so and names the newest complete one. ## Restore a rented server A world save or large file missing from the backup stays as it is. Plugins and logs are not changed. 1. Open the rented server’s **Backups**. Look for **Restore** beside the backup you want. If it is missing, ask a workspace owner to check your restore access and recheck the rented connection. Use your hosting provider’s panel if restore is unavailable. 2. Read the confirmation carefully. It says what will be replaced and whether the backup is missing a world save or large files. 3. Choose **Restore backup** and follow the result. The server stays stopped. Choose **Start** when you are ready, or start it from your host if the page cannot do it. ## Get a copy of a backup or its list of files The zip holds the server settings, including the RCON password, so keep it private. **Restore files to a folder** puts the same files in a folder on the host instead; the result names the folder. 1. To see what a backup holds, open the menu on that backup and choose **Files in this backup**. Choose **Download list** to save it as a spreadsheet file. The page shows its progress and then **Saved as** and the file name; look in your Downloads folder. **Download again** saves it a second time. 2. To take the whole backup, choose **Export or save to folder** on that backup and then **Export as zip**. The page shows **Building the zip**, then the download starts by itself. **Download again** saves it a second time. 3. If you leave the page, open **Activity** and the finished export. **Download** is on that page for 24 hours. ## If the backup cannot be restored Read the reason next to the backup. A different map, size or seed can prevent a restore. Choose a compatible backup. - [Recover a damaged save](https://rustsc.com/support/guides/recover-save/index.html.md) - [An action failed or stopped](https://rustsc.com/support/guides/action-failed/index.html.md) HTML version: https://rustsc.com/support/guides/restore-backup/ --- # Recover a damaged save Use a previous save when Rust cannot load the current one. ## Choose how to recover RustSC puts the damaged file aside before recovery. It uses the game’s older save when possible, otherwise the newest usable RustSC backup. To recover without asking next time, open the server’s **Settings**, **Restarts and recovery**, and set **When the save is damaged** to **Load the last good save**. 1. On the server page, read the recovery message and the time of the previous save. 2. Choose **Use the previous save** to recover and start the server, or **Keep it stopped**. HTML version: https://rustsc.com/support/guides/recover-save/ --- # Wipe your server Start a new map and choose which player data to reset. ## Set up and run the wipe The usual wipe makes a new random map and resets nothing else, so blueprints, player data and clans stay. It takes a backup before replacing the map, and the server starts again afterwards. Nothing wipes until you choose **Wipe now** or schedule it. On a rented server, use the scheduled wipe if offered. To wipe immediately, use your hosting provider’s panel. 1. Open **Schedules**, choose **Add schedule**, then **Wipe**. 2. Under **What to wipe**, choose **New random map**, **Choose a map** or **Keep the current map**. 3. Under **Also reset**, tick **Blueprints**, **Player data** or **Clans** if you want them reset too. 4. Set **Warn players for (minutes)**. Under **Before and after**, leave **Take a backup first** and **Start the server again afterwards** ticked unless you do not want them. 5. Open **What will happen** to check the files the wipe touches. 6. Under **When**, choose **Now**, then **Wipe now**. Confirm in the dialog. ## If something goes wrong - The page says wiping needs permission to stop and start the server too: ask a workspace owner to let you. - The wipe stopped part way: open the wipe in **Activity** to see which step stopped and why. Check **Backups** for a complete, compatible backup before restoring. - If you switched off the backup before the wipe, check **Backups** for an earlier complete, compatible backup of the old map. - [Wipe plans in plain words](https://rustsc.com/support/guides/wipe-plans/index.html.md) - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/index.html.md) HTML version: https://rustsc.com/support/guides/wipe-server/ --- # Schedule a wipe Choose the day and time your Rust server gets a new map, so each wipe happens on its own. ## Schedule the wipe To start from a wipe you set up before, choose **Add** under **Saved wipe settings** at the start of **Add schedule**. The schedule keeps the choices you save with it. Changing your wipe settings later does not update an existing schedule. A seed you enter is used for the first wipe. Later wipes use new random seeds. A server rented from a hosting company appears in the wipe list only where RustSC can wipe on its host. If it is not listed, wipe it from your provider's panel. On a supported rented server, turn on **Let RustSC change files on this server** before the scheduled wipe can run. 1. Open **Schedules**, choose **Add schedule**, then **Wipe**, and set the map and reset choices. 2. Under **When**, choose **Schedule**. Set how often, the day or date, the time and the time zone. The Force wipe day is marked in the date picker. 3. Check the choices, then choose **Schedule wipe**. ## Change a scheduled wipe On **Schedules**, open **More**, then **Earlier wipes** to see wipes that are running or coming up. Use **Edit**, **Pause**, **Resume** or **Delete** to change one. Find wipes that have already run under **Past**. To repeat a finished wipe, choose **Wipe again on a date** when offered, review its settings and choose the new date before saving. A stopped or busy server is skipped. A host that was offline does not run the wipe late. Check **History** on the Schedules page for the reason. - [Wipe plans in plain words](https://rustsc.com/support/guides/wipe-plans/index.html.md) HTML version: https://rustsc.com/support/guides/schedule-wipe/ --- # Wipe plans in plain words A wipe plan is everything one wipe does, saved so you can run it again. ## What a wipe plan holds Every extra is off until you choose it. - **What to wipe**: the map and which of Blueprints, Player data and Clans reset. - **At the wipe**: update the game first, update plugins, and clean up old logs and files left from earlier wipes. - **Files for this wipe**: plugin, settings or data files you add, and files to remove. - **When**: now, or on a date or rhythm you set. ## Use one Plugin updates at a wipe look on uMod only. A plugin from another marketplace is not updated, and you add its new file yourself. Plugin files need Oxide or Carbon on the server. A plugin that does not load after the wipe is taken out again, and the server runs without it. 1. Open **Schedules**, choose **Add schedule**, then **Wipe**. 2. Under **At the wipe**, choose what you want. **Plugin updates** offers **None**, **All** or **Selected**. Each plugin has **Hold** to keep it at its current version. 3. To add your own plugin, use **Add your own plugin**: drop one .cs file, or paste an https address and choose **Check**, then **Approve**. 4. Choose **What will happen**. It lists every file the wipe adds, removes or updates. 5. Under **When**, choose **Now** or **Schedule**. 6. After the wipe has run, find it under **Past** in **Schedules**. Choose **Wipe again on a date** or **Wipe again now** to run it again. ## If something goes wrong - A line says a file is not on this host, or a plugin was not installed: the wipe went on without it. The wipe is marked **Done with notes**; open **Past** in **Schedules** to read the note. - The file at your pasted address changed after you approved it: it is not installed, and the run says so. Check the address and approve it again. - Plugin lines say to ask a workspace owner: your role cannot add plugins or files to this server. - [Wipe your server](https://rustsc.com/support/guides/wipe-server/index.html.md) - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/index.html.md) HTML version: https://rustsc.com/support/guides/wipe-plans/ --- # Preview your map See a map before the server runs it, whether you pick a size and seed or use your own map file. ## Preview a map before a wipe If the preview says there is none for this seed yet, or that the map is still being made, try again later. A missing preview never stops you choosing a map. 1. Open **Schedules**, choose **Add schedule**, then **Wipe**. 2. Under **What to wipe**, under **Map**, choose **Choose a map**. 3. Set **Map type** to **Generated**. Enter a **World size** and a **Seed**, or leave **Seed** empty for a random one. 4. The **Preview** shows the map for that size and seed. Choose **Larger picture** to see more. 5. Choose **Shuffle** to draw another map with its own preview. Nothing changes yet. 6. Choose **Use this map** to keep the one shown, then finish the wipe as usual. ## Preview a custom map on a stopped server 1. Open the server and choose its **Map** tab. 2. While the server is stopped, a picture drawn from the map file shows with a note that the live map appears once the server runs. - This works for a custom map. A generated map has no picture until it has started. - Once the server runs, the live map replaces the picture and shows players and things on the map. - [Wipe plans in plain words](https://rustsc.com/support/guides/wipe-plans/index.html.md) - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/index.html.md) HTML version: https://rustsc.com/support/guides/preview-map/ --- # Kick, ban or unban a player Find a player on your Rust server, kick or ban them from RustSC, and lift a ban when you change your mind. ## Kick or ban a player To ban someone you have not seen, open **Bans** and choose **Add ban**. Enter their 17 digit Steam ID. A ban also disconnects a player who is online. A ban on all servers also applies to servers you add later. To keep some players out without banning them, use **Join rules** on the server's Players tab: **Allowed players only**, blocked **Countries**, and **Steam checks** for private profiles, new Steam accounts and slow connections. Steam checks need your Steam key. Open **Joins checked** to see who was let in or removed and why. Game owners and moderators are never removed. To use the same rules on every server, set them under **Players**, **Settings**, **Global**. If you can manage player links, the **Discord** column shows a linked player's Discord name when it differs from their in-game name. Choose a column heading to sort the list by it. 1. Open **Players** in the left menu. Under **Where**, keep **Global** or choose one server. 2. Search by name or Steam ID. Choose **Show**, then **Online** to see who is on now. 3. To kick, tick the player and choose **Kick** in the bar that appears. Add a reason if you like and confirm. 4. To ban, choose the ban icon on the player's line. It works for a player who is offline too. Add a reason and how long. 5. Under **Ban on**, choose **All servers** or **Only these servers**, then **Ban player**. ## Lift a ban Bans are kept by the game and stay after a restart. A server that also bans the player on its own keeps that ban, and the dialog tells you which. 1. Open **Players**, then **Bans**. Choose a server under **Where** to see its own bans. 2. Choose the lift icon on the player's line and confirm. For a ban on all servers the button is **Lift on all servers**. ## If something goes wrong - The page says to ask a workspace owner: your role cannot ban players. - The page says it cannot read a server's ban list: it needs the host connected and the server running. - A ban was not made on some servers: the page names them. Choose **Try again**. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/index.html.md) HTML version: https://rustsc.com/support/guides/manage-players/ --- # Groups and permissions Give a player or a group the permissions of your plugins, and make staff. ## Give a group a permission A change is made at once. There is nothing to apply afterwards. The **Players** view gives one player their own permissions or groups. The **Plugins** view answers who can use a plugin. **History** lists the changes and can put the earlier version back. 1. Open **Players**, then **Permissions**. With several servers, choose one. 2. Under **Groups**, open a group, or choose **Make a group** and give it a name and a title. 3. Choose **Give permissions**. Search for the plugin, tick what the group may do and choose the **Give** button. 4. To put a player in the group, choose **Add a player** and search by name or paste Steam IDs. Or open the player and tick the group in their list of groups. Untick it to take them out. 5. Read the **Last change** line. It says what was done and whether it happened live or while the server was stopped. ## Owners and moderators Staff status is not in a player's list of groups. Use the **Staff** view to set a player's in-game staff level. It shows what the level sets. ## If something goes wrong - The page says Oxide or Carbon is not installed: groups and permissions need one of them on the server. - A stopped server says to start it once to list every permission: start it, then open the picker again. You can still type a permission name. - The line says a change needs a restart to take effect: choose **Restart now to apply**, or restart later. - A change was not made: the line gives the reason. Fix that and try again. - A change went wrong: choose **Put the earlier version back**. It works until the game or someone else changes the same settings. - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/index.html.md) HTML version: https://rustsc.com/support/guides/player-permissions/ --- # Link your players to Discord Players link their Steam and Discord accounts with a code. Staff look links up with /link search. ## Set it up once The bot posts the instructions in the link channel and keeps it tidy. 1. Open **Integrations**, then **Discord**, and choose **Add the bot to Discord** in the title bar. **Home** has the same button until the bot is added. Pick your Discord server on Discord's page and allow the bot. You need Manage Server there. 2. Back on the **Discord** page, under **Player linking** and **Link channel**, choose **Create a link channel for me**, or pick a channel and choose **Use this channel**. 3. On each server, open **Software** and install the **RustSC plugin**. It needs Oxide or Carbon. 4. Optional: paste your Discord invite link and choose **Save invite link**. Players see it in the game next to their code. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/index.html.md) ## What players do A player presses **Unlink** in the panel or on **Link Status** to end the link. Leaving your Discord server also ends it. If another plugin already uses /link, choose another name under **Command players type** on the Discord page. 1. In the game chat, type /link. A small panel shows a code. 2. In Discord, open the link channel and press **Link my account**. 3. Enter the code. The panel in the game then says who they are linked to. ## Find a link with /link search In Discord, type /link search. Search by Steam ID, Steam name or Discord name, or pick a member. The answer is private to you and has an **Unlink** button. People with Manage Server can always use it. To let other people, choose roles under **Who can search links in Discord**. You can also search and unlink under **Linked players**, inside **Player linking** on the Discord page. **Sync now** there checks every link against Discord again. **Disconnect Discord** in the title bar stops the bot answering in the link channel. Players stay linked. ## Tell players when their upkeep runs low A player stops the alerts for themselves in the game with /upkeep off. 1. On the **Discord** page, find the **Upkeep alerts** card. 2. If you have more than one server, choose the **Server**. 3. Turn on **Track upkeep**. Leave **Tell players** on to let linked players know before their upkeep runs out, then choose **Save**. ## If something goes wrong - The page says the /link command could not be added: choose **Add the bot to Discord again** in the title bar of the Discord page. - Your players linked with another service before: use **Bring your old links** under **Player linking**. - The page says the link channel is gone: choose another channel. - /link does nothing in the game: check that the RustSC plugin is installed on that server and that **Let players link in the game** is on. - A player types a wrong code too often: they must wait a moment. Other players are not affected. - [Install or update the RustSC plugin](https://rustsc.com/support/guides/rustsc-plugin/index.html.md) - [Move existing Discord links](https://rustsc.com/support/guides/move-discord-links/index.html.md) HTML version: https://rustsc.com/support/guides/discord-link/ --- # Move existing Discord links Keep your players’ links when moving from another Discord service. ## Request the move Players already linked in RustSC keep their current link. Players do not need to link again, and we do not message them. If the page says it could not read the file yet, we look at it and tell you on that page. 1. Finish the Discord link setup in RustSC. 2. Export the list of linked players from your previous service. 3. Open **Integrations**, then **Discord**. Under **Player linking**, find **Bring your old links** and choose **Choose file**. 4. Check the line that says how many players are ready to link, then choose **Link them**. - [Contact support](https://app.rustsc.com/support) HTML version: https://rustsc.com/support/guides/move-discord-links/ --- # Set up alerts Get told when a server goes offline, a backup or wipe fails, or a host runs low on space. ## Choose where alerts go and which you get An alert goes only to the channels you tick. With none ticked it goes to no channel, and a channel you add later gets nothing until you tick it. Nothing needs turning on. Browsers and phones with notifications turned on receive the recommended alerts, and **Tell me** on each alert is your own choice. Phone alerts are set up in the RustSC phone app, not on this page. Turn on notifications in the app and your phone receives the alerts this page allows. CPU, memory and disk alerts are not available in the portal for Windows hosts yet. Open alerts show on the **Alerts** page with the problem and the next step. 1. Open **Alerts** in the left menu, then **Alert Destinations**. Choose **Add channel** to send alerts to a Discord channel, or add a webhook for your own tools. 2. Choose **Send test** to check it arrives. 3. Open **Alert settings**. The recommended alerts are already on for browsers and phones that have notifications turned on. 4. Change what you like, such as the level and how long a problem must last, then choose **Save changes**. 5. Under **Send to** on each alert, tick the Discord channels and webhooks it goes to. ## If something goes wrong - A Discord problem shows in the **Alerts** list while it lasts, for example RustSC can no longer post in a channel or use the link channel. It ends by itself when it works again. - The alert says the bot lacks a permission in a channel: give the bot that permission in Discord. The alert ends once it works. - The channel is not in the list, or was deleted in Discord: choose the refresh icon beside the channel list, then pick the channel again. - A channel says the bot is not in your Discord server any more: add the bot to Discord again from **Home**. - A channel shows **Needs attention** or asks you to reconnect: choose **Reconnect** and pick the channel again. - Alert settings says **Alerts are off for this workspace**: the workspace is older and never saved its alerts. Choose **Save and turn on alerts**. - You expected an alert and got none: open the notifications log under **Alerts**. It lists what was sent and what was held back. - The page says to ask a workspace owner: your role cannot change alerts. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/index.html.md) - [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/index.html.md) HTML version: https://rustsc.com/support/guides/resource-alerts/ --- # Understand workspace roles See what each role in your RustSC workspace can do, so you know what you and your team can change. ## Check your access Open Your access in the account menu to see your permissions. - Administrator: manages servers and members, except actions reserved for owners. - Operator: runs, configures, updates and backs up servers. Cannot add or remove servers, wipe maps, run console commands or manage bans. - Moderator: views servers and manages players and bans. - Viewer: views servers, hosts, backups and players without changing them. - [Manage workspace access](https://rustsc.com/support/guides/workspace-access/index.html.md) - [Give someone access to only some servers or hosts](https://rustsc.com/support/guides/limited-access/index.html.md) - [Let a moderator run a few commands](https://rustsc.com/support/guides/mod-commands/index.html.md) HTML version: https://rustsc.com/support/guides/workspace-roles/ --- # Let a moderator run a few commands Write a command with blanks once. A moderator fills in the blanks and presses Run, without the console. ## Set up a command and run it 1. As an owner or administrator, open the server and choose its **Commands** tab. 2. Choose **New command**. 3. Enter a **Name**, and if you like **What it does**. Moderators see both. 4. In **Command**, type the command and put each blank between curly brackets, for example kick {player} {reason}. Each blank appears under **Blanks**. Give it a **Label** and choose what it **Takes**: **Text** or **Digits only**, with a **Shortest** and a **Longest**. 5. Check the **Example**, make sure **Moderators can run it** is on, and choose **Save**. 6. A moderator opens the same **Commands** tab. It is one list for everyone: they choose a command, fill in the boxes and choose **Run**. 7. The result shows under the command, for example Ran the command on the server's name, with what the server replied. A long reply is cut and says Shortened. 8. In Discord, a linked member with permission can type /run, pick an enabled command and fill in the boxes. The reply comes back privately. Connect your Discord server first. ## What to expect - Moderators never see the console or the command itself, only the boxes you made. - Owners, administrators, operators and moderators on that server can run a command. A viewer cannot. - A moderator can type letters, numbers, spaces and . , _ - : @ # + ! ? in a box. Anything else is refused, and nothing is sent. - To stop moderators using a command, turn off the switch beside it. Choose **Edit** to change it or **Remove** to delete it. - Only an owner or administrator sees **New command**, the switch, **Edit** and **Remove**. ## If something goes wrong - The server is not running: start it, then run the command again. - Could not reach the server: the host is offline. Try again when it is online. - An admin changed this command: check the boxes and run it again. - You can't run commands on this server: ask an owner or administrator. - Not confirmed: check in the game before trying again. - [Understand workspace roles](https://rustsc.com/support/guides/workspace-roles/index.html.md) - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/index.html.md) HTML version: https://rustsc.com/support/guides/mod-commands/ --- # Give someone access to only some servers or hosts Invite a helper to the servers and hosts you choose, and nothing else. ## Invite someone with limited access 1. Open **Members** and choose **Invite someone**. 2. Enter their **Discord email address**. Use the email address of their Discord account. 3. Choose a **Role**. It applies to the servers you leave ticked. An Administrator has the whole workspace, so no list shows. 4. Under **Access**, everything starts ticked. Untick each server they should not use, or untick **All servers and hosts** and tick only the ones they may use. Leave a host ticked to let them see it. 5. Read the line under the list. It says what the invitation gives. Then choose **Send invitation**. It waits until at least one server or host is ticked. 6. They open the email, sign in with that address and choose **Accept invitation**. Until then it waits under **Members**, where you can withdraw it. ## Limit someone who is already a member 1. Open **Members** and choose **Access** beside their name. 2. Set **Role in the workspace** to **No role in the workspace** and give a role for each server under **Servers**. Tick the hosts they may see under **Hosts**. 3. Check the **Changes** list and choose **Save**. ## What they see Until they accept, the invitation is listed under **Invitations waiting**. Choose **Send again** or **Withdraw** there. - Only the servers you picked and the hosts you ticked. The rest of the workspace is not shown to them. - Their role decides what they can do on each server. A Moderator handles players and bans, an Operator also starts, stops and changes the server, and a Viewer only looks. - Hosts are view only. They cannot add, update or remove a host, and they do not see **Members**. - A removed server or host leaves their list. - [Understand workspace roles](https://rustsc.com/support/guides/workspace-roles/index.html.md) - [See what your team did](https://rustsc.com/support/guides/team-activity/index.html.md) HTML version: https://rustsc.com/support/guides/limited-access/ --- # See what your team did Find who started a restart, a backup or a wipe, and what came of it. ## Read the Activity page 1. Open **Activity** in the left menu. It lists everything RustSC ran or is running, newest first. 2. Use **Show** to narrow the list: **All activity**, **Unfinished**, **Failed**, **Succeeded** or **Cancelled**. 3. Use **Done by** to show actions taken with API keys. 4. Choose a row to open its **Details**. They say who started it: you, another member by name, a schedule, an automation rule or an API key. 5. Scroll to **Audit trail** for who asked for it and who approved it, with the outcome, oldest first. 6. Choose **Show older activity** to go further back. 7. On a server's overview, open a recent line and choose **Open in Activity** to jump straight to its details. ## What each person sees - Owners and administrators see everything in the workspace. - A member limited to some servers or hosts sees only what happened on those. - If the page says the audit trail is not shown, ask a workspace owner to let you see it. - [Give someone access to only some servers or hosts](https://rustsc.com/support/guides/limited-access/index.html.md) - [Understand workspace roles](https://rustsc.com/support/guides/workspace-roles/index.html.md) HTML version: https://rustsc.com/support/guides/team-activity/ --- # Get help Send a support request from the portal and attach a file if it helps. ## Send a request Replies go to the email address on your account. A request takes up to 5 files, 10 MB each and 20 MB in total. Screenshots, PDFs, logs, text, JSON and ZIP files work. 1. In the portal, choose **Help** at the bottom of the left menu. It opens **Contact support**. 2. Choose a **Topic**, then enter a **Subject** and a **Message**. Say what happened and what you were trying to do. Leave out passwords and sign-in codes. 3. To add a screenshot or a file, choose **Add files** or drop it on the page. You can also paste a screenshot into your message. 4. Choose **Send request**. The page says: Your request was received. We'll reply by email. - [Server support](https://rustsc.com/support/technical/index.html.md) ## Report a problem or suggest an idea 1. Choose **Feedback** in the portal. Select **Something is wrong** or **An idea**. 2. Describe what happened or what you would like. Add a screenshot if it helps, then choose **Send**. 3. Open **Roadmap** from the feedback window to see proposed changes. Choose **Vote** on an idea you want or remove a previous vote to choose another. ## Send a support file from your host If a host or server is not working, a support file helps most. It holds recent log lines and how each server is doing. You can open it and read it first, and nothing is sent until you attach it. Your host also sends troubleshooting information automatically to help support investigate problems. - On Linux, run the command below on the host. It saves one zip in the folder you are in and prints where. - On Windows, open RustSC on the host and choose **Save a support file**. The zip is on your Desktop. ``` sudo rustsc diagnostics bundle ``` ## If something goes wrong - The page says it could not confirm delivery: choose **Check status** before you send another. - The page says your request was not sent: your message and files are still there. Try again later. - The page says your session expired: sign in again, then send it. - A file is refused as too large or the wrong type: remove it or choose a smaller one. - [If something is not working](https://rustsc.com/support/guides/not-working/index.html.md) - [Contact support](https://app.rustsc.com/support) HTML version: https://rustsc.com/support/guides/get-help/ --- # If something is not working What to check first, how to make a support file and how to ask for help. ## Check, then ask 1. On **Add host** or **Reconnect**, open **Not showing up?** under Waiting for the host to connect. 2. Read what the terminal (Linux) or PowerShell (Windows) says. It says what stopped and what to do. On Linux, if it shows only a line that starts with curl:, the download did not start: check the host's internet connection and its date and time. Fix that, then run the same command again. A command works once: if it says it expired, use the new one on the page. 3. On Windows, open RustSC on the host. It says whether the host is connected. 4. On Linux, run the two commands below on the host. The first says what the host reports about the connection. The second saves one zip file in the folder you are in and prints where. Open the zip and read **README.txt** first. Nothing is sent. 5. In the portal, choose **Help**, then **Contact support**. Describe what happened and what you were trying to do. Do not put passwords or sign-in codes in the message. 6. Choose **Add files**, add the zip, then choose **Send request**. The page says: Your request was received. We'll reply by email. ``` rustsc status sudo rustsc diagnostics bundle ``` ## What the support file holds The support file helps support investigate host and server problems. You can read it before you send it. On Windows, open RustSC on the host and choose **Save a support file**. The zip is on your Desktop. - [Reconnect a host](https://rustsc.com/support/guides/reconnect-computer/index.html.md) - [Contact support](https://app.rustsc.com/support) HTML version: https://rustsc.com/support/guides/not-working/ --- # Host offline Restore a connection while keeping your game server running. ## Check the connection Your game and approved local schedules can keep running while the cloud is unreachable. Do not reinstall a working server to fix its cloud connection. 1. Open the host in **Hosts** and check when it was last seen. 2. Check that host’s internet connection. 3. On Windows, open RustSC on the host. On Linux, run **rustsc status** on the host. Either says whether the host is connected. 4. If the host stays disconnected, choose **Reconnect** in the portal. - [Control your server on the host](https://rustsc.com/support/guides/offline-server-control/index.html.md) - [Reconnect a host](https://rustsc.com/support/guides/reconnect-computer/index.html.md) HTML version: https://rustsc.com/support/guides/computer-offline/ --- # Server will not start Find out why your Rust server did not start, read what RustSC reports and choose the next step. ## Check the error Recovering means automatic crash recovery is trying to start the game again. Follow its result before starting another action. 1. Read the reason shown beside **Failed to start**. 2. Open the **Console** tab and look for the latest error. 3. If disk space is low, free space before starting again. 4. If RustSC reports a damaged save, use the recovery choices on the server page. - [Free disk space](https://rustsc.com/support/guides/free-disk-space/index.html.md) - [Recover a damaged save](https://rustsc.com/support/guides/recover-save/index.html.md) - [Contact support](https://app.rustsc.com/support) HTML version: https://rustsc.com/support/guides/server-will-not-start/ --- # An action failed or stopped Check what happened when an action failed or stopped, so you know whether it is safe to try again. ## Find the next step If the result is unknown, check the server before repeating the action. A lost connection does not mean the action failed. 1. Open the action’s result and read the failed stage. 2. Check which earlier steps completed. 3. Fix the reported cause, then use the recovery action offered. - [Contact support](https://app.rustsc.com/support) ## When it says Outcome unknown Outcome unknown means RustSC did not hear back, so it cannot say whether the action happened. The action says what is known and where to check. RustSC blocks conflicting actions on that server while it checks the result. 1. Open the action and read what is known and which step was not confirmed. For an action on several servers, open the affected server's result. 2. Check the server itself: its status, the console, or the folder the action touched. 3. If **Stop waiting** is offered, you can choose it and confirm to free the server for new work. The action closes as **Not confirmed**. If the answer arrives later, RustSC shows what it found. ## Before you try again Try again only after the action says it failed, or you have checked and nothing changed. If the host restarted while an action ran, what it did before then is not known. Wipes and restores change saved data. After an unknown result, look at the server before you run either one again. HTML version: https://rustsc.com/support/guides/action-failed/ --- # What a message means and what to do Plain answers behind the short notices in RustSC: what each check proved and the one next step. ## Players cannot join Choose **Check player access** on the server's Overview or under **Network ports**. Review the result and follow the next step shown. If the check does not get an answer, check that the game and query ports are open on the router and the host firewall. If it works for you but not for others, test from outside your network. ## Opening the ports Rust needs the game port and the query port as UDP, and the RCON port as TCP only if you use it from outside. **Network ports** on the server's Configuration page shows the exact numbers for your server and the command for your system. A router rule is done on the router's own page and cannot be done for you. Forward only the ports shown, not a wide range. ## The host will not connect Never connected means RustSC has not yet held a connection from that host, so run the install command on it again and check it can reach the internet. Not connected since a time means it was connected and has gone quiet: check that the host is on and RustSC is running. Your server and approved local schedules keep running either way. - [If something is not working](https://rustsc.com/support/guides/not-working/index.html.md) ## Install and update problems If the server did not finish installing, check free disk space first (a Rust server needs tens of gigabytes), then retry: the retry carries on and does not delete what finished. If an update failed, retry, then choose **Inspect files** under **Game files** on the server's Software page. It shows what differs, and **Repair** replaces only what you confirm. A plugin that is incompatible needs an update to the plugin or the framework; nothing was deleted. ## Folders and permissions A message that RustSC cannot use a folder means the server could not read or write it. Pick another folder on the host, or follow the one-line fix shown. Backups need a folder on the host itself, not a network share, and removable drives may be missing when the host starts. If a backup or restore cannot write, free space or choose another folder; nothing was changed. ## Recovery and damaged settings A damaged settings file is never replaced by defaults silently. The notice names the file, the last good copy is used when there is one, and otherwise you restore a backup. If a saved world looks corrupt, restore the newest backup from before it; RustSC does not delete or replace your world on its own. - [Recover a damaged save](https://rustsc.com/support/guides/recover-save/index.html.md) - [Contact support](https://app.rustsc.com/support) ## Some changes were made A job that says some changes were made did not finish, but part of it did. Open the job to see what was done and what was not. Check the server before deciding what to do next. If you cannot tell what happened, contact support before repeating the action. ## A part could not be read When a list or a number says it is not available, RustSC could not read it at that moment. It does not mean the list is empty or that everything is fine. Check that the host is connected, then look again. HTML version: https://rustsc.com/support/guides/fix-common-problems/ --- # Manage workspace access Find your workspace or ask for the access you need. ## Find your workspace Each workspace has its own members and permissions. Access to one does not grant access to another. 1. Sign in with the email address used for your workspace membership. 2. Choose your workspace from the workspace menu. 3. If a workspace or action is missing, ask a workspace owner to check your membership and role. - [Fix a sign-in problem](https://rustsc.com/account-recovery/index.html.md) - [Understand workspace roles](https://rustsc.com/support/guides/workspace-roles/index.html.md) ## Find a page quickly Choose the search icon at the top of the portal, or press Ctrl+K or the / key. Type a word such as ban or backup and choose a result to open that page. HTML version: https://rustsc.com/support/guides/workspace-access/ --- # Host command reference Find local and cloud commands and their installed help. ## Before you start Run these commands on the host. Add --help as shown to see the options in your installed version. Availability can vary with the host, RustSC version and server. With more than one server, commands that ask for a server need its name. The files and plugin library commands need a cloud connection and API key. Some host settings need administrator rights. ## Status - `rustsc status`: Show the host service, cloud connection and server status. ``` rustsc status --help ``` ## Another account's folders - `rustsc allow-account`: Let RustSC set up servers in the folders of another account on this host. ``` rustsc allow-account --help ``` ## Servers - `rustsc server`: List the servers this host manages, show one or its measurements, lift a crash recovery hold, or inspect and repair game files. - `rustsc server list`: List the managed servers with their process state. - `rustsc server show`: Show one server: process, desired state, crash recovery and its newest action. - `rustsc server clear-hold`: Lift a crash recovery hold without starting the server. - `rustsc server same-start`: Show whether the next restart will start the server the way it runs now. - `rustsc server recovery`: Read or change automatic crash recovery on this host. - `rustsc server helper`: Programs this host starts around a server's start. - `rustsc server previous-save`: See or answer the request to use the previous save after the game found its save damaged. - `rustsc server inspect`: Check game files for problems. - `rustsc server repair`: Check every game file and replace the ones that differ from the original. - `rustsc server change-branch`: Move the server to another Steam branch, for example staging, or back to public. - `rustsc server update-game`: Update the game to the newest build of the branch the server is on. - `rustsc server check-game-update`: Check whether a newer build of the game is out for the branch the server is on. - `rustsc server metrics`: Show the server's latest measurements. - `rustsc server recovery show`: Show the automatic recovery setting. - `rustsc server recovery set`: Change the automatic recovery setting. - `rustsc server helper list`: List the server's helpers and what happened the last times they started. - `rustsc server helper add`: Add a helper, or replace the one with the same name. - `rustsc server helper remove`: Remove a helper. - `rustsc server previous-save show`: Show what is wrong with the save and which save would be used. - `rustsc server previous-save use`: Use the previous save and start the server. - `rustsc server previous-save decline`: Leave the server stopped. ``` rustsc server --help rustsc server list --help rustsc server show --help rustsc server clear-hold --help rustsc server same-start --help rustsc server recovery --help rustsc server helper --help rustsc server previous-save --help rustsc server inspect --help rustsc server repair --help rustsc server change-branch --help rustsc server update-game --help rustsc server check-game-update --help rustsc server metrics --help rustsc server recovery show --help rustsc server recovery set --help rustsc server helper list --help rustsc server helper add --help rustsc server helper remove --help rustsc server previous-save show --help rustsc server previous-save use --help rustsc server previous-save decline --help ``` ## Start - `rustsc start`: Start a server and wait until it is ready. ``` rustsc start --help ``` ## Stop - `rustsc stop`: Save the world, then stop a server. ``` rustsc stop --help ``` ## Restart - `rustsc restart`: Save the world, stop a server, start it again and wait until it is ready. ``` rustsc restart --help ``` ## End a game - `rustsc kill`: End a server's game at once. ``` rustsc kill --help ``` ## Cancel a countdown - `rustsc cancel-countdown`: Cancel a pending stop or restart countdown. ``` rustsc cancel-countdown --help ``` ## Host Operating system update controls are for Windows and require administrator rights. - `rustsc host`: Control the host itself. - `rustsc host restart`: Restart the host's operating system: warn players on every server, save and stop them, reboot, and start them again after the boot. - `rustsc host os-updates`: Show or change how this host handles operating system updates (Windows). - `rustsc host os-updates status`: Show the choice, what happens next and the last result. - `rustsc host os-updates set`: Change the choice on this host: off, on a schedule, or after the updates become available. - `rustsc host os-updates run-now`: Install the waiting updates now and restart the host only if they need it. ``` rustsc host --help rustsc host restart --help rustsc host os-updates --help rustsc host os-updates status --help rustsc host os-updates set --help rustsc host os-updates run-now --help ``` ## Actions - `rustsc ops`: Show, follow, cancel or resolve local actions. - `rustsc ops list`: List recent actions. - `rustsc ops show`: Show one action and its result. - `rustsc ops watch`: Follow an action until it finishes. - `rustsc ops cancel`: Ask to cancel an action. - `rustsc ops stop-waiting`: Stop waiting when an action's result cannot be confirmed. - `rustsc ops resolve`: Record an action's outcome. ``` rustsc ops --help rustsc ops list --help rustsc ops show --help rustsc ops watch --help rustsc ops cancel --help rustsc ops stop-waiting --help rustsc ops resolve --help ``` ## Schedules - `rustsc schedule`: Show and manage the recurring restarts this host runs, also while the cloud is unreachable. - `rustsc schedule list`: List schedules. - `rustsc schedule show`: Show a schedule with its next and its last occurrence. - `rustsc schedule occurrences`: List the decided occurrences of a schedule, newest first. - `rustsc schedule add`: Add a recurring restart, local backup or wipe that this host runs, also while the cloud is unreachable. - `rustsc schedule enable`: Enable a schedule approved on this host. - `rustsc schedule disable`: Disable a schedule approved on this host. - `rustsc schedule remove`: Remove a schedule approved on this host. ``` rustsc schedule --help rustsc schedule list --help rustsc schedule show --help rustsc schedule occurrences --help rustsc schedule add --help rustsc schedule enable --help rustsc schedule disable --help rustsc schedule remove --help ``` ## Temporary changes - `rustsc timed-change`: Temporary changes: files put in place for a while and the originals put back. - `rustsc timed-change list`: List the temporary changes this host holds, with what each is doing now. - `rustsc timed-change show`: Show one temporary change: its state, its next start and its latest runs. - `rustsc timed-change start`: Start a temporary change now: put its saved files in place. - `rustsc timed-change end`: End a temporary change now: put the original files back. - `rustsc timed-change extend`: Move the end of a temporary change that is on later, for example: rustsc timed-change extend "PvP purge" 4h. - `rustsc timed-change pause`: Pause a temporary change on this host: its starts are skipped until you resume it here. - `rustsc timed-change resume`: Resume a temporary change on this host. - `rustsc timed-change run-again`: Run a finished temporary change again. ``` rustsc timed-change --help rustsc timed-change list --help rustsc timed-change show --help rustsc timed-change start --help rustsc timed-change end --help rustsc timed-change extend --help rustsc timed-change pause --help rustsc timed-change resume --help rustsc timed-change run-again --help ``` ## Backups - `rustsc backup`: List, create, restore or clean up local backups, and choose how many to keep. - `rustsc backup policy`: Back up before every game launch (needs a backup folder). - `rustsc backup list`: List the backups stored on this host for a server, newest first. - `rustsc backup create`: Back up a server now: a running server saves its world first and keeps running. - `rustsc backup restore`: Preview, then restore a server from one of its backups. - `rustsc backup keep`: Show how many backups a server keeps, or change it. - `rustsc backup space`: Show or change what backups do about disk space: make room when the disk is nearly full, and an optional limit on the space they use. - `rustsc backup clean-up`: Remove logs unchanged for a week from a server's folder. - `rustsc backup delete`: Delete one backup of a server. - `rustsc backup check`: Read every stored backup of a server and say whether it is intact, damaged or gone. - `rustsc backup export`: Copy a backup's files into a new folder, each one checked. - `rustsc backup files`: List the files of a backup: each file's path, size, whether it was kept, left out or could not be copied, and why. - `rustsc backup policy show`: Show the backup settings now in use. - `rustsc backup policy set`: Change the backup settings. ``` rustsc backup --help rustsc backup policy --help rustsc backup list --help rustsc backup create --help rustsc backup restore --help rustsc backup keep --help rustsc backup space --help rustsc backup clean-up --help rustsc backup delete --help rustsc backup check --help rustsc backup export --help rustsc backup files --help rustsc backup policy show --help rustsc backup policy set --help ``` ## Backup recovery keys - `rustsc custody`: Manage local repository credentials and independent recovery files. - `rustsc custody status`: Read credential status without revealing its value. - `rustsc custody provision`: Provision one protected local repository key. - `rustsc custody revoke`: Revoke one repository key. - `rustsc custody export`: Export one encrypted recovery bundle and generate its independent key file. - `rustsc custody import`: Recover one repository key from its encrypted bundle and separate key file. ``` rustsc custody --help rustsc custody status --help rustsc custody provision --help rustsc custody revoke --help rustsc custody export --help rustsc custody import --help ``` ## Steam key - `rustsc steam-key`: Your own Steam Web API key on this host. - `rustsc steam-key status`: Say whether a Steam key is set on this host. - `rustsc steam-key set`: Save your Steam key on this host. - `rustsc steam-key clear`: Forget the Steam key on this host. ``` rustsc steam-key --help rustsc steam-key status --help rustsc steam-key set --help rustsc steam-key clear --help ``` ## Framework - `rustsc framework`: Manage the server framework through the local host service. - `rustsc framework status`: Show the installed framework and available releases. - `rustsc framework preview`: Preview a framework change without downloading or changing files. - `rustsc framework change`: Apply a reviewed framework change. ``` rustsc framework --help rustsc framework status --help rustsc framework preview --help rustsc framework change --help ``` ## Ports - `rustsc endpoints`: Read, save and explicitly apply server ports. - `rustsc endpoints status`: Show the saved ports. - `rustsc endpoints refresh`: Re-read the server's ports. - `rustsc endpoints save`: Save ports without applying them. - `rustsc endpoints apply`: Apply saved ports while stopped, or with an explicit warned restart. - `rustsc endpoints firewall-open`: Add the Windows Firewall rule for this server's game and query ports (and Rust+ while it has a port). - `rustsc endpoints firewall-remove`: Remove the Windows Firewall rule RustSC added for this server. ``` rustsc endpoints --help rustsc endpoints status --help rustsc endpoints refresh --help rustsc endpoints save --help rustsc endpoints apply --help rustsc endpoints firewall-open --help rustsc endpoints firewall-remove --help ``` ## Alerts - `rustsc alerts`: Show the resource alerts this host holds open now: low disk space and, when switched on, high CPU, memory or disk use. - `rustsc alerts acknowledge`: Acknowledge an alert, with an optional comment. - `rustsc alerts unacknowledge`: Clear the acknowledgement of an alert, so it shows as not acknowledged again. ``` rustsc alerts --help rustsc alerts acknowledge --help rustsc alerts unacknowledge --help ``` ## Console - `rustsc console`: Open a server's live console: read what it prints, type commands, and search or filter it. ``` rustsc console --help ``` ## Players - `rustsc players`: List the players on the server now. ``` rustsc players --help ``` ## Bans - `rustsc bans`: List the players banned from the server, newest first. - `rustsc bans export`: Write the server's ban list as a file: a CSV (the default) or the game's own bans.cfg lines. - `rustsc bans import`: Ban the players in a file or pasted list: one Steam ID per line with an optional reason, or a file from bans export. ``` rustsc bans --help rustsc bans export --help rustsc bans import --help ``` ## Kick - `rustsc kick`: Remove a player from the server now. ``` rustsc kick --help ``` ## Ban - `rustsc ban`: Ban a player by Steam ID. ``` rustsc ban --help ``` ## Unban - `rustsc unban`: Let a banned player join the server again. ``` rustsc unban --help ``` ## Wipe - `rustsc wipe`: Wipe the server. ``` rustsc wipe --help ``` ## Files These commands need a cloud connection and an API key. - `rustsc files`: List, read, upload and change the files of a server's Oxide or Carbon folder through the RustSC cloud. - `rustsc files ls`: List a folder, for example oxide/plugins. - `rustsc files cat`: Print a text file. - `rustsc files upload`: Upload files or folders into a folder of the server. - `rustsc files rm`: Delete files or folders. - `rustsc files mv`: Move a file or folder to a new path, for example oxide/data/Pack/Kits.json. - `rustsc files cp`: Copy a file or folder to another place. - `rustsc files rename`: Give a file or folder a new name in the same folder. - `rustsc files new-file`: Make an empty file. - `rustsc files new-folder`: Make a folder. - `rustsc files restore`: Put a kept copy (name.kept-date-time) back under its own name. ``` rustsc files --help rustsc files ls --help rustsc files cat --help rustsc files upload --help rustsc files rm --help rustsc files mv --help rustsc files cp --help rustsc files rename --help rustsc files new-file --help rustsc files new-folder --help rustsc files restore --help ``` ## Plugin library These commands need a cloud connection and an API key. - `rustsc plugin-library`: The plugin library of a server's temporary changes through the RustSC cloud: list it, add plugin files, go back to the previous version, look in the inbox, and turn the automatic update and hot swap on or off. - `rustsc plugin-library ls`: List every plugin the server's temporary changes turn on, with its version, what is waiting in the inbox and the automatic update choices. - `rustsc plugin-library add`: Add plugin files to the library. - `rustsc plugin-library back`: Put the previous version of a library plugin back. - `rustsc plugin-library check`: Look in the plugin inbox folder (data/plugin-inbox) for plugin files, for example ones put there with Windows Explorer or SFTP. - `rustsc plugin-library auto`: Turn the automatic update on or off: the library takes a newer version found in the plugins folder or the inbox by itself. - `rustsc plugin-library hot-swap`: Turn the separate hot swap choice on or off: with it on, a plugin a running temporary change has on can be swapped and reloaded from the portal. - `rustsc plugin-library self-healing`: Turn on or off putting the previous version back when an update RustSC applied fails to load. - `rustsc plugin-library source`: Set or take away a plugin's GitHub update source: a repository, a releases page or a link to the plugin's .cs file. - `rustsc plugin-library check-sources`: Look at the plugins' GitHub update sources and say which have a newer version. - `rustsc plugin-library update-from-source`: Take the newer version of the named plugins from their GitHub update sources into the library. - `rustsc plugin-library timing`: Choose when an automatic update is applied: after the next wipe (the default with the automatic switch) or at once. ``` rustsc plugin-library --help rustsc plugin-library ls --help rustsc plugin-library add --help rustsc plugin-library back --help rustsc plugin-library check --help rustsc plugin-library auto --help rustsc plugin-library hot-swap --help rustsc plugin-library self-healing --help rustsc plugin-library source --help rustsc plugin-library check-sources --help rustsc plugin-library update-from-source --help rustsc plugin-library timing --help ``` ## RustSC updates - `rustsc update`: Check and install RustSC updates. - `rustsc update check`: Check for a new host version. - `rustsc update apply`: Install the newest version. - `rustsc update status`: Show how the latest update went. - `rustsc update policy`: Show or set the update policy. ``` rustsc update --help rustsc update check --help rustsc update apply --help rustsc update status --help rustsc update policy --help ``` ## Connect a host - `rustsc enroll`: Connect this host to a workspace. ``` rustsc enroll --help ``` ## Disconnect a host - `rustsc unenroll`: Disconnect this host from its workspace. ``` rustsc unenroll --help ``` ## Logs - `rustsc logs`: Show the latest lines of the RustSC logs on this host. ``` rustsc logs --help ``` ## Support file - `rustsc diagnostics`: Create a support file. - `sudo rustsc diagnostics bundle`: Save one zip file for support. ``` rustsc diagnostics --help rustsc diagnostics bundle --help ``` ## Your local account - `rustsc whoami`: Show the OS user the host service sees for this command. ``` rustsc whoami --help ``` HTML version: https://rustsc.com/support/guides/host-command-reference/ --- # Control a server on its host Use the Windows app or Linux terminal when you are at your host. ## On Windows These controls use the host directly and can work while the workspace connection is down. The RustSC service on the host must be running. **This host** shows the workspace connection and whether local control is available. If the service is not answering, the window reconnects when it returns. 1. Open RustSC on the host and choose your server under **Servers**. 2. Choose **Start**, **Stop** or **Restart** in the server header. Stop and Restart ask once and warn players first. 3. Open **Console** to read the game output and send a command. Use **Players** to see players and bans, and **Backups** to make or find a backup. ## Use the Windows console On the server's **Console** tab, enter a command and send it. The console follows new lines; scroll up to pause the view and choose **Jump to latest** to follow again. Use **Search and filters** or Ctrl+F to find text. Move between matches, change the matching options, search older lines or stop and close that search. Clear a search, save a filter to use again, or delete one you no longer need. Pause and resume the view, copy or save the shown lines, or clear this window's view. Select a line to read it in full or copy it. In the command box, use Up and Down to recall earlier commands. Press Enter to send. For selected lines, use Ctrl+C or the copy menu. In the search box, Enter goes to the next match and Shift+Enter to the previous one. Escape clears the search and closes it; if the options are open, Escape closes those first. ## Open and navigate the Windows app The RustSC icon in the notification area shows whether it is connected or needs attention. Open its menu to open the window or exit the app. Exiting the app leaves your servers running. Choose **Servers** to see the host's servers, refresh the list or open one. Choose **This host** for the workspace connection and host controls. Open the portal from the app when you want the full web view. On a new server, the ready screen offers a start, settings and port controls. The server page has **Console**, **Players**, **Backups** and **Maintenance** tabs. Notices can be dismissed; follow an offered button to fix the item it names. To connect or reconnect, open **This host** and paste the code from the portal. You can cancel and try again if a connection does not finish. Open the saved support file's folder from the same page after making one. When the app offers to restart itself after an update, use its restart button to open the updated app. ## Stop or restart from Windows On a server's page, Start acts immediately. Stop and Restart ask you to confirm; cancel the question if you change your mind. A countdown can also be cancelled while it is still waiting. Kill ends the game immediately without saving or warning players. Use it when you need to end the game at once. If a game is not answering, the app offers force controls and explains their effect before you confirm. ## Manage players on Windows Open **Players** and choose **Online** to see who is connected. Choose **Kick** or **Ban** on a player and confirm. A kick lets the player join again; a ban can be temporary or permanent. Choose **Banned** to find a ban or unban a player. Clear the search to see the list again. Use **Ban a Steam ID** to ban someone who is not online. Press Enter in a ban search to find matching bans, or Escape to clear it. Escape also closes the ban form or cancels a player action question. ## On Linux With one server, the commands below use it. With more than one server, add --server followed by the server name in quotes to start, stop or restart. For the console, put the server name after the command in quotes. Use the name from the server list. Add --help after a command to see the controls available in your installed version. The command line also works on Windows. 1. Open a terminal on the host and run the commands below to check the host and see its servers. 2. To control a server, use the commands in the next sections. Stop and restart save the world and warn players first. ``` rustsc status rustsc server list ``` - [Host offline](https://rustsc.com/support/guides/computer-offline/index.html.md) ## Start the server ``` rustsc start ``` ## Stop the server ``` rustsc stop ``` ## Restart the server ``` rustsc restart ``` ## Open the console Read the console and type commands. Press Ctrl+C to leave it. ``` rustsc console ``` HTML version: https://rustsc.com/support/guides/offline-server-control/ --- # Back up or restore on the host Make a local backup or restore one without the portal. ## On Windows A restore replaces server files and keeps a backup of the current server first. A running server warns players, saves and stops before the restore. The server starts afterwards. If Back up now is unavailable because no backup folder is set, choose a folder on this tab first. Choose **Show backups** to refresh the list. Select a backup and choose **Save as zip** to save a copy. You can also restore the backup from before the last restart. 1. Open RustSC on the host, choose your server, then open **Backups**. 2. Choose **Back up now** to make a backup. To restore, select a saved backup and choose **Restore**. 3. Read the proposed changes and choose **Restore now** if you want to proceed. ## In a terminal Run this command on the host to list backups. With more than one server, add --server and the server name in quotes. ``` rustsc backup list ``` - [Restore a backup](https://rustsc.com/support/guides/restore-backup/index.html.md) ## Make a backup in a terminal Creating a backup saves the world first while a running server stays running. Add --server and the name in quotes if the host has more than one server. ``` rustsc backup create ``` ## Restore in a terminal Read it before proceeding. The help explains how to select a backup and server. ``` rustsc backup restore --help ``` HTML version: https://rustsc.com/support/guides/host-backups/ --- # Maintain a server on its host Check game files and updates, or use the Windows maintenance controls. ## On Windows Open the server in RustSC and choose **Maintenance**. You can check for a game update, choose **Update game**, manage the Windows Firewall rule or free space. Read the update choices before confirming. An update warns players and stops the server; start it again when the update finishes. Open **This host** to check for RustSC updates, install an offered update, change **Automatic updates**, see the workspace connection or save a support file. This page also offers a host restart and shows its confirmation before it proceeds. This host also shows the Windows update choice. Change that choice in the portal. Restarting the host warns players, saves and stops its servers, then starts them after the host restarts. On **Maintenance**, check for a game update and choose what to update before confirming. To free space, check the proposed cleanup and confirm only after reading what it will remove. Add or remove the game's Windows Firewall rule there as well. ## In a terminal Check game files without changing them or stopping the server. With more than one server, add --server and the server name in quotes. ``` rustsc server inspect ``` ## Repair game files Stop the server first. Repair replaces changed game files with the originals. World, configuration and plugin data are kept. With more than one server, add --server and the name in quotes. ``` rustsc server repair ``` ## Update the game in a terminal The update warns players, saves and stops the server, and leaves it stopped. Start it when you are ready. With more than one server, add --server and the name in quotes. ``` rustsc server update-game ``` ## Check RustSC itself Use the command's help to see how to check and apply an update to RustSC on this host. ``` rustsc update --help ``` HTML version: https://rustsc.com/support/guides/host-maintenance/ --- # Schedules and activity on the host See local schedules and follow work from a terminal. ## See and change schedules Run these commands on the host to list schedules and see how to add, disable or remove one. A saved local schedule can run while the workspace connection is down. ``` rustsc schedule list rustsc schedule --help rustsc schedule add --help ``` ## Follow an action List recent actions and use the help to see how to show, follow or cancel one. Check its result before trying an action again. ``` rustsc ops list rustsc ops --help ``` HTML version: https://rustsc.com/support/guides/host-schedules-activity/ --- # Find more host commands Find the command for console, players, backups and other host tasks. ## Open command help Run these on the host to see the available commands and console options. The console can show recent lines, search saved lines, save results or send a command. It can work while the workspace connection is down. ``` rustsc --help rustsc console --help ``` ## Other tasks Use the command help for players and bans, backups, schedules, game files, framework changes, alerts and host updates. Some commands described by help may not be available in your installed version; RustSC says so when you run them. The files and plugin-library commands use the cloud and need a cloud address and an API key. They are not offline file controls. ``` rustsc players --help rustsc bans --help rustsc backup --help rustsc schedule --help rustsc server --help rustsc framework --help rustsc alerts --help rustsc update --help rustsc files --help rustsc plugin-library --help ``` HTML version: https://rustsc.com/support/guides/host-command-line/ --- # Connect and manage a rented server Connect your hosting company, check what works and fix a connection. ## Connect your server What RustSC can do depends on the host and the access your details allow. Use the host's own panel for anything that is not offered. 1. When you add a server, choose **Connect a rented server** and select your host. 2. Enter the details requested. Your host's panel has the server page, key or file login, depending on the host. Add the console details if offered and you want to send commands. 3. Choose **Check**. Read what works, then choose **Connect**. - [Find your hosting company](https://rustsc.com/hosting/index.html.md) ## Check or change the connection - Choose **Check again** on the connected server to refresh what works. If the host is not answering, check its panel and try again. - If a different key is needed, make one in your host's panel. Open the server's **Settings**, find **Connection**, enter the details again and choose **Save changes**. The saved key is not shown. - If the console is missing, use **Add console** where offered and enter the details from your host. A file login can also be added where offered. - To stop using RustSC with the server, choose **Disconnect** and confirm. RustSC forgets the saved key; the server stays with your host. HTML version: https://rustsc.com/support/guides/manage-hosted-server/ --- # Install or update the RustSC plugin Add the RustSC plugin to a server and keep it current. ## Install the plugin On a rented server, RustSC needs a working file connection to install the plugin. The page says what to do if it cannot install it. 1. Open your server and choose **Software**. 2. If the server does not have Oxide or Carbon, install one first. 3. Find **RustSC plugin** and choose **Install**. The page shows the result. ## Update or fix the plugin - When an update is available, choose **Update** in the RustSC plugin section. - To keep it current at server restarts, turn on **Update automatically at server restarts** where offered. - If the page asks you to update RustSC on the host, update it and try again. If the plugin does not answer after installation, try **Update**. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/index.html.md) HTML version: https://rustsc.com/support/guides/rustsc-plugin/ --- # Choose who can join Set join rules and ban lists, then review the decisions made for players. ## Set join rules A server can keep its own setting for a rule. Steam checks need your Steam key, and join rules need the RustSC app on the host. 1. Open **Players**, then **Settings**. Choose the server or the settings for all servers. 2. Under **Join rules**, turn on the checks you want. You can choose **Allowed players only**, countries, private profiles, new Steam accounts or slow connections where offered. 3. Enter the requested details and choose **Save join rules**, or **Save for all servers** for workspace settings. Review the affected servers before confirming. ## Choose ban lists If a list does not answer, the page says so and players are let in. Community lists and removing players need the RustSC app on the host. 1. Open **Ban lists** in the player settings. To add a community list, choose **Add a community list**, enter its name and address, then choose **Add list**. 2. For each list, choose whether to show the information or **Enforce** it. Read the confirmation before enabling enforcement, then save the choices. 3. To exempt a player from removal by ban lists, open their player page and choose **Allow anyway**. Other server bans and join rules still apply. ## See checked joins 1. Open the server's player settings and find **Joins checked** to read the decisions and reasons. HTML version: https://rustsc.com/support/guides/join-rules/ --- # Set a quiet time for alerts Pause selected alerts for a chosen time, then let them resume. ## Choose the quiet time Nothing is quiet until you save the choice. 1. Open **Schedules**, choose **Add schedule**, then **Quiet time for alerts** under **Messages and alerts**. 2. Choose where it applies, set **From** and **Until**, and select what to keep quiet about. 3. Choose **Save**. The schedule shows when the quiet time ends. 4. To change it or end it early, open its actions in **Schedules**. Switching it off keeps the quiet time but sends alerts as usual. HTML version: https://rustsc.com/support/guides/quiet-alerts/ --- # Import or download bans Bring in a list of bans or save a copy of the list. ## Import a list A global import applies to your servers, including servers added later. Rented hosts may not support it; their Bans page shows the status. Check the result for any players that could not be banned. 1. Open **Players**, then **Bans**. Choose the server or **Global bans** before importing. 2. Choose **Import bans**. Paste a list or choose a file. You can use a Steam ID list, a RustSC ban export or the game's ban file. 3. Read the count and any invalid lines. Check the chosen server or global scope, then choose the button to ban the players. ## Download the list 1. On **Bans**, choose the server or global list you need. 2. Choose **Download bans** and select a format. HTML version: https://rustsc.com/support/guides/import-bans/ --- # Schedule a message or command Send a message, run a command or post to Discord on a schedule. ## Add the schedule Nothing runs until you save. Open **History** on **Schedules** to see what happened if a run was skipped or failed. 1. Open **Schedules** and choose **Add schedule**. 2. Under **Messages and alerts**, choose **Send a message**, **Run a command** or **Post to Discord**. 3. Choose the server, enter the message or command, and set when it should run. For a Discord post, choose the channel offered by the form. 4. Review your choices and choose **Save**. Check the next run in the list. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/index.html.md) - [Connect Discord](https://rustsc.com/support/guides/discord-link/index.html.md) HTML version: https://rustsc.com/support/guides/schedule-messages-commands/ --- # Connect Discord chat and roles Choose how your server shares chat and linked player roles with Discord. ## Show server status in Discord Each server has its own settings. The player list and change posts stay off until you turn them on. 1. Open **Integrations**, then **Discord**. Under **Status board**, choose the server and open its settings. 2. Choose the Discord channel for the board. Choose whether to show the player list and send posts when the server changes. 3. Save your choices. Send a test post and check the channel in Discord. ## Set up chat relay Chat must be recorded for the server. Team and clan chat are not posted to Discord. The page says if a direction is unavailable. Choose who can talk from Discord and any muted players in the relay settings. You can choose how messages look and review the preview before saving. 1. Connect your Discord server and the RustSC plugin first. Open **Integrations**, then **Discord**. 2. Under **Chat relay**, choose the server and open its settings. Turn on the relay and choose a **Chat channel**. 3. Choose whether game chat goes to Discord and whether Discord messages go to game chat. Save your choices and use **Send test** to check the channel. ## Give linked players a role To add linked players to a Rust group, choose **Also add to a Rust group** and follow the choices. To use linked players' Steam names as Discord nicknames, use **Discord nicknames** on the same page. 1. On the **Discord** page, open **Role rewards** and choose **Give a role**. 2. Choose who gets the role and the **Discord role**. For boosters, choose how long to keep it after a boost ends. 3. Choose **Give this role**. Players who already had the role keep it. 4. To stop giving it, choose **Remove** and decide whether to take back roles RustSC gave or leave them in place. ## Sync a Discord role and Rust group To remove a sync, choose **Remove** and decide whether to take away what it added or leave it in place. 1. On the **Discord** page, open **Role sync** and choose **Add a sync**. 2. Choose the Discord role, Rust group, server and which way changes should go. Review the choices for removing access before continuing. 3. Choose **Start the sync**. Only linked players are changed. - [Link players to Discord](https://rustsc.com/support/guides/discord-link/index.html.md) - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/index.html.md) HTML version: https://rustsc.com/support/guides/discord-chat-roles/ --- # Find and save console lines and commands Search the console, save a command and watch for words. ## Search and filter 1. Open the server's **Console** and choose **Search and filter**. Enter words in **Search** and use the next and previous controls to move between matches. 2. Use **Filter lines** to show or hide matching lines, or **Highlight lines** to colour matches. These rules stay in this browser. 3. Choose **Pause** while you read and **Resume** to return to new lines. Use the console actions to copy or download the lines shown. 4. Choose **Search older lines** to search the lines saved on the host. ## Save a command Choosing a saved command does not run it. 1. Type a command in the console and choose **Save this command**. Give it a name and choose **Save**. 2. Next time, choose it under **Saved commands**. Check it and fill in any values before choosing **Run**. ## Watch for words Watch words stay in this browser and work while the console is open. Use an event rule when you need an alert without leaving the console open. 1. Open **Watch words**, enter a word or phrase and choose **Add**. 2. Choose whether to play a sound, show a tab count or use browser notifications. HTML version: https://rustsc.com/support/guides/console-tools/ --- # Help a player in game Use the player menu to heal, move, message or give items. ## Choose an action These actions need the RustSC plugin. Some need the player to be online; the page says when an action is unavailable. 1. Open **Players**, find the player and open their player menu. 2. Choose **Heal**, **Give items...**, **Move...** or **Message...**. Fill in the requested details and check them before confirming. 3. Read the result before repeating an action. If the player or server is unavailable, the page says what to do next. - [View a player](https://rustsc.com/support/guides/player-details/index.html.md) - [Manage players](https://rustsc.com/support/guides/manage-players/index.html.md) ## Act on several players 1. On **Players**, select the players you want to change. 2. Use the selection bar to **Kick**, **Ban...**, add a label or add them to a group. Review the action and confirm where asked. 3. Read the result. If only some players were changed, check who was left out before trying again. ## Inspect and change a player Removing items or what a player built cannot be undone. A backup can help you recover the server if needed. Available actions depend on the player, server and plugin. 1. Open the player's full page. Under **What they carry**, choose **Look** to read the inventory. Look again before removing an item, then review and confirm the removal. 2. Under **Health, food and water**, enter the values you want to change and choose **Set**. Leave other values empty. 3. Use **Mute chat**, **Freeze** or **Release** where offered, and read the confirmation and result. 4. Under **What this player built**, refresh the count. To remove it, choose **Remove everything this player built**, read the confirmation and confirm only if you want to proceed. HTML version: https://rustsc.com/support/guides/player-actions/ --- # Schedule a host restart Choose when your host and its servers restart on a schedule. ## Add the restart This restarts the host and its servers. Nothing is scheduled until you save. 1. Open **Schedules** and choose **Add schedule**. 2. Under **Host**, choose **Restart the host** and select the host. 3. Choose when it runs and review the settings, then choose **Save**. 4. Check the next run in **Schedules**. Use the schedule's actions to change or remove it. - [Schedule a server restart or update](https://rustsc.com/support/guides/schedule-tasks/index.html.md) HTML version: https://rustsc.com/support/guides/schedule-host-restart/ --- # Schedule a temporary change Put files or plugins in place for a while and choose when the change ends. ## Set up the change Nothing runs before you save. Open its files from the schedule to see what is ready to use. If you copy it to another server, the copy starts paused so you can review its times before turning it on. 1. Open **Schedules**, choose **Add schedule**, then **Temporary change**. 2. Choose the server, name the change and choose when it starts and ends. 3. Add the files or plugin changes you want and review the choices on the page. A change set to start now starts when you save it. 4. Save the change. Check its next run and whether it is switched on in **Schedules**. - [Work with server files](https://rustsc.com/support/guides/manage-files/index.html.md) - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/index.html.md) ## Change the time If Extend is unavailable, leave the current end in place and edit the next run. A change ending with a wipe or restart cannot be extended. If a rented server's change is waiting, read its status before taking another action; the available choices depend on the host. 1. Open **Schedules**, find the temporary change and choose **Edit**. Change its timing and save. 2. If it is already on, the edited choices apply the next time it starts. To keep the current change on longer, open the active change’s actions menu and choose **Extend** if offered. Pick the new end and confirm. HTML version: https://rustsc.com/support/guides/temporary-changes/ --- # Copy a backup as a new server Make a separate server from a backup and start it when you are ready. ## Make the copy The original server and its backups stay as they are. The new server stays stopped until you start it. Rust+ pairing, logs and files from earlier wipes are not copied. If the copy does not finish, open its details to see the step and reason before trying again. 1. Open your server's **Backups** and find the backup you want. 2. Choose **Copy as new server** from its actions. 3. Enter the name of the new server and check what will be copied. 4. Choose **Make the copy**. Follow its progress and open the new server when it is ready. - [Restore a backup](https://rustsc.com/support/guides/restore-backup/index.html.md) HTML version: https://rustsc.com/support/guides/copy-backup/ --- # See player and server stats See who played and how busy your server has been over a chosen period. ## Choose a period The figures use players RustSC has seen since it first saw each server. A plus sign beside an earlier wipe means RustSC saw only part of it. 1. Open **Players** and choose **Stats**. 2. Choose the server or view your servers together, then choose a **Period**. 3. Read the records, figures and busy hours for that choice. An info button explains each figure. - [Manage players](https://rustsc.com/support/guides/manage-players/index.html.md) HTML version: https://rustsc.com/support/guides/player-stats/ --- # View a player and take action Open a player's history, notes and available actions. ## Open a player Some actions need the RustSC plugin, and some need the player to be online. The menu says when an action is unavailable. Labels and notes are private to your team. 1. Open **Players** and select a player to see their details. 2. Choose **Open full page** to see the full page. If the player has visited several servers, choose a server there. 3. Read their history and any notes or labels your team has added. Open the player menu to see the actions you can take. - [Manage players](https://rustsc.com/support/guides/manage-players/index.html.md) - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/index.html.md) HTML version: https://rustsc.com/support/guides/player-details/ --- # Use the live map See players and events on your server's map and choose what it shows. ## Open the map The live map needs a running server and the RustSC plugin. A rented server shows the world information available from its host. If the map is unavailable, the page tells you what to check. 1. Open your server and choose **Map**. 2. Choose **Layers** to show the things you want to see. Drag the map to move around and use the zoom controls to change the view. 3. Select a marker or use **World tools** to find or count things on the server. - [Change Oxide or Carbon](https://rustsc.com/support/guides/change-framework/index.html.md) HTML version: https://rustsc.com/support/guides/live-map/ --- # Read server events and chat Find a recorded server event, search public chat or download a copy. ## Find an event If recording is switched off, the page offers **Choose what is recorded**. Nothing starts recording until you change the settings. 1. Open your server and choose **Events**. 2. Choose what to show or search public chat. Choose **Show older events** to read further back. 3. Use the download action if you need a copy of the events. HTML version: https://rustsc.com/support/guides/server-events/ --- # Work with server files Find, upload and change files for a server from the Files tab. ## Open the files If the connection is lost while a change is being checked, look in the folder before trying again. Some actions may not be available on a rented host. 1. Open your server and choose **Files**. Open a folder to see its contents. 2. Choose **New** to make a file or folder, or **Upload files** to add files from your device. 3. Select an item to see the actions available for it. You can rename, move or delete items where your host supports those actions. 4. Read the confirmation before deleting. It tells you whether the change can be undone. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/index.html.md) ## Edit a file When offered, **Put the earlier version back** restores the earlier file. Read the result after using it. 1. In **Files**, open the text file and make your changes. 2. Choose **Save**, review the changes and confirm. The result says whether a plugin reloaded or will use them later. 3. If the page says the file changed since you opened it, nothing was saved. Refresh it, check the other change and make your edit again. HTML version: https://rustsc.com/support/guides/manage-files/ --- # Choose where alerts go Choose the alerts you need and where you receive them. ## Set up alerts Alerts do not turn on until you save your choices. 1. Open **Alerts** and choose **Alert settings**. 2. Choose the alerts you want and save your changes. 3. To send alerts to Discord, add a channel under **Alert Destinations** and choose it in the alert settings. You can send a test to check the channel. 4. For browser notifications, open **Alert Destinations**, then **Browser notifications**. Under **This browser**, choose **Turn on notifications** and allow them in your browser. 5. In **Alert settings**, use **Tell me** on each alert to choose what reaches your own devices. - [Link Discord](https://rustsc.com/support/guides/discord-link/index.html.md) HTML version: https://rustsc.com/support/guides/alert-destinations/ --- # Manage several servers at once Send a message, change access or copy settings to a group of servers. ## Preview and apply a change **Cancel what has not started** leaves completed changes in place. If a result is unknown, check that server before sending another change. 1. Open **Servers**, then **Bulk actions**. Choose the action and enter its details. 2. Select the servers or a saved group. To reuse a selection later, choose **Save group** and give it a name. 3. Choose how the servers start, then choose **See what will happen**. Check the names and read the result for each server. 4. Confirm only the servers you intend to change. Open **Results** to see which finished, which are waiting and which need attention. ## Copy settings between servers 1. Use **Settings profiles** to create a profile with the settings you want to copy. Saving the profile changes no server. 2. In **Bulk actions**, choose **Settings**, select the profile and the target servers, and preview the changes. 3. Check which values each server will keep before confirming. If you need to undo a completed settings change, choose **Put the old settings back** where offered and check its preview. ## Compare servers or a group A server with no reading can make the total player count dip. Check its last report before acting on a change. 1. In **Bulk actions**, choose **See players and frame rate of all servers**, or **See this group together** for a group. 2. Choose a period. Check how many servers reported, then open a server’s performance for a closer look. HTML version: https://rustsc.com/support/guides/bulk-actions/ --- # Review F7 reports and find events Find a player's report, check what happened and record your team's decision. ## Respond to a report **Delete report** permanently removes that report, its notes and history. Closing it keeps the record. 1. Open **F7 Reports** from the server’s **Events** tab or use the portal search. Filter to **To do**, or search by name, Steam ID or words in the report. 2. Open the report. Check the message, any picture and **Around this report**. Choose **Pick up** to let your team know you are handling it. 3. Use **Add comment** for a note only your team can see. Choose **Close report** when finished. A closed report can be reopened. ## Find or download events A gap means part of the history is missing. Check the server’s recording settings if you expected more events. 1. Choose **Find events** from the reports page. Search by Steam ID or words from an announcement. Use **Filter** to narrow the results by event type. 2. Open an event for details. Use **Download** where offered to save the results you can read. ## Choose what gets recorded 1. Open the server’s **Settings**, then **Recording**. Turn on **Public chat** or **F7 reports** and save your changes. If F7 reports need the RustSC plugin, install it from **Software**. 2. To stop collecting new events, turn off recording. To clear existing events, find **Recorded events** and choose **Delete…**. Review what will be removed before confirming. F7 reports and previously downloaded copies stay available separately. HTML version: https://rustsc.com/support/guides/review-player-reports/ --- # Check a host’s performance and logs Find a busy host, investigate a game exit or save the log lines you need. ## Check what is busy When a host is offline, the page can show earlier readings. A hosting panel may have no host measurements to show. 1. Open **Hosts**, select your host and choose **Performance**. Check when it last reported. 2. Check processor, memory and disk use for the host. Compare the readings for each game server to see which one needs a closer look. ## Find out why a server stopped 1. On the host, open **Logs**. Under **Game exits**, find the server and the time it stopped. 2. In **Log lines**, choose **Warnings and errors** or search for words in the message. Choose **Show older lines** if needed. 3. Use **Copy these lines** or **Download these lines** to keep the result. - [Set up resource alerts](https://rustsc.com/support/guides/resource-alerts/index.html.md) HTML version: https://rustsc.com/support/guides/host-performance-and-logs/ --- # Remove a host from RustSC Disconnect a host and choose what happens to the servers listed in your workspace. ## Disconnect the host For a server connected through a hosting company's panel, use its connection settings to disconnect it. 1. Open **Hosts**, choose the host, open **Settings** and select **Remove host**. 2. Check the host name. Removing the listed servers ends their schedules. Choose **Keep them listed** if you want their records when you move them to another host. 3. To remove the RustSC software too, select **Also uninstall RustSC from this host** if offered. An offline host shows local uninstall instructions. 4. Confirm your choice. The host can no longer connect. Games keep running, and their folders and saves stay on the host. - [Disconnect a hosting provider](https://rustsc.com/support/guides/manage-hosted-server/#fix) - [Move a server to a new host](https://rustsc.com/support/guides/move-to-new-host/index.html.md) HTML version: https://rustsc.com/support/guides/remove-host/ --- # Find and select servers in a workspace Use Home or the Servers list to find the servers you manage. ## Find the server you want Open **Home** for an overview of the workspace's servers and hosts. Open **Servers** to search the list, filter by status or sort the results. Choose the server's name to open it. To start, stop, restart or update several servers where offered, select them in the list and choose the action. Review which servers will run the action and which will be skipped. After you confirm, check **Activity** for the results. HTML version: https://rustsc.com/support/guides/find-a-server-in-your-workspace/ --- # Announce or recover a temporary change Tell players when a change starts or ends and check what happened to its files. ## Tell players when a change starts or ends Open **Schedules**, add or edit the temporary change and find **Tell players**. Enter optional messages under **When it starts** and **When it ends**, then save. RustSC says each message in game chat at that point if the server is running. ## Check a run or put files back If a start was undone, read the reason before starting again. If you edited a temporary file while the change ran, check the history for the copy RustSC kept. 1. Open **Schedules**, then **Past**, or choose **History** from the temporary change's menu when offered. Find the run by time and read its result. 2. Use **Roll back** where offered on the change that is on, and review what will be put back. Use **Roll forward** where offered to run the same saved change again. 3. To end a change that is still on, choose **End now** and review the confirmation. If the status says it could not turn off yet, RustSC is still trying. Check the result and which files were put back before changing them yourself. HTML version: https://rustsc.com/support/guides/temporary-change-messages-and-recovery/ --- # Use a link to a custom map Give Rust and your players an address that downloads the map file. ## Share and check the map file 1. Share the map file so anyone with the link can download it. Use a link to the file itself. A link to a folder won't work. 2. In the map picker for a new server or a wipe, choose **Custom** and paste the link into **Map address**. RustSC turns supported Dropbox and Google Drive file share links into download addresses. 3. Check the address RustSC shows. If it finds a web page instead of the map, use a direct download link. Keep the file available at that address so players can join. - [Preview your map](https://rustsc.com/support/guides/preview-map/index.html.md) HTML version: https://rustsc.com/support/guides/use-a-custom-map-link/ --- # Plan a map rotation for wipes Choose the maps a saved wipe uses and what happens at the end of the list. ## Choose the list and its order Each wipe uses the next map in the list in order. 1. Open **Schedules**, then **Add schedule**, then **Wipe**, then choose **Rotate through a list of maps** under **What to wipe**. 2. Choose **Add a map**, pick the map and choose **Add to rotation**. Put the maps in the order you want and check which is marked **Next wipe**. - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/index.html.md) HTML version: https://rustsc.com/support/guides/plan-a-map-rotation/ --- # Review startup and performance settings Check what starts your server or change how it uses the host's processors. ## Review the next start In **Configuration**, find **Launch arguments**. Review the **Command line** preview before saving **Startup options** or **Extra arguments**. These choices apply at the next start. Applying extra arguments requires permission to run console commands. ## Change how much of the host the game uses In Configuration, find **Game priority** and **Processors** under **Performance**. Review the choices and use the page's save controls when you have a reason to change them. HTML version: https://rustsc.com/support/guides/advanced-game-settings/ --- # Get alerts for words in chat or console Watch for a word or phrase on the servers you choose. ## Add a word to an alert Chat words match public chat and require chat recording on the server. For a sound on an open console in this browser, use **Words in the console** instead of a workspace alert. 1. Open **Alerts**, then **Alert settings**. Find **A chat word is said** or **A console word appears**, then choose **Edit words** or **Edit console words**. 2. Choose **Add a word**, enter a word or phrase and pick **Whole word** or **Anywhere inside**. Console words also offer **Pattern**. Choose the servers, then **Save word**. 3. Switch on the alert and choose where it goes in **Alert settings**. Check that the individual word is on too. - [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/index.html.md) HTML version: https://rustsc.com/support/guides/watch-chat-and-console-words/ --- # Install a plugin from a link or a file Check a plugin link before installing it, or upload a plugin file you already have. ## Check and install from a link 1. Open **Plugins**, then **Add plugin**. In **Find plugins**, open **More ways to add**, then **Add by address**. 2. Paste the plugin's marketplace page, a direct link to its .cs file or a GitHub release address. Choose **Look up** and check the listing or file it finds. 3. Choose **Install** if offered. For marketplace results, review **Needs** for required plugins. If RustSC cannot install a required plugin, add it first and try again. ## Upload a plugin file If you already have the .cs file, open **Files** on the server and upload it to the plugins folder used by Oxide or Carbon. If the download came in an archive, unpack it first. On a rented server, this depends on its file access. Use your host's panel if the upload is unavailable. - [Work with server files](https://rustsc.com/support/guides/manage-files/index.html.md) HTML version: https://rustsc.com/support/guides/install-plugin-from-a-link/ --- # Choose a plugin update source and go back if needed Check which version you are installing and put the previous plugin file back when needed. ## Choose a source and update For a wipe, choose **All** or **Selected** under **Plugin updates** and use **Hold** for a plugin you want to keep at its current version. Wipe updates use uMod. To bring a different file, add it under **Files for this wipe**. 1. On your server's **Plugins** tab, open the plugin's row menu. Under **Marketplace**, choose the listing you want to follow. Use **Plugin page** if you have the marketplace page for this plugin. 2. Choose **Check for updates** on the list. When **Update** is offered, check the version and source in the confirmation before proceeding. 3. Use **My own version** to keep your own file. **Keep this plugin up to date** saves a preference. To install an available update, choose **Update**. - [Wipe plans in plain words](https://rustsc.com/support/guides/wipe-plans/index.html.md) ## Put the previous plugin file back 1. After an update, choose **Roll back** where offered and confirm. RustSC puts the previous file back and reloads it. Use **Roll forward** if you want the updated file back again. 2. Read the result before retrying. If someone changed the file since the update, RustSC leaves that version in place. Check the plugin files and decide which version to keep. HTML version: https://rustsc.com/support/guides/plugin-update-source-and-recovery/ --- # Edit a plugin's settings and messages Open a plugin's files, review a change and see when it takes effect. ## Change a settings file If your rented server exposes its plugin files, open **Files** to edit them there. Read the save result to see when the plugin will use your changes. 1. Open the server's **Plugins** tab. Open the plugin's row menu and choose **Settings**, then choose **Edit** beside a file in **Settings files**. 2. Make your changes and fix any errors shown in the editor. Choose **Save** and review which lines will change. Choose **Reload** in the confirmation if offered and you want the plugin to use the change now, then confirm the save. 3. Check the result. If the file changed while you had it open, refresh it and make your edit again. Use **Put the earlier version back** where offered to undo a save. ## Translate a plugin's messages 1. On the plugin's own page, choose **Languages**. Open a language to edit it, or enter a language code under **Add a language** and choose **Add language**. A new language starts with the English messages. 2. Keep any placeholders in the original message when translating and save the file. The editor names a message if a placeholder is missing or changed. ## Find the plugin's commands or permissions Open **Commands** on the plugin's page to search and copy its registered console commands when the server and plugin are running. Use the **Permissions** link to see what groups and players can do with the plugin. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/index.html.md) HTML version: https://rustsc.com/support/guides/edit-plugin-settings-and-language/ --- # Import or download server settings Review settings from a file before applying them to a server. ## Import from a file An import leaves the server name, ports, RCON password, Nexus and map out. Importing a file adds changes for review. Nothing changes on the server until you apply them. 1. Open your server's **Configuration** tab and open **More configuration actions**. 2. Choose **Import from a file** and select a server.cfg or JSON settings file. Check the changes and any entries RustSC could not read. 3. Choose **Save** to keep the changes for later or **Save and apply** when offered to send them to the server. Check the result for settings that need a restart. ## Download your settings In **More configuration actions**, choose **Download server.cfg** or **Download settings as JSON**. These files hold settings. To save the world and plugin data as well, make a server backup. - [Back up a server](https://rustsc.com/support/guides/back-up-server/index.html.md) - [Review settings changed outside RustSC](https://rustsc.com/support/guides/review-server-setting-changes/index.html.md) HTML version: https://rustsc.com/support/guides/import-server-settings/ --- # Review settings changed outside RustSC Decide whether to keep the server's setting or the value you saved in RustSC. ## Choose which values to keep When another tool runs the server, Configuration shows what RustSC can read. Change the settings in that tool. If a setting says the server's start script sets it, change that value in the script so it stays in effect after startup. 1. Open the server's **Configuration** tab. On a setting that differs, compare **On the server** with **RustSC**. 2. Choose **Use the server's** to save the value the server has, or **Use RustSC's** to send the saved value to the server. 3. If several settings differ and **Sync** is offered, open it, choose **Use server settings** or **Use RustSC settings**, and review **Values that change** before pressing **Sync**. - [Change server settings](https://rustsc.com/support/guides/server-settings/index.html.md) HTML version: https://rustsc.com/support/guides/review-server-setting-changes/ --- # Change the ports players use to join Change a server's ports and check which ones are in use. ## Save and apply ports Check the ports marked **In use**. If RustSC says a new port did not open, check the console and use **Check again**. The RCON port on your own host is for RustSC's local management. For a rented server, change its ports in your host's panel. If another tool runs a server on your own host, change its ports in that tool. 1. Open your server's **Configuration** tab and find **Ports**. The **Game port** is where players join. The server browser uses the **Query port**. Set a different number for each. 2. Choose **Save and apply** to use the new ports, or **Save** to keep them until you can choose **Apply saved settings**. 3. For a running server, review the warning and confirm **Restart on new ports**. A stopped server uses the new ports at its next start after you apply them. 4. Allow and forward the new game and query ports where your firewall or router needs it. Both use UDP. Give players the new game port and test joining from outside your network. ## Check the firewall and console access Under **Ports**, open **Firewall and port forwarding**. If **Open the ports for me** is offered, review the game and query ports before using it. Use your router's controls for forwarding. Workspace owners can show or change the **RCON password** and review **RCON access** where Configuration offers them. Keep **This host only** for tools on that host. Change a rented server's password in its hosting panel. HTML version: https://rustsc.com/support/guides/change-server-ports/ --- # Save Nexus network settings for a server Use a Nexus key you already have to set up a server's next start. ## Choose a Nexus network You need a key for an existing Facepunch Nexus network. Saving one in RustSC prepares the server's settings. You can check whether the game connects after it starts. 1. Open **Configuration** on the server. Find **Nexus network** in the advanced settings, or search for it using **Search settings**. 2. Choose a saved network, or choose **New network...** and enter a **Network name** and your **Nexus key**. Fill in **Network options** if your network needs them, then choose **Save network**. 3. Save and apply the server settings. Nexus settings take effect at the server's next start. Repeat the selection on each server you want to use with that network. ## Change or remove a saved network Use **Edit network** to change a network, then apply the updated settings on each server using it. To delete a network, first save another network or **None** on every server using it. Select the unused network in the form, choose **Delete network** and confirm. HTML version: https://rustsc.com/support/guides/save-nexus-network-settings/ --- # Find and inspect things on the live map Find entities by name, owner or location, then inspect or count them. ## Locate and inspect an item Map tools are available to workspace members with map access. Inspect shows lock information where available and keeps the lock code private. 1. Open the server's **Map**, choose **World tools**, then **Find things**. 2. Choose a type or enter a name. To narrow it further, use the owner's Steam ID or search near a spot. For a spot, supply east, north and radius together. 3. Choose **Find**, then **Inspect** on a result. Check its location, owner, or contents where available. For totals by type, go to **World tools**, then **Counts** and choose **Count**. - [Use the live map](https://rustsc.com/support/guides/live-map/index.html.md) ## Remove a thing or building These removals take any contents with them and cannot be undone through the map. If some building parts stayed, inspect the building again before deciding what to do next. 1. Inspect the item and check its name and location. If **Remove** is offered, read the confirmation before removing it. 2. For a building, use **Inspect building** where offered. Check which parts and contents would go before choosing **Yes, remove the building**. ## See what a player built In **Players**, open the player's details and look for **What this player built** in the overview. Choose **Refresh** for a new count. It counts the things that player owns, including while they are offline. HTML version: https://rustsc.com/support/guides/find-things-on-the-map/ --- # Keep player permissions the same across servers Preview and share permissions between the servers you choose. ## Check the changes and turn on sync Sync leaves staff status, the admin and moderator groups, starting groups and groups managed by Discord with each server. Turning sync off leaves each server's current permissions in place. 1. Open **Players**, then **Permissions** for the workspace. Find **Keep permissions the same** when at least two servers are visible. 2. Pick the servers you want to sync and choose **Check what will change**. Read the additions for each server before choosing **Turn on sync**. 3. To make a change for the whole set, open a group under **Groups on all these servers**. Review **Waiting to apply** and choose **Apply to** with the named server count. Use **Check now** to check the result. - [Groups and permissions on one server](https://rustsc.com/support/guides/player-permissions/index.html.md) ## Resume a paused sync If **Keep permissions the same** shows a pause, read which server or group needs attention. Use **Check what Resume will send** where offered, review the changes and choose **Resume sync** when ready. ## Save or reuse a server's permission groups In **Players**, then **Permissions**, choose a server and open **Saved lists**. Give the server's groups a name to keep them, or select a saved list and review it before applying it to that server. ## Let one group inherit another's permissions In **Players**, then **Permissions**, choose the server and open a group under **Groups**. Edit it and use **Gets everything from** to choose the parent group. Choose **No group** to remove the inheritance. Only the workspace owner can grant permissions marked as needing an owner. ## Keep staff roles through a ban or wipe When banning a game owner or moderator on one server, leave **Give the owner role back when the ban ends** or its moderator equivalent selected if you want RustSC to restore the role when the ban ends or is lifted. A standard RustSC wipe on a host you control keeps the game's staff list and the framework's permissions. Review **What will happen** for the files and plugin data you chose to reset. Save a permission list or make a backup when you need a separate copy. ## Send the same permission changes from a script Use the customer API to preview a list of changes for servers using the same framework. Choose the files option for stopped servers or the console option for running servers. Set in-game staff levels separately on each server. Replace the server and player values in this example with the ones you want. Review the preview for each server before applying the bulk plan. Read the bulk plan again for the result from each server. ``` { "kind": "player.permissions", "serverIds": ["", ""], "parameters": { "framework": "oxide", "route": "files", "operations": [ { "kind": "user.group.add", "user": "", "group": "vip" } ] } } ``` HTML version: https://rustsc.com/support/guides/sync-player-permissions/ --- # Make a rule that responds to a server event Send a message or alert automatically when something happens on a server. ## Choose an event and a response The events and responses depend on the server. If your workspace cannot make rules, the section shows why. 1. Open **Schedules** for the server. In **When something happens**, choose **Add a rule**. 2. Under **When**, pick an event, such as when the server finishes starting. Under **Then**, pick an available response and enter the message. 3. Read **What will happen**. Leave **Turn it on now** selected if the rule should start listening when you save, or clear it to keep the rule off. Choose **Save rule**. ## Read the result or pause the rule Check **Latest result** on the rule. Use **What it did** in its menu to see earlier runs. Switch **On** off to pause it, or choose **Edit rule** where offered. If the host has not taken the change yet, wait for it to connect and check again. A chat rule marked **Runs on the server's host** can still say its message after the host loses its RustSC connection. Alert and Discord responses need the RustSC connection. - [Read server events and chat](https://rustsc.com/support/guides/server-events/index.html.md) HTML version: https://rustsc.com/support/guides/make-a-server-event-rule/ --- # Manage your sign-in and security Add or remove a sign-in method, see where you are signed in and end a sign-in. ## Add or change a way to sign in Keep another working sign-in method before removing one. If your workspace limits how you can sign in, make sure the method you keep is allowed there. 1. Open your account menu and choose **Sign-in and security**. 2. Under **Passkeys**, choose **Add a passkey** and follow your browser or device prompt. Use the passkey's menu to rename or remove it. 3. Under **Sign-in accounts**, choose an account the page offers and follow the provider's sign-in. Back in RustSC, check that the account is listed as linked. ## Review or end a sign-in 1. Find the other device or browser in the sign-in list. Choose its **Sign out** action to end just that sign-in. 2. Choose **Sign out everywhere** and confirm if you want to end all your sign-ins. This signs you out here as well. 3. Read **Recent sign-in activity** for changes to your account and sign-ins you do not recognise. - [Get help signing in](https://rustsc.com/account-recovery/index.html.md) HTML version: https://rustsc.com/support/guides/account-sign-in-security/ --- # Download your data or delete your account Export your account data and review what happens to workspaces before deleting your account. ## Download a copy 1. Open your account menu and choose **Your account**. 2. Under **Your data**, choose **Download a copy of my data**. The copy includes your account and the settings, members, servers, schedules and activity of workspaces you own. Passwords and keys are left out. ## Change your chat name or email preference 1. If you own or administer the workspace, open **Chat identity** in **Your account** to change your chat name there. You can use a different name in each workspace. 2. Use **Product updates and news by email** to choose whether to get those messages. ## Review account deletion 1. On **Your account**, find **Delete your account**. If you are the only owner of a workspace with other members, follow the link to **Members** and hand it over first. 2. Choose **Delete my account**. Read what will happen to each workspace before confirming. 3. If you change your mind and the request is still pending, choose **Keep my account** when it appears. - [Hand over or close a workspace](https://rustsc.com/support/guides/workspace-data-closing/index.html.md) HTML version: https://rustsc.com/support/guides/account-data/ --- # Choose how people sign in to a workspace Set allowed sign-in methods and decide how often members sign in again. ## Set the sign-in rule Members with workspace access can read the current rule. Changing it requires permission to manage the workspace. Check that you and your team have an allowed method before changing it. If RustSC asks you to **Sign in again**, use an allowed method. RustSC returns you to the workspace page you were using. 1. In the workspace, open **Settings**, then **People** and **Sign-in rule**. 2. Under **Ways to sign in**, choose **Any way** or **Only these ways**. If you limit the choices, select the methods your team can use. 3. Choose how long sign-ins should last, or keep the account default. Choose **Save**. - [Add a way to sign in](https://rustsc.com/support/guides/account-sign-in-security/index.html.md) HTML version: https://rustsc.com/support/guides/workspace-sign-in-rule/ --- # Make, limit or revoke an API key Give a script access to the right workspace and servers, then replace or revoke its key. ## Make a key for a script Start with **Look only** for reports. Select just the servers the tool needs and the shortest expiry that fits the job. If you cannot see **API keys**, ask a workspace owner about your access. For a teammate who uses the portal, invite them with their own role instead. For a shared tool, put its dedicated key directly in the tool’s private settings. 1. Switch to the workspace that the script will use. Open your account menu, choose **API keys**, then **Make a key**. 2. Name the key and choose **Scripts and tools**. Choose how much it can do, which servers it can reach and when it expires. 3. Choose **Make key**. Copy the key from **Your key** into your tool's private settings, then choose **Done**. RustSC shows the full key only once. ## Change the servers or revoke the key 1. Open the key's menu and choose **Servers** to review or change what it can reach. Save the new selection. 2. To replace a key in use, make its replacement and switch the script to it. Then open the old key's menu, choose **Revoke** and confirm. If a key was shared by mistake, revoke it straight away. - [Use the customer API](https://rustsc.com/help/v1/api/index.html.md) HTML version: https://rustsc.com/support/guides/make-api-key/ --- # Download, hand over or close a workspace Download workspace data, make another member the owner or review closing the workspace. ## Download workspace data 1. Open the workspace and choose **Settings**, then **Workspace** and **Data and closing**. 2. Choose **Download this workspace's data** if your role allows it. For a playable copy of a Rust world, make a separate server backup. - [Back up a server](https://rustsc.com/support/guides/back-up-server/index.html.md) ## Make someone else the owner If RustSC says the member already manages another workspace, choose another eligible member. 1. Open **Settings**, then **People** and **Members**. The person needs to be a member first. 2. Open their row menu and choose **Make owner**. If you are the current Owner, handing over makes you an Administrator. Check the member's name before confirming. ## Close the workspace 1. In **Data and closing**, choose **Close this workspace** if your role allows it. 2. Read the review, including when closing can happen, and choose the closing action the page offers. Choose **Keep it open** to leave the review without closing. 3. To keep a closing workspace, open it from your workspace list and use the recovery action shown. If closing was caused by account deletion, follow the link to your account. HTML version: https://rustsc.com/support/guides/workspace-data-closing/ --- # Set up a workspace integration Set up, check or remove the workspace's Steam, Codefling and RustHQ connections. ## Set up or check a connection Workspace owners and administrators can manage integrations. A person with read-only integration access can see the saved state. Use the **Discord** tab for Discord settings, and the **API keys** page in your account for keys used by scripts. 1. Switch to the workspace you want to configure. Open **Integrations** and choose **Other**. 2. Find Steam under **Players**, or Codefling or RustHQ under **Plugin marketplaces**. Choose **Set up** and follow the instructions on that row. 3. Choose **Save and check** if offered. Use the row's check action to test a saved connection, and read the result before using the integration. 4. To replace a key, open its details and save the replacement. To stop using it, choose **Remove key** and confirm. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/index.html.md) - [Make an API key](https://rustsc.com/support/guides/make-api-key/index.html.md) HTML version: https://rustsc.com/support/guides/workspace-integrations/ --- # Alerts reference Find a specific action or setting for alerts and open the related instructions in RustSC. ## See alerts Open Alerts to see what needs attention. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/#alerts) ## Acknowledge an alert Open the alert and choose Acknowledge to stop reminders; clear an alert where that action is offered. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/#alerts) ## Choose alerts Review the alert settings and save the choices you want. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/#alerts) ## Change alert settings Open Alerts, choose Alert settings and save your changes. - [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/#alerts) ## Set alert repeats and waits In Alert settings, choose Repeat and its timing where offered, then save your changes. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/#alerts) ## Choose alerts for yourself Use Tell me on each alert to choose what reaches your devices. - [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/#alerts) ## Quiet team alerts Add a quiet time and choose which alerts it covers. - [Set a quiet time for alerts](https://rustsc.com/support/guides/quiet-alerts/#quiet) ## Hear when a server goes offline Turn on the alert in Alert settings and choose where it goes. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/#alerts) ## Hear about server work Choose the restart, wipe or update alerts you want in Alert settings. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/#alerts) ## Hear about backup problems Choose the backup and restore alerts you want in Alert settings. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/#alerts) ## Hear about a host Choose host alerts in Alert settings and save. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/#alerts) ## Hear about disk space Choose low disk space alerts and their destinations in Alert settings. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/#alerts) ## Hear about server load Choose resource alerts in Alert settings and save. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/#alerts) ## Hear about player activity Choose the player alerts you need in Alert settings. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/#alerts) ## Watch chat and console words Choose the words to watch in Alert settings and save the alert. - [Get alerts for words in chat or console](https://rustsc.com/support/guides/watch-chat-and-console-words/#watch-words) ## Hear about connection problems Choose the alerts you need and check Alerts when an integration needs attention. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/#problems) ## Send alerts to Discord Add a Discord channel in Alert Destinations and choose it in Alert settings. - [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/#alerts) ## Turn on browser notifications Open Browser notifications under Alert Destinations and turn on notifications for this browser. - [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/#alerts) ## Send alerts to another tool Where offered under Alert Destinations, choose Add webhook, enter its name and address, and send a test. - [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/#alerts) ## Check notifications Open the notifications log under Alerts to see what was sent or held back. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/#problems) ## Follow one ongoing alert Open the existing alert to read its latest state. Check Activity to see whether a restart or update explains the interruption. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/#alerts) ## Alerts on the host Read host alerts locally and use the available alert commands. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-alerts) ## Choose alerts for a rented server Check the alert types offered for your rented server. Host measurements such as disk use require a host that reports those figures. - [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/#alerts) HTML version: https://rustsc.com/support/guides/reference-alerts/ --- # API access and assistants reference Find a specific action or setting for api access and assistants and open the related instructions in RustSC. ## Sign in to the API Choose the authentication method for your client. A browser session needs its request token when you change something. - [Developer documentation](https://rustsc.com/help/v1/api/#signin) ## Find an API action Open the reference, choose the feature area and expand an action for its method, permissions, inputs and responses. - [Developer documentation](https://rustsc.com/help/v1/reference/index.html.md) ## Follow long-running work When a request returns an operation, follow it to a final result before deciding what to do next. - [Developer documentation](https://rustsc.com/help/v1/operations/#follow) ## Repeat a request safely For an action that accepts a request key, reuse the same key and unchanged request when the answer is lost. - [Developer documentation](https://rustsc.com/help/v1/operations/#retry) ## Preview a bulk change Review the effect on each selected server and approve the preview you intend to apply. - [Manage several servers at once](https://rustsc.com/support/guides/bulk-actions/#apply) ## Read an API error Check the response status and the problem details before retrying. When the outcome is unknown, inspect the original action. - [Developer documentation](https://rustsc.com/help/v1/operations/#errors) ## Create a key for a tool Choose API keys from the account menu, make a Scripts and tools key and copy it once into the tool’s private settings. - [Make, limit or revoke an API key](https://rustsc.com/support/guides/make-api-key/#make-key) ## Limit a tool’s access Choose Look only for reporting, select the servers the tool needs and set its expiry. - [Make, limit or revoke an API key](https://rustsc.com/support/guides/make-api-key/#make-key) ## Replace or revoke a key Make the replacement, update the tool and check that it works before revoking the old key. - [Make, limit or revoke an API key](https://rustsc.com/support/guides/make-api-key/#replace-key) ## Choose a key type Choose the key type for the client. Review the operations and servers the key will be allowed to use before creating it. - [Make, limit or revoke an API key](https://rustsc.com/support/guides/make-api-key/#make-key) ## Use a command that needs the cloud Check the installed command’s help for its key and connection requirements before using cloud file or plugin library commands. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#before) ## Find a request or response Expand the action in the API reference to see its path, body and responses. Download OpenAPI for use in your own client. - [Developer documentation](https://rustsc.com/help/v1/reference/index.html.md) ## Read the guides with a tool Start with llms.txt for readable links or the versioned guide index for pages, section links and downloads. - [Developer documentation](https://rustsc.com/help/v1/index.html.md) ## Send alerts to another tool Add a webhook destination where offered, enter the receiving address and send a test before relying on alerts. - [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/#alerts) HTML version: https://rustsc.com/support/guides/reference-api-access-and-assistants/ --- # Automation reference Find a specific action or setting for automation and open the related instructions in RustSC. ## Make a server event rule In the server's Schedules, open When something happens and choose Add a rule. - [Make a rule that responds to a server event](https://rustsc.com/support/guides/make-a-server-event-rule/#add-rule) ## Choose what triggers a rule Use the When field to choose an event this server offers. - [Make a rule that responds to a server event](https://rustsc.com/support/guides/make-a-server-event-rule/#add-rule) ## Say something in game chat Choose Say it in chat as the rule's response and enter a message. - [Make a rule that responds to a server event](https://rustsc.com/support/guides/make-a-server-event-rule/#add-rule) ## Send an alert when an event happens Choose Send an alert to my channels and enter the message. - [Make a rule that responds to a server event](https://rustsc.com/support/guides/make-a-server-event-rule/#add-rule) ## Post in Discord when an event happens Choose Post in Discord where offered and select a channel. - [Make a rule that responds to a server event](https://rustsc.com/support/guides/make-a-server-event-rule/#add-rule) ## Read what a rule did Check Latest result or open What it did for earlier runs. - [Make a rule that responds to a server event](https://rustsc.com/support/guides/make-a-server-event-rule/#check-rule) ## 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. - [Make a rule that responds to a server event](https://rustsc.com/support/guides/make-a-server-event-rule/#check-rule) ## Read rules from a script Use the customer API to list the rules you may read. - [Developer documentation](https://rustsc.com/help/v1/reference/#listRules) ## Schedule a temporary change Choose a server, its start and end, and the files the change uses. - [Schedule a temporary change](https://rustsc.com/support/guides/temporary-changes/#create) ## Choose temporary files or plugins Add the files or plugin changes that should be in place for the chosen window. - [Schedule a temporary change](https://rustsc.com/support/guides/temporary-changes/#create) ## Choose when a temporary change starts Choose the start in the form. Now starts it on save. - [Schedule a temporary change](https://rustsc.com/support/guides/temporary-changes/#create) ## Change when a temporary change ends Edit the saved timing, or use Extend where offered for a change that is already on. - [Schedule a temporary change](https://rustsc.com/support/guides/temporary-changes/#change) ## Extend a running temporary change Choose Extend where offered and confirm the new end. - [Schedule a temporary change](https://rustsc.com/support/guides/temporary-changes/#change) ## Copy a temporary change A copy starts paused so you can review its timing before turning it on. - [Schedule a temporary change](https://rustsc.com/support/guides/temporary-changes/#create) ## Tell players when a temporary change starts and ends Add optional start and end messages under Tell players before saving. - [Announce or recover a temporary change](https://rustsc.com/support/guides/temporary-change-messages-and-recovery/#messages) ## Review a temporary change before saving Check the selected files, plugins and timing on the form before you save. - [Schedule a temporary change](https://rustsc.com/support/guides/temporary-changes/#create) ## 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. - [Announce or recover a temporary change](https://rustsc.com/support/guides/temporary-change-messages-and-recovery/#history) ## Review or reverse a temporary-change run Open Past and choose Roll back or Roll forward where the run offers it. - [Announce or recover a temporary change](https://rustsc.com/support/guides/temporary-change-messages-and-recovery/#history) ## Check files for a temporary change Open the files from the schedule and check what is ready before the change runs. - [Schedule a temporary change](https://rustsc.com/support/guides/temporary-changes/#create) ## Read temporary-change history from a script Use the customer API to see when a change ran and how it ended. - [Developer documentation](https://rustsc.com/help/v1/reference/#listTimedChangeActivations) HTML version: https://rustsc.com/support/guides/reference-automation/ --- # Bans and join rules reference Find a specific action or setting for bans and join rules and open the related instructions in RustSC. ## Kick a player Open Players, choose the player and select Kick. - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/#players) ## Ban a player Choose Ban on the player and review the reason and scope. - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/#bans) ## Set a ban length Choose how long the ban lasts before confirming. - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/#bans) ## Lift a ban Open Bans, find the player and choose Unban. - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/#bans) ## Keep a game staff role after a ban When banning a game owner or moderator, review the option to return their role when the ban ends. - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/#bans) ## Read bans Open Players, then Bans to find a player and read the ban. - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/#bans) ## See server bans The server's Bans list includes bans made in the game console. - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/#bans) ## Import bans Choose Import bans, paste a list or choose a file, and review it before banning. - [Import or download bans](https://rustsc.com/support/guides/import-bans/#import) ## Choose where a ban applies Review the server or global scope before confirming a ban. - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/#bans) ## Use global bans Choose Global bans to manage bans for the workspace's servers. - [Import or download bans](https://rustsc.com/support/guides/import-bans/#import) ## Check global bans on a rented server Open the rented server's Bans page to see whether global bans are available and switch them on where offered. - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/#bans) ## See player facts Open a player to see the Steam facts available to you. - [View a player and take action](https://rustsc.com/support/guides/player-details/#player) ## Add a community ban list Open Ban lists, choose Add a community list and enter its name and address. - [Choose who can join](https://rustsc.com/support/guides/join-rules/#lists) ## Add a BattleMetrics list Under Ban lists, choose Add from BattleMetrics and enter the list and your read-only token. - [Choose who can join](https://rustsc.com/support/guides/join-rules/#lists) ## Choose whether a list removes players For a ban list, choose whether to show its information or enforce it, then save. - [Choose who can join](https://rustsc.com/support/guides/join-rules/#lists) ## Allow a player anyway Open the player's page and choose Allow anyway to exempt them from ban lists. - [Choose who can join](https://rustsc.com/support/guides/join-rules/#lists) ## Check a list that is not answering The list's status says when it is unavailable; players are let in while it cannot answer. - [Choose who can join](https://rustsc.com/support/guides/join-rules/#lists) ## Allow listed players only Turn on Allowed players only, enter the Steam IDs and save the join rules. - [Choose who can join](https://rustsc.com/support/guides/join-rules/#rules) ## Set a country rule Choose Countries, enter the country codes and save the join rules. - [Choose who can join](https://rustsc.com/support/guides/join-rules/#rules) ## Check Steam profiles Choose Private profiles or New Steam accounts and save the join rules. - [Choose who can join](https://rustsc.com/support/guides/join-rules/#rules) ## Set a connection rule Choose Slow connections, set the threshold and save the join rules. - [Choose who can join](https://rustsc.com/support/guides/join-rules/#rules) ## Set workspace join rules Open player Settings, choose rules for all servers and review before saving. - [Choose who can join](https://rustsc.com/support/guides/join-rules/#rules) ## Review checked joins Open Joins checked in the server's player settings to read the decisions. - [Choose who can join](https://rustsc.com/support/guides/join-rules/#checked) ## Players on the host Use the Windows app to kick, ban or unban a player on the host. - [Control a server on its host](https://rustsc.com/support/guides/offline-server-control/#windows-players) HTML version: https://rustsc.com/support/guides/reference-bans-and-join-rules/ --- # Backups reference Find a specific action or setting for backups and open the related instructions in RustSC. ## Back up now Make a backup of a server. - [Back up a server](https://rustsc.com/support/guides/back-up-server/#backup) ## See backup files Get a copy of a backup or its file list. - [Restore a backup](https://rustsc.com/support/guides/restore-backup/#copy) ## Protect before changes Choose backup protection before making changes. - [Back up a server](https://rustsc.com/support/guides/back-up-server/#backup) ## Backup before launch Choose a backup before each server launch. - [Back up a server](https://rustsc.com/support/guides/back-up-server/#backup) ## Saved backups See the server's saved backups. - [Back up a server](https://rustsc.com/support/guides/back-up-server/#backup) ## Backup alerts Choose alerts for backup problems. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/#alerts) ## Restore a backup Review the restore and confirm it when ready. - [Restore a backup](https://rustsc.com/support/guides/restore-backup/#restore) ## Restore safety Review what a restore will change; RustSC keeps a backup of the current server first. - [Back up or restore on the host](https://rustsc.com/support/guides/host-backups/#windows) ## Restore files to a folder Use the host backup command to copy backup files to a folder. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-backup) ## Use a backup on another server Use a backup to replace another server after reviewing the result. - [Copy a backup as a new server](https://rustsc.com/support/guides/copy-backup/#copy) ## Copy a backup as a server Create a server from a backup. - [Copy a backup as a new server](https://rustsc.com/support/guides/copy-backup/#copy) ## Save a backup as a zip Select a saved backup in the Windows app and save a zip copy. - [Back up or restore on the host](https://rustsc.com/support/guides/host-backups/#windows) ## Check backups Use the backup check command to see whether stored backups are intact. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-backup) ## Choose backups to keep Choose how many backups to retain. - [Back up a server](https://rustsc.com/support/guides/back-up-server/#keep) ## Make room for backups Under Space, turn on Make room when the disk is nearly full to let RustSC make room for backups. - [Free disk space](https://rustsc.com/support/guides/free-disk-space/#backups) ## Choose a backup folder Choose the folder for backups on the Windows host. - [Back up or restore on the host](https://rustsc.com/support/guides/host-backups/#windows) ## Free up space Review and clean up old files. - [Free disk space](https://rustsc.com/support/guides/free-disk-space/#files) ## Move to another host Move the server to a new host and review the steps. - [Move a server to a new host](https://rustsc.com/support/guides/move-to-new-host/#steps) ## Back up on the host Make or restore a backup from the host. - [Back up or restore on the host](https://rustsc.com/support/guides/host-backups/#terminal) ## Backups from a terminal Use the backup command help on the host. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-backup) HTML version: https://rustsc.com/support/guides/reference-backups/ --- # Console and chat reference Find a specific action or setting for console and chat and open the related instructions in RustSC. ## Read the console Open the server's Console tab to read game messages. - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/#console) ## Read console status The console shows what is available while the server changes state. - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/#console) ## Run a command Enter the command and choose Run, then read the reply. - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/#console) ## Open the console in a window Choose Pop out on the console to open its own window. - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/#console) ## Console on the host Read the console and send commands from the Windows app on the host. - [Control a server on its host](https://rustsc.com/support/guides/offline-server-control/#windows-console) ## Search the console Choose Search and filter and enter the words to find. - [Find and save console lines and commands](https://rustsc.com/support/guides/console-tools/#find) ## Filter and highlight lines Choose Filter lines or Highlight lines and add a rule. - [Find and save console lines and commands](https://rustsc.com/support/guides/console-tools/#find) ## Search older console lines Choose Search older lines to search what the host saved. - [Find and save console lines and commands](https://rustsc.com/support/guides/console-tools/#find) ## Pause or download lines Pause while reading, or use the console actions to copy or download shown lines. - [Find and save console lines and commands](https://rustsc.com/support/guides/console-tools/#find) ## Watch for words Add watch words and choose a sound, tab count or browser notification. - [Find and save console lines and commands](https://rustsc.com/support/guides/console-tools/#watch) ## Read a console flood notice When the console floods, the page says it paused and resumes when the flood stops; chat stays visible. - [Find and save console lines and commands](https://rustsc.com/support/guides/console-tools/#find) ## Hide repeating errors Use Error spam to choose how long to hide repeating errors; the server log keeps the lines. - [Find and save console lines and commands](https://rustsc.com/support/guides/console-tools/#find) ## Read server chat Choose Chat in the console view and use Chat types to select what you see. - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/#console) ## Send a chat message Choose Chat, enter your message and choose Send. - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/#console) ## Change your chat name Open Your account and choose Chat identity for the workspace. - [Download your data or delete your account](https://rustsc.com/support/guides/account-data/#account-preferences) ## See player warnings Players see the countdown before a restart, stop or wipe. - [Messages, restarts and wipes: what players see](https://rustsc.com/support/guides/player-messages/#see) ## Message everyone Open the console's Chat view, write your message and choose Send. - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/#console) ## Save a command Choose Save this command, name it and pick it later under Saved commands. - [Find and save console lines and commands](https://rustsc.com/support/guides/console-tools/#commands) ## Run a moderator command Choose a command, fill in its boxes and choose Run. - [Let a moderator run a few commands](https://rustsc.com/support/guides/mod-commands/#steps) ## Set up a moderator command Open Commands, choose New command and save its name and blanks. - [Let a moderator run a few commands](https://rustsc.com/support/guides/mod-commands/#steps) ## Run an approved command in Discord A linked member with permission can type /run and fill in an enabled moderator command's boxes. - [Let a moderator run a few commands](https://rustsc.com/support/guides/mod-commands/#steps) ## Console commands through the API Run a console command through the customer API. - [Developer documentation](https://rustsc.com/help/v1/reference/#runCommand) ## Send a command to a rented server Open Console when the rented connection offers it, send one command and check the result before sending it again. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#fix) HTML version: https://rustsc.com/support/guides/reference-console-and-chat/ --- # Server configuration reference Find a specific action or setting for server configuration and open the related instructions in RustSC. ## Change the server's name or description Open Configuration and edit how the server appears in the server browser. - [Change server settings](https://rustsc.com/support/guides/server-settings/#settings) ## Edit server listing images and links Open the server listing settings and preview the listing before applying it. - [Change server settings](https://rustsc.com/support/guides/server-settings/#settings) ## Edit server tags Change the tags in the server listing settings. - [Change server settings](https://rustsc.com/support/guides/server-settings/#settings) ## Check the current map Read the current map before applying or planning a world change. - [Change server settings](https://rustsc.com/support/guides/server-settings/#settings) ## Find a server setting Use Search settings in Configuration to find the value you want to change. - [Change server settings](https://rustsc.com/support/guides/server-settings/#settings) ## Save settings for later Choose Save to keep a change or Save and apply to send it to the server. - [Import or download server settings](https://rustsc.com/support/guides/import-server-settings/#import) ## Change player and save settings Open Configuration and review the Players and saves settings. - [Change server settings](https://rustsc.com/support/guides/server-settings/#settings) ## Find game configuration values Look for a setting in Configuration and check when it applies. - [Change server settings](https://rustsc.com/support/guides/server-settings/#settings) ## Review the next start's command line Open Launch arguments and review Command line before saving startup changes. - [Review startup and performance settings](https://rustsc.com/support/guides/advanced-game-settings/#startup) ## Review a game mode or map change before saving Read whether the change will reset players and their items or start a new map before choosing Save anyway. - [Change server settings](https://rustsc.com/support/guides/server-settings/#settings) ## Set game priority or processors Open Performance in Configuration and review Game priority and Processors before saving. - [Review startup and performance settings](https://rustsc.com/support/guides/advanced-game-settings/#performance) ## Review a setting changed outside RustSC Compare the saved and running values and choose which to keep. - [Review settings changed outside RustSC](https://rustsc.com/support/guides/review-server-setting-changes/#compare) ## Import or download configuration Open More configuration actions and choose Import from a file or a download format. - [Import or download server settings](https://rustsc.com/support/guides/import-server-settings/#import) ## Open RustSC's server files Use Files to browse the RustSC folder when it is offered. - [Work with server files](https://rustsc.com/support/guides/manage-files/#files) ## Read settings from another tool Read what Configuration can see and change startup settings in the tool running the server. - [Review settings changed outside RustSC](https://rustsc.com/support/guides/review-server-setting-changes/#compare) ## Change game and query ports Edit Ports in Configuration and review the restart before applying them to a running server. - [Change the ports players use to join](https://rustsc.com/support/guides/change-server-ports/#change) ## Check whether players can join After applying new ports, test joining from outside your network. - [Change the ports players use to join](https://rustsc.com/support/guides/change-server-ports/#change) ## Open game ports in the host firewall Open Firewall and port forwarding and use Open the ports for me where offered. - [Change the ports players use to join](https://rustsc.com/support/guides/change-server-ports/#firewall-and-rcon) ## Review the RCON password and access Workspace owners can review the password and access in the server's Ports settings where offered. - [Change the ports players use to join](https://rustsc.com/support/guides/change-server-ports/#firewall-and-rcon) ## Manage in-game staff Open the server's permissions view to manage who is an owner or moderator in the game. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/#staff) ## Check the schedule's time zone Set the server time zone and review the next scheduled run. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/#schedule) ## Save Nexus network settings Choose a saved network or enter an existing Nexus key and apply the settings for the next start. - [Save Nexus network settings for a server](https://rustsc.com/support/guides/save-nexus-network-settings/#select-network) ## Apply a settings profile Preview a profile on chosen servers and check which values each server will keep. - [Manage several servers at once](https://rustsc.com/support/guides/bulk-actions/#profiles) ## Read server settings from a script Use the customer API to read the server's saved configuration. - [Developer documentation](https://rustsc.com/help/v1/reference/#getServerConfiguration) ## Check settings on a rented server Open Configuration and use the changes offered for that connection. - [Change server settings](https://rustsc.com/support/guides/server-settings/#settings) HTML version: https://rustsc.com/support/guides/reference-server-configuration/ --- # Discord community reference Find a specific action or setting for discord community and open the related instructions in RustSC. ## Connect the bot Add the RustSC bot to your Discord server from Integrations. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/#setup) ## Add the bot Open Integrations, choose Discord and add the bot to your server. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/#setup) ## Fix bot permissions The Discord page tells you when the bot needs a permission. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/#problems) ## Open Discord settings Choose Discord under Integrations to manage the connection. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/#setup) ## Choose a link channel Create or choose the Discord channel where players link. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/#setup) ## Link a player The player types /link in game and enters the code in Discord. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/#players) ## Show a Discord invite Save an invite link so players can see it next to their code. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/#setup) ## Unlink an account A player can choose Unlink in the game panel or Link Status. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/#players) ## Link accounts A linked player's Steam and Discord accounts can be used by enabled features. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/#players) ## Link without a portal account Players link through the game and Discord; they do not need a RustSC account. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/#players) ## Change the link command Change Command players type if another plugin already uses /link. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/#players) ## Change the link message Under Player messages on the Discord page, edit the title, welcome or reply and choose Save wording. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/#setup) ## Find linked players Search Linked players on the Discord page, or use Sync now to check links. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/#staff) ## Find a link in Discord Type /link search and search by name or Steam ID. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/#staff) ## Bring old links Use Bring your old links to move existing links into RustSC. - [Move existing Discord links](https://rustsc.com/support/guides/move-discord-links/#move) ## Hear about Discord problems Choose the Discord alerts you want in Alert settings. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/#alerts) ## Give linked players a role Open Role rewards, choose Give a role and save your choice. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/#rewards) ## Reward boosters In Role rewards, choose players who boost and a Discord role. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/#rewards) ## Add linked players to a Rust group Choose Also add to a Rust group and select the server and group. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/#rewards) ## Sync a role and group Choose a Discord role, Rust group and direction, then start the sync. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/#roles) ## Choose what a sync removes Review the removal choices before starting or removing a sync. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/#roles) ## Review a staff group sync Only a workspace owner can allow a sync into a staff group; read the warning and confirm the group name. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/#roles) ## Use Steam names as nicknames Open Discord nicknames and choose whether linked players' nicknames follow their Steam names. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/#rewards) HTML version: https://rustsc.com/support/guides/reference-discord-community/ --- # Discord server updates reference Find a specific action or setting for discord server updates and open the related instructions in RustSC. ## Choose a Discord channel Choose a channel in the server's Discord settings and save. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/#status) ## Show server status Open Status board, choose the server and channel, then save. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/#status) ## Show players on the board Turn on the player list in the server's status board settings. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/#status) ## Post server changes Turn on change posts in the server's status board settings. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/#status) ## Read the status board When a host is offline, the board can show Offline and its last update instead of a current player count. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/#status) ## Relay game chat Turn on Chat relay and choose a Discord channel. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/#chat) ## Relay Discord chat Choose Discord to game chat where the page offers it. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/#chat) ## Choose who can relay chat In Chat relay, choose who can talk from Discord and add muted players if needed. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/#chat) ## Choose how chat looks Choose a chat line format and review the preview before saving. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/#chat) ## Test the chat relay Save the relay and choose Send test, then check Discord. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/#chat) ## Write Discord posts Open the post's What Discord shows editor, write the wording and save it. - [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/#alerts) ## Add post wordings Choose Add another wording; RustSC picks a wording when it posts. - [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/#alerts) ## Add a value to a post Use Add a value in the post editor and review the preview. - [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/#alerts) ## Choose who a post pings In the post editor, choose Nobody, a role or an offered Discord mention under Ping. - [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/#alerts) ## Choose a post's look In the post editor, choose Message or Card where offered and review the preview. - [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/#alerts) ## Send alerts to Discord Add a channel under Alert Destinations and choose it in Alert settings. - [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/#alerts) ## Run a command in Discord A linked member with permission can type /run and fill in an enabled moderator command's boxes. - [Let a moderator run a few commands](https://rustsc.com/support/guides/mod-commands/#steps) ## Send upkeep alerts Turn on Track upkeep and Tell players for the server. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/#upkeep) ## Connect Discord to a workspace Add the bot once, then choose settings for each server. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/#setup) ## Choose what Discord receives Turn on and save the status, chat or alert functions you want. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/#status) ## Check what the Discord bot offers Use the configured relay or an approved moderator command. For other server management, open the portal. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/#chat) ## Check Discord options on a rented server Check the rented connection and the Discord options offered for that server before setting up a post or relay. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#fix) HTML version: https://rustsc.com/support/guides/reference-discord-server-updates/ --- # Reports and evidence reference Find a specific action or setting for reports and evidence and open the related instructions in RustSC. ## Open F7 reports Open F7 Reports to see the reports your team can work on. - [Review F7 reports and find events](https://rustsc.com/support/guides/review-player-reports/#review) ## Find a report Filter to To do or search by player, Steam ID or words in the report. - [Review F7 reports and find events](https://rustsc.com/support/guides/review-player-reports/#review) ## Work a report with your team Pick up a report, add a comment and close it when finished. - [Review F7 reports and find events](https://rustsc.com/support/guides/review-player-reports/#review) ## Act on a reported player Use the player's available kick or ban action after checking the report. - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/#players) ## See what happened around a report Open the report and check Around this report for nearby events. - [Review F7 reports and find events](https://rustsc.com/support/guides/review-player-reports/#review) ## Choose where report alerts go Open Alert settings and choose a destination for the report alert. - [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/#alerts) ## Delete a report when needed Read the Delete report confirmation because it permanently removes the report and its notes. - [Review F7 reports and find events](https://rustsc.com/support/guides/review-player-reports/#review) ## Choose what a server records Open the server's Recording settings and save your choice for public chat or F7 reports. - [Review F7 reports and find events](https://rustsc.com/support/guides/review-player-reports/#record) ## Search recorded public chat Open Events and use the public chat search to find recorded messages. - [Read server events and chat](https://rustsc.com/support/guides/server-events/#events) ## Read events for one server Open the server's Events tab and choose Show older events to go further back. - [Read server events and chat](https://rustsc.com/support/guides/server-events/#events) ## Search for events across servers Open Find events and filter by event type or search words. - [Review F7 reports and find events](https://rustsc.com/support/guides/review-player-reports/#find) ## Check gaps in recorded events Read the gap in the results and check the server's recording settings. - [Review F7 reports and find events](https://rustsc.com/support/guides/review-player-reports/#find) ## Clear recorded events Use Delete in Recorded events and review what will be removed before confirming. - [Review F7 reports and find events](https://rustsc.com/support/guides/review-player-reports/#record) ## Read private player notes Open the player's details and read the notes your team has added. - [View a player and take action](https://rustsc.com/support/guides/player-details/#player) ## Check a player's history Open the full player page and choose a server to review their history. - [View a player and take action](https://rustsc.com/support/guides/player-details/#player) ## See what staff did Open Activity and read the action and its result. - [See what your team did](https://rustsc.com/support/guides/team-activity/#steps) ## Keep report comments with your team Use Add comment to leave a note for your team on that report. - [Review F7 reports and find events](https://rustsc.com/support/guides/review-player-reports/#review) ## Check which recorded events are still available Read the event retention note on Events or Find events. A report can remain after the events around it expire. - [Read server events and chat](https://rustsc.com/support/guides/server-events/#events) ## Read the report inbox from a script Use the customer API to list reports and narrow the results to the server or status you want. - [Developer documentation](https://rustsc.com/help/v1/reference/#listReports) ## Set up the plugin for F7 reports If recording asks for the RustSC plugin, open Software and install it where offered. - [Review F7 reports and find events](https://rustsc.com/support/guides/review-player-reports/#record) HTML version: https://rustsc.com/support/guides/reference-reports-and-evidence/ --- # Server files reference Find a specific action or setting for server files and open the related instructions in RustSC. ## Browse files Open the server's Files tab and choose a folder. - [Work with server files](https://rustsc.com/support/guides/manage-files/#files) ## Find a file Open a folder and use its search and sorting controls. - [Work with server files](https://rustsc.com/support/guides/manage-files/#files) ## See available folders Files shows the folders RustSC can open for that server. - [Work with server files](https://rustsc.com/support/guides/manage-files/#files) ## Edit a file Open a text file, change it and save. - [Work with server files](https://rustsc.com/support/guides/manage-files/#edit) ## Fix a file before saving If the page reports a problem, correct the file and save again. - [Work with server files](https://rustsc.com/support/guides/manage-files/#edit) ## Review file changes Read the changes shown before confirming Save. - [Work with server files](https://rustsc.com/support/guides/manage-files/#edit) ## Reload a plugin The save result says whether the plugin reloaded or will use the file later. - [Work with server files](https://rustsc.com/support/guides/manage-files/#edit) ## Read large or binary files Files that cannot be edited are shown read only or offer a replacement upload. - [Work with server files](https://rustsc.com/support/guides/manage-files/#edit) ## Create files and folders Open Files and choose New to create a file or folder. - [Work with server files](https://rustsc.com/support/guides/manage-files/#files) ## Rename or move a file Select the item and choose an available action. - [Work with server files](https://rustsc.com/support/guides/manage-files/#files) ## Delete a file Select it, choose Delete and read the confirmation before proceeding. - [Work with server files](https://rustsc.com/support/guides/manage-files/#files) ## Upload files Open Files and choose Upload files. - [Work with server files](https://rustsc.com/support/guides/manage-files/#files) ## Pause an upload Use Pause or Resume on an upload to control its progress. - [Work with server files](https://rustsc.com/support/guides/manage-files/#files) ## Choose what happens to an existing file When uploading, choose Replace or Keep both and read what happens to the old file. - [Work with server files](https://rustsc.com/support/guides/manage-files/#files) ## Add a plugin Open Plugins and choose how to add the plugin, then install it. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/#find) ## Resolve a file problem Read the message on the file action and follow its next step. - [Work with server files](https://rustsc.com/support/guides/manage-files/#files) ## Files from a terminal Use the files commands with a cloud connection and an API key. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-files) ## File changes through the API Use the customer API to edit a server file. - [Developer documentation](https://rustsc.com/help/v1/reference/#editServerFile) ## Files on a rented server Available file actions depend on the hosting company. - [Work with server files](https://rustsc.com/support/guides/manage-files/#files) ## Fix a file access problem Open the result for the affected file. Follow the folder or access correction shown, then retry that file after checking which others succeeded. - [What a message means and what to do](https://rustsc.com/support/guides/fix-common-problems/#folders-and-permissions) HTML version: https://rustsc.com/support/guides/reference-server-files/ --- # Server groups reference Find a specific action or setting for server groups and open the related instructions in RustSC. ## Find your servers in one workspace Choose the workspace that holds the servers and hosts you want to manage. - [Manage workspace access](https://rustsc.com/support/guides/workspace-access/#access) ## See your workspace's servers on Home Open Home to see the servers and hosts in your workspace. - [Find and select servers in a workspace](https://rustsc.com/support/guides/find-a-server-in-your-workspace/#inventory) ## Search, filter or sort your servers Open Servers and narrow the list by status or search text. - [Find and select servers in a workspace](https://rustsc.com/support/guides/find-a-server-in-your-workspace/#inventory) ## Start, stop or restart selected servers Select servers from the list and review which ones will run the action before confirming. - [Find and select servers in a workspace](https://rustsc.com/support/guides/find-a-server-in-your-workspace/#inventory) ## Compare servers together Open See players and frame rate of all servers or choose a saved group. - [Manage several servers at once](https://rustsc.com/support/guides/bulk-actions/#compare) ## Save a server group Select the servers, choose Save group and give the group a name. - [Manage several servers at once](https://rustsc.com/support/guides/bulk-actions/#apply) ## Run an action on several servers Choose the action and select the servers or group to use. - [Manage several servers at once](https://rustsc.com/support/guides/bulk-actions/#apply) ## Preview each server's change Choose See what will happen and check the result for each server. - [Manage several servers at once](https://rustsc.com/support/guides/bulk-actions/#apply) ## Check results by server Open Results and check which servers finished and which need attention. - [Manage several servers at once](https://rustsc.com/support/guides/bulk-actions/#apply) ## Choose how bulk work starts Review how the servers will start before previewing the action. - [Manage several servers at once](https://rustsc.com/support/guides/bulk-actions/#apply) ## Ban or unban across selected servers Choose the player action, then review the exact target servers before confirming. - [Manage several servers at once](https://rustsc.com/support/guides/bulk-actions/#apply) ## Send a message to several servers Choose the message action and check the message and target servers before confirming. - [Manage several servers at once](https://rustsc.com/support/guides/bulk-actions/#apply) ## Make a settings profile Save the settings you want to reuse as a profile before choosing target servers. - [Manage several servers at once](https://rustsc.com/support/guides/bulk-actions/#profiles) ## Review each server's own values Preview a profile and check which values each target keeps. - [Manage several servers at once](https://rustsc.com/support/guides/bulk-actions/#profiles) ## Put earlier settings back Choose Put the old settings back where offered and check its preview. - [Manage several servers at once](https://rustsc.com/support/guides/bulk-actions/#profiles) ## Preview group changes across several servers from a script Preview a list of in-game group or permission changes across selected servers and review each result. - [Keep player permissions the same across servers](https://rustsc.com/support/guides/sync-player-permissions/#bulk-permissions-api) ## Make a server schedule Choose the target servers the schedule offers and check the next run after saving. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/#schedule) ## Schedule a wipe per server Set the wipe and its timing on each server you intend to wipe. - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/#schedule) ## Turn on permission sync Choose the servers and read what would change before turning on sync. - [Keep player permissions the same across servers](https://rustsc.com/support/guides/sync-player-permissions/#start-sync) ## Change a shared group once Open a group under Groups on all these servers and review all targets before applying. - [Keep player permissions the same across servers](https://rustsc.com/support/guides/sync-player-permissions/#start-sync) ## Check which servers received a change Use Check now and read each server's result. - [Keep player permissions the same across servers](https://rustsc.com/support/guides/sync-player-permissions/#start-sync) ## Resume permission sync after a pause Read what needs attention and check what Resume will send before resuming. - [Keep player permissions the same across servers](https://rustsc.com/support/guides/sync-player-permissions/#resume) ## Find a player across servers Open the full player page and choose the server you want to see. - [View a player and take action](https://rustsc.com/support/guides/player-details/#player) ## Find an event across servers Choose Find events, search and use the filters for the records you can read. - [Review F7 reports and find events](https://rustsc.com/support/guides/review-player-reports/#find) ## Choose workspace alerts Open Alert settings and choose which alerts go to each destination. - [Choose where alerts go](https://rustsc.com/support/guides/alert-destinations/#alerts) ## Read activity across servers Open Activity and check which server each action concerned. - [See what your team did](https://rustsc.com/support/guides/team-activity/#steps) ## Connect another host Use Add host in the same workspace, then add its servers after it connects. - [Add a host to your workspace](https://rustsc.com/support/guides/add-host/#steps) ## Give access to selected servers or hosts Choose the role and limit the invitation to the selected servers and hosts. - [Give someone access to only some servers or hosts](https://rustsc.com/support/guides/limited-access/#steps) ## Preview a change on several servers from a script Use the customer API to check which servers can run an action before applying the change. - [Developer documentation](https://rustsc.com/help/v1/reference/#createBulkPlan) ## Use a saved Nexus network on several servers Choose the same saved network on each server that should use it. - [Save Nexus network settings for a server](https://rustsc.com/support/guides/save-nexus-network-settings/#select-network) ## Connect a rented server to your workspace Choose Connect a rented server, enter the requested details and read the connection check. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#connect) HTML version: https://rustsc.com/support/guides/reference-server-groups/ --- # Community features reference Find a specific action or setting for community features and open the related instructions in RustSC. ## Keep an existing community store When adopting a server, review the plugins and settings your existing store uses before changing them. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/#manage) HTML version: https://rustsc.com/support/guides/reference-community-features/ --- # Getting started reference Find a specific action or setting for getting started and open the related instructions in RustSC. ## Sign up Sign up and open your workspace. - [Your first server in RustSC](https://rustsc.com/support/guides/first-server/#steps) ## Your first server Follow the setup steps until the server is running. - [Your first server in RustSC](https://rustsc.com/support/guides/first-server/#expect) ## Find your workspace Choose the workspace you want to manage. - [Manage workspace access](https://rustsc.com/support/guides/workspace-access/#access) ## Install on Linux Copy the install command from the portal and run it on the host. - [Install RustSC on Linux](https://rustsc.com/support/guides/install-linux/#install) ## Install on Windows Copy the Windows command from the portal and run it in PowerShell on the host. - [Install RustSC on Windows](https://rustsc.com/support/guides/install-windows/#install) ## Install command Copy a new command if the old one expires or has already been used. - [Install RustSC on Linux](https://rustsc.com/support/guides/install-linux/#command) ## Host not connected Check the host connection and reconnect it if needed. - [Host offline](https://rustsc.com/support/guides/computer-offline/#check) ## Reconnect a host Reconnect the host without reinstalling its servers. - [Reconnect a host](https://rustsc.com/support/guides/reconnect-computer/#reconnect) ## Add a server Add and install a server from the portal. - [Add your first server](https://rustsc.com/support/guides/add-server/#add) ## Choose a server folder Choose where the server files go. - [Choose a server folder](https://rustsc.com/support/guides/server-folder/#folder) ## Ready to start Start the server when installation finishes. - [Your first server in RustSC](https://rustsc.com/support/guides/first-server/#expect) ## Add an existing server Add a server you already run. - [Add an existing server](https://rustsc.com/support/guides/add-existing-server/#add) ## Check an existing server Review the server RustSC found before continuing. - [Move a server you already run into RustSC](https://rustsc.com/support/guides/move-existing-server/#expect) ## Keep a running server Adding an existing server does not stop a game another tool runs. - [Move a server you already run into RustSC](https://rustsc.com/support/guides/move-existing-server/#expect) ## Run beside another tool Add an existing server while another tool runs it. - [Move a server you already run into RustSC](https://rustsc.com/support/guides/move-existing-server/#switching) ## Switch management tools Choose when to use RustSC for the server. - [Move a server you already run into RustSC](https://rustsc.com/support/guides/move-existing-server/#switching) ## Review server settings Review what RustSC finds when adding an existing server. - [Add an existing server](https://rustsc.com/support/guides/add-existing-server/#add) ## Server folders Check the folder choice before adding the server. - [Choose a server folder](https://rustsc.com/support/guides/server-folder/#folder) ## Connect a rented server Check your host details and connect the server. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#connect) ## Replace a server Review the replacement steps for a server on a new host. - [Move a server to a new host](https://rustsc.com/support/guides/move-to-new-host/#steps) ## Remove a server Remove a server from RustSC while keeping its files. - [Remove a server from RustSC](https://rustsc.com/support/guides/remove-server/#remove) ## Remove a host Remove a host and choose what to do with its server records. - [Remove a host from RustSC](https://rustsc.com/support/guides/remove-host/#remove) ## Rename a server Change the server name in its settings. - [Change server settings](https://rustsc.com/support/guides/server-settings/#settings) ## First server setup Follow the setup steps from connecting the host to starting the server. - [Your first server in RustSC](https://rustsc.com/support/guides/first-server/#steps) HTML version: https://rustsc.com/support/guides/reference-getting-started/ --- # Help and feedback reference Find a specific action or setting for help and feedback and open the related instructions in RustSC. ## Contact support Open Help in the portal, choose the topic and send a message describing what happened. - [Get help](https://rustsc.com/support/guides/get-help/#steps) ## Attach a screenshot or log Add files to the request or paste a screenshot. Review each attachment before sending. - [Get help](https://rustsc.com/support/guides/get-help/#steps) ## Check whether support received a request Look for the receipt before sending the same request again. If sending failed, use the action shown on the form. - [Get help](https://rustsc.com/support/guides/get-help/#problems) ## Collect a support file Create the support file on the affected host and read its README before sharing it. - [Get help](https://rustsc.com/support/guides/get-help/#file) ## Receive a support reply After the portal confirms receipt, check the email address on your account for the reply. - [Get help](https://rustsc.com/support/guides/get-help/#steps) ## Get back into your account Use a linked sign-in method or passkey you still control. Open account recovery if you cannot get in. - [Open the page](https://rustsc.com/account-recovery/index.html.md) ## Find the support form Choose the support topic on the website, then follow the contact link to send your request. - [Open the page](https://rustsc.com/support/contact/index.html.md) ## Report an accessibility problem Open Accessibility on the website for the contact route. Include the affected page and what you were trying to do. - [Open the page](https://rustsc.com/accessibility/index.html.md) ## Read help for a field Open the information button next to a setting for an explanation before changing it. - [Get help](https://rustsc.com/support/guides/get-help/#steps) ## Act on a failure message Open the result, read the failed step and follow the recovery action offered there. - [An action failed or stopped](https://rustsc.com/support/guides/action-failed/#recover) ## Choose a support topic Open Support to choose a task guide, a troubleshooting topic or a way to contact RustSC. - [Open the page](https://rustsc.com/support/index.html.md) ## Browse the help by task Open Guides and start with the group for setup, server tasks, backups, players, troubleshooting or your account. - [Open the page](https://rustsc.com/support/guides/index.html.md) ## Search the documentation Use the search control in Support and enter the name of the action or the words from the message you saw. - [Open the page](https://rustsc.com/support/guides/index.html.md) ## Understand a partial result Open the action details and check which steps completed before repeating any change. - [What a message means and what to do](https://rustsc.com/support/guides/fix-common-problems/#some-changes-were-made) ## Troubleshoot a host Check the host’s status first, then follow the matching connection or server-start guide. - [If something is not working](https://rustsc.com/support/guides/not-working/#steps) ## Check from the host itself On Linux run rustsc status. On Windows open RustSC on the host to check its connection and local servers. - [Control a server on its host](https://rustsc.com/support/guides/offline-server-control/#linux) ## Find a connection problem If the portal shows the host offline, check that the computer is on and connected before reconnecting it. - [Host offline](https://rustsc.com/support/guides/computer-offline/#check) ## Translate portal help Use your browser’s translation control to read web pages in another language. Copy commands as shown. - [Get help](https://rustsc.com/support/guides/get-help/#steps) ## Send feedback Choose Feedback in the portal, select a problem or idea, describe it and choose Send. - [Get help](https://rustsc.com/support/guides/get-help/#feedback) ## Vote on the roadmap Open Roadmap in the feedback window. Vote on an idea or take back an earlier vote. - [Get help](https://rustsc.com/support/guides/get-help/#feedback) ## Find the member roadmap Choose Feedback in the signed-in portal and open Roadmap to see the proposals and cast a vote. - [Get help](https://rustsc.com/support/guides/get-help/#feedback) ## Read release notes Open Release notes on the website to see the changes listed for published releases. - [Open the page](https://rustsc.com/release-notes/index.html.md) HTML version: https://rustsc.com/support/guides/reference-help-and-feedback/ --- # Host maintenance reference Find a specific action or setting for host maintenance and open the related instructions in RustSC. ## Host update status Open This host to see host update information. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/#windows) ## Windows update choice View the Windows update choice on the host and change it in the portal. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/#windows) ## Host update schedule Choose the options offered for the host restart schedule. - [Schedule a host restart](https://rustsc.com/support/guides/schedule-host-restart/#restart) ## Windows update timing Use host update help to see the available timing choices. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-host) ## Windows restart settings Use host update help to see the available restart settings. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-host) ## Install host updates Use the host update command help to see available controls. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-host) ## Restart a host A host restart warns players, stops servers and starts them after the host returns. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/#windows) ## Operating system updates Check the controls available for the host's operating system. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-host) ## Host settings Open This host to view update settings. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/#windows) ## Restart a Windows host Choose Restart this host. RustSC warns players, saves and stops the servers, then starts them after the host returns. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/#windows) ## Schedule a host restart Choose when the host restarts. - [Schedule a host restart](https://rustsc.com/support/guides/schedule-host-restart/#restart) ## Restart when needed Choose the available restart schedule options. - [Schedule a host restart](https://rustsc.com/support/guides/schedule-host-restart/#restart) ## Server and host restarts Review the host restart schedule and server choices. - [Schedule a host restart](https://rustsc.com/support/guides/schedule-host-restart/#restart) ## Host restart schedule Choose a schedule for a host restart. - [Schedule a host restart](https://rustsc.com/support/guides/schedule-host-restart/#restart) ## After a host restart Servers start after a host restart when their settings call for it. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/#windows) ## After a host outage Check the host and its connection before reconnecting. - [Host offline](https://rustsc.com/support/guides/computer-offline/#check) ## Update RustSC Use the host update controls to check and install updates. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/#host-update) ## Automatic RustSC updates Choose whether RustSC updates automatically on the Windows host. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/#windows) ## RustSC update choices Check the RustSC update choices shown on the host. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/#windows) ## RustSC update recovery The Windows app shows the result of a RustSC update. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/#windows) ## RustSC updates Check for a host update and review its result. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/#host-update) ## RustSC update available Check This host for an offered update. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/#windows) ## Windows app updates Check for RustSC updates from This host. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/#windows) ## Update from a terminal Use the update commands on the host. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-update) ## RustSC updates on Linux Use the installed host update help to see the update controls. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-update) ## Maintenance alerts Choose the alerts and destinations you need. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/#alerts) ## Free disk space Review files that can be cleaned up. - [Free disk space](https://rustsc.com/support/guides/free-disk-space/#files) ## Maintenance activity List recent local actions on the host. - [Schedules and activity on the host](https://rustsc.com/support/guides/host-schedules-activity/#activity) HTML version: https://rustsc.com/support/guides/reference-host-maintenance/ --- # Hosts reference Find a specific action or setting for hosts and open the related instructions in RustSC. ## A host for your servers Connect a Windows or Linux host to your workspace. - [Add a host to your workspace](https://rustsc.com/support/guides/add-host/#steps) ## Windows and Linux hosts Choose the install command for the host's operating system. - [Add a host to your workspace](https://rustsc.com/support/guides/add-host/#steps) ## Connect a host Use the install command for the host's operating system. - [Add a host to your workspace](https://rustsc.com/support/guides/add-host/#steps) ## Hosts list Open Hosts to see the hosts in your workspace. - [Add a host to your workspace](https://rustsc.com/support/guides/add-host/#steps) ## Host details Open a host to see its servers and details. - [Add a host to your workspace](https://rustsc.com/support/guides/add-host/#steps) ## Host connection Check when a host was last seen. - [Host offline](https://rustsc.com/support/guides/computer-offline/#check) ## Servers on a host Open a host to see the servers on it. - [Add a host to your workspace](https://rustsc.com/support/guides/add-host/#steps) ## Several hosts Connect another host to the workspace in the same way. - [Add a host to your workspace](https://rustsc.com/support/guides/add-host/#steps) ## Reconnect a host Reconnect a host to your workspace. - [Reconnect a host](https://rustsc.com/support/guides/reconnect-computer/#reconnect) ## Rename a host Open the host and change its name. - [Add a host to your workspace](https://rustsc.com/support/guides/add-host/#steps) ## Host performance Open a host to check its performance and logs. - [Check a host’s performance and logs](https://rustsc.com/support/guides/host-performance-and-logs/#performance) ## Host alerts Choose which alerts to receive and where they go. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/#alerts) ## Remove a host Remove a host from RustSC and choose what to do with its server records. - [Remove a host from RustSC](https://rustsc.com/support/guides/remove-host/#remove) ## Remove RustSC from a host Choose whether to uninstall RustSC when removing a connected host. - [Remove a host from RustSC](https://rustsc.com/support/guides/remove-host/#remove) ## Windows app Use the Windows app on the host to control a server. - [Control a server on its host](https://rustsc.com/support/guides/offline-server-control/#windows) ## Windows notification area Closing the window leaves RustSC running in the notification area. - [Install RustSC on Windows](https://rustsc.com/support/guides/install-windows/#install) ## Connect from Windows Paste a connection code into RustSC on the host. - [Reconnect a host](https://rustsc.com/support/guides/reconnect-computer/#reconnect) ## Server controls on Windows Start, stop or restart a server from its host. - [Control a server on its host](https://rustsc.com/support/guides/offline-server-control/#windows) ## Console on Windows Read the console and send commands on the host. - [Control a server on its host](https://rustsc.com/support/guides/offline-server-control/#windows-console) ## Windows maintenance Update the game and manage server maintenance on the host. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/#windows) ## Support file Save a support file on the host and attach it to a request. - [Get help](https://rustsc.com/support/guides/get-help/#file) ## Host commands Use the command reference to find controls and installed help. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#before) ## Commands in scripts Use the installed command help to see available options. - [Find more host commands](https://rustsc.com/support/guides/host-command-line/#help) ## Servers during a connection outage A game and approved local schedules can keep running when the cloud is unreachable. - [Host offline](https://rustsc.com/support/guides/computer-offline/#check) ## Local control Control a server on its host while its workspace connection is down. - [Control a server on its host](https://rustsc.com/support/guides/offline-server-control/#linux) ## Use controls on the host Use the app or terminal while signed in on the host. - [Control a server on its host](https://rustsc.com/support/guides/offline-server-control/#windows) ## Another account's folder Use the host command help to see how to allow another account's folder. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-allow-account) ## Host command line Use the host command help to find local controls. - [Find more host commands](https://rustsc.com/support/guides/host-command-line/#help) ## Rented servers Connect a rented server and see what its host allows. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#connect) HTML version: https://rustsc.com/support/guides/reference-hosts/ --- # Server lifecycle reference Find a specific action or setting for server lifecycle and open the related instructions in RustSC. ## Start a server Start a server from its page. - [Start, stop or restart a server](https://rustsc.com/support/guides/start-stop-restart/#control) ## Stop with a warning Warn players before stopping the server. - [Start, stop or restart a server](https://rustsc.com/support/guides/start-stop-restart/#warnings) ## Restart a server Restart a server and cancel a pending countdown if needed. - [Start, stop or restart a server](https://rustsc.com/support/guides/start-stop-restart/#control) ## Save the world Send a save command from the server console. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-console) ## End an unresponsive game Use the host controls to end a game that cannot stop normally. - [Control a server on its host](https://rustsc.com/support/guides/offline-server-control/#windows) ## Server status Wait for the server to move from starting to running. - [Your first server in RustSC](https://rustsc.com/support/guides/first-server/#expect) ## Read the console Open Console to read recent game messages. - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/#console) ## Find a failed action Open the action result to see what happened and the next step. - [An action failed or stopped](https://rustsc.com/support/guides/action-failed/#recover) ## Start without waiting for extra checks If a backup before a start fails, the server can start and report a warning. - [Start, stop or restart a server](https://rustsc.com/support/guides/start-stop-restart/#control) ## A change did not finish Read the action result before trying again. - [An action failed or stopped](https://rustsc.com/support/guides/action-failed/#recover) ## Crash recovery Use the server recovery commands to see or change automatic recovery. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-server) ## Recovery hold Use the server command help to see recovery controls. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-server) ## A server is not answering Read the server's status and follow the next step. - [Server will not start](https://rustsc.com/support/guides/server-will-not-start/#check) ## Start with the host Choose whether a server starts with its host. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-server) ## Recover a damaged save Choose how to recover a damaged save. - [Recover a damaged save](https://rustsc.com/support/guides/recover-save/#recover) ## Programs around a start Use the server helper commands to manage programs started around a server start. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-server) ## Another tool runs the game Add a server without stopping a game another tool runs. - [Move a server you already run into RustSC](https://rustsc.com/support/guides/move-existing-server/#switching) ## Recovery settings See or change the host's server recovery setting. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-server) ## Servers on a host Open the host to see its servers. - [Add a host to your workspace](https://rustsc.com/support/guides/add-host/#steps) ## Control from the host Use local controls when working at the host. - [Control a server on its host](https://rustsc.com/support/guides/offline-server-control/#windows) ## Control without the cloud Use local controls on the host. - [Control a server on its host](https://rustsc.com/support/guides/offline-server-control/#linux) ## Keep restarts short Choose Restart to warn players and restart the game. - [Start, stop or restart a server](https://rustsc.com/support/guides/start-stop-restart/#control) ## Rented server controls Check which controls the hosting company makes available. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#connect) HTML version: https://rustsc.com/support/guides/reference-server-lifecycle/ --- # Live maps reference Find a specific action or setting for live maps and open the related instructions in RustSC. ## Open the live map Open Map for a running server with the RustSC plugin. - [Use the live map](https://rustsc.com/support/guides/live-map/#map) ## Choose map layers Use Layers to show the types of markers you need. - [Use the live map](https://rustsc.com/support/guides/live-map/#map) ## Show events on the map Choose the event layer and select a marker to inspect what is available. - [Use the live map](https://rustsc.com/support/guides/live-map/#map) ## Find map markers Use the map's list and search to narrow the markers you see. - [Use the live map](https://rustsc.com/support/guides/live-map/#map) ## Pin map markers Pin a marker in the list when you want to keep it in view. - [Use the live map](https://rustsc.com/support/guides/live-map/#map) ## Select a map marker Select a marker to open its available details and actions. - [Use the live map](https://rustsc.com/support/guides/live-map/#map) ## Move a player in game Choose Move from the player menu where offered and review the destination. - [Help a player in game](https://rustsc.com/support/guides/player-actions/#actions) ## Watch a live map Keep Map open to follow reported world changes while the game runs. - [Use the live map](https://rustsc.com/support/guides/live-map/#map) ## Find out why a map is unavailable Read the reason shown in Map and follow its next step. - [Use the live map](https://rustsc.com/support/guides/live-map/#map) ## Count things on the map Open World tools → Counts and choose Count. - [Find and inspect things on the live map](https://rustsc.com/support/guides/find-things-on-the-map/#find) ## Find things by name, type, owner or place Use Find things and fill in the filters you need. - [Find and inspect things on the live map](https://rustsc.com/support/guides/find-things-on-the-map/#find) ## Inspect one thing Choose Inspect on a result to read its location, owner or contents when shown. - [Find and inspect things on the live map](https://rustsc.com/support/guides/find-things-on-the-map/#find) ## Inspect a tool cupboard Find a cupboard and inspect it to read the details the server returns. - [Find and inspect things on the live map](https://rustsc.com/support/guides/find-things-on-the-map/#find) ## Remove one thing from the world Inspect it first and check its name and location in the removal confirmation. - [Find and inspect things on the live map](https://rustsc.com/support/guides/find-things-on-the-map/#remove) ## Inspect and remove a building Choose Inspect building where offered and review what will be removed. - [Find and inspect things on the live map](https://rustsc.com/support/guides/find-things-on-the-map/#remove) ## Confirm the exact item to remove Review the selected item and any contents before confirming. - [Find and inspect things on the live map](https://rustsc.com/support/guides/find-things-on-the-map/#remove) ## See what a player built Open the player's overview and look for What this player built. - [Find and inspect things on the live map](https://rustsc.com/support/guides/find-things-on-the-map/#player-built) ## Check whether you can remove an item Read the available actions after Inspect and confirm Remove only when it is offered. - [Find and inspect things on the live map](https://rustsc.com/support/guides/find-things-on-the-map/#remove) ## Inspect the map with workspace access Use the signed-in Map tools when your role allows it. Inspect never shows a lock code. - [Find and inspect things on the live map](https://rustsc.com/support/guides/find-things-on-the-map/#find) ## Find things in the world from a script Use the customer API to find things by type, name, owner or area. - [Developer documentation](https://rustsc.com/help/v1/reference/#findWorldEntities) HTML version: https://rustsc.com/support/guides/reference-live-maps/ --- # Maps and worlds reference Find a specific action or setting for maps and worlds and open the related instructions in RustSC. ## Set up a new server's map Review the new server's settings before you install and start it. - [Add your first server](https://rustsc.com/support/guides/add-server/#add) ## Set a generated map's size and seed Choose Generated, enter the World size and Seed, and check the preview. - [Preview your map](https://rustsc.com/support/guides/preview-map/#steps) ## Preview a generated map Choose Larger picture in the preview to see more before using the map. - [Preview your map](https://rustsc.com/support/guides/preview-map/#steps) ## Shuffle for a different map Choose Shuffle to draw another map before committing to one. - [Preview your map](https://rustsc.com/support/guides/preview-map/#steps) ## Choose a map for the next wipe Choose Choose a map in the wipe form and review the offered map types. - [Wipe your server](https://rustsc.com/support/guides/wipe-server/#wipe) ## Choose a custom map from a link Choose Custom in the map picker and enter a public file link. - [Use a link to a custom map](https://rustsc.com/support/guides/use-a-custom-map-link/#address) ## Use a supported map file share link Paste a Dropbox or Google Drive file share link and check the download address RustSC shows. - [Use a link to a custom map](https://rustsc.com/support/guides/use-a-custom-map-link/#address) ## Check a custom map link Use the customer API to see whether the public address serves a file. - [Developer documentation](https://rustsc.com/help/v1/reference/#checkMapLink) ## See a custom map before starting Open the stopped server's Map tab to see the picture drawn from the map file. - [Preview your map](https://rustsc.com/support/guides/preview-map/#custom) ## Read the current map Open Map to check the world the running server is showing. - [Use the live map](https://rustsc.com/support/guides/live-map/#map) ## Compare the current and saved maps Read the world in use and the saved map before applying a change. - [Change server settings](https://rustsc.com/support/guides/server-settings/#settings) ## Review the map before a wipe Check the selected map in What will happen before confirming. - [Wipe your server](https://rustsc.com/support/guides/wipe-server/#wipe) ## Review a conflicting server setting Compare the saved settings and the values read from the server before replacing them. - [Review settings changed outside RustSC](https://rustsc.com/support/guides/review-server-setting-changes/#compare) ## Look at the next wipe's map Open the map preview in the wipe form and choose Use this map if you want it. - [Preview your map](https://rustsc.com/support/guides/preview-map/#steps) ## Put maps in a rotation Choose Rotate through a list of maps and put the maps in the order you want. - [Plan a map rotation for wipes](https://rustsc.com/support/guides/plan-a-map-rotation/#rotation) ## Choose what comes after the last map Under After the last map, choose Repeat list or Random maps. - [Plan a map rotation for wipes](https://rustsc.com/support/guides/plan-a-map-rotation/#rotation) ## Check which map comes next Find the map marked Next wipe. Previewing the rotation leaves it in place. - [Plan a map rotation for wipes](https://rustsc.com/support/guides/plan-a-map-rotation/#rotation) ## Find a generated map to use Preview the size and seed or use Shuffle to look for another map. - [Preview your map](https://rustsc.com/support/guides/preview-map/#steps) ## Choose a wipe map from the host command line Run rustsc wipe --help to see how to choose the map before confirming a wipe. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-wipe) ## Read map choices from a script Use the customer API to look up the available map choices. - [Developer documentation](https://rustsc.com/help/v1/reference/#getMapChoices) ## Check whether the server can show its map Open Map and read its reason if the map is unavailable to you. - [Use the live map](https://rustsc.com/support/guides/live-map/#map) HTML version: https://rustsc.com/support/guides/reference-maps-and-worlds/ --- # Portal on a phone reference Find a specific action or setting for portal on a phone and open the related instructions in RustSC. ## Use the portal in a phone browser Open the portal in your browser and sign in with your usual account. Use the navigation menu to switch between your workspace pages. - [Manage workspace access](https://rustsc.com/support/guides/workspace-access/#access) HTML version: https://rustsc.com/support/guides/reference-portal-on-a-phone/ --- # Performance reference Find a specific action or setting for performance and open the related instructions in RustSC. ## Read game performance Open the server’s Performance tab for game frame rate, players, entities, processor use and memory. - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/#performance) ## Change the chart period Choose the period on Performance to compare recent readings with earlier days. - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/#performance) ## Compare a dip with a restart or wipe Use Restarts and wipes on Performance to find work near the time of a change in the charts. - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/#performance) ## Read an exact measurement Select a point on the chart or choose Show as table to read the figures. - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/#performance) ## Recognize missing readings A gap means there was no reading for that time. Check the host and game status before interpreting it. - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/#performance) ## Spot a slow server Compare the player count and frame rate in the server list, then open Performance for the details. - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/#performance) ## Review what needs attention Open the server Overview and follow a Needs attention item to the page that can resolve it. - [Server will not start](https://rustsc.com/support/guides/server-will-not-start/#check) ## Compare several servers Open All servers or a group to compare the player count and frame rate across the servers you can see. - [Manage several servers at once](https://rustsc.com/support/guides/bulk-actions/#compare) ## Read the host’s current load Open the host’s Performance page for its latest processor, memory, disk and network readings. - [Check a host’s performance and logs](https://rustsc.com/support/guides/host-performance-and-logs/#performance) ## Compare host load over time Change the period on the host charts and compare processor, memory, disk and network use. - [Check a host’s performance and logs](https://rustsc.com/support/guides/host-performance-and-logs/#performance) ## Find which game is using the host Under Each game server, compare the games’ processor and memory use over the same period. - [Check a host’s performance and logs](https://rustsc.com/support/guides/host-performance-and-logs/#performance) ## Read host activity Open Logs on the host and find the relevant action and its result under Host activity. - [Check a host’s performance and logs](https://rustsc.com/support/guides/host-performance-and-logs/#logs) ## Filter host logs Open Log lines, narrow the severity or search for a word around the time of the problem. - [Check a host’s performance and logs](https://rustsc.com/support/guides/host-performance-and-logs/#logs) ## Investigate a game exit Open Game exits and check the time and reason against host activity and the server console. - [Check a host’s performance and logs](https://rustsc.com/support/guides/host-performance-and-logs/#logs) ## Read the startup console Open Console while the game starts. If a start fails, open its result to find the stage that stopped. - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/#console) ## Share diagnostics with support Create the support file on the affected computer, read it and attach it to the support request. - [Get help](https://rustsc.com/support/guides/get-help/#file) ## See measurements at the host Use the installed logs help to choose the lines to read. Use server metrics for the most recent game figures. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-logs) ## Read measurements from a script Open the Performance section in the customer API reference for its available readings, inputs and responses. - [Developer documentation](https://rustsc.com/help/v1/reference/index.html.md) ## Set a performance alert Choose the host or server alert in Alerts, review its settings and choose where to send it. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/#alerts) ## Check measurements on a rented server Open the connected rented server and check which readings its hosting connection offers. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#fix) HTML version: https://rustsc.com/support/guides/reference-performance/ --- # Player permissions reference Find a specific action or setting for player permissions and open the related instructions in RustSC. ## Open server permissions Choose Players → Permissions and select a server. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/#steps) ## Manage Oxide or Carbon permissions Open the server's permissions page to manage the framework's groups and players. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/#steps) ## Check when a permission change took effect Read Last change after changing a group or permission. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/#steps) ## Restart to apply permissions when needed Choose Restart now to apply if the result says a restart is needed. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/#problems) ## Make a permission group Choose Make a group, then give it a name and title. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/#steps) ## Give a group the permissions of another group Edit the group and select its parent under Gets everything from. - [Keep player permissions the same across servers](https://rustsc.com/support/guides/sync-player-permissions/#group-inheritance) ## Add players to a group Choose Add a player and search by name or paste Steam IDs. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/#steps) ## Give permissions to a group Choose Give permissions and tick what members can do. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/#steps) ## Check a player's own permissions Open a player in Permissions to review their groups and direct grants. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/#steps) ## Review where permissions are set Check the player's groups and their own permissions separately. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/#steps) ## Look up permissions by plugin Use Permissions from the plugin's page to see the relevant grants. - [Edit a plugin's settings and messages](https://rustsc.com/support/guides/edit-plugin-settings-and-language/#controls) ## Set a player's in-game staff level Use the Staff view to set their level and check what that level grants. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/#staff) ## See in-game staff Use Staff in the server's Permissions view. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/#staff) ## Check staff actions Open Staff and use only the staff levels offered to your account. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/#staff) ## See which grants require the workspace owner Only the workspace owner can give permissions marked as needing an owner. - [Keep player permissions the same across servers](https://rustsc.com/support/guides/sync-player-permissions/#group-inheritance) ## Restore an in-game staff role after a ban When banning an owner or moderator on one server, leave the option to give the role back when the ban ends selected. - [Keep player permissions the same across servers](https://rustsc.com/support/guides/sync-player-permissions/#staff-roles) ## Read permission history Open History on the Permissions page to see earlier changes. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/#steps) ## Put the prior permissions back Choose Put the earlier version back when the change still offers it. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/#problems) ## Save or reuse a permission list Open Saved lists on a server's Permissions page and review the list before applying it. - [Keep player permissions the same across servers](https://rustsc.com/support/guides/sync-player-permissions/#lists) ## Sync permissions across selected servers Preview the initial additions before choosing Turn on sync. - [Keep player permissions the same across servers](https://rustsc.com/support/guides/sync-player-permissions/#start-sync) ## Preview the same permission changes on several servers Use the customer API to preview a list of group or permission changes on servers using the same framework. - [Keep player permissions the same across servers](https://rustsc.com/support/guides/sync-player-permissions/#bulk-permissions-api) ## Sync a Discord role with a Rust group Choose the role, group, server and the direction of the sync before saving. - [Connect Discord chat and roles](https://rustsc.com/support/guides/discord-chat-roles/#roles) ## Keep staff roles through an ordinary wipe Review what the wipe resets. A standard wipe on your own host keeps staff roles and framework permissions. - [Keep player permissions the same across servers](https://rustsc.com/support/guides/sync-player-permissions/#staff-roles) ## Read player permissions from a script Use the customer API to read a server's groups, player permissions and staff. - [Developer documentation](https://rustsc.com/help/v1/reference/#readServerPlayerPermissions) HTML version: https://rustsc.com/support/guides/reference-player-permissions/ --- # Players reference Find a specific action or setting for players and open the related instructions in RustSC. ## Open Players Open Players to find and manage the people on your servers. - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/#players) ## Find a player Search Players by name or Steam ID. - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/#players) ## Open the player menu Open a player's menu to see the actions available to you. - [View a player and take action](https://rustsc.com/support/guides/player-details/#player) ## Copy a player name or Steam ID Open the player menu, choose Copy and select Name, Steam ID or Both. - [View a player and take action](https://rustsc.com/support/guides/player-details/#player) ## Act on several players Select players and choose an action from the selection bar. - [Help a player in game](https://rustsc.com/support/guides/player-actions/#several) ## Open a player page Select the player and choose Open full page. - [View a player and take action](https://rustsc.com/support/guides/player-details/#player) ## Choose a server for a player On a player's page, choose the server whose details you want. - [View a player and take action](https://rustsc.com/support/guides/player-details/#player) ## Read Steam facts Open the player to see available Steam information. - [View a player and take action](https://rustsc.com/support/guides/player-details/#player) ## Read player history Open a player's page and choose History. - [View a player and take action](https://rustsc.com/support/guides/player-details/#player) ## Read player notes Open a player to read the private notes your team keeps. - [View a player and take action](https://rustsc.com/support/guides/player-details/#player) ## Use player labels Open a player to see your team's private labels. - [View a player and take action](https://rustsc.com/support/guides/player-details/#player) ## See the live map Open Map and choose the layers you want to see. - [Use the live map](https://rustsc.com/support/guides/live-map/#map) ## Kick a player Choose Kick from the player's menu and confirm. - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/#players) ## Manage game staff Open the player's permissions to manage their game staff role. - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/#staff) ## Message a player Choose Message in the player's menu and enter your message. - [Help a player in game](https://rustsc.com/support/guides/player-actions/#actions) ## Help a player Choose Heal from the player's menu and review the result. - [Help a player in game](https://rustsc.com/support/guides/player-actions/#actions) ## Move a player Choose Move from the player's menu and pick the destination. - [Help a player in game](https://rustsc.com/support/guides/player-actions/#actions) ## Give items Choose Give items from the player's menu and enter the details. - [Help a player in game](https://rustsc.com/support/guides/player-actions/#actions) ## Inspect a player's inventory Choose Look under What they carry; look again before confirming an item removal. - [Help a player in game](https://rustsc.com/support/guides/player-actions/#details) ## Edit an inventory Open the player page, choose Manage inventory, review the changes and choose Save changes. - [Help a player in game](https://rustsc.com/support/guides/player-actions/#details) ## Use an item set Open Item sets to save a group of items, then choose a set when giving items. - [Help a player in game](https://rustsc.com/support/guides/player-actions/#actions) ## Change blueprints Under Blueprints on the player page, choose Unlock blueprints or restore the earlier list. - [Help a player in game](https://rustsc.com/support/guides/player-actions/#details) ## Mute or freeze a player Choose Mute chat, Freeze or Release on the player's page and confirm. - [Help a player in game](https://rustsc.com/support/guides/player-actions/#details) ## Count what a player built Open the player's page and refresh What this player built. - [Help a player in game](https://rustsc.com/support/guides/player-actions/#details) ## Remove what a player built Review the count and confirmation under What this player built before removing it. - [Help a player in game](https://rustsc.com/support/guides/player-actions/#details) ## Track upkeep Choose the server and turn on Track upkeep in Discord settings. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/#upkeep) ## Tell players about upkeep Turn on Tell players and save the upkeep settings. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/#upkeep) ## Stop your upkeep messages A player can type /upkeep off in the game. - [Link your players to Discord](https://rustsc.com/support/guides/discord-link/#upkeep) ## Players at the host See connected players and use the player controls in the Windows app. - [Control a server on its host](https://rustsc.com/support/guides/offline-server-control/#windows-players) ## Players through the API List connected players through the customer API. - [Developer documentation](https://rustsc.com/help/v1/reference/#listConnectedPlayers) ## Check a player action Read the result before repeating an action. - [Help a player in game](https://rustsc.com/support/guides/player-actions/#actions) HTML version: https://rustsc.com/support/guides/reference-players/ --- # Plugins reference Find a specific action or setting for plugins and open the related instructions in RustSC. ## List installed plugins Open Plugins to see the plugin files on the server. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/#manage) ## See which plugins loaded Check the plugin status while the game is running and connected. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/#manage) ## Filter installed plugins Use Updates available or Failed to load to narrow the list. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/#manage) ## Update a plugin in a subfolder Update the listed plugin to replace that file in its own subfolder. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/#manage) ## Turn a plugin on or off Use Enable, Disable or Reload in the plugin's actions where offered. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/#manage) ## Remove a plugin and keep its file Remove moves the plugin file aside and keeps its settings and data. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/#manage) ## Check for plugin updates Choose Check for updates and look for an available version beside the plugin. - [Choose a plugin update source and go back if needed](https://rustsc.com/support/guides/plugin-update-source-and-recovery/#source) ## Choose a plugin update source Open the row menu and choose which marketplace listing to follow. - [Choose a plugin update source and go back if needed](https://rustsc.com/support/guides/plugin-update-source-and-recovery/#source) ## Update a plugin Check the source and version in the Update confirmation. - [Choose a plugin update source and go back if needed](https://rustsc.com/support/guides/plugin-update-source-and-recovery/#source) ## Roll an update back or forward Use Roll back or Roll forward where the plugin row offers them. - [Choose a plugin update source and go back if needed](https://rustsc.com/support/guides/plugin-update-source-and-recovery/#recover) ## Keep your own plugin version Choose My own version in the row menu to keep your file. - [Choose a plugin update source and go back if needed](https://rustsc.com/support/guides/plugin-update-source-and-recovery/#source) ## Save a plugin update preference Keep this plugin up to date saves the preference. Choose Update to install an available version. - [Choose a plugin update source and go back if needed](https://rustsc.com/support/guides/plugin-update-source-and-recovery/#source) ## Choose plugin updates at a wipe Set Plugin updates to All or Selected and use Hold for a plugin you want to keep. - [Choose a plugin update source and go back if needed](https://rustsc.com/support/guides/plugin-update-source-and-recovery/#source) ## Check what schedules use a plugin Use the schedule information beside an installed plugin to see which changes use it. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/#manage) ## Edit a plugin's files Open Settings from the plugin row, edit a file and review its changed lines before saving. - [Edit a plugin's settings and messages](https://rustsc.com/support/guides/edit-plugin-settings-and-language/#edit-file) ## Edit or add plugin languages Open Languages and keep the original message placeholders when translating. - [Edit a plugin's settings and messages](https://rustsc.com/support/guides/edit-plugin-settings-and-language/#languages) ## Find a plugin's commands Open Commands on the plugin's page to search and copy its registered console commands. - [Edit a plugin's settings and messages](https://rustsc.com/support/guides/edit-plugin-settings-and-language/#controls) ## Find a plugin's permissions Use the plugin's Permissions link to see its permissions and groups. - [Edit a plugin's settings and messages](https://rustsc.com/support/guides/edit-plugin-settings-and-language/#controls) ## Add the RustSC plugin Open Software to find the RustSC plugin for Oxide or Carbon. - [Install or update the RustSC plugin](https://rustsc.com/support/guides/rustsc-plugin/#install) ## Install the RustSC plugin from Software Choose Install in the RustSC plugin section when offered. - [Install or update the RustSC plugin](https://rustsc.com/support/guides/rustsc-plugin/#install) ## Read the installed plugin list from a script Use the customer API to read plugin files and their reported states. - [Developer documentation](https://rustsc.com/help/v1/reference/#listServerPlugins) ## Upload plugin files to a rented server Use Files if the rented server offers uploads, or the host's own panel. - [Install a plugin from a link or a file](https://rustsc.com/support/guides/install-plugin-from-a-link/#file) ## Search plugin marketplaces Open Add plugin and search by name or by what you need the plugin to do. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/#find) ## Read a plugin's listing Open a search result to read the details the marketplace provides. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/#find) ## Compare plugin listings Look beneath a grouped search result for other marketplace listings. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/#find) ## Filter and sort plugin results Use Filter and Sort to narrow the results. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/#find) ## Install an available uMod plugin Choose Install on a supported result and check whether the plugin loaded. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/#find) ## Check required plugins Review Needs on the result and install any dependency RustSC cannot add for you. - [Install a plugin from a link or a file](https://rustsc.com/support/guides/install-plugin-from-a-link/#address) ## Add a plugin by address Open More ways to add, choose Add by address and review the result before installing. - [Install a plugin from a link or a file](https://rustsc.com/support/guides/install-plugin-from-a-link/#address) ## Find a plugin by name Enter the plugin's name in Find plugins and check the matching result. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/#find) ## Open a marketplace listing Open the marketplace when a result sends you there to buy or download the plugin. - [Find and manage plugins](https://rustsc.com/support/guides/plugins/#find) ## Connect a Codefling account Open Integrations → Other and set up the Codefling account under Plugin marketplaces. - [Set up a workspace integration](https://rustsc.com/support/guides/workspace-integrations/#workspace-credentials) ## Connect a RustHQ account Open Integrations → Other and set up the RustHQ account under Plugin marketplaces. - [Set up a workspace integration](https://rustsc.com/support/guides/workspace-integrations/#workspace-credentials) ## Check a marketplace connection Use the integration's check action to test the saved connection. - [Set up a workspace integration](https://rustsc.com/support/guides/workspace-integrations/#workspace-credentials) HTML version: https://rustsc.com/support/guides/reference-plugins/ --- # Rented servers reference Find a specific action or setting for rented servers and open the related instructions in RustSC. ## Rented server capabilities Check what the host and your access allow. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#connect) ## Hosting company panel Use the hosting company's panel for work RustSC does not offer. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#connect) ## Connect a rented server Enter the details from your hosting company, check them and connect. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#connect) ## Choose a hosting company Select your hosting company when connecting a rented server. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#connect) ## Check what works Check what your hosting details allow before connecting. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#connect) ## Hosting key Enter the key requested for your rented server. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#connect) ## Change a rented connection Check the connection again, change its details or disconnect it. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#fix) ## No connection option Use the hosting company's panel for work RustSC cannot offer. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#connect) ## Rented server list A connected rented server appears with your other servers. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#connect) ## What works Check the available controls before connecting. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#connect) ## Rented server power Use the controls that your host makes available. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#connect) ## Rented server console Add the console details where offered to send commands. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#fix) ## Rented server files Use the available file connection for server files. - [Work with server files](https://rustsc.com/support/guides/manage-files/#files) ## Plugin files on a rented server Use the file connection where your host offers it. - [Work with server files](https://rustsc.com/support/guides/manage-files/#files) ## Rented server settings Check what your host and connection allow before changing server settings. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#connect) ## Hosting company schedules The hosting company keeps control of its own schedules. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#connect) ## Rented server schedules A rented server can have a scheduled restart; wipe availability depends on its host. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/#schedule) ## Manage players Use the controls available for the server and its host. - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/#players) ## RustSC plugin Install the RustSC plugin through a working file connection. - [Install or update the RustSC plugin](https://rustsc.com/support/guides/rustsc-plugin/#install) ## Server alerts Choose the alerts and destinations available for your servers. - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/#alerts) ## Hosting company controls Use the hosting company's panel for controls RustSC does not offer. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#connect) ## What your host allows Use your hosting company's panel for controls RustSC does not offer. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#connect) ## Hosting connection problem Check the hosting company's panel and try the connection again. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#fix) ## Multiple hosts Connect additional hosts in the same workspace. - [Add a host to your workspace](https://rustsc.com/support/guides/add-host/#steps) ## Move to your own host Add the server on a host you control after moving its files. - [Add an existing server](https://rustsc.com/support/guides/add-existing-server/#add) ## Rented server connection Connect through the available hosting company route. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#connect) HTML version: https://rustsc.com/support/guides/reference-rented-servers/ --- # Schedules reference Find a specific action or setting for schedules and open the related instructions in RustSC. ## See schedules Open Schedules to see upcoming work and its next run. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/#schedule) ## Add a schedule Choose Add schedule, select the task, set its time and save. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/#schedule) ## Switch a schedule off Use its switch in Schedules to stop it running without deleting it. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/#schedule) ## Check schedule history Open History on Schedules to see the result of a run. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/#problems) ## Schedule a restart Choose Restart, set the server and time, then save. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/#schedule) ## Schedule a game update Choose Update the game, set when it should run and save. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/#schedule) ## Schedule backups Choose Back up under Add schedule and save a time for the server. - [Back up a server](https://rustsc.com/support/guides/back-up-server/#backup) ## Schedule a wipe Choose Wipe under Add schedule, set the wipe and its timing, and save. - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/#schedule) ## Schedule a message Choose Send a message, write it, set a time and save. - [Schedule a message or command](https://rustsc.com/support/guides/schedule-messages-commands/#schedule) ## Schedule a command Choose Run a command, enter it, set a time and save. - [Schedule a message or command](https://rustsc.com/support/guides/schedule-messages-commands/#schedule) ## Schedule a Discord post Choose Post to Discord, choose a channel and save the message and time. - [Schedule a message or command](https://rustsc.com/support/guides/schedule-messages-commands/#schedule) ## Quiet alerts Choose Quiet time for alerts and save the scope, alerts and time. - [Set a quiet time for alerts](https://rustsc.com/support/guides/quiet-alerts/#quiet) ## Schedule a host restart Choose Restart the host, select the host and save its timing. - [Schedule a host restart](https://rustsc.com/support/guides/schedule-host-restart/#restart) ## Schedule Windows updates Where offered on a Windows host, choose Install host updates, review the timing and restart choices, then save. - [Schedule a host restart](https://rustsc.com/support/guides/schedule-host-restart/#restart) ## Choose when work repeats Choose Repeat and the days and time before saving. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/#schedule) ## Choose the server clock Schedules use the server's time zone and follow daylight saving. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/#schedule) ## Change player warnings Set the warning time and message before saving the schedule. - [Messages, restarts and wipes: what players see](https://rustsc.com/support/guides/player-messages/#change) ## Cancel a countdown Choose Cancel countdown in the server header while it is counting down. - [Messages, restarts and wipes: what players see](https://rustsc.com/support/guides/player-messages/#change) ## Check skipped work Open History on Schedules to see why a run did not happen. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/#problems) ## Pause usual restarts on wipe day In a scheduled wipe, choose Pause the usual restarts on the wipe day until the wipe and review the affected schedules before saving. - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/#schedule) ## Schedule work for several servers Where offered, choose several servers or a group in the schedule form, then review and save. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/#schedule) ## Keep schedules on the host Approved local schedules can continue on your host while it is offline; rented-server and Discord work needs a connection. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/#problems) ## Schedules on the host List and manage local schedules from a terminal on the host. - [Schedules and activity on the host](https://rustsc.com/support/guides/host-schedules-activity/#schedules) ## Schedules through the API Create a schedule through the customer API. - [Developer documentation](https://rustsc.com/help/v1/reference/#createSchedule) ## Schedules on a rented server The available schedules depend on what the hosting company supports. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/#schedule) HTML version: https://rustsc.com/support/guides/reference-schedules/ --- # Members and accounts reference Find a specific action or setting for members and accounts and open the related instructions in RustSC. ## Use several workspaces Sign in once, then choose the workspace you need from the workspace menu. - [Manage workspace access](https://rustsc.com/support/guides/workspace-access/#access) ## Switch or rename a workspace Use the workspace menu to switch. For a name change, open the intended workspace’s settings first. - [Manage workspace access](https://rustsc.com/support/guides/workspace-access/#access) ## Start a workspace Follow the sign-up option shown on the website. If it offers notifications, register your interest there. - [Your first server in RustSC](https://rustsc.com/support/guides/first-server/#steps) ## Choose a sign-in method Use an account you have linked or a passkey you have registered with RustSC. - [Manage your sign-in and security](https://rustsc.com/support/guides/account-sign-in-security/#methods) ## Add a passkey Open Sign-in and security and choose the passkey action. Follow the prompt on your device. - [Manage your sign-in and security](https://rustsc.com/support/guides/account-sign-in-security/#methods) ## Link or remove a sign-in account Review Sign-in accounts, add the method you want and keep a working way back in before removing one. - [Manage your sign-in and security](https://rustsc.com/support/guides/account-sign-in-security/#methods) ## Recover access Try a linked account or passkey first, then follow the account recovery page. - [Open the page](https://rustsc.com/account-recovery/index.html.md) ## Choose news by email In Your account set Product updates and news by email to the choice you want. - [Download your data or delete your account](https://rustsc.com/support/guides/account-data/#account-preferences) ## Invite a member From Members, invite the person and choose their role and the servers they may access. - [Give someone access to only some servers or hosts](https://rustsc.com/support/guides/limited-access/#steps) ## Accept a workspace invitation Open the invitation and sign in with the account you intend to use for that workspace. - [Give someone access to only some servers or hosts](https://rustsc.com/support/guides/limited-access/#steps) ## Choose a workspace role Review the listed roles and choose the least access that lets the person do their job. - [Understand workspace roles](https://rustsc.com/support/guides/workspace-roles/#roles) ## Give someone server operations access Choose Operator for a teammate who runs servers and review which servers they can reach. - [Understand workspace roles](https://rustsc.com/support/guides/workspace-roles/#roles) ## Give someone moderation access Choose Moderator for a teammate who manages players. Check the selected servers before saving. - [Understand workspace roles](https://rustsc.com/support/guides/workspace-roles/#roles) ## Give read-only access Choose Viewer for someone who needs to see server information without changing it. - [Understand workspace roles](https://rustsc.com/support/guides/workspace-roles/#roles) ## Restrict a teammate’s scope Choose specific servers or hosts when you set up the member’s access. - [Give someone access to only some servers or hosts](https://rustsc.com/support/guides/limited-access/#steps) ## Update a member’s access Open the person in Members, adjust their role or assigned servers and save the change. - [Give someone access to only some servers or hosts](https://rustsc.com/support/guides/limited-access/#existing) ## Understand a missing player detail Read the reason shown for the unavailable action. If it needs more access, ask a workspace owner to check your role. - [View a player and take action](https://rustsc.com/support/guides/player-details/#player) ## End a member’s access Open Members and choose the removal action for that person. Review the selected workspace before confirming. - [Give someone access to only some servers or hosts](https://rustsc.com/support/guides/limited-access/#existing) ## Transfer workspace ownership Use the ownership action in Members, select an eligible member and read how your own role will change. - [Download, hand over or close a workspace](https://rustsc.com/support/guides/workspace-data-closing/#hand-over) ## Define a custom role through the API Use the permission index and the role operations in the API reference to choose a role’s permitted actions. - [Developer documentation](https://rustsc.com/help/v1/permissions/#how) ## Set a workspace sign-in rule Choose the allowed methods and sign-in duration under Settings, People, Sign-in rule, then save. - [Choose how people sign in to a workspace](https://rustsc.com/support/guides/workspace-sign-in-rule/#set-rule) ## Resume after a sign-in expires If a page asks you to sign in again, use its sign-in action and return to your original tab to continue. - [Manage your sign-in and security](https://rustsc.com/support/guides/account-sign-in-security/#methods) ## Sign out another device Open Sign-in and security, find the device in the list of sessions and sign it out. - [Manage your sign-in and security](https://rustsc.com/support/guides/account-sign-in-security/#sessions) ## Review an unfamiliar sign-in Check the recent sign-in activity and sign out sessions you do not recognize. - [Manage your sign-in and security](https://rustsc.com/support/guides/account-sign-in-security/#sessions) ## Download account data Open Your account, then Your data and Download a copy of my data. - [Download your data or delete your account](https://rustsc.com/support/guides/account-data/#personal-data) ## Review account deletion Check the effect on owned workspaces and resolve any ownership requirement before confirming deletion. - [Download your data or delete your account](https://rustsc.com/support/guides/account-data/#delete-account) ## Choose a workspace time zone Set Workspace time zone under Settings, General. Review the time zone on each schedule when setting its time. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/#schedule) ## Export workspace data Open the workspace data settings and request the export for the intended workspace. - [Download, hand over or close a workspace](https://rustsc.com/support/guides/workspace-data-closing/#export-workspace) ## Close or recover a workspace Review the closing date and any available recovery action on the workspace data page. - [Download, hand over or close a workspace](https://rustsc.com/support/guides/workspace-data-closing/#close-workspace) ## Read workspace activity Find the operation in Activity and open its details to check the result on each server. - [See what your team did](https://rustsc.com/support/guides/team-activity/#steps) ## Identify a staff change Use workspace Activity to see who requested a change and what happened to it. - [See what your team did](https://rustsc.com/support/guides/team-activity/#scope) ## Set a workspace chat name If you own or administer the workspace, use Chat identity in Your account to choose your name there. - [Download your data or delete your account](https://rustsc.com/support/guides/account-data/#account-preferences) ## Manage account email Use Your account to set your news preference. Watch the account inbox for invitations and account notices. - [Download your data or delete your account](https://rustsc.com/support/guides/account-data/#account-preferences) ## Read the support access policy Read the support access section of the privacy policy before sending a support request. - [Open the page](https://rustsc.com/privacy/index.html.md) ## Manage members from a script Check the Members permissions and corresponding actions in the customer API reference before changing workspace access. - [Developer documentation](https://rustsc.com/help/v1/permissions/#members) HTML version: https://rustsc.com/support/guides/reference-members-and-accounts/ --- # Access and privacy reference Find a specific action or setting for access and privacy and open the related instructions in RustSC. ## Adopt an existing setup Review what RustSC found. Changes to how your game runs are made through the features you choose to use. - [Move a server you already run into RustSC](https://rustsc.com/support/guides/move-existing-server/#expect) ## Keep control of a running server If the portal cannot reach the host, check the game from the host before repeating a start or restart. - [Control a server on its host](https://rustsc.com/support/guides/offline-server-control/#windows) ## Manage the game locally Use the Windows host app or the Linux command line when the cloud connection is unavailable. - [Control a server on its host](https://rustsc.com/support/guides/offline-server-control/#linux) ## Give each teammate an account Invite the member with their own account and select the access they need. - [Give someone access to only some servers or hosts](https://rustsc.com/support/guides/limited-access/#steps) ## Change who can manage a server Open Members, choose the person’s access and select their role and permitted servers. - [Give someone access to only some servers or hosts](https://rustsc.com/support/guides/limited-access/#existing) ## Check the workspace first Use the workspace menu to choose the community whose servers and settings you intend to manage. - [Manage workspace access](https://rustsc.com/support/guides/workspace-access/#access) ## Add another way to sign in Open Sign-in and security to add a passkey or link another offered sign-in account. - [Manage your sign-in and security](https://rustsc.com/support/guides/account-sign-in-security/#methods) ## Replace an integration key Enter the replacement in the integration’s settings and check the connection there. - [Set up a workspace integration](https://rustsc.com/support/guides/workspace-integrations/#workspace-credentials) ## Reconnect a known host Use the reconnect steps for the intended workspace and verify that the host shows Connected. - [Reconnect a host](https://rustsc.com/support/guides/reconnect-computer/#reconnect) ## Update the host application Check for a RustSC update from the host and review the result after installation. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/#host-update) ## See who changed something Open Activity, find the action and read who requested it, the affected server and the result. - [See what your team did](https://rustsc.com/support/guides/team-activity/#steps) ## Understand support access See the privacy policy for what support accesses and how it is kept confidential. - [Open the page](https://rustsc.com/privacy/index.html.md) ## Get a copy of your data Download your account data from Your account. Workspace owners can also export workspace data from Settings. - [Download your data or delete your account](https://rustsc.com/support/guides/account-data/#personal-data) ## Keep staff notes private Use the player’s workspace record for staff notes and labels. Access depends on the member’s role. - [View a player and take action](https://rustsc.com/support/guides/player-details/#player) ## Limit a script Create a key with the role, servers and expiry the tool actually needs. Revoke it when you stop using the tool. - [Make, limit or revoke an API key](https://rustsc.com/support/guides/make-api-key/#make-key) ## Resolve a host access problem Read the host message and use the repair action when offered. Check the result before retrying the original task. - [What a message means and what to do](https://rustsc.com/support/guides/fix-common-problems/#folders-and-permissions) ## Check a rental before connecting it Choose the hosting company and check the connection to see which actions are available for that server. - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/#connect) HTML version: https://rustsc.com/support/guides/reference-access-and-privacy/ --- # Software updates reference Find a specific action or setting for software updates and open the related instructions in RustSC. ## Install a server Add a server and install its game files. - [Add your first server](https://rustsc.com/support/guides/add-server/#add) ## Choose a game branch Choose the game branch when adding a server. - [Add your first server](https://rustsc.com/support/guides/add-server/#add) ## Change release branch Use the server command help to see branch choices. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-server) ## Game version Check for a newer game build from Software. - [Update Rust](https://rustsc.com/support/guides/update-rust/#update) ## Update Rust Choose Update game to install an available update. - [Update Rust](https://rustsc.com/support/guides/update-rust/#update) ## Update game and framework Choose the game and framework update steps. - [Update Rust](https://rustsc.com/support/guides/update-rust/#update) ## Update recovery RustSC reports a failed update and its result. - [Update Rust](https://rustsc.com/support/guides/update-rust/#update) ## Update at restart Choose the automatic update setting you want. - [Update Rust](https://rustsc.com/support/guides/update-rust/#automatic) ## Updates at restart Choose whether to check for updates at restarts. - [Update Rust](https://rustsc.com/support/guides/update-rust/#automatic) ## Wait before updating Choose a delay before automatic updates. - [Update Rust](https://rustsc.com/support/guides/update-rust/#automatic) ## Schedule an update Choose a schedule for a supported server update. - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/#schedule) ## Monthly game update Check for the game update before choosing when to install it. - [Update Rust](https://rustsc.com/support/guides/update-rust/#update) ## Inspect game files Check game files without changing them. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/#terminal) ## Repair game files Stop the server before repairing game files. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/#repair) ## Install a framework Install Oxide or Carbon for your plugins. - [Change Oxide or Carbon](https://rustsc.com/support/guides/change-framework/#framework) ## Update a framework Use Software to update or change Oxide or Carbon. - [Change Oxide or Carbon](https://rustsc.com/support/guides/change-framework/#framework) ## Change framework Switch between Oxide and Carbon. - [Change Oxide or Carbon](https://rustsc.com/support/guides/change-framework/#framework) ## Remove a framework Use the framework controls on the Software page. - [Change Oxide or Carbon](https://rustsc.com/support/guides/change-framework/#framework) ## Framework channel Choose the available framework channel. - [Change Oxide or Carbon](https://rustsc.com/support/guides/change-framework/#framework) ## RustEdit Use Software to manage RustEdit. - [Change Oxide or Carbon](https://rustsc.com/support/guides/change-framework/#extensions) ## Update the RustSC plugin Update the plugin from the Software page. - [Install or update the RustSC plugin](https://rustsc.com/support/guides/rustsc-plugin/#update) ## Update an existing server Use the available game update controls for an added server. - [Update Rust](https://rustsc.com/support/guides/update-rust/#update) ## Update from the host Use the host command to update the game. - [Maintain a server on its host](https://rustsc.com/support/guides/host-maintenance/#game-update) HTML version: https://rustsc.com/support/guides/reference-software-updates/ --- # Wipes reference Find a specific action or setting for wipes and open the related instructions in RustSC. ## Wipe a server Choose what to wipe and review the action before confirming. - [Wipe your server](https://rustsc.com/support/guides/wipe-server/#wipe) ## Choose what to reset Choose the server data to reset with the wipe. - [Wipe your server](https://rustsc.com/support/guides/wipe-server/#wipe) ## Choose a map Choose the next map while setting up a wipe. - [Wipe your server](https://rustsc.com/support/guides/wipe-server/#wipe) ## Review a wipe Read the wipe choices before confirming. - [Wipe your server](https://rustsc.com/support/guides/wipe-server/#wipe) ## Warn players Players see the configured warning before the wipe. - [Messages, restarts and wipes: what players see](https://rustsc.com/support/guides/player-messages/#see) ## Backup before a wipe Choose the backup and restart steps for the wipe. - [Wipe your server](https://rustsc.com/support/guides/wipe-server/#wipe) ## Schedule a wipe Choose when the wipe should run. - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/#schedule) ## Force wipe dates The calendar marks force wipe dates. - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/#schedule) ## Restarts on wipe day Pause the usual restarts for the wipe day. - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/#schedule) ## Updates in a wipe Review the wipe plan's update steps. - [Wipe plans in plain words](https://rustsc.com/support/guides/wipe-plans/#what) ## Check a scheduled wipe Review the scheduled wipe and its result. - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/#schedule) ## Local schedules Approved schedules can keep running during a cloud outage. - [Host offline](https://rustsc.com/support/guides/computer-offline/#check) ## Save wipe choices Use a wipe plan to keep choices together. - [Wipe plans in plain words](https://rustsc.com/support/guides/wipe-plans/#what) ## Earlier wipes Review an earlier wipe and use its choices again. - [Wipe your server](https://rustsc.com/support/guides/wipe-server/#wipe) ## Files for a wipe Include the files you want in a wipe plan. - [Wipe plans in plain words](https://rustsc.com/support/guides/wipe-plans/#what) ## Reset files on a wipe Choose cleanup steps in the wipe plan. - [Wipe plans in plain words](https://rustsc.com/support/guides/wipe-plans/#what) ## Clean up old files Review old files before removing them. - [Free disk space](https://rustsc.com/support/guides/free-disk-space/#files) ## Plugins in a wipe Review the wipe plan's plugin choices. - [Wipe plans in plain words](https://rustsc.com/support/guides/wipe-plans/#what) ## After the wipe RustSC checks the server after it starts. - [Wipe your server](https://rustsc.com/support/guides/wipe-server/#wipe) ## Files from a recent wipe A second wipe does not remove files protected by the recent wipe. - [Wipe plans in plain words](https://rustsc.com/support/guides/wipe-plans/#what) ## A wipe stopped Read the result and follow the next step before retrying. - [Wipe your server](https://rustsc.com/support/guides/wipe-server/#problems) ## Wipe from a terminal Use the host command help to see the available wipe choices. - [Host command reference](https://rustsc.com/support/guides/host-command-reference/#commands-wipe) ## Wipe several servers Set up the wipe for each server. - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/#schedule) HTML version: https://rustsc.com/support/guides/reference-wipes/ --- # Rust server guides Set up, run and troubleshoot a Rust dedicated server with practical guides for server owners. ## Start here - [Your Rust server boots. What should you do in the first week?](https://rustsc.com/learn/setup/first-week-after-your-rust-server-boots/index.html.md). Set up a usable first-week routine for saves, restarts and keeping players informed. - [What changes at your first Rust force wipe?](https://rustsc.com/learn/wipes/first-force-wipe-versus-elective-wipe/index.html.md). Separate the reset required by the studio’s update from the additional wipes you schedule. - [How to prove your Rust server backup can be restored](https://rustsc.com/learn/recovery/prove-a-local-backup-with-a-test-restore/index.html.md). Restore a local backup into a separate test server and check the world you actually get back. ## [Server setup](https://rustsc.com/learn/setup/index.html.md) Install a Rust dedicated server and get ready for your first players. - [Your Rust server boots. What should you do in the first week?](https://rustsc.com/learn/setup/first-week-after-your-rust-server-boots/index.html.md) - [How to read a Rust server launch script](https://rustsc.com/learn/setup/read-your-rust-server-launch-script/index.html.md) - [Where does your Rust server keep its active world?](https://rustsc.com/learn/setup/find-the-active-rust-server-identity-folder/index.html.md) - [How to make yourself a Rust server admin and check it worked](https://rustsc.com/learn/setup/give-yourself-rust-game-admin/index.html.md) - [How to assign ports to a second Rust server on one host](https://rustsc.com/learn/setup/allocate-ports-for-a-second-rust-server/index.html.md) - [How to test your Rust server from another network](https://rustsc.com/learn/setup/test-your-rust-server-from-another-network/index.html.md) - [Install Carbon on a self-hosted Rust server](https://rustsc.com/learn/setup/install-carbon-launch-script/index.html.md) - [Install your first Rust plugin and test what it does](https://rustsc.com/learn/setup/first-plugin-download-to-working-feature/index.html.md) - [Where do Rust plugin .cs files and extension DLLs go?](https://rustsc.com/learn/setup/plugin-cs-vs-extension-dll/index.html.md) - [Which Rust plugin dependencies should you install first?](https://rustsc.com/learn/setup/install-rust-plugin-dependencies-in-order/index.html.md) - [How to set up Rust+ on your dedicated server](https://rustsc.com/learn/setup/set-up-rust-plus-on-your-dedicated-server/index.html.md) - [Which Rust ports should you forward at home?](https://rustsc.com/learn/setup/game-port-and-query-port-at-home/index.html.md) ## [Hosting](https://rustsc.com/learn/hosting/index.html.md) Choose where to host a Rust server and understand what access you need. - [Windows or Linux for your first Rust server?](https://rustsc.com/learn/hosting/windows-or-linux-for-your-first-rust-server/index.html.md) - [Can you play Rust and host a Rust server on the same PC?](https://rustsc.com/learn/hosting/play-and-host-on-one-pc/index.html.md) - [How to turn a public Rust server into a friends-only server](https://rustsc.com/learn/hosting/make-a-public-rust-server-friends-only/index.html.md) - [Will a second Rust server fit on the same host?](https://rustsc.com/learn/hosting/will-a-second-rust-server-fit-on-one-host/index.html.md) - [Host Rust at home or rent a server?](https://rustsc.com/learn/hosting/home-network-or-rented-rust-server/index.html.md) - [What backup access should a rented Rust server helper have?](https://rustsc.com/learn/hosting/give-a-helper-backup-access-on-rented-rust/index.html.md) - [How to move a Rust server hostname to a new host](https://rustsc.com/learn/hosting/move-your-rust-server-hostname/index.html.md) - [What to take with you before cancelling a Rust server rental](https://rustsc.com/learn/hosting/before-you-cancel-a-rust-server-rental/index.html.md) - [Can you run a Rust server just for game night?](https://rustsc.com/learn/hosting/run-a-rust-server-just-for-game-night/index.html.md) - [Will a Rust management tool do the same jobs on both your hosts?](https://rustsc.com/learn/hosting/test-a-rust-management-tool-on-different-hosts/index.html.md) - [How to compare Rust server rental renewal costs](https://rustsc.com/learn/hosting/rust-server-rental-renewal-cost/index.html.md) - [Which hosting region should you pick for your Rust players?](https://rustsc.com/learn/hosting/choose-a-rust-rental-region-with-players/index.html.md) - [What will a Rust server host help you fix?](https://rustsc.com/learn/hosting/check-rust-rental-support-before-buying/index.html.md) - [Does your Rust rental need more disk space or more memory?](https://rustsc.com/learn/hosting/choose-rust-rental-disk-or-memory/index.html.md) - [Will Rust backup downloads use up your host’s transfer allowance?](https://rustsc.com/learn/hosting/rust-host-transfer-allowance-for-backups/index.html.md) - [What does a Rust rental’s backup allowance actually cover?](https://rustsc.com/learn/hosting/compare-rust-rental-backup-allowances/index.html.md) - [Shared or dedicated CPU for a Rust rental?](https://rustsc.com/learn/hosting/rust-rental-shared-or-dedicated-cpu/index.html.md) - [Can a Rust rental run the custom map you already have?](https://rustsc.com/learn/hosting/choose-rust-rental-with-custom-map-access/index.html.md) - [Will a Rust rental keep its address when the host moves it?](https://rustsc.com/learn/hosting/rust-rental-region-transfer-keep-or-change-address/index.html.md) - [Do more Rust rental slots mean more capacity?](https://rustsc.com/learn/hosting/rust-rental-slot-count-and-resource-limits/index.html.md) - [How to try a Rust rental without moving your players](https://rustsc.com/learn/hosting/try-a-rust-rental-without-moving-your-players/index.html.md) - [Would losing your Rust rental login also lock you out of backups?](https://rustsc.com/learn/hosting/check-rust-rental-and-backup-account-separation/index.html.md) - [Who controls game and framework updates on a Rust rental?](https://rustsc.com/learn/hosting/choose-updates-you-control-on-a-rust-rental/index.html.md) - [Will your Rust rental have enough disk for the next map?](https://rustsc.com/learn/hosting/check-rust-rental-disk-quota-before-a-map-change/index.html.md) - [Should two Rust worlds share one host?](https://rustsc.com/learn/hosting/choose-one-or-two-hosts-for-rust-worlds/index.html.md) - [Does your Rust community need a second world?](https://rustsc.com/learn/hosting/does-your-rust-community-need-a-second-world/index.html.md) - [What address should friends use to join your Rust server?](https://rustsc.com/learn/hosting/which-address-should-friends-use/index.html.md) - [Can you add a Rust server manager and keep your rented server?](https://rustsc.com/learn/hosting/access-needed-for-rented-server-maintenance/index.html.md) ## [Wipes](https://rustsc.com/learn/wipes/index.html.md) Plan Rust server wipes and decide what players will keep or lose. - [What changes at your first Rust force wipe?](https://rustsc.com/learn/wipes/first-force-wipe-versus-elective-wipe/index.html.md) - [Should your Rust server wipe weekly or monthly?](https://rustsc.com/learn/wipes/weekly-or-monthly-rust-wipes/index.html.md) - [What should your Rust wipe announcement say will reset?](https://rustsc.com/learn/wipes/announce-what-a-rust-wipe-resets/index.html.md) - [How to stop two Rust wipe schedules from colliding](https://rustsc.com/learn/wipes/avoid-two-rust-wipes-in-one-window/index.html.md) - [Should you change your Rust map seed at the next wipe?](https://rustsc.com/learn/wipes/new-seed-or-same-layout-next-wipe/index.html.md) - [Which Rust plugin data should reset at a wipe?](https://rustsc.com/learn/wipes/choose-plugin-data-to-reset-at-wipe/index.html.md) - [How to rehearse a Rust wipe before wipe night](https://rustsc.com/learn/wipes/test-a-rust-wipe-plan-before-running-it/index.html.md) - [A Rust wipe stopped halfway. What should you check first?](https://rustsc.com/learn/wipes/check-an-interrupted-rust-wipe-before-retrying/index.html.md) - [How to check Rust’s in-game wipe countdown](https://rustsc.com/learn/wipes/match-rust-in-game-countdown-to-real-wipe/index.html.md) - [What to check before telling players a Rust wipe is finished](https://rustsc.com/learn/wipes/check-rust-world-before-announcing-wipe-complete/index.html.md) - [Which Rust server changes should wait until after the wipe?](https://rustsc.com/learn/wipes/choose-rust-changes-to-defer-on-wipe-night/index.html.md) - [Which scheduled Rust jobs should wait until the wipe is over?](https://rustsc.com/learn/wipes/pause-rust-jobs-during-a-wipe-window/index.html.md) - [What should you write down after a Rust wipe?](https://rustsc.com/learn/wipes/keep-a-short-rust-wipe-change-record/index.html.md) - [How to tell your Rust players a wipe is delayed](https://rustsc.com/learn/wipes/update-a-rust-wipe-announcement-after-a-delay/index.html.md) - [How to check that blueprints survived a Rust map wipe](https://rustsc.com/learn/wipes/verify-blueprints-after-map-wipe/index.html.md) ## [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) Back up your Rust server and recover a world when something goes wrong. - [Move Rust plugin settings and player data to another server](https://rustsc.com/learn/recovery/move-plugin-settings-and-player-data/index.html.md) - [Which Rust server backup should you restore after an incident?](https://rustsc.com/learn/recovery/choose-rust-backup-before-an-incident/index.html.md) - [Why is my Rust world empty after changing the server identity?](https://rustsc.com/learn/recovery/rust-world-empty-after-server-identity-change/index.html.md) - [Should you stop a Rust server before taking a backup?](https://rustsc.com/learn/recovery/rust-backup-running-or-stopped/index.html.md) - [Which files belong in a Rust server backup?](https://rustsc.com/learn/recovery/what-a-rust-server-backup-needs-to-include/index.html.md) - [Is a Rust server backup on the same disk enough?](https://rustsc.com/learn/recovery/rust-backup-on-the-same-disk/index.html.md) - [How many Rust server backups should you keep on the host?](https://rustsc.com/learn/recovery/keep-enough-rust-backups-without-filling-disk/index.html.md) - [When can a previous Rust save recover a damaged world?](https://rustsc.com/learn/recovery/rust-rotated-save-or-full-backup/index.html.md) - [What to save before rolling back a Rust server](https://rustsc.com/learn/recovery/save-current-rust-world-before-rollback/index.html.md) - [How to recover one Rust server setting without rolling back the map](https://rustsc.com/learn/recovery/recover-rust-setting-without-rolling-back-world/index.html.md) - [How to recover deleted Oxide plugin data](https://rustsc.com/learn/recovery/recover-deleted-oxide-plugin-data/index.html.md) - [How to change a restic password without losing your Rust backups](https://rustsc.com/learn/recovery/change-restic-backup-password-without-losing-history/index.html.md) - [Can you get to your Rust backups if the host is gone?](https://rustsc.com/learn/recovery/check-backup-access-with-host-unavailable/index.html.md) - [What to bring when restoring a Rust backup from Windows to Linux](https://rustsc.com/learn/recovery/move-rust-backup-from-windows-to-linux/index.html.md) - [Can you restore an old Rust save after a forced wipe?](https://rustsc.com/learn/recovery/restore-rust-save-after-forced-wipe/index.html.md) - [What to keep for Rust+ when restoring the same server](https://rustsc.com/learn/recovery/preserve-rust-plus-pairing-when-restoring/index.html.md) - [Which SQLite files do you need when copying a Rust database?](https://rustsc.com/learn/recovery/copy-rust-sqlite-database-and-wal/index.html.md) - [How often should you back up a Rust server?](https://rustsc.com/learn/recovery/rust-backup-frequency-and-manual-checkpoints/index.html.md) - [Which custom map file should you keep with a Rust backup?](https://rustsc.com/learn/recovery/archive-custom-rust-map-for-recovery/index.html.md) - [Which bans and staff permissions should you check after a Rust restore?](https://rustsc.com/learn/recovery/check-bans-and-staff-after-rust-restore/index.html.md) - [What can you share from a Rust server backup when asking for help?](https://rustsc.com/learn/recovery/what-to-share-from-rust-backup/index.html.md) - [Why is your Rust panel backup download so small?](https://rustsc.com/learn/recovery/rust-panel-backup-download-smaller-than-expected/index.html.md) - [Can a Rust backup restore fit into your wipe window?](https://rustsc.com/learn/recovery/measure-rust-restore-time-before-wipe/index.html.md) - [Did your Rust backup restore go into the wrong world?](https://rustsc.com/learn/recovery/rust-restore-changed-the-wrong-world/index.html.md) - [A Rust backup is missing from the panel. Can you still use the file?](https://rustsc.com/learn/recovery/rust-backup-missing-from-panel-but-file-exists/index.html.md) - [What should you check after replacing your Rust server disk?](https://rustsc.com/learn/recovery/restore-rust-after-a-disk-replacement/index.html.md) - [What if a Rust restore leaves plugin balances from a later day?](https://rustsc.com/learn/recovery/rust-world-restore-with-external-plugin-data/index.html.md) - [How to recover a Rust world after its custom map link stops working](https://rustsc.com/learn/recovery/recover-rust-when-the-custom-map-url-is-gone/index.html.md) - [Did your Rust backup finish copying over a slow connection?](https://rustsc.com/learn/recovery/verify-a-rust-archive-copy-on-a-slow-link/index.html.md) - [Prove a Rust backup belongs to the right world](https://rustsc.com/learn/recovery/prove-a-backup-belongs-to-the-right-rust-world/index.html.md) - [Move one Rust world while its neighbour stays open](https://rustsc.com/learn/recovery/move-one-rust-world-while-the-other-stays-open/index.html.md) - [How to prove your Rust server backup can be restored](https://rustsc.com/learn/recovery/prove-a-local-backup-with-a-test-restore/index.html.md) ## [Updates](https://rustsc.com/learn/updates/index.html.md) Keep your Rust server, framework and plugins ready for game updates. - [How to keep Windows Update from interrupting your busiest Rust hours](https://rustsc.com/learn/updates/windows-update-restarts-on-a-rust-host/index.html.md) - [How to put Oxide back after a Rust update](https://rustsc.com/learn/updates/install-oxide-after-rust-update/index.html.md) - [Should you run Oxide or Carbon on your Rust server?](https://rustsc.com/learn/updates/choose-oxide-or-carbon/index.html.md) - [Rehearse an Oxide-to-Carbon migration before switching live](https://rustsc.com/learn/updates/rehearse-oxide-to-carbon-migration/index.html.md) - [Does your Oxide plugin work on Carbon?](https://rustsc.com/learn/updates/test-oxide-plugin-compatibility-on-carbon/index.html.md) - [Remove a Rust plugin and keep a way to bring it back](https://rustsc.com/learn/updates/remove-rust-plugin-without-losing-data/index.html.md) - [Track Rust plugin versions across marketplaces](https://rustsc.com/learn/updates/rust-plugin-version-register/index.html.md) - [Roll back a plugin update that changed its data files](https://rustsc.com/learn/updates/rollback-plugin-update-with-data-conversion/index.html.md) - [SteamCMD succeeded. Why is Rust still on the old build?](https://rustsc.com/learn/updates/steamcmd-updated-a-different-rust-folder/index.html.md) - [Check the Rust branches when a new build will not connect](https://rustsc.com/learn/updates/rust-client-and-server-on-different-branches/index.html.md) - [When should you validate Rust server files?](https://rustsc.com/learn/updates/when-to-validate-rust-server-files/index.html.md) - [How to prepare your Rust server for a seasonal event](https://rustsc.com/learn/updates/prepare-rust-seasonal-world-settings/index.html.md) - [How to test an existing custom map after a Rust update](https://rustsc.com/learn/updates/check-a-custom-map-after-rust-updates/index.html.md) - [Which Rust plugin updates belong on force-wipe day?](https://rustsc.com/learn/updates/should-you-update-a-rust-plugin-on-force-wipe-day/index.html.md) - [Introduce a small Rust plugin change to one world first](https://rustsc.com/learn/updates/introduce-a-rust-plugin-to-one-live-world-first/index.html.md) - [What to do when a required Rust plugin is no longer maintained](https://rustsc.com/learn/updates/when-a-required-rust-plugin-is-no-longer-maintained/index.html.md) - [When should you update a Rust server extension by itself?](https://rustsc.com/learn/updates/should-you-update-a-rust-server-extension-separately/index.html.md) ## [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Find the cause when your Rust server will not start or players cannot join. - [What to send your rental host when Rust will not start](https://rustsc.com/learn/troubleshooting/support-ticket-for-rust-server-startup-failure/index.html.md) - [Can RCON start a Rust server that is offline?](https://rustsc.com/learn/troubleshooting/rust-rcon-versus-panel-power/index.html.md) - [Why your Rust plugin settings revert when you reload it](https://rustsc.com/learn/troubleshooting/plugin-settings-overwritten-on-reload/index.html.md) - [Read the first useful line in a Rust plugin compile error](https://rustsc.com/learn/troubleshooting/read-rust-plugin-compile-errors/index.html.md) - [Is one Carbon plugin slowing down your Rust server?](https://rustsc.com/learn/troubleshooting/measure-one-carbon-plugin-during-a-server-stall/index.html.md) - [The Rust process is running, but the game is frozen](https://rustsc.com/learn/troubleshooting/rust-process-running-but-game-frozen/index.html.md) - [Why does Rust keep restarting after a crash?](https://rustsc.com/learn/troubleshooting/automatic-recovery-keeps-restarting-rust/index.html.md) - [Rust exits after an update. Was it short of memory?](https://rustsc.com/learn/troubleshooting/rust-closed-after-update-check-memory/index.html.md) - [Is high RAM use a problem for your Rust server?](https://rustsc.com/learn/troubleshooting/high-memory-use-or-real-pressure/index.html.md) - [Is it low client FPS or a slow Rust server?](https://rustsc.com/learn/troubleshooting/client-fps-or-rust-server-lag/index.html.md) - [Why does one Rust server lag while another backs up?](https://rustsc.com/learn/troubleshooting/one-rust-server-lags-during-another-backup/index.html.md) - [Why does Rust say the save folder is read-only?](https://rustsc.com/learn/troubleshooting/rust-save-fails-on-a-read-only-filesystem/index.html.md) - [Which log explains why a Rust server quit?](https://rustsc.com/learn/troubleshooting/find-the-log-for-an-unexpected-rust-exit/index.html.md) - [Rust startup or remote console failure?](https://rustsc.com/learn/troubleshooting/rust-starts-but-remote-console-is-waiting/index.html.md) - [Why did a scheduled Rust restart not happen?](https://rustsc.com/learn/troubleshooting/scheduled-rust-restart-did-not-run/index.html.md) - [Why does Rust+ say your paired server is offline?](https://rustsc.com/learn/troubleshooting/rust-plus-paired-server-offline/index.html.md) - [Why does Rust+ connect but send no phone notifications?](https://rustsc.com/learn/troubleshooting/rust-plus-phone-notifications-missing/index.html.md) - [Rust+ says the Smart Switch is on. Why is the light off?](https://rustsc.com/learn/troubleshooting/why-rust-plus-smart-switch-on-but-light-off/index.html.md) - [How to test a Rust+ Smart Alarm without waiting for its usual trigger](https://rustsc.com/learn/troubleshooting/test-rust-plus-smart-alarm/index.html.md) - [Is your Rust Storage Monitor showing the right box?](https://rustsc.com/learn/troubleshooting/rust-plus-storage-monitor-wrong-box/index.html.md) - [Why won't your Rust CCTV station show a base camera?](https://rustsc.com/learn/troubleshooting/rust-computer-station-cannot-show-base-camera/index.html.md) - [What does the last death marker on the Rust map show?](https://rustsc.com/learn/troubleshooting/rust-death-map-marker-versus-respawn-point/index.html.md) - [Why is a Rust vending machine missing from the in-game map?](https://rustsc.com/learn/troubleshooting/rust-shop-vending-machine-absent-from-game-map/index.html.md) - [Why are shops and events missing from the Rust+ map?](https://rustsc.com/learn/troubleshooting/rust-plus-map-missing-shops-and-events/index.html.md) - [Why can't you give a friend a sleeping bag in Rust?](https://rustsc.com/learn/troubleshooting/rust-cannot-give-sleeping-bag-to-friend/index.html.md) - [Why can one Rust teammate build at the base while another can't?](https://rustsc.com/learn/troubleshooting/why-rust-teammate-cannot-build-at-base/index.html.md) - [Why does a Rust planter stay dry with the sprinkler running?](https://rustsc.com/learn/troubleshooting/rust-farm-sprinkler-runs-but-planter-stays-dry/index.html.md) - [Why do your Rust base lights go out at night?](https://rustsc.com/learn/troubleshooting/rust-base-lights-go-out-at-night/index.html.md) - [Why did your Rust Industrial Conveyor stop moving items?](https://rustsc.com/learn/troubleshooting/rust-conveyor-stops-moving-items/index.html.md) - [A player's microphone works elsewhere. Why can't you hear them in Rust?](https://rustsc.com/learn/troubleshooting/rust-player-microphone-works-elsewhere-not-in-game/index.html.md) - [Why does the Rust sign look blank to only one player?](https://rustsc.com/learn/troubleshooting/rust-sign-blank-for-one-player/index.html.md) - [Why did your Rust plugin compile but fail to load?](https://rustsc.com/learn/troubleshooting/rust-plugin-compiles-but-does-not-load/index.html.md) - [A Rust reward arrived. Why won’t the shop accept it?](https://rustsc.com/learn/troubleshooting/rust-plugin-balance-changes-but-shop-disagrees/index.html.md) - [Why does your Rust plugin work after reload but fail on restart?](https://rustsc.com/learn/troubleshooting/rust-plugin-works-after-reload-but-not-after-restart/index.html.md) - [Report a Rust plugin bug the maintainer can reproduce](https://rustsc.com/learn/troubleshooting/report-a-rust-plugin-error-the-maintainer-can-reproduce/index.html.md) - [Do two Rust worlds stall when their saves overlap?](https://rustsc.com/learn/troubleshooting/two-rust-worlds-stall-when-saving-at-the-same-time/index.html.md) - [Why does Rust plugin progress disappear after a restart?](https://rustsc.com/learn/troubleshooting/rust-plugin-saves-progress-until-the-next-restart/index.html.md) - [Why does a Rust plugin run an action twice after reload?](https://rustsc.com/learn/troubleshooting/rust-plugin-runs-an-action-twice-after-reload/index.html.md) - [Why can a Rust player still use a plugin after leaving a group?](https://rustsc.com/learn/troubleshooting/rust-plugin-permission-remains-after-group-removal/index.html.md) - [Check which Rust worlds actually enforce a ban](https://rustsc.com/learn/troubleshooting/check-a-rust-ban-on-the-intended-worlds/index.html.md) - [Direct join works, but your Rust server is missing from the browser](https://rustsc.com/learn/troubleshooting/direct-join-works-server-missing-from-browser/index.html.md) ## [Configuration](https://rustsc.com/learn/configuration/index.html.md) Understand the settings that control your Rust server and how players find it. - [Which Rust setting renames the server in the browser?](https://rustsc.com/learn/configuration/server-name-versus-server-identity/index.html.md) - [Which Rust plugin JSON file should you edit?](https://rustsc.com/learn/configuration/find-active-plugin-settings-file/index.html.md) - [Why a Rust plugin can reject valid JSON](https://rustsc.com/learn/configuration/plugin-json-syntax-and-types/index.html.md) - [Change the messages players see from an Oxide plugin](https://rustsc.com/learn/configuration/change-player-facing-rust-plugin-messages/index.html.md) - [How to pick a Rust map size for the players you actually get](https://rustsc.com/learn/configuration/choose-map-size-for-player-density/index.html.md) - [How to check a Rust seed has the monuments your players expect](https://rustsc.com/learn/configuration/verify-procedural-monuments-before-wipe/index.html.md) - [Why did Rust ignore a change to your procedural map settings?](https://rustsc.com/learn/configuration/procedural-config-change-did-not-apply/index.html.md) - [How to change Rust biomes without losing safe spawn areas](https://rustsc.com/learn/configuration/rust-world-biomes-and-safe-player-spawns/index.html.md) - [How to check rail and road routes on a Rust map candidate](https://rustsc.com/learn/configuration/check-rust-rail-and-road-routes/index.html.md) - [How to check buildable space on a Rust map candidate](https://rustsc.com/learn/configuration/compare-rust-worlds-by-coastline-build-space/index.html.md) - [How to write a Rust server description that fits the browser](https://rustsc.com/learn/configuration/write-a-rust-server-browser-description/index.html.md) - [How to add a header image and icon to a Rust server listing](https://rustsc.com/learn/configuration/add-a-header-and-icon-to-your-rust-server-listing/index.html.md) - [Which page should you link from your Rust server listing?](https://rustsc.com/learn/configuration/link-a-website-from-your-rust-server-listing/index.html.md) - [Which Rust server tags should you show?](https://rustsc.com/learn/configuration/choose-rust-browser-tags-that-describe-your-game/index.html.md) - [Should your Rust server be listed under Community or Modded?](https://rustsc.com/learn/configuration/choose-community-or-modded-for-a-rust-server/index.html.md) - [Why does your Rust server listing show the wrong country?](https://rustsc.com/learn/configuration/fix-the-location-on-a-rust-server-listing/index.html.md) - [Should you turn on Premium for your Rust server?](https://rustsc.com/learn/configuration/decide-whether-to-use-premium-on-a-rust-server/index.html.md) - [How many player slots should you set on a Rust server?](https://rustsc.com/learn/configuration/choose-a-rust-server-player-cap/index.html.md) - [Why did a Rust setting change back after restart?](https://rustsc.com/learn/configuration/keep-a-rust-setting-after-restart/index.html.md) - [Which Rust settings affect eligibility for the secure server list?](https://rustsc.com/learn/configuration/check-secure-listing-settings-on-a-rust-server/index.html.md) - [Would Softcore suit the people on your Rust server?](https://rustsc.com/learn/configuration/try-softcore-before-choosing-it-for-your-rust-server/index.html.md) - [How to tell if your Rust group will enjoy Hardcore navigation](https://rustsc.com/learn/configuration/test-hardcore-navigation-on-a-rust-server/index.html.md) - [What should you test before running a Rust Primitive server?](https://rustsc.com/learn/configuration/check-primitive-progression-on-a-rust-server/index.html.md) - [How to set up a Rust server for creative building practice](https://rustsc.com/learn/configuration/set-up-a-rust-creative-building-practice-server/index.html.md) - [How to check Tutorial Island on your Rust server](https://rustsc.com/learn/configuration/enable-and-check-rust-tutorial-island/index.html.md) - [Should you change the sleeping bag limit on a Rust server?](https://rustsc.com/learn/configuration/choose-a-sleeping-bag-limit-for-your-rust-server/index.html.md) - [Is Rust decay too fast, or is a base out of upkeep?](https://rustsc.com/learn/configuration/check-rust-upkeep-before-changing-decay/index.html.md) - [How to check the built-in team size on a Rust server](https://rustsc.com/learn/configuration/check-the-built-in-rust-team-size-setting/index.html.md) - [How to test a shorter locked crate timer on a Rust server](https://rustsc.com/learn/configuration/test-a-rust-locked-crate-hack-timer/index.html.md) - [What should you check before advertising a Rust server as PvE?](https://rustsc.com/learn/configuration/check-what-pve-means-on-your-rust-server/index.html.md) - [Choose one tool to control Rust item stack sizes](https://rustsc.com/learn/configuration/choose-one-source-for-rust-item-stack-sizes/index.html.md) - [Check what your Rust gather multiplier actually changes](https://rustsc.com/learn/configuration/test-rust-gather-multipliers-by-source/index.html.md) - [Test Rust kit claims, cooldowns and limits before opening them](https://rustsc.com/learn/configuration/test-rust-kit-redemption-and-cooldowns/index.html.md) - [Copy one Rust setting between worlds without changing the save identity](https://rustsc.com/learn/configuration/copy-rust-settings-between-worlds-without-copying-identity/index.html.md) - [Reproduce a Rust plugin issue without sharing player data](https://rustsc.com/learn/configuration/check-per-player-rust-plugin-data-before-sharing-a-copy/index.html.md) - [Test a permanent safe zone on your Rust server](https://rustsc.com/learn/configuration/test-a-fixed-rust-safe-zone-before-opening-it/index.html.md) - [Keep live Discord feeds out of a Rust plugin test server](https://rustsc.com/learn/configuration/keep-live-discord-links-out-of-a-rust-plugin-test-server/index.html.md) - [Which Rust plugin settings should survive an update?](https://rustsc.com/learn/configuration/compare-rust-plugin-defaults-before-keeping-your-settings/index.html.md) - [Check Rust plugin message placeholders after an update](https://rustsc.com/learn/configuration/test-rust-plugin-language-placeholders-in-game/index.html.md) - [Why won't my Rust custom map URL load?](https://rustsc.com/learn/configuration/custom-map-url-wont-load/index.html.md) - [Why does my Rust server disappear when I apply a tag filter?](https://rustsc.com/learn/configuration/server-visible-until-browser-tag-filter/index.html.md) ## [Players and community](https://rustsc.com/learn/community/index.html.md) Manage player access, moderation and communication on your Rust server. - [Run a PvP weekend on your PvE Rust server](https://rustsc.com/learn/community/weekend-pvp-on-a-pve-rust-server/index.html.md) - [What should friends agree before starting a private Rust world?](https://rustsc.com/learn/community/agree-a-first-wipe-with-friends/index.html.md) - [Find which Rust plugin handles a chat command](https://rustsc.com/learn/community/find-which-plugin-owns-a-command/index.html.md) - [Set up Oxide group inheritance for junior and senior staff](https://rustsc.com/learn/community/oxide-group-inheritance-for-staff/index.html.md) - [How to write Rust server rules players can use](https://rustsc.com/learn/community/write-rust-server-rules-players-can-use/index.html.md) - [How to announce a Rust server rule change](https://rustsc.com/learn/community/announce-a-rust-server-rule-change/index.html.md) - [Where should players send reports about your Rust server?](https://rustsc.com/learn/community/give-rust-players-a-private-report-route/index.html.md) - [How to triage Rust player reports](https://rustsc.com/learn/community/triage-rust-player-reports/index.html.md) - [What does a Rust team-limit report actually show?](https://rustsc.com/learn/community/check-a-rust-team-limit-report/index.html.md) - [What to do when several Rust players report the same incident](https://rustsc.com/learn/community/handle-duplicate-rust-player-reports/index.html.md) - [How to review a ban appeal for your Rust server](https://rustsc.com/learn/community/run-a-rust-community-ban-appeal/index.html.md) - [How to correct a moderation mistake on your Rust server](https://rustsc.com/learn/community/correct-a-rust-moderation-mistake/index.html.md) - [What should a Rust moderator tell players about a report?](https://rustsc.com/learn/community/share-rust-moderation-decisions-without-exposing-reports/index.html.md) - [Who should handle a Rust player report?](https://rustsc.com/learn/community/escalate-rust-player-reports-to-the-right-place/index.html.md) - [Who handles a report involving a Rust moderator’s own team?](https://rustsc.com/learn/community/when-a-rust-moderator-should-step-aside/index.html.md) - [Onboard your first Rust moderator without sharing your login](https://rustsc.com/learn/community/onboard-a-first-rust-server-moderator/index.html.md) - [What to check when a Rust server moderator leaves](https://rustsc.com/learn/community/remove-rust-server-staff-access-when-someone-leaves/index.html.md) - [What access does your Rust moderator actually need?](https://rustsc.com/learn/community/choose-access-for-a-rust-moderator/index.html.md) - [How to check a Rust moderator’s access after a role change](https://rustsc.com/learn/community/verify-a-rust-moderator-access-change/index.html.md) - [How to hand over an open Rust moderation case](https://rustsc.com/learn/community/hand-over-an-open-rust-moderation-case/index.html.md) - [Which Discord channels does a small Rust community need?](https://rustsc.com/learn/community/organise-discord-channels-for-a-rust-community/index.html.md) - [What Rust chat should you share in Discord?](https://rustsc.com/learn/community/choose-which-rust-chat-to-share-in-discord/index.html.md) - [How to help Rust players recognise real staff messages](https://rustsc.com/learn/community/help-rust-players-recognise-real-staff-messages/index.html.md) - [What to say when a Rust raid argument takes over global chat](https://rustsc.com/learn/community/calm-a-rust-global-chat-argument/index.html.md) - [Where should your Rust players look when Discord is down?](https://rustsc.com/learn/community/keep-rust-players-informed-when-discord-is-down/index.html.md) - [Keep one current Rust join post in Discord](https://rustsc.com/learn/community/one-current-rust-join-post/index.html.md) - [Turn repeated Rust questions into answers players can find](https://rustsc.com/learn/community/turn-repeat-rust-questions-into-discord-answers/index.html.md) - [How to share Rust announcements with another Discord server](https://rustsc.com/learn/community/share-rust-updates-with-partner-discords/index.html.md) - [What to put in a new Rust server launch announcement](https://rustsc.com/learn/community/write-a-rust-server-launch-announcement/index.html.md) - [What to do when a shout-out fills your Rust server](https://rustsc.com/learn/community/rust-server-fills-after-a-shout-out/index.html.md) - [What to tell players when your Rust server goes down](https://rustsc.com/learn/community/rust-outage-status-post/index.html.md) - [Schedule an in-game Rust event in Discord](https://rustsc.com/learn/community/schedule-a-rust-game-event-in-discord/index.html.md) - [Will enough players show up for your Rust event?](https://rustsc.com/learn/community/rust-event-attendance-before-you-commit/index.html.md) - [How to run signups for a Rust event with limited spots](https://rustsc.com/learn/community/rust-event-spots-and-waitlist/index.html.md) - [Help late players catch up at a Rust community event](https://rustsc.com/learn/community/help-late-players-join-a-rust-event/index.html.md) - [Run one Rust event with another community](https://rustsc.com/learn/community/one-rust-event-two-communities/index.html.md) - [How to tell players your Rust server is closing](https://rustsc.com/learn/community/tell-players-a-rust-server-is-closing/index.html.md) - [What to do with Discord after your Rust community winds down](https://rustsc.com/learn/community/wind-down-a-rust-community-discord/index.html.md) - [Why is team chat missing in Rust+ after changing teams?](https://rustsc.com/learn/community/rust-plus-team-chat-missing-after-team-change/index.html.md) - [Which Rust map markers can teammates see?](https://rustsc.com/learn/community/which-rust-map-markers-do-teammates-see/index.html.md) - [How can a visitor use one door in your Rust community workshop?](https://rustsc.com/learn/community/give-a-visitor-access-to-one-rust-workshop-door/index.html.md) - [Should your PvE Rust server add a dueling area or a combat weekend?](https://rustsc.com/learn/community/choose-a-combat-format-for-a-pve-rust-server/index.html.md) - [Open a trading market on your PvE Rust server](https://rustsc.com/learn/community/open-a-pve-rust-trading-market/index.html.md) - [Teach your Rust server's roleplay in one first encounter](https://rustsc.com/learn/community/write-a-first-roleplay-encounter-for-your-rust-server/index.html.md) - [Run a shadow shift for a new Rust moderator](https://rustsc.com/learn/community/run-a-shadow-shift-for-a-rust-moderator/index.html.md) - [Which rules should all your Rust worlds share?](https://rustsc.com/learn/community/choose-shared-rules-for-multiple-rust-worlds/index.html.md) - [How should PvE players share a Rust monument?](https://rustsc.com/learn/community/share-a-rust-pve-monument-with-other-groups/index.html.md) - [Judge a Rust building contest players want to enter again](https://rustsc.com/learn/community/judge-a-rust-building-contest/index.html.md) - [Run a tool-lending bench for new PvE Rust players](https://rustsc.com/learn/community/start-a-rust-pve-tool-lending-bench/index.html.md) - [Interview two Rust moderator volunteers for the same job](https://rustsc.com/learn/community/interview-a-rust-moderator-volunteer/index.html.md) - [Get two Rust moderators to apply the same rule consistently](https://rustsc.com/learn/community/calibrate-rust-moderators-on-one-rule/index.html.md) - [Lay out a Rust village with private plots and open paths](https://rustsc.com/learn/community/lay-out-a-rust-village-with-private-plots/index.html.md) - [Save the story of your Rust roleplay town before wipe](https://rustsc.com/learn/community/archive-a-rust-roleplay-town-before-wipe/index.html.md) - [Record and check a Rust demo for your community showcase](https://rustsc.com/learn/community/record-a-rust-demo-for-a-community-showcase/index.html.md) - [Run a Rust roleplay ferry that can finish on foot](https://rustsc.com/learn/community/run-a-rust-roleplay-ferry-with-a-backup/index.html.md) - [What should a Rust event host be able to decide?](https://rustsc.com/learn/community/decide-what-an-event-host-can-settle-in-rust/index.html.md) - [Review a report that a Rust moderator misused staff powers](https://rustsc.com/learn/community/review-a-rust-moderator-staff-powers-report/index.html.md) - [Offer a starter kit without making it the best way to gather](https://rustsc.com/learn/community/offer-a-pve-rust-starter-kit-once/index.html.md) - [Host a Rust creator shoot without filming live players](https://rustsc.com/learn/community/host-a-rust-creator-shoot-without-filming-players/index.html.md) - [Write a staff conduct agreement your Rust players can use](https://rustsc.com/learn/community/write-a-rust-staff-conduct-agreement/index.html.md) - [What should you take off an overloaded Rust volunteer's plate?](https://rustsc.com/learn/community/reduce-one-rust-volunteers-workload/index.html.md) - [Run one events calendar for several Rust worlds](https://rustsc.com/learn/community/run-one-event-calendar-for-your-rust-worlds/index.html.md) - [Why did a player take damage on your PvE Rust server?](https://rustsc.com/learn/community/diagnose-unexpected-player-damage-on-a-pve-rust-server/index.html.md) - [Open your Rust builders' town for a guided tour](https://rustsc.com/learn/community/run-a-guided-rust-builders-town-tour/index.html.md) - [Clear a Rust report backlog after wipe weekend](https://rustsc.com/learn/community/clear-a-rust-player-report-backlog-after-wipe/index.html.md) - [Hold a short staff debrief after a rough Rust wipe](https://rustsc.com/learn/community/debrief-with-rust-staff-after-a-rough-wipe/index.html.md) - [Resolve a disagreement between your Rust moderation leads](https://rustsc.com/learn/community/resolve-a-disagreement-between-rust-moderation-leads/index.html.md) - [Tell players when one of your Rust worlds is taking a break](https://rustsc.com/learn/community/announce-a-temporary-pause-on-one-rust-world/index.html.md) - [How should you reclaim an abandoned plot in a Rust village?](https://rustsc.com/learn/community/return-an-abandoned-plot-to-your-rust-village/index.html.md) - [Pair a new PvE Rust player with a guide for one session](https://rustsc.com/learn/community/pair-new-rust-pve-players-with-a-volunteer-guide/index.html.md) - [Bring a Rust moderator back after a long break](https://rustsc.com/learn/community/bring-a-rust-moderator-back-after-a-break/index.html.md) - [Give a Rust volunteer their first lead shift](https://rustsc.com/learn/community/give-a-rust-volunteer-the-first-lead-shift/index.html.md) - [Handle one conduct incident reported from two Rust worlds](https://rustsc.com/learn/community/handle-a-conduct-incident-reported-from-two-rust-worlds/index.html.md) - [Help players choose the right world in your Rust community](https://rustsc.com/learn/community/help-players-pick-the-right-world-in-your-rust-community/index.html.md) - [An Oxide plugin loaded. Why is a player denied permission?](https://rustsc.com/learn/community/oxide-plugin-loaded-player-permission-denied/index.html.md) ## [Server management](https://rustsc.com/learn/management/index.html.md) Build a routine for running and maintaining a Rust dedicated server. - [How to bring your Rust server back after a power cut](https://rustsc.com/learn/management/rust-server-start-after-power-returns/index.html.md) - [How to choose a host reboot window around two Rust worlds](https://rustsc.com/learn/management/choose-a-maintenance-window-for-host-reboot/index.html.md) - [How to restart a Rust server without losing the latest save](https://rustsc.com/learn/management/restart-rust-without-losing-the-latest-save/index.html.md) - [Should you restart Rust or reboot the host?](https://rustsc.com/learn/management/restart-rust-or-reboot-the-host/index.html.md) - [Track disk space as your Rust world grows](https://rustsc.com/learn/management/measure-rust-save-growth-before-disk-fills/index.html.md) - [What to do when Rust logs fill the drive](https://rustsc.com/learn/management/rust-disk-filling-with-logs/index.html.md) - [Schedule a Rust restart in your players’ time zone](https://rustsc.com/learn/management/schedule-rust-restart-in-player-time-zone/index.html.md) - [How to reboot a host running several Rust servers](https://rustsc.com/learn/management/reboot-a-host-with-several-rust-servers/index.html.md) - [Replace a Rust restart script one job at a time](https://rustsc.com/learn/management/replace-an-old-rust-restart-script-safely/index.html.md) - [What to tell players in Discord and in Rust chat on wipe day](https://rustsc.com/learn/management/rust-wipe-messages-for-discord-and-game-chat/index.html.md) - [How to announce a Rust wipe across time zones](https://rustsc.com/learn/management/plan-a-rust-wipe-across-time-zones/index.html.md) - [How to hand over a Rust server outage to another helper](https://rustsc.com/learn/management/hand-over-a-rust-server-outage/index.html.md) - [Make a Rust server staff rota people can stick to](https://rustsc.com/learn/management/make-a-rust-server-staff-rota/index.html.md) - [What should your Rust server helper cover this weekend?](https://rustsc.com/learn/management/weekend-rust-server-cover/index.html.md) - [Reduce the Discord pings your Rust volunteers have to answer](https://rustsc.com/learn/management/reduce-rust-volunteer-pings/index.html.md) - [How to take a break when you run a Rust server alone](https://rustsc.com/learn/management/take-a-break-from-running-your-rust-server/index.html.md) - [Compare Rust server managers with one real job](https://rustsc.com/learn/management/compare-rust-server-managers-with-one-workflow/index.html.md) - [Try a Rust manager beside the tools you already use](https://rustsc.com/learn/management/try-a-rust-manager-with-your-current-tools-running/index.html.md) - [Which jobs can your management tool do on vanilla Rust?](https://rustsc.com/learn/management/test-manager-jobs-on-vanilla-rust/index.html.md) - [What can you still do when your Rust dashboard is unavailable?](https://rustsc.com/learn/management/manage-rust-without-the-usual-dashboard/index.html.md) - [Can your activity history tell you who restarted Rust?](https://rustsc.com/learn/management/tell-who-restarted-rust-from-activity-history/index.html.md) - [Hand one Rust maintenance window to a helper](https://rustsc.com/learn/management/delegate-a-rust-maintenance-window/index.html.md) - [How to hand a running Rust server to a new owner](https://rustsc.com/learn/management/hand-rust-server-ownership-to-a-new-owner/index.html.md) - [Put your Rust server’s operating details on one page](https://rustsc.com/learn/management/write-a-rust-server-operator-card/index.html.md) - [What does ‘online’ mean in your Rust management tool?](https://rustsc.com/learn/management/test-what-online-means-in-a-rust-dashboard/index.html.md) - [Which Rust server job should you automate first?](https://rustsc.com/learn/management/pick-your-first-rust-server-automation/index.html.md) - [Should a missed Rust job run when the host comes back?](https://rustsc.com/learn/management/check-what-rust-schedules-do-after-an-outage/index.html.md) - [Pause a Rust automation and know when it will come back](https://rustsc.com/learn/management/pause-a-rust-automation-with-a-return-date/index.html.md) - [When should automatic Rust recovery send you an alert?](https://rustsc.com/learn/management/decide-when-rust-recovery-should-alert-you/index.html.md) - [Test a bulk Rust action before using it on every server](https://rustsc.com/learn/management/test-bulk-actions-across-rust-servers/index.html.md) - [What happens when two helpers restart the same Rust server?](https://rustsc.com/learn/management/test-two-simultaneous-rust-restart-requests/index.html.md) - [Should you retry a Rust panel action after a timeout?](https://rustsc.com/learn/management/retry-a-rust-panel-action-after-a-timeout/index.html.md) - [Try a management tool update on one Rust host first](https://rustsc.com/learn/management/try-a-manager-update-on-one-rust-host-first/index.html.md) - [What still runs after you disconnect a Rust manager?](https://rustsc.com/learn/management/find-rust-jobs-before-disconnecting-a-manager/index.html.md) - [What schedule details should you keep when changing Rust tools?](https://rustsc.com/learn/management/keep-your-rust-schedules-when-changing-tools/index.html.md) - [Can you open a Rust management tool’s export somewhere else?](https://rustsc.com/learn/management/test-a-rust-manager-export-before-paying/index.html.md) - [Do you need the Rust console or the host panel away from home?](https://rustsc.com/learn/management/choose-console-or-panel-for-rust-admin-away/index.html.md) - [Can you do your Rust admin work on your phone?](https://rustsc.com/learn/management/test-a-rust-tool-on-your-phone/index.html.md) - [How much of your week will a Rust management tool take?](https://rustsc.com/learn/management/check-hours-to-run-rust-tools-before-switching/index.html.md) - [What will a Rust management tool tell you when a wipe fails?](https://rustsc.com/learn/management/test-how-a-rust-manager-shows-failed-wipes/index.html.md) - [Open a Rust practice world alongside your survival server](https://rustsc.com/learn/management/open-a-rust-practice-world-without-copying-the-main-world/index.html.md) - [Which settings should your Rust worlds share?](https://rustsc.com/learn/management/choose-what-rust-worlds-should-share/index.html.md) - [Should a Rust moderator have access to one world or all of them?](https://rustsc.com/learn/management/scope-rust-moderators-to-one-world-or-all-worlds/index.html.md) - [Work out which Rust worlds are affected before restarting](https://rustsc.com/learn/management/check-which-rust-worlds-are-affected-before-restarting-anything/index.html.md) - [Retire one Rust world while keeping your community open](https://rustsc.com/learn/management/retire-one-rust-world-without-closing-your-community/index.html.md) - [Help staff target the right Rust world before a restart](https://rustsc.com/learn/management/label-two-rust-worlds-so-staff-restart-the-right-one/index.html.md) - [What to check before sharing your new Rust server address](https://rustsc.com/learn/management/before-sharing-a-new-server-address/index.html.md) [Browse RustSC product guides](https://rustsc.com/support/guides/index.html.md) ## About these guides Rust Server Cupboard publishes these guides for people running Rust dedicated servers. We check the instructions against the sources listed on each article. [Suggest a correction](https://rustsc.com/support/contact/index.html.md) --- HTML version: https://rustsc.com/learn/ --- # Server setup Install a Rust dedicated server and get ready for your first players. ## Start here - [Your Rust server boots. What should you do in the first week?](https://rustsc.com/learn/setup/first-week-after-your-rust-server-boots/index.html.md) - [Build a plugin change rehearsal checklist](https://rustsc.com/learn/setup/first-plugin-download-to-working-feature/index.html.md) - [Manage plugins in RustSC](https://rustsc.com/support/guides/plugins/index.html.md) [Rust server guides](https://rustsc.com/learn/index.html.md) - [Your Rust server boots. What should you do in the first week?](https://rustsc.com/learn/setup/first-week-after-your-rust-server-boots/index.html.md). Set up a usable first-week routine for saves, restarts and keeping players informed. - [How to read a Rust server launch script](https://rustsc.com/learn/setup/read-your-rust-server-launch-script/index.html.md). Find the lines that install or update Rust, launch the server and choose its settings. - [Where does your Rust server keep its active world?](https://rustsc.com/learn/setup/find-the-active-rust-server-identity-folder/index.html.md). Follow server.identity from startup settings to the folder with the live world, blueprints and game settings. - [How to make yourself a Rust server admin and check it worked](https://rustsc.com/learn/setup/give-yourself-rust-game-admin/index.html.md). Grant game owner access to your Steam account and verify that the intended account received it. - [How to assign ports to a second Rust server on one host](https://rustsc.com/learn/setup/allocate-ports-for-a-second-rust-server/index.html.md). List each game's, browser's, console's and Rust+'s own endpoints and confirm which world each connection reaches. - [How to test your Rust server from another network](https://rustsc.com/learn/setup/test-your-rust-server-from-another-network/index.html.md). Use a mobile hotspot or an outside player to verify your public game address. - [Install Carbon on a self-hosted Rust server](https://rustsc.com/learn/setup/install-carbon-launch-script/index.html.md). Choose the Carbon build for your host and check that your normal startup command actually loads it. - [Install your first Rust plugin and test what it does](https://rustsc.com/learn/setup/first-plugin-download-to-working-feature/index.html.md). Download an Oxide plugin, rehearse a player-visible change on a spare world and check you can put it back. - [Where do Rust plugin .cs files and extension DLLs go?](https://rustsc.com/learn/setup/plugin-cs-vs-extension-dll/index.html.md). Identify a Rust add-on before installing it and confirm an extension loaded in the right framework. - [Which Rust plugin dependencies should you install first?](https://rustsc.com/learn/setup/install-rust-plugin-dependencies-in-order/index.html.md). Read a plugin's required and optional integrations and prove the dependencies before loading the main plugin. - [How to set up Rust+ on your dedicated server](https://rustsc.com/learn/setup/set-up-rust-plus-on-your-dedicated-server/index.html.md). Enable the Rust companion port, pair your phone in the game and check it from outside the host network. - [Which Rust ports should you forward at home?](https://rustsc.com/learn/setup/game-port-and-query-port-at-home/index.html.md). Set up separate UDP rules for playing on a home Rust server and finding it in the browser. --- HTML version: https://rustsc.com/learn/setup/ --- # Hosting Choose where to host a Rust server and understand what access you need. ## Start here - [Host Rust at home or rent a server?](https://rustsc.com/learn/hosting/home-network-or-rented-rust-server/index.html.md) - [Compare your renewal and moving costs](https://rustsc.com/learn/hosting/rust-server-rental-renewal-cost/index.html.md) - [Check RustSC hosting compatibility](https://rustsc.com/compatibility/index.html.md) [Rust server guides](https://rustsc.com/learn/index.html.md) - [Windows or Linux for your first Rust server?](https://rustsc.com/learn/hosting/windows-or-linux-for-your-first-rust-server/index.html.md). Choose the operating system you can maintain and recover on your own. - [Can you play Rust and host a Rust server on the same PC?](https://rustsc.com/learn/hosting/play-and-host-on-one-pc/index.html.md). Try a realistic play session and check what friends experience before committing your gaming PC to hosting. - [How to turn a public Rust server into a friends-only server](https://rustsc.com/learn/hosting/make-a-public-rust-server-friends-only/index.html.md). Remove a public browser listing and separately control who can connect by address. - [Will a second Rust server fit on the same host?](https://rustsc.com/learn/hosting/will-a-second-rust-server-fit-on-one-host/index.html.md). Compare one busy Rust world with both worlds running, then decide whether to keep them on one host. - [Host Rust at home or rent a server?](https://rustsc.com/learn/hosting/home-network-or-rented-rust-server/index.html.md). Choose a home host or rental for your friend group's Rust world, including play while the owner is offline. - [What backup access should a rented Rust server helper have?](https://rustsc.com/learn/hosting/give-a-helper-backup-access-on-rented-rust/index.html.md). Decide whether a helper needs to create, download or restore server backups. - [How to move a Rust server hostname to a new host](https://rustsc.com/learn/hosting/move-your-rust-server-hostname/index.html.md). Update the address behind your domain name and check the game port players reach. - [What to take with you before cancelling a Rust server rental](https://rustsc.com/learn/hosting/before-you-cancel-a-rust-server-rental/index.html.md). Download the world and settings from the old rental and prove the copy is useful while you still have access. - [Can you run a Rust server just for game night?](https://rustsc.com/learn/hosting/run-a-rust-server-just-for-game-night/index.html.md). Arrange an on-demand Rust session with friends and make offline hours and the end-of-night stop clear. - [Will a Rust management tool do the same jobs on both your hosts?](https://rustsc.com/learn/hosting/test-a-rust-management-tool-on-different-hosts/index.html.md). Verify the exact actions a tool can perform on each rental or self-hosted server before planning one routine for both. - [How to compare Rust server rental renewal costs](https://rustsc.com/learn/hosting/rust-server-rental-renewal-cost/index.html.md). Use your next charge to compare keeping a Rust rental with moving, including extra services and any period of paying for both. - [Which hosting region should you pick for your Rust players?](https://rustsc.com/learn/hosting/choose-a-rust-rental-region-with-players/index.html.md). Compare two candidate locations with the players who will actually join, then choose based on a short play test. - [What will a Rust server host help you fix?](https://rustsc.com/learn/hosting/check-rust-rental-support-before-buying/index.html.md). Use one realistic startup failure to find out who can diagnose it and who will make the repair before you rent. - [Does your Rust rental need more disk space or more memory?](https://rustsc.com/learn/hosting/choose-rust-rental-disk-or-memory/index.html.md). Use the last failed save or start and your panel’s measurements to ask for the resource you actually need. - [Will Rust backup downloads use up your host’s transfer allowance?](https://rustsc.com/learn/hosting/rust-host-transfer-allowance-for-backups/index.html.md). Estimate backup traffic through one rental period and find out which direction or storage service counts it. - [What does a Rust rental’s backup allowance actually cover?](https://rustsc.com/learn/hosting/compare-rust-rental-backup-allowances/index.html.md). Compare two rental backup offers by who can make, download and restore a copy, and what happens when the allowance fills. - [Shared or dedicated CPU for a Rust rental?](https://rustsc.com/learn/hosting/rust-rental-shared-or-dedicated-cpu/index.html.md). Find out what CPU access a rental provides and compare it during the play sessions that matter to your server. - [Can a Rust rental run the custom map you already have?](https://rustsc.com/learn/hosting/choose-rust-rental-with-custom-map-access/index.html.md). Confirm where the map can live, who sets its startup URL and how a player would download it. - [Will a Rust rental keep its address when the host moves it?](https://rustsc.com/learn/hosting/rust-rental-region-transfer-keep-or-change-address/index.html.md). Confirm which address and ports survive a provider move, then choose a cutover your players can follow. - [Do more Rust rental slots mean more capacity?](https://rustsc.com/learn/hosting/rust-rental-slot-count-and-resource-limits/index.html.md). Check which resources change with a higher slot allowance before paying for room your Rust world might never use. - [How to try a Rust rental without moving your players](https://rustsc.com/learn/hosting/try-a-rust-rental-without-moving-your-players/index.html.md). Use a temporary Rust world to test the rental's join, save and recovery jobs while your main world stays open. - [Would losing your Rust rental login also lock you out of backups?](https://rustsc.com/learn/hosting/check-rust-rental-and-backup-account-separation/index.html.md). Find out who can still read a backup if the rental account or its recovery email is unavailable. - [Who controls game and framework updates on a Rust rental?](https://rustsc.com/learn/hosting/choose-updates-you-control-on-a-rust-rental/index.html.md). Before renting a modded Rust server, ask who updates it and how you verify that the framework and plugins work again. - [Will your Rust rental have enough disk for the next map?](https://rustsc.com/learn/hosting/check-rust-rental-disk-quota-before-a-map-change/index.html.md). Find out which files count towards the rental's disk allowance while the old and new maps both need space. - [Should two Rust worlds share one host?](https://rustsc.com/learn/hosting/choose-one-or-two-hosts-for-rust-worlds/index.html.md). Choose which worlds can go offline together before deciding where to put your main and event servers. - [Does your Rust community need a second world?](https://rustsc.com/learn/hosting/does-your-rust-community-need-a-second-world/index.html.md). Choose between a permanent second world, a short event and a change to your current world using player demand and staff coverage. - [What address should friends use to join your Rust server?](https://rustsc.com/learn/hosting/which-address-should-friends-use/index.html.md). Give friends the public game address and test it from outside your home network. - [Can you add a Rust server manager and keep your rented server?](https://rustsc.com/learn/hosting/access-needed-for-rented-server-maintenance/index.html.md). Match the jobs you want a Rust server manager to do with the console, file or panel access your rental includes. Know what to ask your host before connecting. --- HTML version: https://rustsc.com/learn/hosting/ --- # Wipes Plan Rust server wipes and decide what players will keep or lose. [Rust server guides](https://rustsc.com/learn/index.html.md) - [What changes at your first Rust force wipe?](https://rustsc.com/learn/wipes/first-force-wipe-versus-elective-wipe/index.html.md). Separate the reset required by the studio’s update from the additional wipes you schedule. - [Should your Rust server wipe weekly or monthly?](https://rustsc.com/learn/wipes/weekly-or-monthly-rust-wipes/index.html.md). Choose a cadence based on how long players need to reach the parts of the game they enjoy. - [What should your Rust wipe announcement say will reset?](https://rustsc.com/learn/wipes/announce-what-a-rust-wipe-resets/index.html.md). Tell players precisely what happens to bases, learned blueprints and community progress. - [How to stop two Rust wipe schedules from colliding](https://rustsc.com/learn/wipes/avoid-two-rust-wipes-in-one-window/index.html.md). Check the next dated jobs, leave one reset for each world and verify staff can cover both worlds when windows overlap. - [Should you change your Rust map seed at the next wipe?](https://rustsc.com/learn/wipes/new-seed-or-same-layout-next-wipe/index.html.md). Decide whether players should return to a familiar layout or explore a new one. - [Which Rust plugin data should reset at a wipe?](https://rustsc.com/learn/wipes/choose-plugin-data-to-reset-at-wipe/index.html.md). Separate world-specific plugin records from settings and progress your community expects to keep. - [How to rehearse a Rust wipe before wipe night](https://rustsc.com/learn/wipes/test-a-rust-wipe-plan-before-running-it/index.html.md). Test the exact reset on a disposable world and compare what changed with your wipe checklist. - [A Rust wipe stopped halfway. What should you check first?](https://rustsc.com/learn/wipes/check-an-interrupted-rust-wipe-before-retrying/index.html.md). Find the last completed step and preserve the current state before you retry anything. - [How to check Rust’s in-game wipe countdown](https://rustsc.com/learn/wipes/match-rust-in-game-countdown-to-real-wipe/index.html.md). Use PrintWipe to compare the time shown in Rust with the schedule that actually runs your wipe. - [What to check before telling players a Rust wipe is finished](https://rustsc.com/learn/wipes/check-rust-world-before-announcing-wipe-complete/index.html.md). Verify the new world is playable with a fresh client before posting the all-clear. - [Which Rust server changes should wait until after the wipe?](https://rustsc.com/learn/wipes/choose-rust-changes-to-defer-on-wipe-night/index.html.md). Pick the changes that must ship together and leave a playable first session if an optional job slips. - [Which scheduled Rust jobs should wait until the wipe is over?](https://rustsc.com/learn/wipes/pause-rust-jobs-during-a-wipe-window/index.html.md). Pause the jobs that could interrupt the wipe, preserve the notice and check what will run after you reopen. - [What should you write down after a Rust wipe?](https://rustsc.com/learn/wipes/keep-a-short-rust-wipe-change-record/index.html.md). Leave a short record that lets you or a helper reconstruct the last wipe without searching several tools. - [How to tell your Rust players a wipe is delayed](https://rustsc.com/learn/wipes/update-a-rust-wipe-announcement-after-a-delay/index.html.md). Replace the old wipe time in the places players actually look, with a confirmed new time or the time of your next update. - [How to check that blueprints survived a Rust map wipe](https://rustsc.com/learn/wipes/verify-blueprints-after-map-wipe/index.html.md). Use a known learned blueprint and one player account to check what carried over to the new map. [Schedule a wipe in RustSC](https://rustsc.com/support/guides/schedule-wipe/index.html.md) --- HTML version: https://rustsc.com/learn/wipes/ --- # Backups and recovery Back up your Rust server and recover a world when something goes wrong. ## Start here - [How to prove your Rust server backup can be restored](https://rustsc.com/learn/recovery/prove-a-local-backup-with-a-test-restore/index.html.md) - [Estimate space for your backup copies](https://rustsc.com/learn/recovery/keep-enough-rust-backups-without-filling-disk/index.html.md) - [Restore a backup in RustSC](https://rustsc.com/support/guides/restore-backup/index.html.md) [Rust server guides](https://rustsc.com/learn/index.html.md) - [Move Rust plugin settings and player data to another server](https://rustsc.com/learn/recovery/move-plugin-settings-and-player-data/index.html.md). Identify the files and storage your plugin needs before moving its settings and player history to a new host. - [Which Rust server backup should you restore after an incident?](https://rustsc.com/learn/recovery/choose-rust-backup-before-an-incident/index.html.md). Use the incident, save and backup times to choose a usable recovery point and explain what players would lose. - [Why is my Rust world empty after changing the server identity?](https://rustsc.com/learn/recovery/rust-world-empty-after-server-identity-change/index.html.md). Find out if Rust opened a new save folder and recover the original world without writing over either copy. - [Should you stop a Rust server before taking a backup?](https://rustsc.com/learn/recovery/rust-backup-running-or-stopped/index.html.md). Decide when a running backup is suitable and when to use a short maintenance window for a coordinated copy. - [Which files belong in a Rust server backup?](https://rustsc.com/learn/recovery/what-a-rust-server-backup-needs-to-include/index.html.md). Build a backup inventory for terrain, buildings, player progress, configuration and modded server data. - [Is a Rust server backup on the same disk enough?](https://rustsc.com/learn/recovery/rust-backup-on-the-same-disk/index.html.md). Choose a backup destination that covers the failures you want to recover from. - [How many Rust server backups should you keep on the host?](https://rustsc.com/learn/recovery/keep-enough-rust-backups-without-filling-disk/index.html.md). Estimate the space for your Rust backup history, the next backup and room for the game to keep saving. - [When can a previous Rust save recover a damaged world?](https://rustsc.com/learn/recovery/rust-rotated-save-or-full-backup/index.html.md). Choose between Rust's previous world save and a full backup based on what was damaged. - [What to save before rolling back a Rust server](https://rustsc.com/learn/recovery/save-current-rust-world-before-rollback/index.html.md). Preserve the current world, records and settings so you can recover from the rollback itself. - [How to recover one Rust server setting without rolling back the map](https://rustsc.com/learn/recovery/recover-rust-setting-without-rolling-back-world/index.html.md). Read an old backup in a separate folder and put back a known value while keeping current play. - [How to recover deleted Oxide plugin data](https://rustsc.com/learn/recovery/recover-deleted-oxide-plugin-data/index.html.md). Find the plugin's saved records, check which files belong together, and recover them without an unnecessary world rollback. - [How to change a restic password without losing your Rust backups](https://rustsc.com/learn/recovery/change-restic-backup-password-without-losing-history/index.html.md). Verify replacement access to a self-managed repository before retiring old credentials. - [Can you get to your Rust backups if the host is gone?](https://rustsc.com/learn/recovery/check-backup-access-with-host-unavailable/index.html.md). Rehearse getting an independent copy with the access and tools you will have after losing the host. - [What to bring when restoring a Rust backup from Windows to Linux](https://rustsc.com/learn/recovery/move-rust-backup-from-windows-to-linux/index.html.md). Move the server data, rebuild the launch settings, and catch path or permission errors before cutover. - [Can you restore an old Rust save after a forced wipe?](https://rustsc.com/learn/recovery/restore-rust-save-after-forced-wipe/index.html.md). Check the save version and world settings before using a backup on the updated game. - [What to keep for Rust+ when restoring the same server](https://rustsc.com/learn/recovery/preserve-rust-plus-pairing-when-restoring/index.html.md). Keep the files used by Rust+ with the original server and check pairing safely after a move. - [Which SQLite files do you need when copying a Rust database?](https://rustsc.com/learn/recovery/copy-rust-sqlite-database-and-wal/index.html.md). Keep a Rust player or plugin database with its matching side files and check the copy before restoring it. - [How often should you back up a Rust server?](https://rustsc.com/learn/recovery/rust-backup-frequency-and-manual-checkpoints/index.html.md). Choose a routine based on how much play you can replay, and save extra copies before risky changes. - [Which custom map file should you keep with a Rust backup?](https://rustsc.com/learn/recovery/archive-custom-rust-map-for-recovery/index.html.md). Archive the exact custom map behind a save so a changed download link does not block recovery. - [Which bans and staff permissions should you check after a Rust restore?](https://rustsc.com/learn/recovery/check-bans-and-staff-after-rust-restore/index.html.md). Keep an earlier world without undoing later moderation and staff decisions. - [What can you share from a Rust server backup when asking for help?](https://rustsc.com/learn/recovery/what-to-share-from-rust-backup/index.html.md). Send the smallest useful piece of a backup without exposing server access, player records or Rust+ pairing files. - [Why is your Rust panel backup download so small?](https://rustsc.com/learn/recovery/rust-panel-backup-download-smaller-than-expected/index.html.md). Open the downloaded archive and compare its actual contents with the world you meant to back up. - [Can a Rust backup restore fit into your wipe window?](https://rustsc.com/learn/recovery/measure-rust-restore-time-before-wipe/index.html.md). Time a separate restore from retrieval through successful player join so you know what can fit on wipe night. - [Did your Rust backup restore go into the wrong world?](https://rustsc.com/learn/recovery/rust-restore-changed-the-wrong-world/index.html.md). Identify which prepared world received the restore while preserving both worlds and their remaining recovery points. - [A Rust backup is missing from the panel. Can you still use the file?](https://rustsc.com/learn/recovery/rust-backup-missing-from-panel-but-file-exists/index.html.md). Preserve a backup file outside the host and identify it before assuming the panel can restore it. - [What should you check after replacing your Rust server disk?](https://rustsc.com/learn/recovery/restore-rust-after-a-disk-replacement/index.html.md). Confirm the game and backup jobs point to the intended drives and prove the restored world can save. - [What if a Rust restore leaves plugin balances from a later day?](https://rustsc.com/learn/recovery/rust-world-restore-with-external-plugin-data/index.html.md). Align the game restore and external plugin data in an isolated copy before deciding what progress to keep. - [How to recover a Rust world after its custom map link stops working](https://rustsc.com/learn/recovery/recover-rust-when-the-custom-map-url-is-gone/index.html.md). Provide a replacement download for the exact archived custom map and verify an uncached client can join the saved world. - [Did your Rust backup finish copying over a slow connection?](https://rustsc.com/learn/recovery/verify-a-rust-archive-copy-on-a-slow-link/index.html.md). Compare the archive with a trusted source before discarding either recovery copy. - [Prove a Rust backup belongs to the right world](https://rustsc.com/learn/recovery/prove-a-backup-belongs-to-the-right-rust-world/index.html.md). Check the backup’s origin and recognizable state on an isolated restore before choosing it for the live world. - [Move one Rust world while its neighbour stays open](https://rustsc.com/learn/recovery/move-one-rust-world-while-the-other-stays-open/index.html.md). Use two separate join paths, one final checkpoint and a clear opening decision when moving only one world. - [How to prove your Rust server backup can be restored](https://rustsc.com/learn/recovery/prove-a-local-backup-with-a-test-restore/index.html.md). Restore a local backup into a separate test server and check the world you actually get back. --- HTML version: https://rustsc.com/learn/recovery/ --- # Updates Keep your Rust server, framework and plugins ready for game updates. [Rust server guides](https://rustsc.com/learn/index.html.md) - [How to keep Windows Update from interrupting your busiest Rust hours](https://rustsc.com/learn/updates/windows-update-restarts-on-a-rust-host/index.html.md). Use active hours and a planned restart without turning off Windows updates. - [How to put Oxide back after a Rust update](https://rustsc.com/learn/updates/install-oxide-after-rust-update/index.html.md). Check whether an update replaced Oxide and reinstall the matching build without starting over on your world. - [Should you run Oxide or Carbon on your Rust server?](https://rustsc.com/learn/updates/choose-oxide-or-carbon/index.html.md). Choose a framework by checking your essential plugins, your host's install options and who will maintain it. - [Rehearse an Oxide-to-Carbon migration before switching live](https://rustsc.com/learn/updates/rehearse-oxide-to-carbon-migration/index.html.md). Use a stopped copy of your Rust server to prove the files, permissions and player features survive a framework switch. - [Does your Oxide plugin work on Carbon?](https://rustsc.com/learn/updates/test-oxide-plugin-compatibility-on-carbon/index.html.md). Record the build, feature, permission and persistence results for the Oxide plugin you need on Carbon. - [Remove a Rust plugin and keep a way to bring it back](https://rustsc.com/learn/updates/remove-rust-plugin-without-losing-data/index.html.md). Retire a Rust plugin without deleting shared files, historical data or the only working copy. - [Track Rust plugin versions across marketplaces](https://rustsc.com/learn/updates/rust-plugin-version-register/index.html.md). Keep a short plugin register that distinguishes the file your server loaded from the release a marketplace lists. - [Roll back a plugin update that changed its data files](https://rustsc.com/learn/updates/rollback-plugin-update-with-data-conversion/index.html.md). Test whether the old Rust plugin can recover a matching pre-update copy and decide what to do with newer player progress. - [SteamCMD succeeded. Why is Rust still on the old build?](https://rustsc.com/learn/updates/steamcmd-updated-a-different-rust-folder/index.html.md). Match SteamCMD’s target directory to the executable your Rust server actually starts after the update. - [Check the Rust branches when a new build will not connect](https://rustsc.com/learn/updates/rust-client-and-server-on-different-branches/index.html.md). Verify the client and dedicated server target the same release branch before repeating a successful download. - [When should you validate Rust server files?](https://rustsc.com/learn/updates/when-to-validate-rust-server-files/index.html.md). Use SteamCMD validation for a suspected damaged installation and keep a known copy of files you intentionally changed. - [How to prepare your Rust server for a seasonal event](https://rustsc.com/learn/updates/prepare-rust-seasonal-world-settings/index.html.md). Rehearse one documented seasonal setting, then check the affected route and the switch back with ordinary players. - [How to test an existing custom map after a Rust update](https://rustsc.com/learn/updates/check-a-custom-map-after-rust-updates/index.html.md). Use a play route and a small comparison to find what changed when Rust, a custom map or a plugin was updated. - [Which Rust plugin updates belong on force-wipe day?](https://rustsc.com/learn/updates/should-you-update-a-rust-plugin-on-force-wipe-day/index.html.md). Separate build-critical fixes from optional releases and check dependent plugins before reopening. - [Introduce a small Rust plugin change to one world first](https://rustsc.com/learn/updates/introduce-a-rust-plugin-to-one-live-world-first/index.html.md). Use a representative world and a steady comparison world to decide whether to widen a low-impact plugin change. - [What to do when a required Rust plugin is no longer maintained](https://rustsc.com/learn/updates/when-a-required-rust-plugin-is-no-longer-maintained/index.html.md). Find which player features rely on an unsupported plugin and decide whether to maintain, replace or retire it. - [When should you update a Rust server extension by itself?](https://rustsc.com/learn/updates/should-you-update-a-rust-server-extension-separately/index.html.md). Separate an Oxide extension change from other updates when you need to test which dependent plugins still work. [Update your Rust server](https://rustsc.com/support/guides/update-rust/index.html.md) --- HTML version: https://rustsc.com/learn/updates/ --- # Troubleshooting Find the cause when your Rust server will not start or players cannot join. [Rust server guides](https://rustsc.com/learn/index.html.md) - [What to send your rental host when Rust will not start](https://rustsc.com/learn/troubleshooting/support-ticket-for-rust-server-startup-failure/index.html.md). Capture one failed start with the time, first meaningful error and last change so support can find it. - [Can RCON start a Rust server that is offline?](https://rustsc.com/learn/troubleshooting/rust-rcon-versus-panel-power/index.html.md). Choose the game console or the rental panel power control based on which part is running. - [Why your Rust plugin settings revert when you reload it](https://rustsc.com/learn/troubleshooting/plugin-settings-overwritten-on-reload/index.html.md). Use three file reads and one console timeline to see whether a plugin rewrote the file or was reading a different one. - [Read the first useful line in a Rust plugin compile error](https://rustsc.com/learn/troubleshooting/read-rust-plugin-compile-errors/index.html.md). Use the first compiler error to distinguish a missing dependency, a duplicate type and a mismatch with the current game build. - [Is one Carbon plugin slowing down your Rust server?](https://rustsc.com/learn/troubleshooting/measure-one-carbon-plugin-during-a-server-stall/index.html.md). Compare a quiet interval with one repeatable player action and give the plugin author evidence from a Carbon profile. - [The Rust process is running, but the game is frozen](https://rustsc.com/learn/troubleshooting/rust-process-running-but-game-frozen/index.html.md). Check whether Rust stopped responding or whether the problem only affects the network or a remote console. - [Why does Rust keep restarting after a crash?](https://rustsc.com/learn/troubleshooting/automatic-recovery-keeps-restarting-rust/index.html.md). Recognize a repeatable startup failure, preserve the first error and stop automatic retries while you fix it. - [Rust exits after an update. Was it short of memory?](https://rustsc.com/learn/troubleshooting/rust-closed-after-update-check-memory/index.html.md). Match the new build’s exit to host or service memory evidence before upgrading the host or changing the world. - [Is high RAM use a problem for your Rust server?](https://rustsc.com/learn/troubleshooting/high-memory-use-or-real-pressure/index.html.md). Distinguish a large working set from memory pressure using available RAM, paging and stall measurements. - [Is it low client FPS or a slow Rust server?](https://rustsc.com/learn/troubleshooting/client-fps-or-rust-server-lag/index.html.md). Compare a player’s rendering frame rate with symptoms reported by other players before changing the server. - [Why does one Rust server lag while another backs up?](https://rustsc.com/learn/troubleshooting/one-rust-server-lags-during-another-backup/index.html.md). Use timestamps and a separate backup window to test whether two Rust servers are competing for the same disk. - [Why does Rust say the save folder is read-only?](https://rustsc.com/learn/troubleshooting/rust-save-fails-on-a-read-only-filesystem/index.html.md). Distinguish a read-only Linux filesystem from a full disk or a permission error when Rust cannot write its world save. - [Which log explains why a Rust server quit?](https://rustsc.com/learn/troubleshooting/find-the-log-for-an-unexpected-rust-exit/index.html.md). Line up the last game messages, the service exit record and the host’s system log before trying another start. - [Rust startup or remote console failure?](https://rustsc.com/learn/troubleshooting/rust-starts-but-remote-console-is-waiting/index.html.md). Read the startup output to tell whether Rust is loading the world or only its remote console connection has failed. - [Why did a scheduled Rust restart not happen?](https://rustsc.com/learn/troubleshooting/scheduled-rust-restart-did-not-run/index.html.md). Check whether the scheduling tool triggered, then verify what its command actually did to the Rust process. - [Why does Rust+ say your paired server is offline?](https://rustsc.com/learn/troubleshooting/rust-plus-paired-server-offline/index.html.md). Find out whether Rust+ is failing for one phone or everyone, then check the companion port the game actually advertises. - [Why does Rust+ connect but send no phone notifications?](https://rustsc.com/learn/troubleshooting/rust-plus-phone-notifications-missing/index.html.md). Use a teammate join to distinguish the Rust+ alert setting from notification delivery on the phone. - [Rust+ says the Smart Switch is on. Why is the light off?](https://rustsc.com/learn/troubleshooting/why-rust-plus-smart-switch-on-but-light-off/index.html.md). Separate a working remote switch from a missing power feed, the wrong socket or a downstream problem. - [How to test a Rust+ Smart Alarm without waiting for its usual trigger](https://rustsc.com/learn/troubleshooting/test-rust-plus-smart-alarm/index.html.md). Use a button to create a known electrical signal and check where the Smart Alarm stops working. - [Is your Rust Storage Monitor showing the right box?](https://rustsc.com/learn/troubleshooting/rust-plus-storage-monitor-wrong-box/index.html.md). Use one item change to identify the paired container and catch a monitor that has lost power. - [Why won't your Rust CCTV station show a base camera?](https://rustsc.com/learn/troubleshooting/rust-computer-station-cannot-show-base-camera/index.html.md). Check power at both ends, then verify the camera identifier at your in-game CCTV station. - [What does the last death marker on the Rust map show?](https://rustsc.com/learn/troubleshooting/rust-death-map-marker-versus-respawn-point/index.html.md). Help a player separate the recorded place of death from their selectable respawn points and the current location of a body. - [Why is a Rust vending machine missing from the in-game map?](https://rustsc.com/learn/troubleshooting/rust-shop-vending-machine-absent-from-game-map/index.html.md). Check the shop's broadcast setting separately from stock, sell orders and the buyer's map view. - [Why are shops and events missing from the Rust+ map?](https://rustsc.com/learn/troubleshooting/rust-plus-map-missing-shops-and-events/index.html.md). Check what the Rust+ map is expected to show and tell a missing app marker from a failed connection. - [Why can't you give a friend a sleeping bag in Rust?](https://rustsc.com/learn/troubleshooting/rust-cannot-give-sleeping-bag-to-friend/index.html.md). Check the recipient's Bag Gifting setting and respawn point allowance before changing the server. - [Why can one Rust teammate build at the base while another can't?](https://rustsc.com/learn/troubleshooting/why-rust-teammate-cannot-build-at-base/index.html.md). Check the blocked player's Tool Cupboard authorization at the exact spot where building fails. - [Why does a Rust planter stay dry with the sprinkler running?](https://rustsc.com/learn/troubleshooting/rust-farm-sprinkler-runs-but-planter-stays-dry/index.html.md). Follow the water from its source and test one planter before redesigning the farm. - [Why do your Rust base lights go out at night?](https://rustsc.com/learn/troubleshooting/rust-base-lights-go-out-at-night/index.html.md). Check whether the lamps are running directly from the panel or whether the battery cannot carry the load. - [Why did your Rust Industrial Conveyor stop moving items?](https://rustsc.com/learn/troubleshooting/rust-conveyor-stops-moving-items/index.html.md). Prove the transport path with a spare box, then check the filter counts that can keep items in place. - [A player's microphone works elsewhere. Why can't you hear them in Rust?](https://rustsc.com/learn/troubleshooting/rust-player-microphone-works-elsewhere-not-in-game/index.html.md). Compare who can hear the player, then test the input Rust gets before touching the server. - [Why does the Rust sign look blank to only one player?](https://rustsc.com/learn/troubleshooting/rust-sign-blank-for-one-player/index.html.md). Use a known safe sign to separate a player's display preferences from missing artwork on the server. - [Why did your Rust plugin compile but fail to load?](https://rustsc.com/learn/troubleshooting/rust-plugin-compiles-but-does-not-load/index.html.md). Read the next lines in the Oxide console to tell a compiled file from a loaded plugin or a broken feature. - [A Rust reward arrived. Why won’t the shop accept it?](https://rustsc.com/learn/troubleshooting/rust-plugin-balance-changes-but-shop-disagrees/index.html.md). Follow a test reward from the plugin that grants it to the currency the shop actually spends. - [Why does your Rust plugin work after reload but fail on restart?](https://rustsc.com/learn/troubleshooting/rust-plugin-works-after-reload-but-not-after-restart/index.html.md). Compare one clean Oxide startup with one later plugin reload to see when a dependency or feature becomes ready. - [Report a Rust plugin bug the maintainer can reproduce](https://rustsc.com/learn/troubleshooting/report-a-rust-plugin-error-the-maintainer-can-reproduce/index.html.md). Describe one failing player action, its context and a passing comparison in the plugin author's support channel. - [Do two Rust worlds stall when their saves overlap?](https://rustsc.com/learn/troubleshooting/two-rust-worlds-stall-when-saving-at-the-same-time/index.html.md). Compare player symptoms, natural save records and the host’s disk activity before changing either world’s schedule. - [Why does Rust plugin progress disappear after a restart?](https://rustsc.com/learn/troubleshooting/rust-plugin-saves-progress-until-the-next-restart/index.html.md). Follow one test record through a clean stop, a write to the plugin’s store and a fresh startup. - [Why does a Rust plugin run an action twice after reload?](https://rustsc.com/learn/troubleshooting/rust-plugin-runs-an-action-twice-after-reload/index.html.md). Trace a single test event through fresh start and reload to find which tools emit duplicate actions. - [Why can a Rust player still use a plugin after leaving a group?](https://rustsc.com/learn/troubleshooting/rust-plugin-permission-remains-after-group-removal/index.html.md). Trace direct, default and inherited Oxide grants before removing the one permission that should end. - [Check which Rust worlds actually enforce a ban](https://rustsc.com/learn/troubleshooting/check-a-rust-ban-on-the-intended-worlds/index.html.md). Verify an already-decided ban and its removal using expected joins on two test worlds. - [Direct join works, but your Rust server is missing from the browser](https://rustsc.com/learn/troubleshooting/direct-join-works-server-missing-from-browser/index.html.md). Find out whether the query port or a browser filter is hiding a Rust server that players can already join. [Find and fix a server problem](https://rustsc.com/support/guides/not-working/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/ --- # Configuration Understand the settings that control your Rust server and how players find it. [Rust server guides](https://rustsc.com/learn/index.html.md) - [Which Rust setting renames the server in the browser?](https://rustsc.com/learn/configuration/server-name-versus-server-identity/index.html.md). Change the advertised name while keeping the same identity and world save. - [Which Rust plugin JSON file should you edit?](https://rustsc.com/learn/configuration/find-active-plugin-settings-file/index.html.md). Find the settings read by the live copy of your plugin when folders contain similar JSON files. - [Why a Rust plugin can reject valid JSON](https://rustsc.com/learn/configuration/plugin-json-syntax-and-types/index.html.md). Distinguish a JSON punctuation error from a setting in the wrong shape when a plugin rejects its config. - [Change the messages players see from an Oxide plugin](https://rustsc.com/learn/configuration/change-player-facing-rust-plugin-messages/index.html.md). Find the plugin's language file, preserve replacement fields and test the edited message in game. - [How to pick a Rust map size for the players you actually get](https://rustsc.com/learn/configuration/choose-map-size-for-player-density/index.html.md). Compare how concentrated routes and encounters feel on two candidate worlds. - [How to check a Rust seed has the monuments your players expect](https://rustsc.com/learn/configuration/verify-procedural-monuments-before-wipe/index.html.md). Check a candidate world on the intended Rust build before naming its landmarks in a wipe notice. - [Why did Rust ignore a change to your procedural map settings?](https://rustsc.com/learn/configuration/procedural-config-change-did-not-apply/index.html.md). Tell whether Rust reused an existing map or generated a new one with your configuration. - [How to change Rust biomes without losing safe spawn areas](https://rustsc.com/learn/configuration/rust-world-biomes-and-safe-player-spawns/index.html.md). Check spawn terrain and early routes after a procedural change to biomes or terrain difficulty. - [How to check rail and road routes on a Rust map candidate](https://rustsc.com/learn/configuration/check-rust-rail-and-road-routes/index.html.md). Check the actual route between places players will use rather than relying on a generation toggle. - [How to check buildable space on a Rust map candidate](https://rustsc.com/learn/configuration/compare-rust-worlds-by-coastline-build-space/index.html.md). Walk a prospective building area before choosing a world for a building-focused community. - [How to write a Rust server description that fits the browser](https://rustsc.com/learn/configuration/write-a-rust-server-browser-description/index.html.md). Put the kind of game you run first and check the text in the actual Rust details panel. - [How to add a header image and icon to a Rust server listing](https://rustsc.com/learn/configuration/add-a-header-and-icon-to-your-rust-server-listing/index.html.md). Use separate image addresses for the server’s header and logo, then open the listing to check both. - [Which page should you link from your Rust server listing?](https://rustsc.com/learn/configuration/link-a-website-from-your-rust-server-listing/index.html.md). Send players to the right server page and verify that the link opens for someone new. - [Which Rust server tags should you show?](https://rustsc.com/learn/configuration/choose-rust-browser-tags-that-describe-your-game/index.html.md). Choose a short set of supported browser tags that describes how your server actually plays. - [Should your Rust server be listed under Community or Modded?](https://rustsc.com/learn/configuration/choose-community-or-modded-for-a-rust-server/index.html.md). Check how a planned change affects the game before deciding where the server belongs in the browser. - [Why does your Rust server listing show the wrong country?](https://rustsc.com/learn/configuration/fix-the-location-on-a-rust-server-listing/index.html.md). Check the detected location of your Rust host before changing a manual region label. - [Should you turn on Premium for your Rust server?](https://rustsc.com/learn/configuration/decide-whether-to-use-premium-on-a-rust-server/index.html.md). Check who can see and enter a Premium server before switching the setting on. - [How many player slots should you set on a Rust server?](https://rustsc.com/learn/configuration/choose-a-rust-server-player-cap/index.html.md). Choose a cap based on your expected group and a busy session you can actually test. - [Why did a Rust setting change back after restart?](https://rustsc.com/learn/configuration/keep-a-rust-setting-after-restart/index.html.md). Trace one value across the running console, server.cfg and the arguments that start the game. - [Which Rust settings affect eligibility for the secure server list?](https://rustsc.com/learn/configuration/check-secure-listing-settings-on-a-rust-server/index.html.md). Check a public Rust server for legacy security settings before changing the rest of its listing. - [Would Softcore suit the people on your Rust server?](https://rustsc.com/learn/configuration/try-softcore-before-choosing-it-for-your-rust-server/index.html.md). Compare one ordinary gathering trip and respawn in standard survival and Softcore. - [How to tell if your Rust group will enjoy Hardcore navigation](https://rustsc.com/learn/configuration/test-hardcore-navigation-on-a-rust-server/index.html.md). Try a short trip on a Hardcore test server and compare the map before and after equipping a compass. - [What should you test before running a Rust Primitive server?](https://rustsc.com/learn/configuration/check-primitive-progression-on-a-rust-server/index.html.md). Check which gear your group can get and how a typical fight changes in the Primitive game mode. - [How to set up a Rust server for creative building practice](https://rustsc.com/learn/configuration/set-up-a-rust-creative-building-practice-server/index.html.md). Build freely on a practice world, reproduce the tricky placement under survival rules and put the practice area back when you finish. - [How to check Tutorial Island on your Rust server](https://rustsc.com/learn/configuration/enable-and-check-rust-tutorial-island/index.html.md). Enable the tutorial, verify the path for a new player, then advertise it in the browser. - [Should you change the sleeping bag limit on a Rust server?](https://rustsc.com/learn/configuration/choose-a-sleeping-bag-limit-for-your-rust-server/index.html.md). Choose how many respawn options players should have and test what happens at the limit. - [Is Rust decay too fast, or is a base out of upkeep?](https://rustsc.com/learn/configuration/check-rust-upkeep-before-changing-decay/index.html.md). Check one base’s materials and cupboard coverage before changing decay for the whole server. - [How to check the built-in team size on a Rust server](https://rustsc.com/learn/configuration/check-the-built-in-rust-team-size-setting/index.html.md). Set a team roster size and verify invitations inside the game with regular player accounts. - [How to test a shorter locked crate timer on a Rust server](https://rustsc.com/learn/configuration/test-a-rust-locked-crate-hack-timer/index.html.md). Change the hack duration on a test world and see how it changes one encounter. - [What should you check before advertising a Rust server as PvE?](https://rustsc.com/learn/configuration/check-what-pve-means-on-your-rust-server/index.html.md). Turn a PvE listing into an acceptance sheet for damage, homes, sleepers, loot and the hazards you keep. - [Choose one tool to control Rust item stack sizes](https://rustsc.com/learn/configuration/choose-one-source-for-rust-item-stack-sizes/index.html.md). Check whether a Carbon module or a plugin owns your stack limits, then test fresh items and stored stacks on a spare world. - [Check what your Rust gather multiplier actually changes](https://rustsc.com/learn/configuration/test-rust-gather-multipliers-by-source/index.html.md). Compare mining hits, ground pickups and quarry output before you advertise a gather rate to players. - [Test Rust kit claims, cooldowns and limits before opening them](https://rustsc.com/learn/configuration/test-rust-kit-redemption-and-cooldowns/index.html.md). Prove one Rust Kits loadout gives the right items to the right players and still enforces its limits after a restart. - [Copy one Rust setting between worlds without changing the save identity](https://rustsc.com/learn/configuration/copy-rust-settings-between-worlds-without-copying-identity/index.html.md). Transfer an approved setting and confirm the target keeps its own map, progress and ports. - [Reproduce a Rust plugin issue without sharing player data](https://rustsc.com/learn/configuration/check-per-player-rust-plugin-data-before-sharing-a-copy/index.html.md). Build a fresh test record for one plugin behavior and share only the observations a maintainer needs. - [Test a permanent safe zone on your Rust server](https://rustsc.com/learn/configuration/test-a-fixed-rust-safe-zone-before-opening-it/index.html.md). Walk a Zone Manager boundary from both sides and confirm the same protections return after a restart. - [Keep live Discord feeds out of a Rust plugin test server](https://rustsc.com/learn/configuration/keep-live-discord-links-out-of-a-rust-plugin-test-server/index.html.md). Give a test world its own destination and verify one synthetic event reaches only the private test channel. - [Which Rust plugin settings should survive an update?](https://rustsc.com/learn/configuration/compare-rust-plugin-defaults-before-keeping-your-settings/index.html.md). Compare the old defaults, your working configuration and fresh defaults from the new plugin before moving options over. - [Check Rust plugin message placeholders after an update](https://rustsc.com/learn/configuration/test-rust-plugin-language-placeholders-in-game/index.html.md). Verify the current English and translated messages display the intended values for real player actions. - [Why won't my Rust custom map URL load?](https://rustsc.com/learn/configuration/custom-map-url-wont-load/index.html.md). Check that your custom map URL downloads a map file and confirm a new player can join on it. - [Why does my Rust server disappear when I apply a tag filter?](https://rustsc.com/learn/configuration/server-visible-until-browser-tag-filter/index.html.md). Check conflicting server tags when the listing appears with filters cleared. [Change your server settings](https://rustsc.com/support/guides/server-settings/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/ --- # Players and community Manage player access, moderation and communication on your Rust server. [Rust server guides](https://rustsc.com/learn/index.html.md) - [Run a PvP weekend on your PvE Rust server](https://rustsc.com/learn/community/weekend-pvp-on-a-pve-rust-server/index.html.md). Work through a TruePVE event from the first rehearsal to player announcements, boundary checks and the return to peaceful building. - [What should friends agree before starting a private Rust world?](https://rustsc.com/learn/community/agree-a-first-wipe-with-friends/index.html.md). Settle raids, mixed play schedules, late joiners and progress before your friend group commits to its first Rust world. - [Find which Rust plugin handles a chat command](https://rustsc.com/learn/community/find-which-plugin-owns-a-command/index.html.md). Trace a command to its owner when several plugins document the same name or one responds unexpectedly. - [Set up Oxide group inheritance for junior and senior staff](https://rustsc.com/learn/community/oxide-group-inheritance-for-staff/index.html.md). Share a narrow set of Rust plugin permissions and test what each staff level can actually do. - [How to write Rust server rules players can use](https://rustsc.com/learn/community/write-rust-server-rules-players-can-use/index.html.md). Turn a team limit or chat rule into a clear boundary players can follow during a wipe. - [How to announce a Rust server rule change](https://rustsc.com/learn/community/announce-a-rust-server-rule-change/index.html.md). Tell players when a rule applies and what happens to teams already playing under the old wording. - [Where should players send reports about your Rust server?](https://rustsc.com/learn/community/give-rust-players-a-private-report-route/index.html.md). Give players a private way to report local rule breaks and ask for details staff can actually check. - [How to triage Rust player reports](https://rustsc.com/learn/community/triage-rust-player-reports/index.html.md). Work out which report needs attention first and give each open case one next step. - [What does a Rust team-limit report actually show?](https://rustsc.com/learn/community/check-a-rust-team-limit-report/index.html.md). Work through a short raid clip and decide what it establishes before taking action. - [What to do when several Rust players report the same incident](https://rustsc.com/learn/community/handle-duplicate-rust-player-reports/index.html.md). Review one incident together while keeping each player’s original account and evidence. - [How to review a ban appeal for your Rust server](https://rustsc.com/learn/community/run-a-rust-community-ban-appeal/index.html.md). Review a private appeal, line up the original evidence and check that the resulting ban decision takes effect. - [How to correct a moderation mistake on your Rust server](https://rustsc.com/learn/community/correct-a-rust-moderation-mistake/index.html.md). Reverse an incorrect action, update the record and tell the people affected. - [What should a Rust moderator tell players about a report?](https://rustsc.com/learn/community/share-rust-moderation-decisions-without-exposing-reports/index.html.md). Give the reporter, the affected player and the public the details each needs. - [Who should handle a Rust player report?](https://rustsc.com/learn/community/escalate-rust-player-reports-to-the-right-place/index.html.md). Route a server-rule complaint, a suspected cheat or a Discord policy violation to the right place. - [Who handles a report involving a Rust moderator’s own team?](https://rustsc.com/learn/community/when-a-rust-moderator-should-step-aside/index.html.md). Hand a case to someone outside the dispute and keep urgent moderation possible. - [Onboard your first Rust moderator without sharing your login](https://rustsc.com/learn/community/onboard-a-first-rust-server-moderator/index.html.md). Give a first moderator a role sheet and individual access, then review what they can do after their first week. - [What to check when a Rust server moderator leaves](https://rustsc.com/learn/community/remove-rust-server-staff-access-when-someone-leaves/index.html.md). Transfer an unfinished case, remove the former moderator's separate staff roles and check who can still do the job. - [What access does your Rust moderator actually need?](https://rustsc.com/learn/community/choose-access-for-a-rust-moderator/index.html.md). Choose staff access from the job they will do and the server they will cover. - [How to check a Rust moderator’s access after a role change](https://rustsc.com/learn/community/verify-a-rust-moderator-access-change/index.html.md). Use one allowed task and one restricted task to see what a staff access change did. - [How to hand over an open Rust moderation case](https://rustsc.com/learn/community/hand-over-an-open-rust-moderation-case/index.html.md). Leave enough for the next moderator to continue a case without asking the player to start over. - [Which Discord channels does a small Rust community need?](https://rustsc.com/learn/community/organise-discord-channels-for-a-rust-community/index.html.md). Give rules, announcements, ordinary chat and private player reports a place people can find. - [What Rust chat should you share in Discord?](https://rustsc.com/learn/community/choose-which-rust-chat-to-share-in-discord/index.html.md). Pick the chat an outside audience should see and check where a message and reply can go. - [How to help Rust players recognise real staff messages](https://rustsc.com/learn/community/help-rust-players-recognise-real-staff-messages/index.html.md). Give players a way to verify moderation messages and report an account posing as staff. - [What to say when a Rust raid argument takes over global chat](https://rustsc.com/learn/community/calm-a-rust-global-chat-argument/index.html.md). Name the behaviour that needs to stop, move the complaint to staff and follow up privately. - [Where should your Rust players look when Discord is down?](https://rustsc.com/learn/community/keep-rust-players-informed-when-discord-is-down/index.html.md). Give players a way to find the join address and the next event update when they can’t open Discord. - [Keep one current Rust join post in Discord](https://rustsc.com/learn/community/one-current-rust-join-post/index.html.md). Replace scattered server addresses with a single pinned post that works on mobile and is easy to update. - [Turn repeated Rust questions into answers players can find](https://rustsc.com/learn/community/turn-repeat-rust-questions-into-discord-answers/index.html.md). Use real questions from chat to build a short Discord reference with an assigned owner for each answer. - [How to share Rust announcements with another Discord server](https://rustsc.com/learn/community/share-rust-updates-with-partner-discords/index.html.md). Follow a partner’s announcement channel and check that updates, edits and links make it to both communities. - [What to put in a new Rust server launch announcement](https://rustsc.com/learn/community/write-a-rust-server-launch-announcement/index.html.md). Tell players what kind of Rust world is opening, when to turn up and where to get the confirmed join details. - [What to do when a shout-out fills your Rust server](https://rustsc.com/learn/community/rust-server-fills-after-a-shout-out/index.html.md). Handle a sudden rush of players by checking playability, redirecting repeat questions and setting a clear capacity message. - [What to tell players when your Rust server goes down](https://rustsc.com/learn/community/rust-outage-status-post/index.html.md). Post one clear outage update, tell players when to check again and confirm the game is playable before closing it. - [Schedule an in-game Rust event in Discord](https://rustsc.com/learn/community/schedule-a-rust-game-event-in-discord/index.html.md). Create a Discord event for an activity inside Rust, add a usable meeting point and send the start notification. - [Will enough players show up for your Rust event?](https://rustsc.com/learn/community/rust-event-attendance-before-you-commit/index.html.md). Use a time poll, confirmations and a smaller fallback format before volunteers spend an evening preparing. - [How to run signups for a Rust event with limited spots](https://rustsc.com/learn/community/rust-event-spots-and-waitlist/index.html.md). Count participants against the event’s real capacity and give substitutes a clear way to take a free place. - [Help late players catch up at a Rust community event](https://rustsc.com/learn/community/help-late-players-join-a-rust-event/index.html.md). Give late arrivals a meeting point or a next round so the host can keep the activity moving. - [Run one Rust event with another community](https://rustsc.com/learn/community/one-rust-event-two-communities/index.html.md). Agree who hosts the game, who briefs each Discord and where both groups will see a schedule change. - [How to tell players your Rust server is closing](https://rustsc.com/learn/community/tell-players-a-rust-server-is-closing/index.html.md). Announce the final playable time, explain where players can regroup and remove old paths into the closed server. - [What to do with Discord after your Rust community winds down](https://rustsc.com/learn/community/wind-down-a-rust-community-discord/index.html.md). Decide if members still need the Discord, where to find each other and what to preserve before removing it. - [Why is team chat missing in Rust+ after changing teams?](https://rustsc.com/learn/community/rust-plus-team-chat-missing-after-team-change/index.html.md). Check the paired account and the active in-game team with a short test in both directions. - [Which Rust map markers can teammates see?](https://rustsc.com/learn/community/which-rust-map-markers-do-teammates-see/index.html.md). Choose a shared leader marker for a lasting meeting point or a temporary ping for something happening now. - [How can a visitor use one door in your Rust community workshop?](https://rustsc.com/learn/community/give-a-visitor-access-to-one-rust-workshop-door/index.html.md). Test access to one workshop door as a guest and as a passerby, then close access after the visit. - [Should your PvE Rust server add a dueling area or a combat weekend?](https://rustsc.com/learn/community/choose-a-combat-format-for-a-pve-rust-server/index.html.md). Choose a combat format by testing who can opt out, what can be lost and where PvE protection resumes. - [Open a trading market on your PvE Rust server](https://rustsc.com/learn/community/open-a-pve-rust-trading-market/index.html.md). Walk a buyer and vendor through a market trade, then test delivery, private stock and the end of trading. - [Teach your Rust server's roleplay in one first encounter](https://rustsc.com/learn/community/write-a-first-roleplay-encounter-for-your-rust-server/index.html.md). Write a two-minute arrival at a roleplay dock that a stranger can join, pause or leave without reading a lore guide. - [Run a shadow shift for a new Rust moderator](https://rustsc.com/learn/community/run-a-shadow-shift-for-a-rust-moderator/index.html.md). Rehearse moderation judgment with three practice cases and decide which duties the volunteer can perform independently. - [Which rules should all your Rust worlds share?](https://rustsc.com/learn/community/choose-shared-rules-for-multiple-rust-worlds/index.html.md). Choose one set of community conduct rules and short world-specific rules players can distinguish when they switch worlds. - [How should PvE players share a Rust monument?](https://rustsc.com/learn/community/share-a-rust-pve-monument-with-other-groups/index.html.md). Choose who can start, join and loot a contested monument encounter, then explain the rule clearly at the approach. - [Judge a Rust building contest players want to enter again](https://rustsc.com/learn/community/judge-a-rust-building-contest/index.html.md). Set a shared building brief, score two example entries and resolve a tie using a rule announced before the contest. - [Run a tool-lending bench for new PvE Rust players](https://rustsc.com/learn/community/start-a-rust-pve-tool-lending-bench/index.html.md). Lend starter tools without opening the stockroom and handle a late or lost item with a simple household rule. - [Interview two Rust moderator volunteers for the same job](https://rustsc.com/learn/community/interview-a-rust-moderator-volunteer/index.html.md). Use shared questions and compare real availability before choosing a volunteer for your Rust server's vacant shift. - [Get two Rust moderators to apply the same rule consistently](https://rustsc.com/learn/community/calibrate-rust-moderators-on-one-rule/index.html.md). Compare independent decisions on near-matching cases and rewrite the guidance that produced different actions. - [Lay out a Rust village with private plots and open paths](https://rustsc.com/learn/community/lay-out-a-rust-village-with-private-plots/index.html.md). Walk a sample village plot before you allocate land so players can build, reach their doors and keep public paths open. - [Save the story of your Rust roleplay town before wipe](https://rustsc.com/learn/community/archive-a-rust-roleplay-town-before-wipe/index.html.md). Collect a small, readable town archive with dates, captions and community permission before the map resets. - [Record and check a Rust demo for your community showcase](https://rustsc.com/learn/community/record-a-rust-demo-for-a-community-showcase/index.html.md). Record two short client demos, replay them locally and inspect the final video before opening the showcase. - [Run a Rust roleplay ferry that can finish on foot](https://rustsc.com/learn/community/run-a-rust-roleplay-ferry-with-a-backup/index.html.md). Rehearse a passenger journey, a missed departure and a late arrival before making a roleplay ferry public. - [What should a Rust event host be able to decide?](https://rustsc.com/learn/community/decide-what-an-event-host-can-settle-in-rust/index.html.md). Give the event host authority over scores and reruns while defining who handles conduct reports and server changes. - [Review a report that a Rust moderator misused staff powers](https://rustsc.com/learn/community/review-a-rust-moderator-staff-powers-report/index.html.md). Assign an independent reviewer, compare evidence about the staff action and reply to both people in private. - [Offer a starter kit without making it the best way to gather](https://rustsc.com/learn/community/offer-a-pve-rust-starter-kit-once/index.html.md). Choose a modest starter kit and test who can claim it after joining, respawning or returning after a map wipe. - [Host a Rust creator shoot without filming live players](https://rustsc.com/learn/community/host-a-rust-creator-shoot-without-filming-players/index.html.md). Set a separate filming route and repeat a shot with a clean frame when an unrelated player or private location appears. - [Write a staff conduct agreement your Rust players can use](https://rustsc.com/learn/community/write-a-rust-staff-conduct-agreement/index.html.md). Publish what players can expect from moderators and keep a matching staff guide for using powers and handling complaints. - [What should you take off an overloaded Rust volunteer's plate?](https://rustsc.com/learn/community/reduce-one-rust-volunteers-workload/index.html.md). Move one recurring duty, agree when to check in and give the remaining team a clear handoff. - [Run one events calendar for several Rust worlds](https://rustsc.com/learn/community/run-one-event-calendar-for-your-rust-worlds/index.html.md). Resolve a shared staff conflict and publish named world entries players can use to reach the right event. - [Why did a player take damage on your PvE Rust server?](https://rustsc.com/learn/community/diagnose-unexpected-player-damage-on-a-pve-rust-server/index.html.md). Reproduce a reported hit, isolate its source and compare locations before changing a global PvE rule. - [Open your Rust builders' town for a guided tour](https://rustsc.com/learn/community/run-a-guided-rust-builders-town-tour/index.html.md). Walk a three-stop route, check ordinary visitor access and give late arrivals a place to catch up. - [Clear a Rust report backlog after wipe weekend](https://rustsc.com/learn/community/clear-a-rust-player-report-backlog-after-wipe/index.html.md). Assign urgent reports, close resolved follow-ups and leave a named next action for every case kept open. - [Hold a short staff debrief after a rough Rust wipe](https://rustsc.com/learn/community/debrief-with-rust-staff-after-a-rough-wipe/index.html.md). Build a shared timeline and choose one change another volunteer can verify next wipe. - [Resolve a disagreement between your Rust moderation leads](https://rustsc.com/learn/community/resolve-a-disagreement-between-rust-moderation-leads/index.html.md). Assign the immediate decision, hear both readings in private and clarify the staff rule that caused the split. - [Tell players when one of your Rust worlds is taking a break](https://rustsc.com/learn/community/announce-a-temporary-pause-on-one-rust-world/index.html.md). Publish a server-specific pause, an optional place to play and the next update without promising a transfer. - [How should you reclaim an abandoned plot in a Rust village?](https://rustsc.com/learn/community/return-an-abandoned-plot-to-your-rust-village/index.html.md). Give the original resident a fair chance to reply and hand the next resident a plot with clear boundaries and access. - [Pair a new PvE Rust player with a guide for one session](https://rustsc.com/learn/community/pair-new-rust-pve-players-with-a-volunteer-guide/index.html.md). Use one meeting point, one first task and a short check that leaves the newcomer able to play alone. - [Bring a Rust moderator back after a long break](https://rustsc.com/learn/community/bring-a-rust-moderator-back-after-a-break/index.html.md). Catch up on changed duties, practice a recent case and restore only the staff access the returning volunteer needs. - [Give a Rust volunteer their first lead shift](https://rustsc.com/learn/community/give-a-rust-volunteer-the-first-lead-shift/index.html.md). Set the acting lead's staff decisions, backup path and handback time, then test three requests before the owner leaves. - [Handle one conduct incident reported from two Rust worlds](https://rustsc.com/learn/community/handle-a-conduct-incident-reported-from-two-rust-worlds/index.html.md). Link related reports privately, separate local play rules from shared conduct and check the scope of the outcome. - [Help players choose the right world in your Rust community](https://rustsc.com/learn/community/help-players-pick-the-right-world-in-your-rust-community/index.html.md). Write a two-world join guide that tells players how each world plays and gets them to the right place. - [An Oxide plugin loaded. Why is a player denied permission?](https://rustsc.com/learn/community/oxide-plugin-loaded-player-permission-denied/index.html.md). Find the exact permission an Oxide command needs, check the player's access, and test a narrow grant. [Manage players in RustSC](https://rustsc.com/support/guides/manage-players/index.html.md) --- HTML version: https://rustsc.com/learn/community/ --- # Server management Build a routine for running and maintaining a Rust dedicated server. ## Start here - [What to tell players in Discord and in Rust chat on wipe day](https://rustsc.com/learn/management/rust-wipe-messages-for-discord-and-game-chat/index.html.md) - [Write a wipe announcement](https://rustsc.com/learn/management/plan-a-rust-wipe-across-time-zones/index.html.md) - [Schedule a wipe in RustSC](https://rustsc.com/support/guides/schedule-wipe/index.html.md) [Rust server guides](https://rustsc.com/learn/index.html.md) - [How to bring your Rust server back after a power cut](https://rustsc.com/learn/management/rust-server-start-after-power-returns/index.html.md). Check whether the host powers up again and starts Rust without a desktop sign-in. - [How to choose a host reboot window around two Rust worlds](https://rustsc.com/learn/management/choose-a-maintenance-window-for-host-reboot/index.html.md). Plan a host reboot around every game it runs and leave time to check that each one comes back. - [How to restart a Rust server without losing the latest save](https://rustsc.com/learn/management/restart-rust-without-losing-the-latest-save/index.html.md). Warn players, confirm a clean save and shutdown, and check that Rust reopens the expected world. - [Should you restart Rust or reboot the host?](https://rustsc.com/learn/management/restart-rust-or-reboot-the-host/index.html.md). Choose the smaller interruption and verify whether the game, the host or both actually restarted. - [Track disk space as your Rust world grows](https://rustsc.com/learn/management/measure-rust-save-growth-before-disk-fills/index.html.md). Track free space and the active save over time so you can act before a Rust world runs out of room to save. - [What to do when Rust logs fill the drive](https://rustsc.com/learn/management/rust-disk-filling-with-logs/index.html.md). Find out whether game, framework or system logs are using the space and reduce growth while preserving recent errors. - [Schedule a Rust restart in your players’ time zone](https://rustsc.com/learn/management/schedule-rust-restart-in-player-time-zone/index.html.md). Choose a named local time zone and check the next run on both sides of a daylight-saving change. - [How to reboot a host running several Rust servers](https://rustsc.com/learn/management/reboot-a-host-with-several-rust-servers/index.html.md). Give each server a clean shutdown and bring the worlds back in a deliberate order after a shared host reboot. - [Replace a Rust restart script one job at a time](https://rustsc.com/learn/management/replace-an-old-rust-restart-script-safely/index.html.md). Move routine restarts and crash recovery to a new tool without leaving two processes in charge of the same Rust server. - [What to tell players in Discord and in Rust chat on wipe day](https://rustsc.com/learn/management/rust-wipe-messages-for-discord-and-game-chat/index.html.md). Publish the wipe details where people can find it and use game chat for the immediate warning. - [How to announce a Rust wipe across time zones](https://rustsc.com/learn/management/plan-a-rust-wipe-across-time-zones/index.html.md). Turn a scheduled Rust wipe into a local-time Discord notice and check that it matches the actual run. - [How to hand over a Rust server outage to another helper](https://rustsc.com/learn/management/hand-over-a-rust-server-outage/index.html.md). Leave a short incident note that tells the next helper what players see, what you tried and what to do next. - [Make a Rust server staff rota people can stick to](https://rustsc.com/learn/management/make-a-rust-server-staff-rota/index.html.md). Set up confirmed volunteer shifts, rehearse a missed shift and tell players when they can expect a reply. - [What should your Rust server helper cover this weekend?](https://rustsc.com/learn/management/weekend-rust-server-cover/index.html.md). Leave a usable weekend brief with covered hours, player checks, a contact for trouble and a Monday handback. - [Reduce the Discord pings your Rust volunteers have to answer](https://rustsc.com/learn/management/reduce-rust-volunteer-pings/index.html.md). Review one week of interruptions and give each common request a response that fits its urgency. - [How to take a break when you run a Rust server alone](https://rustsc.com/learn/management/take-a-break-from-running-your-rust-server/index.html.md). Choose whether to keep your Rust world running unstaffed or put it on pause while you are away. - [Compare Rust server managers with one real job](https://rustsc.com/learn/management/compare-rust-server-managers-with-one-workflow/index.html.md). Give two management tools the same Rust job, record what each actually lets you finish and make a decision from the result. - [Try a Rust manager beside the tools you already use](https://rustsc.com/learn/management/try-a-rust-manager-with-your-current-tools-running/index.html.md). Check what connecting a tool changes before moving any responsibility away from your current setup. - [Which jobs can your management tool do on vanilla Rust?](https://rustsc.com/learn/management/test-manager-jobs-on-vanilla-rust/index.html.md). Try startup, game chat and one specialist job to see whether you can use the tool without adding a game plugin. - [What can you still do when your Rust dashboard is unavailable?](https://rustsc.com/learn/management/manage-rust-without-the-usual-dashboard/index.html.md). Test a second route to check the game and recover a stopped Rust server when the usual management site is unreachable. - [Can your activity history tell you who restarted Rust?](https://rustsc.com/learn/management/tell-who-restarted-rust-from-activity-history/index.html.md). Test whether you can distinguish a restart from a helper, a scheduled restart and a request that never ran. - [Hand one Rust maintenance window to a helper](https://rustsc.com/learn/management/delegate-a-rust-maintenance-window/index.html.md). Give a helper the exact world, an agreed player notice and a clear result to report back after a planned restart. - [How to hand a running Rust server to a new owner](https://rustsc.com/learn/management/hand-rust-server-ownership-to-a-new-owner/index.html.md). Transfer daily control and the accounts that keep the game online, then ask the new owner to run a full check. - [Put your Rust server’s operating details on one page](https://rustsc.com/learn/management/write-a-rust-server-operator-card/index.html.md). Give a new helper a durable reference for the world, host, current jobs and where to look when something changes. - [What does ‘online’ mean in your Rust management tool?](https://rustsc.com/learn/management/test-what-online-means-in-a-rust-dashboard/index.html.md). Check what the dashboard shows during normal play, startup and lost contact before relying on its status label. - [Which Rust server job should you automate first?](https://rustsc.com/learn/management/pick-your-first-rust-server-automation/index.html.md). Identify a repeated job with a clear result and test how much of it can run without your judgement. - [Should a missed Rust job run when the host comes back?](https://rustsc.com/learn/management/check-what-rust-schedules-do-after-an-outage/index.html.md). Decide whether to catch up or skip each missed job, then check that the scheduler behaves that way on your host. - [Pause a Rust automation and know when it will come back](https://rustsc.com/learn/management/pause-a-rust-automation-with-a-return-date/index.html.md). Skip or move a scheduled job for one session, keep its normal settings and check the next run before leaving it unattended. - [When should automatic Rust recovery send you an alert?](https://rustsc.com/learn/management/decide-when-rust-recovery-should-alert-you/index.html.md). Check whether a notice helps you act when a world stays down and keeps routine recovery visible without repeated pings. - [Test a bulk Rust action before using it on every server](https://rustsc.com/learn/management/test-bulk-actions-across-rust-servers/index.html.md). Use two spare worlds and a harmless action to check targets, skipped servers and the result for each world. - [What happens when two helpers restart the same Rust server?](https://rustsc.com/learn/management/test-two-simultaneous-rust-restart-requests/index.html.md). Check whether your tool blocks, queues or repeats overlapping restarts and pick one way for helpers to coordinate. - [Should you retry a Rust panel action after a timeout?](https://rustsc.com/learn/management/retry-a-rust-panel-action-after-a-timeout/index.html.md). Check whether a timed-out request already reached your Rust server before you send it again. - [Try a management tool update on one Rust host first](https://rustsc.com/learn/management/try-a-manager-update-on-one-rust-host-first/index.html.md). Choose a spare or lower-impact host, prove your regular jobs still work, then decide whether to update the rest. - [What still runs after you disconnect a Rust manager?](https://rustsc.com/learn/management/find-rust-jobs-before-disconnecting-a-manager/index.html.md). Find out where each automatic job lives and verify what runs after the old tool is out of the picture. - [What schedule details should you keep when changing Rust tools?](https://rustsc.com/learn/management/keep-your-rust-schedules-when-changing-tools/index.html.md). Record enough about each recurring job to rebuild it correctly even if the two tools export schedules differently. - [Can you open a Rust management tool’s export somewhere else?](https://rustsc.com/learn/management/test-a-rust-manager-export-before-paying/index.html.md). Test one useful export with sample records to learn what you can keep and read if you switch tools. - [Do you need the Rust console or the host panel away from home?](https://rustsc.com/learn/management/choose-console-or-panel-for-rust-admin-away/index.html.md). Match the access you carry to an away-from-home task and test it from the device you will use. - [Can you do your Rust admin work on your phone?](https://rustsc.com/learn/management/test-a-rust-tool-on-your-phone/index.html.md). Take one realistic reading job onto mobile data and see if the screen still tells you enough to act. - [How much of your week will a Rust management tool take?](https://rustsc.com/learn/management/check-hours-to-run-rust-tools-before-switching/index.html.md). Compare the time you spend on repeat Rust admin jobs using a typical week and a one-off move. - [What will a Rust management tool tell you when a wipe fails?](https://rustsc.com/learn/management/test-how-a-rust-manager-shows-failed-wipes/index.html.md). Check whether a failed test wipe tells you which world was affected and where to look before trying again. - [Open a Rust practice world alongside your survival server](https://rustsc.com/learn/management/open-a-rust-practice-world-without-copying-the-main-world/index.html.md). Work through a two-world example using a fresh save, separate staff access and disabled live integrations. - [Which settings should your Rust worlds share?](https://rustsc.com/learn/management/choose-what-rust-worlds-should-share/index.html.md). Make a small ownership sheet for community defaults, world-specific choices and private values before copying settings. - [Should a Rust moderator have access to one world or all of them?](https://rustsc.com/learn/management/scope-rust-moderators-to-one-world-or-all-worlds/index.html.md). Match moderation authority to the world a helper covers, then check both permitted and restricted actions. - [Work out which Rust worlds are affected before restarting](https://rustsc.com/learn/management/check-which-rust-worlds-are-affected-before-restarting-anything/index.html.md). Use the same outside join, listing and management checks across two worlds to narrow a fault without interrupting play. - [Retire one Rust world while keeping your community open](https://rustsc.com/learn/management/retire-one-rust-world-without-closing-your-community/index.html.md). Close one world at the agreed date, keep an identifiable archive and check the remaining links and jobs. - [Help staff target the right Rust world before a restart](https://rustsc.com/learn/management/label-two-rust-worlds-so-staff-restart-the-right-one/index.html.md). Give each world a matching name and address across the game, staff handoff and management tools. - [What to check before sharing your new Rust server address](https://rustsc.com/learn/management/before-sharing-a-new-server-address/index.html.md). Verify the world on the new host and test the exact join address before announcing a Rust server move. --- HTML version: https://rustsc.com/learn/management/ --- # Your Rust server boots. What should you do in the first week? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server setup](https://rustsc.com/learn/setup/index.html.md) Once someone has joined, make sure the world you opened will still be there after you close the server. Start with one save and one planned stop and start before you spend time on plugins. ## Keep a record of the working setup Write down which start script or panel button you used, the server identity and the address your players used. Keep the details somewhere you can read while the server is down. If you make a file copy by hand, save and stop the game cleanly first. Keep the copy somewhere away from the server. Tell your first players when you will do maintenance and where they should look for updates. If you intend to wipe the map or learned blueprints, tell them which progress they can expect to keep. ## Rehearse one normal maintenance cycle Choose a quiet time to stop the game cleanly and start it again using the same settings. For example, build a small test structure or ask a player to note where they logged off. Rejoin after the restart and confirm the expected state is still there. If you land on a blank world, compare the startup settings with your working notes before inviting more people. Once stop and start are predictable, make your next change on its own so you can see what effect it had. ## Sources - [Facepunch guide to creating a Rust server](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch reference for server identity and save files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Facepunch console command reference](https://wiki.facepunch.com/rust/useful_commands) ## Related resources - [Your first server in RustSC](https://rustsc.com/support/guides/first-server/index.html.md) - [Back up a server](https://rustsc.com/support/guides/back-up-server/index.html.md) --- HTML version: https://rustsc.com/learn/setup/first-week-after-your-rust-server-boots/ --- # How to read a Rust server launch script [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server setup](https://rustsc.com/learn/setup/index.html.md) Find the line that starts RustDedicated. That line tells you which world and network settings the script hands to the server. A SteamCMD line belongs to installation or updates. ## Follow the launch from top to bottom Open the script in a text editor. Find the command that runs SteamCMD, if present, and the one that runs RustDedicated. Read the options following RustDedicated as settings for the running game. Look for server.identity to find the save folder and server.port to find the game port. Treat any password in the script as private. If a panel starts the game for you, look at its startup settings for the same values. Some settings can also come from server.cfg. Check that file before assuming the script is the only place a value is set. ## Check your reading against the running server For example, find server.hostname in the startup settings, then compare it with the name shown when you join locally. Compare the identity with the folder that contains the active world save. When those match, you know where to look before the next change. If the name differs, check the server's configuration file and confirm you opened the script that actually starts it. ## Sources - [Facepunch guide to creating a Rust server](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch reference for server identity and save files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) ## Related resources - [Change server settings](https://rustsc.com/support/guides/server-settings/index.html.md) - [Update Rust](https://rustsc.com/support/guides/update-rust/index.html.md) --- HTML version: https://rustsc.com/learn/setup/read-your-rust-server-launch-script/ --- # Where does your Rust server keep its active world? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server setup](https://rustsc.com/learn/setup/index.html.md) Start with server.identity in the launch settings or host panel. It tells you which folder inside the server directory holds that instance's data. ## Follow the configured identity name For example, if the identity is coast, look for server/coast inside the game server installation. There you can look for the world save, the blueprint database and the cfg folder. Other identity folders might belong to a past map test or a second instance. Read which map the server loaded in its startup output. If the folder contains several saves, match the map described at startup to the current save. A map file describes the terrain. The corresponding world save holds buildings and other objects placed in that world. ## Use a normal save as a cross-check If you are still unsure which copy is active, note the current save's modified time and use your usual server save command from the server console. Recheck that file after the save finishes. Seeing the expected save updated in the expected folder gives you a practical check before copying or backing up anything. ## Sources - [Facepunch reference for server identity and save files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Facepunch guide to creating a Rust server](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Choose a server folder](https://rustsc.com/support/guides/server-folder/index.html.md) - [Back up a server](https://rustsc.com/support/guides/back-up-server/index.html.md) --- HTML version: https://rustsc.com/learn/setup/find-the-active-rust-server-identity-folder/ --- # How to make yourself a Rust server admin and check it worked [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server setup](https://rustsc.com/learn/setup/index.html.md) Run the owner command in your own server's console with your Steam ID. On current builds, Rust applies the new role to the connected player immediately. ## Confirm the player account before granting access Join the intended server and run users in its server console. Match your player to the Steam ID shown there. Use ownerid with that Steam ID and your player name. For example, enter ownerid followed by your own ID and then your name in quotes. Save any console response so you can check which account received the role. Run the command in the server console or a remote console already connected to that server. If you own more than one instance, check the displayed server name and world before making the grant. ## Check which account received the role Check the grant response for your Steam ID. To verify it also applies to a fresh connection, rejoin with the same account and look for your account and its owner access in the server console. If you are using an older build that still shows regular player access immediately after a grant, rejoining can also apply the role. If it still does not appear, compare the Steam IDs and check which server received the command. ## Sources - [Facepunch guide to creating a Rust server](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch changelist for immediate staff grants on existing connections](https://rust.facepunch.com/changelist/4034) ## Related resources - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/index.html.md) - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/index.html.md) --- HTML version: https://rustsc.com/learn/setup/give-yourself-rust-game-admin/ --- # How to assign ports to a second Rust server on one host [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server setup](https://rustsc.com/learn/setup/index.html.md) Record the first server's active endpoints before adding the second. Then choose available ports for the new world and make them explicit in its launch or hosting settings. Keep the original world's player address handy as the comparison. ## Prepare one row per world The example assumes the worlds share a host and the listed ports are available. These are explicit assignments. On a rental, use the assignments from the provider. Each world also needs its own save location. Set optional endpoints only for services you use. | World | Game UDP | Browser query UDP | RCON TCP | Rust+ TCP | | --- | --- | --- | --- | --- | | Harbour | 28015 | 28017 | 28016, private | 28082, if used | | Valley | 28115 | 28117 | 28116, private | 28182, if used | ## Check what each connection is for Use the game port for direct joins and the query port for discovery. Match only the intended game and query paths through your firewall and router. Keep the administrator console on your existing private management path. If you use Rust+, set app.port in the launch configuration to the chosen Rust+ value. If you leave it unset, Rust+ derives a port from the game's other settings. Check the actual port with app.info on each running server. For Rust+ on two independent worlds, keep their saved companion identities separate. If Rust+ opens the wrong world or fails after a copy, compare the settings and identities on the two worlds before touching the first world's pairing. ## Prove the rows while both worlds are running Use a test host first where you can. Start the second world and keep both processes running through each check. 1. Join each game endpoint from the network your players use. Check the matching world name and a familiar landmark. 2. Find each intended public listing and join it from the Rust browser. If direct join works and the listing does not, check the query assignment for that row. 3. Read a harmless status from each remote console endpoint on your private management path. The output should belong to the intended world. 4. If you offer Rust+ on either world, pair with that world and open it from the app. Repeat independently for the other world if you support Rust+ there. 5. If a port is already in use, compare the startup log for the new world with the written rows. Fix the conflicting new assignment before sharing its address. ## Sources - [Facepunch dedicated-server port settings](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch companion server ports and identity](https://wiki.facepunch.com/rust/rust-companion-server) ## Related resources - [Change server settings](https://rustsc.com/support/guides/server-settings/index.html.md) - [How to test your Rust server from another network](https://rustsc.com/learn/setup/test-your-rust-server-from-another-network/index.html.md) - [How to set up Rust+ on your dedicated server](https://rustsc.com/learn/setup/set-up-rust-plus-on-your-dedicated-server/index.html.md) --- HTML version: https://rustsc.com/learn/setup/allocate-ports-for-a-second-rust-server/ --- # How to test your Rust server from another network [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server setup](https://rustsc.com/learn/setup/index.html.md) Leave the game server on its normal connection. Move only the Rust client to another network, then try the address you will give out. ## Switch the client, keep the server where it is If your server is on a separate home host, connect your gaming PC to a phone's hotspot using cellular data. Disconnect the gaming PC from home Wi-Fi and unplug its wired network if it has one. Leave the host connected to your home router. If the game and server share the only PC, moving it would also move the server. Keep it connected and ask one friend on their own network to run the join test. ## Use the exact address the group will use Open the F1 console and type connect followed by the public game address, a colon and the game port. For example, a friend can confirm the welcome name and spawn into the intended world while you see their connection at the server. A browser result is optional if the goal is direct join. If external joining fails but local joining works, check the public game address and where its UDP game port goes. ## Sources - [Facepunch guide to creating a Rust server](https://wiki.facepunch.com/rust/Creating-a-server) - [Apple guide to joining an iPhone hotspot](https://support.apple.com/en-gb/111785) - [Android guide to sharing a mobile connection](https://support.google.com/android/answer/9059108/share-a-mobile-connection-by-hotspot-or-tethering) ## Related resources - [Your first server in RustSC](https://rustsc.com/support/guides/first-server/index.html.md) - [What a message means and what to do](https://rustsc.com/support/guides/fix-common-problems/index.html.md) --- HTML version: https://rustsc.com/learn/setup/test-your-rust-server-from-another-network/ --- # Install Carbon on a self-hosted Rust server [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server setup](https://rustsc.com/learn/setup/index.html.md) For a new Carbon install on the public Rust branch, use Carbon's Production build for the operating system of the server. Install it in the game root, then check for Carbon when the server starts. ## Windows Start with a working vanilla installation. Stop it, then unpack the Windows production ZIP in the directory that holds RustDedicated.exe. Keep the directory structure from the ZIP and use your normal launch script. ## Linux Stop the server and unpack the Linux archive in the directory that holds RustDedicated. In your Bash launcher, put source ./carbon/tools/environment.sh before the line that starts RustDedicated, with the game root as the working directory. Keep your existing game arguments. If a service starts the server, have the service run that launcher so Carbon gets the same environment on every boot. ## What a successful launch looks like Run c.version in the server console. A Carbon version and build channel confirm the framework started with Rust. If a manual start works and the Linux service gives you no Carbon version, compare the service's entry point and working directory with the ones you used by hand. ## Sources - [Carbon production downloads](https://carbonmod.gg/owners/getting-started) - [Carbon installation by operating system](https://carbonmod.gg/owners/installing-carbon) - [Carbon Linux launcher source](https://github.com/CarbonCommunity/Carbon/blob/b27f51570ebe53873ff79aea21331290ee2afbd5/tools/helpers/carbon.sh) - [Carbon console command reference](https://carbonmod.gg/references/commands/) ## Related resources - [Change Oxide or Carbon](https://rustsc.com/support/guides/change-framework/index.html.md) --- HTML version: https://rustsc.com/learn/setup/install-carbon-launch-script/ --- # Install your first Rust plugin and test what it does [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server setup](https://rustsc.com/learn/setup/index.html.md) Pick one small plugin whose effect a player can see. A welcome message is a useful first change. On a private test instance, prove that the message appears to the right audience and that you can return to the starting behavior. ## Build a plugin change rehearsal checklist Choose the change and the data it touches. Copy the resulting checklist into your test notes. **Worked example** For a first install that adds a player command, try the command as an ordinary player and again with its intended permission. Restart the test world and repeat both checks before deciding whether to install it on the live server. ## Start with a download you can trace Read the publisher's install instructions and note the game, framework, plugin version and any other plugins it needs. For a GitHub release, use the asset the author names. The automatic source archive is a snapshot of the repository and can contain a whole project rather than the installable file. Use an Oxide test server with its own ports, game folder and save. Start with no connection to your live announcements or other services. Save the plugin file you intend to install and keep a copy of any existing plugin, settings, data and permissions the change will touch. For a first install, record that the plugin and its settings are absent. ## Rehearse the plugin change Write what a player should see and what must stay unchanged. For a first-visit greeting, that might be ‘A new arrival sees the welcome line. A returning player gets no extra message.’ Check the author's description before picking your two test accounts. 1. Record the known-good plugin, configuration and data, or record that this is the first install. 2. Prepare an isolated test server with the same game build and framework and no live integrations. 3. Put the file, with its original name, into the configured plugins folder. For a default Oxide setup, that folder is oxide/plugins. Check the current loaded version. 4. Try the promised action with an ordinary player and check the case that should stay unchanged. If the plugin offers a privileged action, verify it separately with a tester who should have that permission. 5. Restart the test server cleanly. Repeat the player checks to see whether the change survives a cold start. 6. Practice going back. Remove the first install using the framework's plugin controls and move its file out of the active plugin folder. For a replacement, use the old plugin with its matching settings and data. Confirm the original behavior returns. 7. Choose whether to release it. Wait if the result, restart or return to the original behavior still needs work. ## Take only the tested change live Save the live starting files immediately before the change, then repeat the same install and player checks. Keep other plugins unchanged until you see the result. If the expected version or player result is missing, save the first relevant console error and restore the tested starting state. In a disposable Oxide rehearsal, our test plugin gave the same permission results before and after a restart. Its direct and group grants still worked, and its revoked grant stayed revoked. That is the kind of restart check a permission-sensitive plugin needs before you rely on it. ## Sources - [Oxide plugin installation and verification](https://docs.oxidemod.com/guides/owners/install-plugins) - [Oxide plugin lifecycle](https://docs.oxidemod.com/guides/developers/plugin-lifecycle) - [Oxide permissions](https://docs.oxidemod.com/guides/owners/permissions) - [Facepunch dedicated server setup](https://wiki.facepunch.com/rust/Creating-a-server) - [GitHub release assets and source archives](https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases) ## Related resources - [Find and manage plugins](https://rustsc.com/support/guides/plugins/index.html.md) - [Which Rust plugin dependencies should you install first?](https://rustsc.com/learn/setup/install-rust-plugin-dependencies-in-order/index.html.md) - [Why did your Rust plugin compile but fail to load?](https://rustsc.com/learn/troubleshooting/rust-plugin-compiles-but-does-not-load/index.html.md) --- HTML version: https://rustsc.com/learn/setup/first-plugin-download-to-working-feature/ --- # Where do Rust plugin .cs files and extension DLLs go? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server setup](https://rustsc.com/learn/setup/index.html.md) A .cs plugin and a framework extension DLL have different install steps. If a release provides both, check the author's instructions for what the plugin needs and which framework the DLL supports. ## Match the file to the framework Oxide normally compiles .cs files from oxide/plugins. Its extension guide puts supported extension libraries in RustDedicated_Data/Managed. Carbon's porting guide uses carbon/extensions for migrated Oxide extension DLLs. Keep the library name from the author and follow their version requirements. An arbitrary DLL sitting beside the download may be a helper library or the wrong build for your server. Find the installation instructions for that release before putting anything into the game folder. ## Verify the DLL before testing the plugin Install the extension with the server stopped and then inspect the startup log for its name. On Carbon, c.extensions also lists the loaded extensions. If the library is absent, solve that first and try the plugin after it is available. For example, after replacing an extension with a newer build, check the version or startup line before testing the plugin that depends on it. A plugin reload alone does not repeat the full server startup that loads the DLL. ## Sources - [Oxide guide to installing extensions](https://docs.oxidemod.com/guides/owners/extensions) - [Carbon extension paths during migration](https://carbonmod.gg/owners/oxide-porting) - [Carbon extension listing command](https://carbonmod.gg/references/commands/) ## Related resources - [Change Oxide or Carbon](https://rustsc.com/support/guides/change-framework/index.html.md) --- HTML version: https://rustsc.com/learn/setup/plugin-cs-vs-extension-dll/ --- # Which Rust plugin dependencies should you install first? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server setup](https://rustsc.com/learn/setup/index.html.md) Start with what the author's page lists as required and get each dependency working first. Optional integrations belong on your list only if you intend to use the feature they supply. ## Turn the plugin page into an install order Rust Kits is a worked example. Its listing puts Image Library under depends on and Copy Paste under works with. For regular item kits, set up Image Library before Rust Kits. For a kit that spawns a saved structure, include Copy Paste and confirm that the referenced structure is available too. Keep any stated version ranges with your downloads. Load the dependency, check its result in the console, then load the plugin that needs it. The separate load results show which end of the chain failed. ## Test the feature you installed Try a kit with an image if your requirement was the image integration. Try the saved structure only if you installed the structure integration and have a spare test area. The failure message can appear at different points. A hard dependency can stop compilation entirely. A plugin using a reference can load and report that the referenced feature is unavailable. Check the named requirement before editing either plugin. ## Sources - [Rust Kits dependencies and integrations](https://umod.org/plugins/rust-kits) - [Image Library's published purpose](https://umod.org/plugins/image-library) - [uMod explanation of hard and optional dependencies](https://umod.org/documentation/api/dependencies) ## Related resources - [Find and manage plugins](https://rustsc.com/support/guides/plugins/index.html.md) --- HTML version: https://rustsc.com/learn/setup/install-rust-plugin-dependencies-in-order/ --- # How to set up Rust+ on your dedicated server [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server setup](https://rustsc.com/learn/setup/index.html.md) Set up the Rust+ companion connection on the server, then pair from the Rust game client while joined. Check it from a phone on mobile data before inviting players to pair. ## Give Rust+ its own reachable TCP port If your host panel provides a Rust+ setting, use the companion port assigned to that server. On a host you control, choose an available TCP port of 10000 or higher and set it as `app.port` in the server's startup settings. Allow only that companion TCP port for Rust+ in the host firewall, and forward it to the game host if it sits behind your router. Keep the remote console port private. Give players a restart warning and restart after the firewall and forwarding are ready. Run `app.info` in the server console to check which port Rust is using. ## Pair after joining in the game Install Facepunch's Rust+ app, allow its notifications and sign in with the Steam account you play Rust on. On that account, join your server in the desktop game, open the Rust+ tab in the game menu and choose the server pairing action. Use the notification on your phone to accept the pairing request for that server. 1. Switch the phone to mobile data. Open the paired server in the app and check for its current player count or in-game time. 2. For a second check, ask a player on another network to pair using their own account and confirm they see fresh information from the same server. 3. If pairing appears to succeed but the server stays offline in the app, compare the address and port the server reports with what is reachable from outside. ## Sources - [Facepunch instructions for the Rust+ companion server](https://wiki.facepunch.com/rust/rust-companion-server) - [Facepunch companion app overview](https://rust.facepunch.com/companion/) - [Facepunch release notes for server pairing in Rust+](https://rust.facepunch.com/news/companion-app-update) ## Related resources - [Why does Rust+ say your paired server is offline?](https://rustsc.com/learn/troubleshooting/rust-plus-paired-server-offline/index.html.md) - [Which Rust ports should you forward at home?](https://rustsc.com/learn/setup/game-port-and-query-port-at-home/index.html.md) --- HTML version: https://rustsc.com/learn/setup/set-up-rust-plus-on-your-dedicated-server/ --- # Which Rust ports should you forward at home? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server setup](https://rustsc.com/learn/setup/index.html.md) Start with the game port, which players enter when they join by address. Add the query port if you want the server to appear in the public browser. Both use UDP and need different port numbers. ## Read the ports from your own server Find server.port and server.queryport in your startup settings. Facepunch documents that when you leave the query port unset, Rust takes the higher of the game and RCON ports and adds one. Read the values on your host before copying any example from a guide. Here is an example for a server using game port 28015 and query port 28017. Both rules point to the game's host. Allow both ports in its firewall and reserve its local address in the router if possible. | Purpose | Router rule | What proves it works | | --- | --- | --- | | Play | UDP 28015 to 28015 | A friend joins by address from outside the home. | | List the server | UDP 28017 to 28017 | The friend finds the correct entry in the browser. | ## Check each rule from outside your home Ask a friend on another network to join by your public address and game port. Once that works, ask them to find the server in the browser if you enabled public listing. A successful direct join is your check for the game rule. Finding the server in the browser checks the listing path. Remote console access and Rust+ have their own ports. Leave those out of this setup when the goal is to let friends play and find the server. ## Sources - [Facepunch server ports and router setup](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [What a message means and what to do](https://rustsc.com/support/guides/fix-common-problems/index.html.md) --- HTML version: https://rustsc.com/learn/setup/game-port-and-query-port-at-home/ --- # Windows or Linux for your first Rust server? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Pick the system you can use to stop the game, find the save and bring it back up. Rust's dedicated server supports both Windows and Linux, so base the choice on how you will manage your host when something goes wrong. ## Try the jobs you will actually need If you usually work at a Windows desktop, practise opening the server console and finding the server folder there. If you intend to rent or use a Linux machine without a desktop, practise opening a remote session, finding the console output and seeing which process is running. Facepunch's setup guide gives launch examples for both. Imagine you are away when the server stops. On either system, you need some way to reach the host or its management panel. Decide how you will get to the console and files before choosing an operating system just because you can install the game on it. ## Choose after a short recovery rehearsal On a test server, open the console, stop the game cleanly and copy the world folder to another location. Then start the same world and join it. If you want unattended startup, check which method you would use. Windows can run a task at system startup, and Linux systems using systemd can start a configured service at boot. Choose the setup you can maintain without somebody else taking over. ## Sources - [Facepunch guide to creating a Rust server](https://wiki.facepunch.com/rust/Creating-a-server) - [Microsoft guide to starting a task at boot](https://learn.microsoft.com/en-us/windows/win32/taskschd/starting-an-executable-on-system-boot) - [systemd documentation for services started at boot](https://www.freedesktop.org/software/systemd/man/latest/daemon.html) ## Related resources - [Install RustSC on Windows](https://rustsc.com/support/guides/install-windows/index.html.md) - [Install RustSC on Linux](https://rustsc.com/support/guides/install-linux/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/windows-or-linux-for-your-first-rust-server/ --- # Can you play Rust and host a Rust server on the same PC? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) You can run the dedicated server and play on the same PC. The useful test is what happens when both are busy and a friend joins from elsewhere. ## Compare a server session with and without your game open Start the server and have a friend join. Ask them to try something they can repeat, such as running a route through a built-up area. Watch the host's processor and memory use while they play. Then open your own Rust client, join, and ask them to repeat the route. For example, if your own game feels smooth but your friend starts seeing pauses whenever you load in, look at what changed on the host. Repeat the check at the map size and player count you expect to have before buying more hardware. ## Decide when to leave your host running Your friend can use the server only while both the host and the game server are running. If you intend to shut your gaming PC down after playing, agree on session times or put the server on a host that can stay up. Keep the shared setup if both players can play reliably and its hours suit the group. ## Sources - [Facepunch guide to creating a Rust server](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch Rust client requirements](https://wiki.facepunch.com/rust/Purchase-and-Installation) ## Related resources - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/index.html.md) - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/play-and-host-on-one-pc/ --- # How to turn a public Rust server into a friends-only server [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Give the friends you want to keep an explicit way in, then hide the public listing if you want it out of search. Players who saved the old address can still try a direct connection. ## Limit joining before changing the listing Use your host's supported allowlist or an allowlist plugin compatible with your server's framework. Add the intended players using their Steam IDs and keep an owner account on the list. Ask one permitted friend to try it during a planned window. If you also want the listing gone, close public access to the query port and keep the game port reachable for the people who will connect directly. On a rental, ask your host how to take the query port out of public use without losing the game port. ## Test with two accounts Have an allowed account use the direct address. Ask a willing friend whose account is outside the allowlist to try the same address and confirm the server refuses entry. Then search from outside your network with filters cleared to check whether the listing is gone. Each test answers a different question. ## Sources - [Facepunch guide to hidden and allowlisted servers](https://wiki.facepunch.com/rust/Creating_a_hidden_whitelisted_server) - [Facepunch guide to creating a Rust server](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/index.html.md) - [What a message means and what to do](https://rustsc.com/support/guides/fix-common-problems/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/make-a-public-rust-server-friends-only/ --- # Will a second Rust server fit on the same host? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Test the second Rust server while the first is doing its normal busy work. A successful startup shows the second map can load. Players on both worlds need to be able to join, play and save while the host handles both workloads. ## Write down a good normal session first Choose one repeatable player action on your existing world, such as joining and opening a crate near a busy base. Ask a regular player to run it when the world is active. Record its population, map, plugin set, noticeable pauses, free disk space, and how the host behaves when the game saves. Look at memory and disk activity alongside the player result. On Windows, Task Manager and Resource Monitor show available memory and disk activity. On Linux, a host that exposes /proc/pressure can show whether work stalls waiting for CPU, memory or I/O. Compare the same readings during both runs. The readings help you explain a bad result and cannot tell you alone how many slots you can offer. ## Test the work that will overlap Prepare the second instance with its planned map and plugins, its own ports and its own Rust server identity. Use a disposable setup or a staffed test window so you can stop the test if the first world becomes hard to play. | Test phase | Record | | --- | --- | | Start the second world during a realistic session on the first | Whether the first world keeps accepting joins and the crate interaction still responds. | | Put players on both worlds with both running normally | Whether activities that use plugins, crowded areas or lots of entities feel normal on each world. | | Watch each world's normal save and a backup if you expect overlap | Whether either world stalls and whether free space covers both saves and retained backups. | | Pause the second instance if the first regresses, then repeat the same action on the first | Whether the original symptom clears with the extra work gone. | ## Make the decision from the paired results Keep one host if the original world stays playable, the second meets the same standard you set for it, and there is room for both to save and keep backups. A one-player dry run can reveal a problem but cannot prove busy-night capacity. If you cannot reproduce representative demand, treat capacity as undecided and limit who joins the test. If one specific overlap causes the trouble, change that overlap and retest. If ordinary play suffers whenever both worlds are busy, use separate hosts or reduce the proposed load before opening the second world. Keep the before-and-after notes so you can repeat the same check after changing maps or plugin packs. ## Sources - [Facepunch dedicated server requirements and settings](https://wiki.facepunch.com/rust/Creating-a-server) - [Linux kernel pressure stall information](https://docs.kernel.org/accounting/psi.html) ## Related resources - [Does your Rust community need a second world?](https://rustsc.com/learn/hosting/does-your-rust-community-need-a-second-world/index.html.md) - [How to assign ports to a second Rust server on one host](https://rustsc.com/learn/setup/allocate-ports-for-a-second-rust-server/index.html.md) - [Why does one Rust server lag while another backs up?](https://rustsc.com/learn/troubleshooting/one-rust-server-lags-during-another-backup/index.html.md) - [Set up alerts](https://rustsc.com/support/guides/resource-alerts/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/will-a-second-rust-server-fit-on-one-host/ --- # Host Rust at home or rent a server? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Your friends can play while you are logged out of Rust. The dedicated server runs separately from your game, but its host and internet connection must stay on. Choose where to run it around the hours your group wants to play, then choose who will look after it. ## Does the world need to stay open after you leave? Start with the person who plays at the least convenient time. If you finish at 22:00 UTC but a friend comes home at 23:00 UTC, hosting on a gaming PC that you shut down at bedtime will leave them outside. Keeping your own Rust client open is unnecessary. Keeping the dedicated server running is what matters. A spare home host can cover those hours if you are comfortable leaving it powered and connected. A rental puts the game elsewhere, so switching off your home PC does not stop it. Neither arrangement removes maintenance or interruptions. Agree on the hours you intend to offer rather than promising the world will never go down. | Your group wants | A possible fit | Settle this first | | --- | --- | --- | | Only the evenings you play together | A home host started for each session | Who starts it and when the evening ends | | Friends building at different times | A home host left running or a rented server | Who keeps it running when the organiser is away | | A world independent of household power and internet | A rented server | Who holds the account and handles maintenance | ## Agree who can act when something stops At home, decide whether the person paying for the always-on host also handles power, router access and restarts. If the only person with access is away for a week, work out who could bring the world back or tell players it will stay closed. With a rental, decide who holds the account, who pays the next bill and who could open a support request or recover a copy safely during that week. Pick one person to keep a separate copy of the world and one route for another person to reach that copy if you stop running the server. Ask the rental provider what updates you control and whether you can download the save. If only your friends should get in, verify the chosen setup can limit admission by trying an invited and an outside account. | Question for the group | Agree on it before choosing | | --- | --- | | Who pays to keep it available? | Name who covers the household machine or pays the rental’s next charge. | | Who responds if it stops? | Name the person with agreed access and say what happens if they are away. | | Where does the world go if we stop? | Agree who holds the separate copy and can explain how to open it. | ## Try an evening without the organiser Have a friend on another connection join, leave and rejoin with your Rust client closed. With a rental or a separate home host, turn off your gaming PC during the test. Keep a combined game-and-server PC on. Ask the person who provides cover to show where they would check whether the world is running and where to find the latest separate copy. You have a workable arrangement when friends can join at the agreed time, someone can take over a routine outage, and you know what you would do if nobody wants to keep paying. If you cannot accept outside connections at home or nobody wants to leave the host running, test a rental before committing. If you only need the world while you play together, start with shared game nights. ## Sources - [Facepunch guide to creating a Rust server](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch guidance on hidden servers and allowed players](https://wiki.facepunch.com/rust/Creating_a_hidden_whitelisted_server) ## Related resources - [Can you run a Rust server just for game night?](https://rustsc.com/learn/hosting/run-a-rust-server-just-for-game-night/index.html.md) - [Can you play Rust and host a Rust server on the same PC?](https://rustsc.com/learn/hosting/play-and-host-on-one-pc/index.html.md) - [How to turn a public Rust server into a friends-only server](https://rustsc.com/learn/hosting/make-a-public-rust-server-friends-only/index.html.md) - [What should friends agree before starting a private Rust world?](https://rustsc.com/learn/community/agree-a-first-wipe-with-friends/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/home-network-or-rented-rust-server/ --- # What backup access should a rented Rust server helper have? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Work from the job you want the helper to do. Copying a backup off the host, creating a new backup and restoring one can have different permissions. ## Choose the steps the helper will own If their job is to keep an independent copy, look for a separate account that can see and download backups. Give it backup creation access only if the helper also needs to make new copies. Keep restore and delete with whoever decides when live progress should be replaced or when old backups are safe to remove. For example, ask a helper to download the latest pre-wipe backup while you handle restores yourself. If the panel bundles those actions, you can download the copy yourself or ask the host whether it offers separate controls. ## Test using the helper's own login Have the helper sign in, find a test backup and download it to the intended storage location. Check the available restore and delete controls on that account without running them on the live server. Success means the helper can complete the agreed job and you still control the actions that could replace or remove player progress. ## Sources - [Facepunch reference for server identity and save files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) ## Related resources - [Give someone access to only some servers or hosts](https://rustsc.com/support/guides/limited-access/index.html.md) - [Back up a server](https://rustsc.com/support/guides/back-up-server/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/give-a-helper-backup-access-on-rented-rust/ --- # How to move a Rust server hostname to a new host [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) If players already join with a domain name you control, update the records for that name when you move hosts. Check the game port if the destination uses a new one. ## Record the new host's game address and port Read the new host's public game address and game port from its panel or startup settings. Use Facepunch's DNS guide to check the records behind your existing name. The A record points at the server's IPv4 address. The Rust SRV record points to that hostname and game port. Check that the service is _rust and the protocol is _udp. For example, if the new host changed the game port as well as the address, update the address record and the port in the SRV record. Note the old values so you can see exactly what changed. ## Have someone use the existing hostname Ask a friend on another network to use the same hostname players already have pinned, without substituting the new address. Confirm they reach the new server by checking an agreed name or world detail. If they still reach the old server, check the published DNS values and allow for cached answers before announcing the move is complete. ## Sources - [Facepunch guide to Rust server DNS records](https://wiki.facepunch.com/rust/dns-records) - [Facepunch guide to creating a Rust server](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Move a server to a new host](https://rustsc.com/support/guides/move-to-new-host/index.html.md) - [What a message means and what to do](https://rustsc.com/support/guides/fix-common-problems/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/move-your-rust-server-hostname/ --- # What to take with you before cancelling a Rust server rental [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Keep the rental accessible until the files you need are outside it and you have checked a copy. Make the cancellation decision after that check, especially if the panel contains your only backup. ## Keep the exit date separate from the move date Ask the host to confirm the last moment you can use the panel, file login and hosted backups. Find out whether cancellation acts immediately or at the end of the current period, and whether you also need to change an automatic payment. Record the service name and the reply so you can confirm you are ending the right rental. ## Make something you can take with you Download the active identity folder and note the startup settings and game build. Include the custom map and its link, plus any plugin files, settings and data you want to keep. If a plugin uses a separate database, arrange its own export. Open the files on storage you control without using the rental panel. If you are moving, tell players when progress on the old world ends. Once it has saved and stopped cleanly, take the final copy before the access deadline. If you are closing for good, write down what you chose to keep and where someone can find the resulting archive. ## Check the world before ending the service Use a separate test installation or replacement with private admission, its own ports and storage, and live integrations and automatic jobs disconnected. Join the intended world and check a known base or learned blueprint. If a required file is missing or nobody can join, use the remaining access to obtain it or ask for more time before cancelling. Once the copy meets your needs, end the correct service and save the confirmation that shows when it ends. Check that the provider’s account shows the agreed status. If you move, update the current join instructions after testing the replacement from outside your network. ## Sources - [Facepunch reference for server identity and save files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Facepunch guide to creating a Rust server](https://wiki.facepunch.com/rust/Creating-a-server) - [Example provider’s cancellation guidance](https://nodecraft.com/support/knowledgebase/account/how-do-i-cancel-my-service) ## Related resources - [Back up a server](https://rustsc.com/support/guides/back-up-server/index.html.md) - [Move a server to a new host](https://rustsc.com/support/guides/move-to-new-host/index.html.md) - [How to compare Rust server rental renewal costs](https://rustsc.com/learn/hosting/rust-server-rental-renewal-cost/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/before-you-cancel-a-rust-server-rental/ --- # Can you run a Rust server just for game night? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) If the same friends usually play together, agree to start the dedicated server for the session and stop it afterwards. When the process is stopped, friends can’t join. If people want to gather or build between sessions, agree on an extra opening window or keep the server running. ## Agree when the world will be open Pin the join instruction and use your usual group chat for session times. Name a host who can start the server before people are waiting for it. For a first session, have a friend connect from their own network and reach the correct world before confirming that everyone can join. Keep the same game address in the pinned post and check it before the session if your home address can change. A group message can be as short as ‘We’re opening North Pier tonight at 19:00 UTC. Join from the pin once I say it’s ready. We’ll wrap up at 22:00 UTC.’ Tell friends whether they should expect to keep making progress between Fridays if that matters to how they play. ## Close the session the same way each time Give the group a chance to finish and use your normal graceful save and stop procedure. Leave a short message confirming the session ended and when the server is next expected to open. Next time, use the same Rust server identity and map settings. Before you announce the opening, join and check a landmark or build the group remembers from last time. If a friend finishes work after your usual stop time, decide whether to add a short late window before changing the whole hosting routine. Put their session in the same group chat so other players know when the world will be available. ## Sources - [Facepunch dedicated server startup, identity and join instructions](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch console reference for saving and closing the server](https://wiki.facepunch.com/rust/useful_commands) - [Discord pinning instructions in channels and direct messages](https://support.discord.com/hc/en-us/articles/221421867-Pin-Messages-FAQ) ## Related resources - [What address should friends use to join your Rust server?](https://rustsc.com/learn/hosting/which-address-should-friends-use/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/run-a-rust-server-just-for-game-night/ --- # Will a Rust management tool do the same jobs on both your hosts? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Test the job against each host you intend to use. A rental can let a tool read Rust’s console while the start button still belongs to the rental panel. Even two rentals with a similar panel can give your accounts different access. ## Write down which connection you are testing Use a spare instance and the account that will handle the job on each host. Record whether you connected through the game’s remote console, the rental panel or software on a host you control. A successful connection only proves that route is available. Try the actual job using it. For example, Harbour is self-hosted and Dunes is rented. You can read fresh console output for both through the manager. On Dunes the tool can see the stopped game but says it cannot start it with your current access. Use the rental panel directly and record the difference instead of changing the helper’s permissions just to make the two screens match. | Job | Harbour | Dunes | | --- | --- | --- | | Read new console output | Manager shows a fresh line | Manager shows a fresh line | | Start a stopped game | Manager starts it | Open the rental’s panel | | Change a test startup setting | Make and verify the change in the manager | Ask who controls the setting before altering it | ## Hand over the exact exception For each job that moved to another screen, write who can finish it there. Have the person who covers the server use their own account on the spare instance. If they cannot use the fallback, revise the job they take on or ask the owner to remain available for that step. Keep a separate result for each rental even if the panels look alike. Repeat the limited set of jobs when a connection or account role changes. Verify a start by joining the intended world and verify a startup setting still applies after the game opens. ## Sources - [Carbon web panel account and console permissions](https://carbonmod.gg/owners/features/webcontrolpanel) - [Facepunch dedicated server startup settings](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Compare Rust server managers with one real job](https://rustsc.com/learn/management/compare-rust-server-managers-with-one-workflow/index.html.md) - [Can you add a Rust server manager and keep your rented server?](https://rustsc.com/learn/hosting/access-needed-for-rented-server-maintenance/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/test-a-rust-management-tool-on-different-hosts/ --- # How to compare Rust server rental renewal costs [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Start with what the current host will charge at renewal and when the payment is due. Compare that with a replacement over the same period. Include the overlap you need to copy the world and test that players can join. ## Compare your renewal and moving costs Use one currency and include any overlap or setup charges in your moving costs. **Worked example** Over six months, renewing at 30 per month costs 180. Moving at 24 per month plus 50 upfront costs 194. Renewing costs 14 less over that period. ## Find the dates on your own account Open the next charge or renewal screen for the service that actually runs your world. Record the renewal amount, the period it covers, and the date an automatic payment will go through. Check when you would need to turn renewal off and when panel and file access would end. Ask the provider for the dates in writing if the account leaves them unclear. Read the replacement quote through the second charge. If the first bill includes a discount, record the period it applies to. Use the same currency and treatment of tax for both offers. Add only the extras your world needs, such as backup storage, and include any separate charge for the migration itself. ## Compare the cash you would pay through the same date Suppose your next three months on the current service cost 20 a month plus 4 for backups, or 72 altogether. The replacement costs 12 in the first month, then 17 a month, with backups included. That is 46. If you must renew the old rental for a full month to keep access during the move, add 24 to the replacement for a total of 70. A difference of 2 over the whole period gives you little room for another month of overlap. If copy testing fits inside the period already covered, that is a different comparison. Count the bill you would actually pay to keep the old service available, even when you expect to use it for only a day. | Cost to compare | Keep | Move | | --- | --- | --- | | Next three months | 72 | 46 | | Extra charge to keep the old rental | 0 | 24 | | Total | 72 | 70 | ## Set a date to make the decision Put the host’s renewal deadline and your own decision date in your calendar. If you are considering a move, allow time to download the files and join a test copy before the decision date. When the replacement’s backup access or renewal amount is still unknown, mark that line as unknown and get an answer before choosing. Write one sentence you can act on. For example, “Keep Harbour for one more period unless we can join the replacement copy by Wednesday evening and confirm its next charge.” If you decide to end the old service, check your provider’s confirmation and the date your file access ends. ## Sources - [Provider documentation on renewal and overdue payments](https://nodecraft.com/support/knowledgebase/account/what-happens-if-my-service-is-suspended-due-to-non-payment) - [Example provider terms on the renewal period and charges](https://storage.gra.cloud.ovh.net/v1/AUTH_325716a587c64897acbef9a4a4726e38/contracts/7824b7f-Conditions_Particulieres_VPS-WE-4.1.pdf) ## Related resources - [What to take with you before cancelling a Rust server rental](https://rustsc.com/learn/hosting/before-you-cancel-a-rust-server-rental/index.html.md) - [Host Rust at home or rent a server?](https://rustsc.com/learn/hosting/home-network-or-rented-rust-server/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/rust-server-rental-renewal-cost/ --- # Which hosting region should you pick for your Rust players? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Ask one regular player from each part of your group to try both locations. Geography can help make the shortlist. Repeated trouble during an actual join or a short session tells you more about whether the group can play together. ## Choose who needs a good connection For a group split between Manchester and Toronto, ask someone from each city to try two host locations during your normal game night. Include the person who runs the session if they use a different network. Decide in advance what would rule a region out. For example, no regular player should be dropped during the play test, and people should be able to move through a busy area together. ## Repeat one short session at each location Ask for a test server or a joining address for each region. If you control both servers, use the same game branch, world setup and mod list. Join during comparable hours from the networks you actually use. A successful connection to a provider's test page cannot show whether the game accepts the connection or stays responsive. Try the same routine on each Rust server. Load in, open a door or container, move with another player, then leave and rejoin. Record the local time with its zone, whether everyone got in, and any stalls or disconnects. If everyone sees the same stall at the same moment, check whether that test server itself was busy before attributing it to the location. ## Use the result that could change your choice Say the first location feels fine to both groups on two visits. The second feels slightly quicker in Manchester but repeatedly drops the Toronto player. Pick the first region if the group needs to play together on Fridays. If both locations work, choose by another practical factor, such as whether you can download your backups. If the host can show only a ping test, use it to narrow the list and ask how you can test the actual game before committing for longer. ## Sources - [Facepunch dedicated server guide](https://wiki.facepunch.com/rust/Creating-a-server) - [Hosting region and availability zone documentation](https://docs.aws.amazon.com/lightsail/latest/userguide/understanding-regions-and-availability-zones-in-amazon-lightsail.html) ## Related resources - [How to test your Rust server from another network](https://rustsc.com/learn/setup/test-your-rust-server-from-another-network/index.html.md) - [What address should friends use to join your Rust server?](https://rustsc.com/learn/hosting/which-address-should-friends-use/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/choose-a-rust-rental-region-with-players/ --- # What will a Rust server host help you fix? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Ask about a failure that could interrupt the world you intend to run. For a custom map server, ask what would happen if the game stops opening after a map change. The reply should leave you knowing who can inspect the failure and what you could do without waiting. ## Ask one question tied to your setup Try this with the host you are considering. “I want to run a Rust server with a custom map. On wipe night the server gets as far as downloading the map and then stops. Which startup messages can I read in the panel, which settings can I put back myself, and when would you ask me to open a ticket?” Ask about the route you would actually use that evening. If the reply offers help with the hosting service, ask whether that includes setting the previous map URL or only helping you locate the error. If the host gives you a demo, open a startup log and find where you would see or change the setting. ## Separate the actions you need available Rust can fail when the server tries to fetch a map. A different failure can happen after startup when an individual Rust client tries to retrieve it. Ask whether the host can give you the startup output for the first case. For the second, you and the player can compare the client error with what another player sees from their network. | You would need to | What you want to hear | | --- | --- | | See where startup stopped | Where the full start output is available and who can get a copy | | Undo the last map setting | Whether you can put back the previous map URL or need staff to do it | | Ask for help outside your usual hours | Which support route handles an unavailable server and what details it needs | ## Decide who will get the world back An answer such as “You can read startup output and change the URL from your account. We investigate host failures. You are responsible for the custom map file” gives you a workable boundary if you know where to get a working map. If you need a host to carry out that change, get that included task confirmed before choosing the service. ## Sources - [Facepunch custom map troubleshooting](https://wiki.facepunch.com/rust/FAQ_and_Troubleshooting) - [Example provider’s guide to custom map settings](https://nodecraft.com/support/games/rust/adding-a-custom-map-to-your-rust-server) ## Related resources - [What to send your rental host when Rust will not start](https://rustsc.com/learn/troubleshooting/support-ticket-for-rust-server-startup-failure/index.html.md) - [Why won't my Rust custom map URL load?](https://rustsc.com/learn/configuration/custom-map-url-wont-load/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/check-rust-rental-support-before-buying/ --- # Does your Rust rental need more disk space or more memory? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Start with what failed at a known time. If the game ran out of room to write a backup, ask how to increase available storage. If the process stopped under a memory limit, ask about memory. Get the host to tell you which limit it saw when the evidence is unclear. ## Put the symptom and the reading together Open the console and the rental’s resource display. Match the time of the failure to the closest readings available. A full disk after a large save or archive points to a space problem. An abrupt exit while the host reports that the service exceeded its memory limit points to a need for more memory. A high reading by itself does not connect either limit to the failure. | What you observed | Ask the host | | --- | --- | | The new save failed and the panel shows no free disk space | Which files count toward my disk limit, and can we raise that limit without increasing memory? | | Rust exited during map load and the host confirmed it reached the memory limit | How much memory would this change add to my service, and would the existing disk and files stay in place? | | Both graphs look high, but the console has a map download error | Can you confirm which resource limit was reached or whether I should start with the download? | ## Find out what the change affects A provider may sell compute and storage together, or let you change one separately. Ask whether the resize requires downtime, changes the address or prevents going back to the smaller service. If the increase needs a move or an interruption, keep a separate backup and set a time the community can use. Name one check to repeat after the change. For more disk space, compare available space at the same point during the next backup and check that the game can still save afterward. For more memory, repeat the startup that previously failed and confirm the intended world opens. If the original error returns, give the host those two readings and times before asking for another resource change. ## Sources - [Facepunch dedicated server guide](https://wiki.facepunch.com/rust/Creating-a-server) - [Example compute and storage resize options](https://docs.digitalocean.com/products/droplets/how-to/resize/) ## Related resources - [Is high RAM use a problem for your Rust server?](https://rustsc.com/learn/troubleshooting/high-memory-use-or-real-pressure/index.html.md) - [Track disk space as your Rust world grows](https://rustsc.com/learn/management/measure-rust-save-growth-before-disk-fills/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/choose-rust-rental-disk-or-memory/ --- # Will Rust backup downloads use up your host’s transfer allowance? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Find out where the bytes leave from. Downloading an archive from the host running Rust can affect a different allowance from downloading it through a separate backup store. Use one real transfer to check which meter moves. ## Follow one archive from its source Draw a line from where the backup is stored to where you open it. A panel file copied to your laptop leaves the rental. Uploading that file from your laptop to the new rental goes in the opposite direction. A download from a remote backup store may appear on that store’s bill instead. Ask how the provider counts those three transfers and how often its usage counter updates. ## Add the copies you actually move For example, one 3 GB archive per week means four downloads, or 12 GB in a four-week period. Downloading the same archive for a rehearsal adds another 3 GB. Two attempts during a move would add up to another 6 GB if both transfer the whole file. That is up to 21 GB in the worked example, before game traffic and any other copies your provider counts. Use the amount transferred or the size of the archived file. An archive that takes up 9 GB after extraction can be a 3 GB download. If the backup uploads directly somewhere else, include that route only where it contributes to the allowance you are checking. ## Compare the estimate with a real reading Record the usage meter before and after the next ordinary download, allowing for its reporting delay and other traffic in the same period. If you cannot match the change to the download, give the host the file size, approximate time and storage source and ask which meter to watch. Take that answer and the normal traffic for a similar rental period into the renewal decision. ## Sources - [Example provider documentation on transfer direction and allowances](https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-faq-data-transfer-allowance.html) - [Game panel documentation on backup storage](https://nodecraft.com/support/knowledgebase/nodepanel/server-backups) ## Related resources - [How to compare Rust server rental renewal costs](https://rustsc.com/learn/hosting/rust-server-rental-renewal-cost/index.html.md) - [Is a Rust server backup on the same disk enough?](https://rustsc.com/learn/recovery/rust-backup-on-the-same-disk/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/rust-host-transfer-allowance-for-backups/ --- # What does a Rust rental’s backup allowance actually cover? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Give both hosts the same example. You want to keep your last ordinary backup and make a second copy just before wipe night. Ask what happens to the first copy, and where you would get it if the game machine was unavailable. ## Compare backup jobs rather than the headline count A panel may store backups on the game machine or send them elsewhere. The number of backups in the offer cannot tell you which setup applies. Ask whether the allowance counts saved archives, storage capacity or both. A manual checkpoint and a scheduled backup may share that allowance. | Your example | Get this in the reply | | --- | --- | | Make a manual backup before wipe | What happens if the allowance is already full | | Keep the copy from before the previous wipe | Whether a new scheduled backup can remove it, and how you keep it separately | | Recover when the game machine is unavailable | Whether the backup stays accessible, where to download it, and who can restore it | ## Ask to try the job you would depend on If you have a test panel, make a small backup of a spare world and open the downloaded file outside the panel. Check which sections of the service the archive actually covers. If you need the host to restore it, ask what they need from you and whether they can restore to a spare target so you can try it. A service that keeps several backups but lacks downloads might suit someone who has their own verified copies. If you need to keep a copy independently, choose the offer that lets you open one elsewhere and verify the world files you expect. ## Sources - [Game panel documentation on backup storage](https://nodecraft.com/support/knowledgebase/nodepanel/server-backups) - [Facepunch guide to server files and saves](https://wiki.facepunch.com/rust/Getting-Started_w-Server) ## Related resources - [How many Rust server backups should you keep on the host?](https://rustsc.com/learn/recovery/keep-enough-rust-backups-without-filling-disk/index.html.md) - [Why is your Rust panel backup download so small?](https://rustsc.com/learn/recovery/rust-panel-backup-download-smaller-than-expected/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/compare-rust-rental-backup-allowances/ --- # Shared or dedicated CPU for a Rust rental? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Ask the host whether the quoted CPU is shared, reserved or subject to a sustained usage limit. If you have access to both options, compare equivalent Rust worlds during the hours when players gather. A quick join to an empty world can miss a difference that appears later. ## Ask what the CPU number really gives you Try “Does this allocation give my server CPU time shared with other customers or reserved for the service? If the game stays busy through our Friday session, how do you handle sustained use, and what can I see in the panel?” If the host offers both choices, ask what else changes, such as memory or storage, so you can interpret the test fairly. Provider terms vary. Some virtual machines share processing time and others reserve access. Some services report burst capacity separately from CPU use. An answer about faster hardware still leaves you needing to know how much access the rental gives your game during a long busy session. ## Repeat a representative busy period On spare instances, use the same Rust build, map and plugin setup. Have the same testers spend part of their normal session playing together. Note server FPS if available, save times and the timestamp of an issue several people see. Keep large backups and other known work in the same place in the test or outside both sessions. For example, the shared and reserved instances both feel fine at first. At two similar evening tests the shared instance shows repeated server FPS drops as players report delayed actions. Ask the host what it observed at those times and compare the results with the reserved option. If both stay responsive, you have little evidence that reserved CPU would improve this workload. ## Sources - [Example documentation on shared and reserved compute](https://docs.digitalocean.com/products/droplets/concepts/choosing-a-plan/) - [Example guidance on sustained CPU measurements](https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-right-size-instance.html) ## Related resources - [Is it low client FPS or a slow Rust server?](https://rustsc.com/learn/troubleshooting/client-fps-or-rust-server-lag/index.html.md) - [Does your Rust rental need more disk space or more memory?](https://rustsc.com/learn/hosting/choose-rust-rental-disk-or-memory/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/rust-rental-shared-or-dedicated-cpu/ --- # Can a Rust rental run the custom map you already have? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Send the provider one example from your actual setup. Ask where the .map file will be served and whether your account can set the game's map URL. Get that part of the job confirmed before choosing a rental for a custom world. ## Ask about your map's delivery method If you already have a direct download URL, ask where you'll enter it and when a change takes effect. If you only have a .map file, ask whether the host provides a place to serve it or expects you to supply a separate public link. Ask who can change the URL back if a new revision fails on wipe day. Facepunch describes different paths for a file on the game host and a direct link that new players can reach. A file uploaded through the panel's file manager can exist on the game host without becoming a public download. Ask for a direct working link before relying on that upload feature. ## Prove the job on an empty world Use a disposable instance and a map you are allowed to share. Set the agreed link, bring that world up and join from outside the host network using a client that has never downloaded the map. Check a landmark that identifies the custom terrain. Keep the successful method in your notes. If startup works but the new client cannot download, take the exact URL the client tried back to the host. If the host must apply each change through support, weigh whether you can work around that delay at your usual wipe hour. ## Sources - [Facepunch guide to hosting a custom map](https://wiki.facepunch.com/rust/Hosting_a_custom_map) - [Facepunch custom map troubleshooting](https://wiki.facepunch.com/rust/FAQ_and_Troubleshooting) ## Related resources - [Why won't my Rust custom map URL load?](https://rustsc.com/learn/configuration/custom-map-url-wont-load/index.html.md) - [What will a Rust server host help you fix?](https://rustsc.com/learn/hosting/check-rust-rental-support-before-buying/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/choose-rust-rental-with-custom-map-access/ --- # Will a Rust rental keep its address when the host moves it? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Ask for the exact new joining address and game port before accepting a location move. Keeping the same company or even the same service name leaves room for either value to change. Plan your notice from the written answer. ## Separate the address from the service name Send one question with the move. “If you transfer Harbour to the new location, will players use the exact same hostname and game port? If either changes, what are the new values and when will each address work?” Ask separately whether you must change the address in tools that use the game query port or the remote console. A fixed IP can have location restrictions. For example, one provider's static addresses attach only within the same region. The answer for a rental depends on its own network and whether the hostname is yours or supplied by the provider. ## Prepare for the answer you actually receive If the public address and port stay the same, verify that existing players can use them from another network after the move. If only the port changes, update join instructions that include it. If the hostname changes, prepare the newest join post and check whether the old address will disappear or point somewhere else. | Host’s reply | Verify after the move | | --- | --- | | Same host name and game port | A player joins with their saved address. | | Same host name but a new port | A player joins using the new port from your refreshed notice. | | Different address | A player who follows only the current join post reaches the moved world. | ## Keep the move reversible until you have a join result Before agreeing, ask whether the host can undo a failed move or how long you can reach the old world. Download a separate backup. After the provider finishes, have a player join the intended world and check a known location, then update the current instructions for everyone else. ## Sources - [Facepunch dedicated server guide](https://wiki.facepunch.com/rust/Creating-a-server) - [Example provider documentation on static IP location limits](https://docs.aws.amazon.com/lightsail/latest/userguide/lightsail-create-static-ip.html) ## Related resources - [How to move a Rust server hostname to a new host](https://rustsc.com/learn/hosting/move-your-rust-server-hostname/index.html.md) - [What to check before sharing your new Rust server address](https://rustsc.com/learn/management/before-sharing-a-new-server-address/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/rust-rental-region-transfer-keep-or-change-address/ --- # Do more Rust rental slots mean more capacity? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) A larger player allowance means you can admit more players if the game and rental allow it. Ask which resources come with that allowance. Decide using the map, plugins and busiest session you intend to support. ## Ask for the limit behind each number Facepunch documents maxplayers as a simultaneous player setting. Ask whether the rental exposes that setting to you and whether there is a separate limit on the service. Then ask what changes for CPU, memory and disk when you choose the larger slot allowance. | Provider lists | Question to ask | | --- | --- | | Player slots | Can I set the game’s cap up to this number? | | CPU and memory | What changes when I choose more slots, and what can I observe during busy sessions? | | Disk | Is the available space the same after adding slots? Which saves or backups count toward it? | ## Use a busy session to choose the next change For example, the higher slot offer leaves CPU and memory the same. You currently see a full queue, and normal gameplay remains responsive when you are at the cap. A small cap increase within your current allowance, if available, can show whether the same resources handle more people. Monitor the same busy activities and use the previous cap again if play noticeably worsens. If players are already reporting delays before the world fills, gather the time and host readings before raising the cap. Choose more slots when you can identify admission as the limit and you have a way to check the world as attendance grows. ## Sources - [Facepunch dedicated server guide](https://wiki.facepunch.com/rust/Creating-a-server) - [Example documentation on separate compute and storage measurements](https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-right-size-instance.html) ## Related resources - [How many player slots should you set on a Rust server?](https://rustsc.com/learn/configuration/choose-a-rust-server-player-cap/index.html.md) - [Shared or dedicated CPU for a Rust rental?](https://rustsc.com/learn/hosting/rust-rental-shared-or-dedicated-cpu/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/rust-rental-slot-count-and-resource-limits/ --- # How to try a Rust rental without moving your players [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Leave the current server and its join post in place. Use a new test world at the rental and invite only the people who will test it. Give them one thing to try that could change whether you take the rental. ## Name the skill the host needs to prove If an owner is evaluating whether friends can play while they are away, have one friend join without them. If a modded world needs easy recovery, use a harmless setting in the test and prove you can keep and reopen its backup. Name the rental world clearly so the tester recognises it before making changes. Ask the provider how to restrict access. A server missing from the browser may still accept direct connections. Confirm any admission restriction with an invited player and an account that should stay out before doing private rehearsals. Leave live plugin credentials and integrations out of the test. ## Check one save survives a clean restart From another network, join the test world and place a small marker you can recognise. Allow the game to save, use the host’s normal clean stop or restart action, then return using the same address. Check the marker and download a dated copy if access to the save matters to your choice. If the essential job fails, give the provider the exact step and the time. Keep the old join details current until you can repeat a passing result. If you decide to take the rental, arrange a separate move for the real world and its final save. ## Sources - [Facepunch dedicated server guide](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch guide to hidden and restricted servers](https://wiki.facepunch.com/rust/Creating_a_hidden_whitelisted_server) - [Facepunch guide to server files and saves](https://wiki.facepunch.com/rust/Getting-Started_w-Server) ## Related resources - [What to check before sharing your new Rust server address](https://rustsc.com/learn/management/before-sharing-a-new-server-address/index.html.md) - [What will a Rust server host help you fix?](https://rustsc.com/learn/hosting/check-rust-rental-support-before-buying/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/try-a-rust-rental-without-moving-your-players/ --- # Would losing your Rust rental login also lock you out of backups? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Ask which account controls the only copy you could restore. If the rental login and the backup access use the same recovery route, keep a copy you can reach another way. ## Check where access actually depends on the rental Ask the provider whether you can download a backup after losing panel access or closing the service, and how you would request it. Determine whether a second staff account can reach the archives without signing in as the account owner. If they can, check whether that access would disappear when the rental service is suspended. Separate storage is useful only if you can reach it independently. For example, a remote download link may still need a fresh panel login each time. An archive on a separate drive or under a different storage account can stay reachable when that login fails. ## Try retrieving a copy without the owner session From a separate device, leave the hosting panel unopened and use the recovery route you intend to keep. Download or open a dated spare archive and confirm it contains the expected world file. If it is encrypted, check that you can reach the recovery password independently as well. If you cannot reach the copy, select another destination or access route and repeat the check. Keep the route in your recovery notes. Give a helper only the separate access they need, and keep your account password and recovery codes private. ## Sources - [CISA guidance on independent and tested backups](https://www.cisa.gov/sites/default/files/2025-03/StopRansomware-Guide%20508.pdf) - [Example provider documentation on backed-up instance data](https://nodecraft.com/support/knowledgebase/nodepanel/what-are-instances-and-how-to-use-them) ## Related resources - [What does a Rust rental’s backup allowance actually cover?](https://rustsc.com/learn/hosting/compare-rust-rental-backup-allowances/index.html.md) - [Can you get to your Rust backups if the host is gone?](https://rustsc.com/learn/recovery/check-backup-access-with-host-unavailable/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/check-rust-rental-and-backup-account-separation/ --- # Who controls game and framework updates on a Rust rental? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Ask what happens on the next ordinary start after a game patch. A rental can update the game, the framework or both. Find out who can control the order and what you can check before players return. ## Describe the update you need to handle Ask: “I intend to run an Oxide server. If Rust releases a patch while my server is stopped, what gets installed the next time I start? Can I see or choose the game and framework versions, and who puts the framework back if the game update leaves a vanilla server?” Confirm whether the provider handles the framework, gives you a control for the install, or requires you to do it from files. Oxide’s installation guide describes updating Rust back to vanilla as a common mistake. Use the provider’s own answer for its sequence instead of assuming that behaviour applies to every start. ## Choose who makes the call to reopen Ask who can leave players out while you check one plugin action. For example, after the update on a spare world, you can read the build and framework status and verify that a known welcome message appears for a regular tester. If that requires a support request, check who can send it during your usual patch window. Keep the answer with the rental choice. Choose the arrangement where you know who starts the update and who can verify the intended modded world before reopening. ## Sources - [Facepunch dedicated server guide](https://wiki.facepunch.com/rust/Creating-a-server) - [Oxide installation and verification guide](https://docs.oxidemod.com/guides/owners/install-oxide) - [Official Rust release announcements](https://rust.facepunch.com/news/) ## Related resources - [How to put Oxide back after a Rust update](https://rustsc.com/learn/updates/install-oxide-after-rust-update/index.html.md) - [What will a Rust server host help you fix?](https://rustsc.com/learn/hosting/check-rust-rental-support-before-buying/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/choose-updates-you-control-on-a-rust-rental/ --- # Will your Rust rental have enough disk for the next map? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Check the space needed at the busiest point of the switch. That can include the running installation, the new map as it downloads, and an archive or spare copy you need while verifying it. ## List what must fit before you replace anything Ask the host whether the available-space number covers the whole installation or a narrower data folder. Ask where uploaded files, temporary downloads and panel backups count. If the panel moves an archive into the game directory when you export it, include it during the time it stays there. Use the existing usage as the starting point. For example, if the panel shows 13 GB in use of a 20 GB allowance, you have 7 GB left. A 1 GB map download, a 3 GB copy left in the game folder and 2 GB measured for extra working files or saves would use another 6 GB. One further copy could exhaust the remaining space. Measure the files from your own setup. ## Confirm where the recovery copy will go Leave the active world and its only working recovery point intact. If the numbers are too close, have the host confirm which space can be increased or put an independently verified copy on separate storage before the map work. A separate backup allowance may help without changing the game disk. During a rehearsal, compare the maximum usage you see with the headroom you expected. After the switch, verify the game can save and the agreed backup can complete. Ask the host which folder grew if the panel runs out of space sooner than your figures suggest. ## Sources - [Facepunch guide to server files and saves](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Example game panel documentation on archives in the server folder](https://nodecraft.com/support/knowledgebase/nodepanel/server-backups) - [Example documentation on storage and compute limits](https://docs.digitalocean.com/products/droplets/how-to/resize/) ## Related resources - [Track disk space as your Rust world grows](https://rustsc.com/learn/management/measure-rust-save-growth-before-disk-fills/index.html.md) - [What does a Rust rental’s backup allowance actually cover?](https://rustsc.com/learn/hosting/compare-rust-rental-backup-allowances/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/check-rust-rental-disk-quota-before-a-map-change/ --- # Should two Rust worlds share one host? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Start with what you want players to be able to do when one host is unavailable. If the event world is your fallback during a main-world outage, keep it somewhere that can stay up independently. If both worlds can close together for maintenance, running them on one suitable host may be simpler. ## Name the event that would take both out Restarting a host interrupts every Rust process it runs. Two separate services on that host still depend on its power, storage and connection. Two rentals could also be on the same physical host or in the same location. Ask the provider what the two services share if the second one needs to stay reachable when the first fails. Agree what you mean by a fallback. For an ordinary scheduled reboot, a second host may be enough. To keep an event running during an outage of one location, check the dependence on that location too. | Worlds | Reasonable decision | | --- | --- | | Main world and private practice world | Share a host if neither needs to stay available during the other's host work. | | Main world and the world advertised as its fallback | Choose a separate host and check the particular outage you need it to survive. | | Worlds for different groups with independent maintenance | Decide whether both groups can accept the same downtime before sharing a host. | ## Rehearse the route players would use With spare instances, keep the intended fallback running while the primary test world is closed. Have a player follow your fallback join instructions from another network and confirm the expected world. Make any separate backups reachable without the primary host. Record the rehearsed condition. A stopped game demonstrates the join route, and provider information is needed to confirm the services do not share a host or location. ## Sources - [Facepunch dedicated server guide](https://wiki.facepunch.com/rust/Creating-a-server) - [Cloud hosting documentation on locations and shared points of failure](https://docs.aws.amazon.com/lightsail/latest/userguide/understanding-regions-and-availability-zones-in-amazon-lightsail.html) - [Example documentation on copies across regions](https://docs.aws.amazon.com/lightsail/latest/userguide/understanding-snapshots-in-amazon-lightsail.html) ## Related resources - [Will a second Rust server fit on the same host?](https://rustsc.com/learn/hosting/will-a-second-rust-server-fit-on-one-host/index.html.md) - [How to reboot a host running several Rust servers](https://rustsc.com/learn/management/reboot-a-host-with-several-rust-servers/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/choose-one-or-two-hosts-for-rust-worlds/ --- # Does your Rust community need a second world? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Open a second world when people want a different way to play and you can keep both worlds available. A crowded wipe night or one popular request gives you a reason to investigate. A second world adds a second set of promises to keep. ## Choose the smallest change that serves the players Ask interested players what they would actually join and for how long. Give them a named option, a play window and the proposed rules. People who ask for a quiet place to practise building might happily use a weekend world. | What you heard | What to try | | --- | --- | | Players mainly want better hours, a clearer wipe date or fewer surprises in the current rules | Discuss a change on the existing world and check who would lose a rule they value. | | Players want a different activity for one evening or a single weekend | Offer a weekend session with a clear closing date and tell players what progress ends with it. | | A second set of players wants an incompatible ruleset throughout the wipe | Write a separate player promise and hold a short opening with the intended rules and joining route. | ## See if your staff can keep both promises For a permanent second world, write who answers reports for each world, who opens it after a wipe and who can take over when that person is away. Walk through the first evening both worlds are busy. If the same person has to resolve a moderation incident on one and verify a wipe on the other, move a discretionary task or keep the second world to a staffed event. Give a helper the two candidate names and proposed browser tags. Ask them which server a new player would pick for each ruleset. Rust uses tags to help players filter its browser, so a player-facing distinction helps you test whether the two listings make sense. ## Pick a decision date before you open the test world Set the evidence you want by the end. For example, Harbor's weekend builders say they would come back and one helper agrees to cover the practice world, while the survival schedule keeps its usual cover. If the only turnout came from people leaving survival during its busiest hour, ask whether a recurring event suits the same community better. Once the second world has its own purpose and reliable cover, test capacity before putting it on the same host. ## Sources - [Facepunch dedicated server guide](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch server browser tags](https://wiki.facepunch.com/rust/server-browser-tags) - [Google SRE Workbook on testing changes in a limited rollout](https://sre.google/workbook/canarying-releases/) ## Related resources - [Will a second Rust server fit on the same host?](https://rustsc.com/learn/hosting/will-a-second-rust-server-fit-on-one-host/index.html.md) - [Can you run a Rust server just for game night?](https://rustsc.com/learn/hosting/run-a-rust-server-just-for-game-night/index.html.md) - [Open a Rust practice world alongside your survival server](https://rustsc.com/learn/management/open-a-rust-practice-world-without-copying-the-main-world/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/does-your-rust-community-need-a-second-world/ --- # What address should friends use to join your Rust server? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Use the public game address and game port for friends joining from outside your home. A command that works on the host or on your home Wi-Fi may contain an address that only works there. ## Match the address to where the player is On the host, localhost points back to the host itself. From another device on your home network, use the host’s private address. For friends elsewhere, use your public address at home or the public game address shown by your rental host. Send the complete instruction they will use in the Rust F1 console. For example, if your public address were 203.0.113.42 and your public game port were 28015, the instruction would be connect 203.0.113.42:28015. Replace both parts with the values for your server. ## Ask one friend to try the exact instruction Have a friend outside your network paste the instruction and confirm they loaded into your world. A friend who tried a private address earlier should retry with the replacement before you change any server settings. If the public address still fails while the private address works, check where the public game port goes. On a home connection, the router needs to forward that UDP port to the host. On a rental, check the game address and port in the panel before asking support to look at the connection. ## Sources - [Facepunch direct connection instructions](https://wiki.facepunch.com/rust/Creating-a-server) - [RFC 1918 private IPv4 addresses](https://www.rfc-editor.org/rfc/rfc1918.html) - [RFC 5737 addresses for examples](https://www.rfc-editor.org/rfc/rfc5737.html) ## Related resources - [What a message means and what to do](https://rustsc.com/support/guides/fix-common-problems/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/which-address-should-friends-use/ --- # Can you add a Rust server manager and keep your rented server? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Hosting](https://rustsc.com/learn/hosting/index.html.md) Yes, if your host gives the manager the access it needs. Your world can stay on the same rental and your players can keep using the same address. Start with the job you want help with. Reading chat during a game and bringing the server back after it stops need different controls. ## What do you want to manage outside the panel? Being able to do something in a browser panel does not automatically give a separate tool the same access. Use this list with your host's connection details. | Your job | What the manager would need | | --- | --- | | Talk to players during maintenance | A remote console connection (RCON) or a panel connection that can send commands to the running game. | | Change a plugin setting | A file login or panel key that can read and write the plugin’s configuration folder. Check how that plugin loads changes. | | Start the game after it has stopped | A panel connection with permission to start this server. A stopped game cannot answer its remote console. | | Recover yesterday’s world | Access to the saved backup and a way to restore it. If the host holds the only copy, find out who can request the restore. | ## Work through a Saturday restart Suppose your host already restarts the game on Saturday morning. All you want is to warn players beforehand. Leave that restart in the host panel and use a console connection for the announcement. Adding the same restart to a second scheduler gives both tools a reason to interrupt the game. If the real problem is that nobody can start the server again when it stays down, chat access solves the wrong problem. Look for a start control that works from the manager, or arrange for a helper to use their own panel account. ## What to ask your hosting company “I’d like to keep this Rust server and its address. Which connection can I give a management tool for this server? I want it to read chat and start the game if it goes offline. Can it do both, and where do I find the connection details?” Swap in the jobs from your own list. Once connected, open the player list while someone you know is online. Check both the server name and the player you expect to see. Check separately which power and file controls the connection offers. You can keep using the host panel for any job it still needs to handle. ## Sources - [Facepunch guide to Rust remote console access](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Hosting providers](https://rustsc.com/hosting/index.html.md) - [Connect and manage a rented server](https://rustsc.com/support/guides/manage-hosted-server/index.html.md) --- HTML version: https://rustsc.com/learn/hosting/access-needed-for-rented-server-maintenance/ --- # What changes at your first Rust force wipe? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Wipes](https://rustsc.com/learn/wipes/index.html.md) A force wipe comes with a Rust release. An elective wipe is a reset you choose for your server. For your first one, read the release notes before promising which progress players will keep. ## Read the release for this date Check the Rust release announcement and find what it says about world saves and learned blueprints. An update can make old world saves unusable, and Facepunch has required blueprint resets on specific releases. A previous month's scope gives you a starting point for questions to ask about this release. ## Write down your own additional choices For example, you might plan a new map at the required reset and also want to clear a community leaderboard. Record the map reset against the release and the leaderboard reset as your community’s choice. If you also run regular wipes, identify which of those will happen independently of the release. You are ready to announce the scope when you can explain each reset and where the requirement came from. ## Before the required update Take a pre-wipe copy and identify which schedule will run the update. Once it finishes, join before posting the all-clear. The release notes answer what the game requires. Joining confirms the server reached the world you meant to open. ## Sources - [Official Rust release notes](https://rust.facepunch.com/news/) - [Facepunch release notes on forced blueprint wipes](https://rust.facepunch.com/news/pivot-or-die/) - [Facepunch reference for Rust save files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) ## Related resources - [Wipe your server](https://rustsc.com/support/guides/wipe-server/index.html.md) - [Update Rust](https://rustsc.com/support/guides/update-rust/index.html.md) --- HTML version: https://rustsc.com/learn/wipes/first-force-wipe-versus-elective-wipe/ --- # Should your Rust server wipe weekly or monthly? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Wipes](https://rustsc.com/learn/wipes/index.html.md) Choose a wipe rhythm around the time your regulars have to play. Think about when they build a base, reach their preferred monuments and feel ready to start fresh. ## Compare two actual player weeks For example, if your group mostly meets on weekends, a weekly world can give people only one long session before they lose their bases. A monthly map gives those same players more weekends together. If regulars prefer the rush of early progression every week, a weekly schedule may suit them better. Decide what to do with blueprints separately. Set only the browser tag that reflects your chosen schedule and check the next required reset against the official release date. | If players want | Try | Check after one cycle | | --- | --- | --- | | A fresh start most weekends | Weekly | Could people play the early game on the day they expected? | | Time for a shared build across weekends | Monthly | Did the group finish its build before the map reset? | ## Ask returning players after two wipes Tell players when the new schedule starts and what you'll review before its next reset. Ask whether they reached the activities they joined for and whether they were ready to restart. Keep the cadence if it matches those answers and your ability to run the wipes reliably. ## Sources - [Facepunch wipe timer reference](https://wiki.facepunch.com/rust/Server-Wipe-Timer) - [Facepunch server browser tags](https://wiki.facepunch.com/rust/server-browser-tags) - [Official Rust release notes](https://rust.facepunch.com/news/) ## Related resources - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/index.html.md) - [Wipe your server](https://rustsc.com/support/guides/wipe-server/index.html.md) --- HTML version: https://rustsc.com/learn/wipes/weekly-or-monthly-rust-wipes/ --- # What should your Rust wipe announcement say will reset? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Wipes](https://rustsc.com/learn/wipes/index.html.md) Name the progress affected by the wipe. For each part that matters to your players, say whether it resets or carries over. ## Work down the kinds of progress on your server Start with the world and its structures, then learned blueprints, then any relevant plugin progress. Ask separately about balances, ranks and claims if you use plugins for them. Check the announced release scope and your own choices before writing the final post. ## A sample post for a map and claim reset Thursday, 10 December at 19:00 UTC. The map and bases reset. Learned blueprints carry over. Quarry claims reset with the map. Supporter roles stay. We’ll post here when the new world is open. Change all five details to match your wipe checklist. If the release scope is still unknown, say when you will confirm it before telling players what they can keep. ## Read it as someone with progress to lose Before posting, have a regular player answer what happens to their base and one other thing they care about using your draft. If their answer differs from the announcement, change that line. Publish the specific date and time with the final scope. ## Sources - [Facepunch reference for Rust save files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Facepunch release notes on forced blueprint wipes](https://rust.facepunch.com/news/pivot-or-die/) - [Oxide plugin data file guide](https://docs.oxidemod.com/guides/owners/data-files) ## Related resources - [Wipe your server](https://rustsc.com/support/guides/wipe-server/index.html.md) - [Messages, restarts and wipes: what players see](https://rustsc.com/support/guides/player-messages/index.html.md) --- HTML version: https://rustsc.com/learn/wipes/announce-what-a-rust-wipe-resets/ --- # How to stop two Rust wipe schedules from colliding [Rust server guides](https://rustsc.com/learn/index.html.md) / [Wipes](https://rustsc.com/learn/wipes/index.html.md) Start with the next two dated occurrences. One world can have two jobs competing to wipe it, and two worlds can need the same staff at once. Give each world a single reset owner and check the full maintenance window for both. ## Make each occurrence visible in one calendar Read the next run in your panel, startup scripts and any maintenance manager. Write the world, actual date, local time with its zone, and which tool runs the job. Include the player warning, backup, wipe, restart and final join check. Use the time for the actual date, since the same named hour can move when clocks change. For a regular wipe that collides with a required reset on the same world, select which job will own the reset and pause or skip the competing occurrence using that tool's own controls. Read back the next run before you rely on it. The in-game wipe timer uses separate inputs for its countdown, so check that it still describes the date you will actually run. ## Give the worlds a sequence staff can cover Example for Harbor Weekly and Harbor Monthly on one host. Replace these relative dates with next run dates from your own calendars. | Window | Write down | Check before proceeding | | --- | --- | --- | | Release window on the first Thursday | One approved required reset per world. Which operator verifies Weekly and who covers Monthly. | No competing regular wipe for either world. If one person must check both, arrange separate start points around the required update and keep players informed. | | Optional cleanup or plugin job during that window | Which world it touches and whether it must finish before reopening. | Move a discretionary job if it could overlap the handoff or staff cannot verify it. | | Following Thursday | Weekly's normal occurrence if that is your cadence. | Confirm the recurring job is back on its normal date and Monthly has no extra wipe. | ## Decide when to postpone and how to reopen If a world has no confirmed running version, no usable backup or no one to verify the reset, keep that world closed and communicate the revised opening. Defer the optional jobs. After each wipe, check the intended world in the client before announcing it. Confirm the calendar shows only the intended next run for each world. In a disposable real Carbon rehearsal with overlapping jobs on one server, one scheduled change missed its intended start while the wipe used the server. The rehearsal did not test two simultaneous game instances. Check the schedule for both worlds yourself before relying on the handoff. ## Sources - [Facepunch official Rust release updates](https://rust.facepunch.com/news/) - [Facepunch in-game wipe timer](https://wiki.facepunch.com/rust/server-wipe-timer) - [Google SRE on assigning work during an incident](https://sre.google/sre-book/managing-incidents/) ## Related resources - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/index.html.md) - [How to check Rust’s in-game wipe countdown](https://rustsc.com/learn/wipes/match-rust-in-game-countdown-to-real-wipe/index.html.md) - [What to check before telling players a Rust wipe is finished](https://rustsc.com/learn/wipes/check-rust-world-before-announcing-wipe-complete/index.html.md) --- HTML version: https://rustsc.com/learn/wipes/avoid-two-rust-wipes-in-one-window/ --- # Should you change your Rust map seed at the next wipe? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Wipes](https://rustsc.com/learn/wipes/index.html.md) Keep the seed and size if your community wants a familiar island, then verify the layout on the target release. Choose a new seed when you want new routes and build locations. ## Choose what should feel different to players If a casual building group likes the route from its beach to a town, preview the existing seed and size first. If regulars can already name every nearby monument and want exploration, keep the size and compare a few new seeds. A changed seed is a map choice. Your wipe settings still decide what happens to saved progress. ## Check a few landmarks on the target build Use the map itself to settle whether it feels familiar. Even when the seed and size match, check the new build before promising players the same routes. 1. Record the old seed, size and world configuration before you try a candidate. 2. Generate on the build you intend to use. Compare the same landmarks using the in-game map. 3. If the new map will be unfamiliar, replace the old meetup instructions in your notice with a location players can actually find. ## Sources - [Facepunch map data reference](https://wiki.facepunch.com/rust/Map_Data) - [Facepunch reference for Rust save files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Facepunch procedural world configuration](https://wiki.facepunch.com/rust/procedural_generation_customization) ## Related resources - [Preview your map](https://rustsc.com/support/guides/preview-map/index.html.md) - [Wipe your server](https://rustsc.com/support/guides/wipe-server/index.html.md) --- HTML version: https://rustsc.com/learn/wipes/new-seed-or-same-layout-next-wipe/ --- # Which Rust plugin data should reset at a wipe? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Wipes](https://rustsc.com/learn/wipes/index.html.md) Review each plugin by what it stores. A record tied to a building on the old map may need to go. A permission or account entitlement may still belong to the same player after the wipe. ## Make a decision for each affected plugin Use the plugin author's wipe instructions and distinguish settings from saved data. For example, a shop plugin can store item costs separately from player balances. Keep those costs if they still apply and reset balances only if that's your wipe policy. Some plugins handle map wipes themselves, so check the documented behaviour before adding extra cleanup. | Sample record | Decision in this example | Check in the test world | | --- | --- | --- | | Shop item costs | Keep | The same item still costs the expected amount. | | Player balances | Reset | The test player has the configured starting balance. | | Player access | Keep | A test account still has its intended access. | ## Check a specific keep and reset case List what each affected plugin should show afterwards and keep a copy before changing anything. Try the documented reset on a test instance while the live plugin keeps running. In the shop example, check how much a familiar item costs and a test player's balance. The accepted result is that the item still costs the same and the balance returns to the intended starting value. ## Sources - [Oxide plugin data file guide](https://docs.oxidemod.com/guides/owners/data-files) - [Oxide plugin configuration guide](https://docs.oxidemod.com/guides/owners/configure-plugins) - [Facepunch reference for Rust save files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) ## Related resources - [Find and manage plugins](https://rustsc.com/support/guides/plugins/index.html.md) - [Wipe plans in plain words](https://rustsc.com/support/guides/wipe-plans/index.html.md) --- HTML version: https://rustsc.com/learn/wipes/choose-plugin-data-to-reset-at-wipe/ --- # How to rehearse a Rust wipe before wipe night [Rust server guides](https://rustsc.com/learn/index.html.md) / [Wipes](https://rustsc.com/learn/wipes/index.html.md) Give the wipe job a small world with deliberately recognisable data to clear. The rehearsal succeeds when it clears the items you planned and keeps the items you promised. ## Put test data on both sides of the decision Use a separate install or test rental with its own save location, ports reachable only by testers and no live schedules or integrations. Before starting a copy, turn off Rust+ and point any plugin databases or webhooks at test services. For example, add a test structure to the old world and give a shop item a cost of ten scrap that you intend to keep. If a plugin should lose map claims, give it one test claim to remove. Use the same wipe choices and any map or configuration files you intend to publish. Read the wipe steps to check the paths point at the test instance before you run it. ## Check the resulting world and files Join the new world and open the places or menus where you recorded the test data. If one result differs, change the responsible wipe step. Reset the disposable fixture before trying again, so the next run still has all the same data to work on. 1. Before running the wipe, record which test objects and settings are present. 2. Run the same reset and startup steps you intend to use on wipe night. 3. Compare the results with your recorded list. Use these steps on the live server only after each expected reset and keep case passes. ## Sources - [Facepunch reference for Rust save files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Oxide plugin data file guide](https://docs.oxidemod.com/guides/owners/data-files) - [Facepunch guide to creating a server](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Wipe plans in plain words](https://rustsc.com/support/guides/wipe-plans/index.html.md) - [How to prove your Rust server backup can be restored](https://rustsc.com/learn/recovery/prove-a-local-backup-with-a-test-restore/index.html.md) - [What to keep for Rust+ when restoring the same server](https://rustsc.com/learn/recovery/preserve-rust-plus-pairing-when-restoring/index.html.md) --- HTML version: https://rustsc.com/learn/wipes/test-a-rust-wipe-plan-before-running-it/ --- # A Rust wipe stopped halfway. What should you check first? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Wipes](https://rustsc.com/learn/wipes/index.html.md) Identify the last step that definitely finished. A wipe might have stopped before reset, after removing the old save, or after the new world began loading. ## Preserve what you can still inspect Pause future runs for that wipe. If a run is still active, let it finish or follow the wipe tool’s recovery instructions before changing files. Keep the pre-wipe copy and read the wipe tool's run result and the game console. Before taking a manual copy of any new save, stop the game and any other process writing to those files. Keep the new state separately from the pre-wipe copy. ## Finish the smallest step your evidence supports Correct the named problem first. If the reset completed and only startup failed, check the startup error and the intended map settings, then start the game without sending another wipe. If you cannot establish what was removed, leave the live world closed while you compare the current files with the expected result or ask the host for the failed step. Reopen after joining the expected world and confirming the wipe scope. | What you can establish | Next check | | --- | --- | | Game stopped, old save remains | Check whether the wipe recorded a failed prerequisite before it reached reset. | | New save exists, game won’t load | Read the startup error and verify the expected map settings. | | Tool and files disagree | Keep both copies and get the failed stage confirmed before another write. | ## Sources - [Facepunch reference for Rust save files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Facepunch console command reference](https://wiki.facepunch.com/rust/useful_commands) ## Related resources - [Wipe plans in plain words](https://rustsc.com/support/guides/wipe-plans/index.html.md) - [Recover a damaged save](https://rustsc.com/support/guides/recover-save/index.html.md) --- HTML version: https://rustsc.com/learn/wipes/check-an-interrupted-rust-wipe-before-retrying/ --- # How to check Rust’s in-game wipe countdown [Rust server guides](https://rustsc.com/learn/index.html.md) / [Wipes](https://rustsc.com/learn/wipes/index.html.md) Rust's countdown shows the game's calculated wipe time. Compare it with the date in the panel or tool that performs your wipe. ## Read the countdown's next date A copied override could still point at Thursday while your panel is set for Friday. Check which setting determines the result before editing the wipe day. 1. Read the next scheduled run in the tool that performs the wipe. 2. Run PrintWipe and compare its date, time and time zone. 3. Check for a timestamp or cron override before editing the regular weekday or hour. ## Confirm the new values agree Correct the setting that no longer matches your wipe checklist and run PrintWipe again. Check the resulting date against the schedule and your public notice. The countdown also helps time the game's end-of-wipe events, so this check matters even when everyone already knows the date. ## Sources - [Facepunch wipe timer reference](https://wiki.facepunch.com/rust/Server-Wipe-Timer) - [Facepunch server browser tags](https://wiki.facepunch.com/rust/server-browser-tags) ## Related resources - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/index.html.md) - [Change server settings](https://rustsc.com/support/guides/server-settings/index.html.md) --- HTML version: https://rustsc.com/learn/wipes/match-rust-in-game-countdown-to-real-wipe/ --- # What to check before telling players a Rust wipe is finished [Rust server guides](https://rustsc.com/learn/index.html.md) / [Wipes](https://rustsc.com/learn/wipes/index.html.md) Have someone join through the normal route and play a short first session. A server can appear online before you have checked the things players need on the new world. ## Use the same route as a player Find the public listing if that is how people join, or use the shared direct address. Confirm the new map is the one you announced. For example, check that the advertised landmark is present and the entry takes you to this world rather than an old instance. ## Try the first few minutes of actual play Pick an action that would catch a problem the server status alone cannot show. A starter foundation is good for a building server. An ordinary player accepting the welcome rules is a better test when a plugin controls entry. If a check fails, tell players what is holding up reopening. 1. Spawn and move inland using an ordinary player account. 2. Try one first-session action and one essential join-time plugin if the server uses one. 3. Post the all-clear after the new world passes those checks. ## Sources - [Facepunch guide to creating a server](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch reference for Rust save files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Facepunch console command reference](https://wiki.facepunch.com/rust/useful_commands) ## Related resources - [Wipe plans in plain words](https://rustsc.com/support/guides/wipe-plans/index.html.md) - [What a message means and what to do](https://rustsc.com/support/guides/fix-common-problems/index.html.md) --- HTML version: https://rustsc.com/learn/wipes/check-rust-world-before-announcing-wipe-complete/ --- # Which Rust server changes should wait until after the wipe? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Wipes](https://rustsc.com/learn/wipes/index.html.md) Write down the wipe you promised players. Keep the changes required for that version of the world together. Move an optional change to a separate session if you can verify it later without resetting player progress again. ## Keep the work small enough to open on time Suppose you announced a new generated world with blueprints retained. The new map and the blueprint check belong to that wipe. A new welcome message can wait, since players can join and play under the current message. A plugin that must be installed before the first players act needs its own decision before opening, even if you originally called it optional. If the game update requires a matching framework update for the world you advertised, include that dependency in the wipe checklist. Facepunch’s wipe timer can announce the window, but use the job that actually performs the change to decide which steps must finish. | Proposed change | Can you defer it? | | --- | --- | | New advertised world | Only by telling players the wipe plan changed | | Revised community message | Yes, if the existing rules remain accurate | | Plugin required to enforce the advertised first-session rules | Only if players are told which rules or admission will change | ## Give postponed work a next check On a spare world, run the smallest version you can open. Join as a regular player and check what you promised, such as the intended map and a retained test blueprint. If the rehearsal passes, label the other jobs with their own next rehearsal. When a change would require another wipe to verify, move it to the next planned wipe instead of testing it on the open world. ## Sources - [Facepunch wipe timer reference](https://wiki.facepunch.com/rust/server-wipe-timer) - [Facepunch dedicated server guide](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch custom map troubleshooting](https://wiki.facepunch.com/rust/FAQ_and_Troubleshooting) ## Related resources - [How to rehearse a Rust wipe before wipe night](https://rustsc.com/learn/wipes/test-a-rust-wipe-plan-before-running-it/index.html.md) - [What to check before telling players a Rust wipe is finished](https://rustsc.com/learn/wipes/check-rust-world-before-announcing-wipe-complete/index.html.md) --- HTML version: https://rustsc.com/learn/wipes/choose-rust-changes-to-defer-on-wipe-night/ --- # Which scheduled Rust jobs should wait until the wipe is over? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Wipes](https://rustsc.com/learn/wipes/index.html.md) Look at the jobs that can run while you reset and verify the world. Pause or move any job that could interrupt that work. Record each change so the normal backup and update routine returns afterward. ## Look outside the wipe screen Read the next runs in the host panel, your management tool and any schedule on the host. Compare times in one zone. On a Linux host that uses systemd timers, systemctl list-timers shows next runs for timers currently loaded. For jobs you know are elsewhere, check those schedulers too. Suppose the wipe starts at 19:00 UTC. A 19:05 UTC update that can restart the game belongs after verification unless it is part of your wipe. A 19:10 UTC backup can wait if it would copy a partly changed world. Keep the scheduled notice if it matches the current time and can still go out. | Job to move or pause | Write down | | --- | --- | | Ordinary backup | Its controller, original next run and the next known-good backup to take | | Unrelated restart or update | Its original schedule and when you want it to resume | | Wipe notices | The exact time and reset you told players to expect | ## Read the next runs after you reopen Before re-enabling a job, check whether that scheduler runs missed work immediately. If it does, arrange an intentional next run that will not interrupt the newly opened world. Check that the deleted or completed one-off wipe cannot run a second time. Your notes are complete when the ordinary backup and update schedules show the intended next times and the first backup after the wipe captures the playable world. If another person covers the next shift, give them the next-run list. ## Sources - [Facepunch wipe timer reference](https://wiki.facepunch.com/rust/server-wipe-timer) - [systemd timer and missed-run behavior](https://www.freedesktop.org/software/systemd/man/latest/systemd.timer.html) - [systemd command to list timers](https://www.freedesktop.org/software/systemd/man/latest/systemctl.html) ## Related resources - [How to stop two Rust wipe schedules from colliding](https://rustsc.com/learn/wipes/avoid-two-rust-wipes-in-one-window/index.html.md) - [Should a missed Rust job run when the host comes back?](https://rustsc.com/learn/management/check-what-rust-schedules-do-after-an-outage/index.html.md) --- HTML version: https://rustsc.com/learn/wipes/pause-rust-jobs-during-a-wipe-window/ --- # What should you write down after a Rust wipe? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Wipes](https://rustsc.com/learn/wipes/index.html.md) Write one entry for the wipe you actually performed. Keep it beside your owner notes with the server name, time, changed files or settings, and what a player verified. Include any important difference from the announcement. ## Write the records you would want to find next week Start with “Harbour, Friday 18:30 UTC map wipe. Started the new East Bay map. Map revision east-bay-v3.map. Previous world is in Thursday’s verified separate backup. Blueprints retained and Mei confirmed hers after opening.” Give your own entry a full date so you can match its time to logs. Use an exact filename if there are multiple revisions. For a generated map, write the active seed and world size. Keep the source of any plugin changes in the same notes, such as the settings copy kept with the prior backup. | Keep in one entry | Why you might need it later | | --- | --- | | Before and after map or seed | Identify the world before choosing any repair | | Checkpoint location and recorded time | Find the real before-wipe copy | | Player-side check and one unresolved detail | Know what someone verified and what to inspect next | ## Close an open item deliberately If the player report says the new map was correct but the shop rules were still untested, name who will check that and when. When they do, add the result to the same record. Ask the person covering the next shift to point to the correct backup and the change you still need to verify. ## Sources - [Facepunch wipe timer reference](https://wiki.facepunch.com/rust/server-wipe-timer) - [Facepunch dedicated server guide](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch guide to server files and saves](https://wiki.facepunch.com/rust/Getting-Started_w-Server) ## Related resources - [What to check before telling players a Rust wipe is finished](https://rustsc.com/learn/wipes/check-rust-world-before-announcing-wipe-complete/index.html.md) - [Put your Rust server’s operating details on one page](https://rustsc.com/learn/management/write-a-rust-server-operator-card/index.html.md) --- HTML version: https://rustsc.com/learn/wipes/keep-a-short-rust-wipe-change-record/ --- # How to tell your Rust players a wipe is delayed [Rust server guides](https://rustsc.com/learn/index.html.md) / [Wipes](https://rustsc.com/learn/wipes/index.html.md) If the old wipe job is still queued, pause or cancel that run first. Then correct the announcement players will find. If the replacement time is unknown, say when you will post the next update. ## Keep the old run from firing Open the tool that performs the elective wipe. If the old run is queued, pause or cancel it and confirm the scheduler no longer shows it at the old time. If it has already started, record what has happened and check the current world before deciding what to do. Leave the job alone until you know what it changed. ## Correct the old post before the new message travels Edit the pinned or linked announcement so it starts with “Wipe delayed”. Remove the obsolete timestamp from the current instructions. Put either the confirmed new time with its zone or the time of your next update in its place. Then post a short reply that points people back to that updated message. For example, if Harbour was due to wipe at 19:00 UTC and the new map has not downloaded, try “Harbour’s map wipe is delayed. We’re checking the new map. Next update here at 19:30 UTC. Blueprints still stay.” The 19:30 UTC time belongs to the update, so label it that way in Discord and game chat. ## Check the timer and any scheduled messages Review messages that might still announce the old time. Once you know the replacement time, set it in the scheduler and check any in-game countdown separately. Discord timestamps display an actual instant for each reader, so replace the old markup as part of editing the announcement. Ask a player who only reads the pinned post to tell you what time they should next look at it. If the answer is the previous wipe time or they think your update time is a reopening promise, change the message before you send it elsewhere. ## Sources - [Facepunch wipe timer reference](https://wiki.facepunch.com/rust/server-wipe-timer) - [Discord timestamp styles](https://docs.discord.com/developers/reference#message-formatting) ## Related resources - [How to announce a Rust wipe across time zones](https://rustsc.com/learn/management/plan-a-rust-wipe-across-time-zones/index.html.md) - [What to tell players in Discord and in Rust chat on wipe day](https://rustsc.com/learn/management/rust-wipe-messages-for-discord-and-game-chat/index.html.md) - [A Rust wipe stopped halfway. What should you check first?](https://rustsc.com/learn/wipes/check-an-interrupted-rust-wipe-before-retrying/index.html.md) --- HTML version: https://rustsc.com/learn/wipes/update-a-rust-wipe-announcement-after-a-delay/ --- # How to check that blueprints survived a Rust map wipe [Rust server guides](https://rustsc.com/learn/index.html.md) / [Wipes](https://rustsc.com/learn/wipes/index.html.md) A fresh world can still have learned blueprints. Rust stores buildings and other world objects in the world save and stores blueprints separately. Check both in-game before telling players the wipe is complete. ## Pick a blueprint you can check Before the wipe, have a player note an item they previously researched and confirm it shows as learned. Choose something that requires learning. For example, use a researched weapon the account had unlocked before the wipe. Keep a backup of the server before making changes. Read the notes for the current Rust release if the wipe comes with an update. Use this check when your wipe settings and the game update both allow blueprints to carry over. ## Join the new world with the same account Have the player confirm the world reset, then open the crafting menu and look up the same item. An empty inventory or a missing base tells you about the reset world. Check whether the item still shows as learned, even if the player needs to gather materials or find a workbench to craft it. If it shows as unknown, confirm the player joined the intended server and check that the server started with the intended identity and that the wipe kept the blueprint data. Take a copy of the current state before trying any recovery. Restoring the old world wholesale would bring back the old map state as well. ## Sources - [Facepunch reference for Rust server save files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Official Rust release notes](https://rust.facepunch.com/news/) ## Related resources - [Wipe your server](https://rustsc.com/support/guides/wipe-server/index.html.md) - [Back up a server](https://rustsc.com/support/guides/back-up-server/index.html.md) --- HTML version: https://rustsc.com/learn/wipes/verify-blueprints-after-map-wipe/ --- # Move Rust plugin settings and player data to another server [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) Configuration controls how a plugin behaves. Data records what already happened, such as a player's reward balance. A successful startup on a new host only proves the plugin could load. ## Choose what the move is supposed to carry For a faithful move, list the plugin build, required libraries, settings, language files and stored data that your players need. Read the publisher's storage instructions. Data might live in a named subfolder or an external database. For example, Better Chat keeps the chat group definitions in oxide/data/BetterChat.json and its messages under oxide/lang. If the goal is to preserve the existing chat format, write down the title and message color of a test player. If the goal also includes keeping the same people in the same groups, include the framework's group and membership data. ## Copy after writes finish Stop the source server cleanly so the plugin can finish saving. Move the documented files or database backup to the corresponding locations on the stopped destination. Keep the originals. Verify that the destination uses its own copy of storage before both servers can run at once. On the destination, use the same supported plugin release. Give your test player the expected group if memberships were intentionally left behind, then send a message. If their title or color changed, check the chat group definitions. If the definitions are present, check the player's group membership. ## Sources - [Oxide distinction between configuration and data](https://docs.oxidemod.com/guides/owners/data-files) - [Better Chat group data and language files](https://umod.org/plugins/better-chat) ## Related resources - [Restore a backup](https://rustsc.com/support/guides/restore-backup/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/move-plugin-settings-and-player-data/ --- # Which Rust server backup should you restore after an incident? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) Choose the newest compatible backup that still contains the state you want. Work out when the damage started, then check what the closest copies actually contain. ## Start the timeline where things changed Separate the first report from the first bad change. If players report missing deployables at 21:00 UTC, a staff note about a plugin change at 20:10 UTC is a better starting point for the search. Compare staff messages, console history and backup times using the same time zone. Include the last time someone saw the data intact. A backup's end time can be later than the save it contains. A copy that finished at 20:20 UTC might hold the world saved at 20:00 UTC and plugin files captured after 20:10 UTC. Look for the associated save time and check the specific data you need. When the times are uncertain, compare the closest usable copies from either side. ## Choose between two close candidates Suppose the 19:55 UTC backup has the missing deployables and the 20:20 UTC copy already shows empty foundations. For a world rollback, the 19:55 UTC point is the better candidate. If the loss turns out to be a vanished plugin menu with the world intact, check whether you can recover its settings or data independently so players can keep their later world progress. 1. Preserve the current server and its logs separately so you can compare both states after a restore. 2. Check the candidate against the active map and game version. Use the linked test-restore guide to boot a separate copy with its own ports and live integrations disabled. Verify the missing feature or a known landmark. 3. Tell players which point you verified and which play time it could replace. After restoring, check the same spot on the server before reopening it. ## Sources - [Facepunch guide to Rust saves and player files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Oxide guide to plugin data files](https://docs.oxidemod.com/guides/owners/data-files) ## Related resources - [How to prove your Rust server backup can be restored](https://rustsc.com/learn/recovery/prove-a-local-backup-with-a-test-restore/index.html.md) - [How to recover deleted Oxide plugin data](https://rustsc.com/learn/recovery/recover-deleted-oxide-plugin-data/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/choose-rust-backup-before-an-incident/ --- # Why is my Rust world empty after changing the server identity? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) Check the Rust server identity and game folder before assuming your world was wiped. Changing `server.identity` can make Rust start in a different save folder, even when the original files are still on the host. ## Find the folder the server opened Read the startup command or the identity field in your host panel. The identity is the name Rust uses under the install's `server/` folder. The display name in the server browser is a separate setting. If you changed `+server.identity coast` to `+server.identity coast-new`, check both `server/coast` and `server/coast-new` under the active game install. Look for the expected `.sav` in the old folder and compare the date, map and saved state with what players remember. A new install may also have its own `server/` folder, so check the working game folder if the identity value stayed the same. A map with familiar terrain and missing buildings can still be a fresh save. ## Reconnect the original save safely If players built on the empty server, their new progress is in the new folder. Explain the switch before stopping it. Keep both identity folders and the launch settings in a separate copy so you can return to either state. 1. Stop the server and pause any scheduled starts while you work. Confirm the game has exited before copying the folders. 2. Set the original Rust server identity in the startup options. Check that the game folder and map settings also match the old save. Leave both copies of the files in place. 3. Start with access limited to your testers. Join the expected server and visit a landmark with a known building. If it is still missing, stop and compare the map settings and version with the old save before trying a restore. ## Sources - [Facepunch guide to server identity files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Facepunch guide to Rust startup options](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Can you restore an old Rust save after a forced wipe?](https://rustsc.com/learn/recovery/restore-rust-save-after-forced-wipe/index.html.md) - [Choose a server folder](https://rustsc.com/support/guides/server-folder/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/rust-world-empty-after-server-identity-change/ --- # Should you stop a Rust server before taking a backup? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) Use your backup tool's running mode for routine copies if it handles the active save and databases. For a manual file copy or a change that needs the world and plugins to line up, plan a clean stop. ## Find out what changes while Rust runs Rust keeps writing world saves and player data. A map save and a plugin database can change at different moments during the same copy. A file browser or archive tool copying one file after another can read files mid-write, even after the game reports a successful save. A running backup needs a way to take a completed save and handle the databases and plugin files it claims to cover. | What you need to protect | What to do | | --- | --- | | Routine world recovery with a tool that handles live data | Use the tool's running backup workflow. Check that the completed copy includes the world save and the player or plugin data you rely on. | | World and plugin state from the same quiet period | Warn players and stop Rust cleanly. Wait for every writer to finish, including any separate plugin service, then copy the files or use that service's export. | | Files copied while the game crashed or was stuck | Keep the result as evidence. Check an earlier verified backup as your first recovery option. | ## Use a quiet copy before a coordinated change Imagine a plugin that links shop listings to vending machines in the world. A sale can change the plugin's records while the game is still saving older vending machine state. Before replacing that plugin, announce a short stop, let Rust exit normally and make the backup while the writers are stopped. If the plugin uses an external service, follow its supported export procedure as part of that window. Check the copy for the expected save and the shop's data. For a recovery check, use the same compatible plugin version in a separate test server with the shop connected to a test copy of its data. Keep production webhooks and any shared database disconnected. Confirm a known listing and its vending machine agree. That checks the relationship a file list alone misses. ## Sources - [Facepunch guide to rotating Rust saves and databases](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [SQLite documentation on backing up an active database](https://www.sqlite.org/backup.html) ## Related resources - [Which SQLite files do you need when copying a Rust database?](https://rustsc.com/learn/recovery/copy-rust-sqlite-database-and-wal/index.html.md) - [How to prove your Rust server backup can be restored](https://rustsc.com/learn/recovery/prove-a-local-backup-with-a-test-restore/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/rust-backup-running-or-stopped/ --- # Which files belong in a Rust server backup? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) Start with what you need back. A playable world, learned blueprints, staff permissions and plugin progress can each depend on different files. Keep the list beside the backup so you can check it after an update or a move. ## Match the files to what players will notice Find the active game install and Rust server identity. For shared installs, check you have the folder for the right server. Confirm the actual locations on your host because frameworks and plugins can use other folders or external services. | What to recover | What to include | | --- | --- | | Terrain and built world | The matching `.map` and `.sav`. Keep the original custom map download or record the procedural map settings. | | Learned blueprints and other player state | The corresponding player databases and any matching database side files from that capture. | | Server rules and access | The active identity's `cfg` folder and a private copy of the startup settings the host uses. | | Modded features and progress | Framework settings and permissions, required plugin versions, configuration, data and any supported export from an external service. | ## Follow one feature from files to in-game behavior On a server with a tournament arena, a world copy might contain the course while the scoreboard lives in a plugin database. Open a recent backup in a separate folder and find the plugin's data alongside the world files. If the scores live in an external database, record how to restore the matching export and who can access it. Check the inventory after adding a feature that saves progress. For the arena, check that you can recover the course, the spawn settings and a known score. Update the list if any of those depend on files or settings outside the original backup. ## Sources - [Facepunch reference for the contents of a Rust identity folder](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Oxide reference for configuration and plugin data](https://docs.oxidemod.com/guides/owners/data-files) ## Related resources - [Which custom map file should you keep with a Rust backup?](https://rustsc.com/learn/recovery/archive-custom-rust-map-for-recovery/index.html.md) - [How to recover deleted Oxide plugin data](https://rustsc.com/learn/recovery/recover-deleted-oxide-plugin-data/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/what-a-rust-server-backup-needs-to-include/ --- # Is a Rust server backup on the same disk enough? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) A backup on the game disk gives you a quick way back after a bad edit or plugin change. Keep a copy somewhere else for the day that disk or host is unavailable. ## Ask what disappears along with the game Two Windows drive letters can be partitions on one physical disk. Two Linux folders can be on the same mounted disk. In Windows Disk Management or your Linux disk utility, match the game and backup locations to their devices. On a rented server, check whether you can download a copy and open it after the game service or account goes away. | Copy location | When it can help | What else to allow for | | --- | --- | --- | | Another folder on the game disk | A wrong config edit or a damaged save | Losing the disk takes both folders. | | A separate disk attached to the host | Failure of the game disk | Losing the host can take both disks. | | A disconnected drive or separate storage you can reach from another device | Loss of the game host | Keep the copy recent and check that you can open it independently. | ## Keep the fast copy and add a separate one Suppose your game and daily backups both sit on one SSD. Keep the daily copies for quick recovery. Copy a finished backup to a separate destination and open it from another device. Use an encrypted destination for copies containing server credentials or player records. Disconnect a removable drive after the copy finishes. Check the newest date you can still reach with the game host unavailable. If it is last Sunday's copy and you need to preserve Thursday's progress, move the separate copies more often. ## Sources - [Canadian Centre for Cyber Security guidance on separate, encrypted backup copies](https://www.cyber.gc.ca/en/guidance/tips-backing-your-information-itsap40002) ## Related resources - [Can you get to your Rust backups if the host is gone?](https://rustsc.com/learn/recovery/check-backup-access-with-host-unavailable/index.html.md) - [How often should you back up a Rust server?](https://rustsc.com/learn/recovery/rust-backup-frequency-and-manual-checkpoints/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/rust-backup-on-the-same-disk/ --- # How many Rust server backups should you keep on the host? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) Decide which dates you need to restore. Measure the space those copies take, then add room for a new backup while the old ones are still there. Check which drive the backup job writes to as it runs. ## Estimate space for your backup copies Use the size of a finished full backup. Enter the total space set aside for these copies, including space they already occupy. Leave room for the game and temporary files outside that amount. **Worked example** Seven full copies at 8 GB use 56 GB. With 70 GB set aside, the next copy fits with 6 GB to spare before cleanup. Incremental or shared-block backups use a different calculation. ## Count recovery points by date If you keep seven copies and normally back up once a day, two extra before-change copies can push out two older daily points. Look at actual dates in the backup list. Keep a separate copy of a point you must retain beyond that window, such as the last good save before a map change. Decide how far back you need to go to catch a problem you might notice late. A copy from this morning is useful after a crash. It gives you no way back to a configuration that was already missing by then. ## Measure the space your method actually uses For separate full archives, use the stored size of the largest recent completed archive you expect to keep taking. Eight 2 GB archives take about 16 GB. If a ninth is written in the same place before an old one is removed, allow another 2 GB. If the backup job also stages a working copy, check its location and peak size while a job runs. If Rust saves to the same drive, leave room for the game to write its next save and logs as well. For backups that share data between snapshots, compare the total stored size before and after several comparable runs. A full restore can be much bigger than the additional space one snapshot used. Include a busy day in your measurements and measure again after a map or plugin change. Where the staging and backup folders are on different drives, check the space each drive needs separately. | Example on one drive | Room | | --- | --- | | Eight archives around 2 GB each | 16 GB in use | | Next archive before cleanup | 2 GB free | | Temporary files, new saves and logs | Add what you measured on this drive | ## Check the next backup before relying on the estimate Lowering retention can remove older copies. Before changing the count, copy any point you need to a separate location and open it there. If space is tight, make the copy on another drive. Leave the running world and its rotated saves in place. After the next job, check its recorded completion, the oldest needed date, and how much free space remains. If the next backup can finish but leaves too little room for the game to save, move backup storage or revise the history you retain. ## Sources - [Facepunch guide to world saves and rotated copies](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Restic documentation on keeping and removing backup history](https://restic.readthedocs.io/en/stable/060_forget.html) - [Restic backup and restore documentation](https://restic.readthedocs.io/en/stable/manual_rest.html) ## Related resources - [Free disk space](https://rustsc.com/support/guides/free-disk-space/index.html.md) - [How often should you back up a Rust server?](https://rustsc.com/learn/recovery/rust-backup-frequency-and-manual-checkpoints/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/keep-enough-rust-backups-without-filling-disk/ --- # When can a previous Rust save recover a damaged world? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) Try a rotated world save when the current `.sav` is damaged and the surrounding files are healthy. Use a compatible full backup when the incident affected other files that need to recover together. ## Check whether the failure is limited to the world save Rust keeps older copies of its world save as it saves again. These copies describe earlier states of the buildings and entities on that map. Compare the console message with the active Rust server identity, map and save file. An empty world after a launch setting change calls for checking the folder and map first. A save-load error after the host lost power points to a different check. | What you find | Which copy to check first | | --- | --- | | The current `.sav` will not load and the prior save is for the same map and compatible game version | A rotated world save. Check any plugin state tied to world entities before letting players back in. | | The disk failed or the world and related databases were damaged | A full backup of the matching server and world, including any external data the server needs. | | An older save belongs to a different map or forced-wipe generation | A point that matches the current world and is compatible with the game version you are running. | ## Compare the older world with the data you would keep After a host power cut, an older world might predate the placement of a prize crate that a plugin still expects to find. Preserve the existing save, its rotated copies and the other active data while the server is stopped. Test the previous save in a private test server with its own ports and Rust+ disabled. Give plugins test copies of any data they share with the live server. If the older world and newer plugin state disagree, check a compatible backup that includes both from the same point. Tell players what the earlier save would replace. Join before reopening and check a known building and the plugin feature that depends on the world. If both checks pass, confirm the game can make a new save in the expected identity folder. ## Sources - [Facepunch reference for world saves, rotated copies and save versions](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Oxide guide to plugin-specific world data](https://docs.oxidemod.com/guides/owners/data-files) ## Related resources - [Recover a damaged save](https://rustsc.com/support/guides/recover-save/index.html.md) - [Which Rust server backup should you restore after an incident?](https://rustsc.com/learn/recovery/choose-rust-backup-before-an-incident/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/rust-rotated-save-or-full-backup/ --- # What to save before rolling back a Rust server [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) Keep a verified copy of the server as it is now before replacing anything. Even a broken world can contain usable plugin records, recent settings or evidence that helps you choose the right fix. ## Keep one copy of the incident and one of the recovery point If the wrong plugin ran at midday, your earlier backup might hold a working world and your current copy might still hold the staff changes made that afternoon. Store both. Use names that identify the server, the date and the reason for the copy, such as `coast-before-rollback`. Keep the incident copy out of any rotation that might remove it while you work. 1. Keep the relevant console or plugin logs and note the active startup settings. Record the last time players saw the expected world or feature. 2. Arrange the stop and pause automated starts. Once Rust and other writers have exited, capture the active identity, current config and any affected plugin or external data. 3. Open the resulting copy somewhere separate. Check that it holds the files and recent changes you would need to go back. If you need it to be bootable, use a separate test server with its own ports and live integrations disabled. ## Protect the chance to reverse course If the disk is too full for a safety copy, use a separate destination or recover into a separate install first. If some files are unreadable, make a note of the gaps and keep the known good backup untouched. ## Decide what would make you switch back Set a check before the restore starts. For example, the protected area should still exist and a tester should be able to use its gate. When a restore recovers the area but leaves the gate broken, keep access closed and check the plugin separately while you still have both copies. Once players build again, reversing the restore also affects their new progress. ## Sources - [Facepunch reference for world, player and configuration files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Restic documentation on restoring files to a separate location](https://restic.readthedocs.io/en/stable/050_restore.html) ## Related resources - [Restore a backup](https://rustsc.com/support/guides/restore-backup/index.html.md) - [Which Rust server backup should you restore after an incident?](https://rustsc.com/learn/recovery/choose-rust-backup-before-an-incident/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/save-current-rust-world-before-rollback/ --- # How to recover one Rust server setting without rolling back the map [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) If the world is healthy and a setting changed by mistake, use the backup to find the old value. Apply that value to the active setting and leave the world save alone. ## Find the saved setting and its active source Restore the older backup to an empty working folder and leave the archive intact. Check `server//cfg/server.cfg` using the Rust server identity from that backup. Also check any saved startup settings. Your host panel or launch arguments may set the same value, so check what the running server actually reads. For example, the locked crate timer changed during a settings edit and players have since built a new base. Compare the backed-up and active values for `hackablelockedcrate.requiredhackseconds`. Recovering this one setting keeps the base and any unrelated settings changed since that backup. ## Apply and check just that value Save a copy of the active settings before editing. Change the value where your server gets it, whether in the host panel or the active config file. If it is a startup-only setting or you must edit the file directly, schedule a clean stop and restart. 1. Check the active value after applying the change. If it returns to the newer value on restart, inspect the startup settings or panel that may be applying it. 2. Check the intended behavior on a test server or during the next normal event. In the crate example, verify the timer for a newly started hack. 3. Keep the backed-up settings until the check passes. For a setting that affects map selection, test the planned change on a separate copy first. ## Sources - [Facepunch guide to server.cfg and startup settings](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch reference for configuration files in the identity folder](https://wiki.facepunch.com/rust/Getting-Started_w-Server) ## Related resources - [Change server settings](https://rustsc.com/support/guides/server-settings/index.html.md) - [Restore a backup](https://rustsc.com/support/guides/restore-backup/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/recover-rust-setting-without-rolling-back-world/ --- # How to recover deleted Oxide plugin data [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) Find out what the plugin lost before restoring files. A plugin can load normally with fresh data even though its old balances, statistics or shop records are gone. ## Look for the records the plugin writes Oxide normally keeps plugin settings in `oxide/config` and plugin records in `oxide/data`. The author chooses the data file names, so check the plugin documentation before assuming the data file is named after the plugin. Some plugins use several files or an external database. Preserve the current data even if some of it looks empty. | What disappeared | What to compare in the backup | | --- | --- | | A plugin's welcome message or option | Compare its config. Leave player records in place if they are healthy. | | A points balance or player statistics | Find the data file, folder or database the plugin documents. Check for newer entries that a restore would remove. | | A plugin's links to buildings or vending machines | Check that the referenced entities still exist in the current world. Test the data with that world before restoring it. | ## Test the recovered group of files before replacing it Say an event plugin lost its points file and issued new points before you noticed. Preserve the current file after stopping the server, then extract the older copy into a new folder. Check that it matches the plugin version and includes any companion files the plugin needs. If the plugin supports merging or importing records, use that method on the test copy first. Otherwise, choose which point to keep and tell players which later points it replaces. Test with live webhooks and external storage disconnected or pointed at test services. If the files use an unsupported format, keep both copies and check which versions the author says can read them. ## Check for new records before applying the fix If the live plugin has kept running during the test, new points may have appeared since you made your safety copy. Stop the live server and other writers, take a final copy of the current records and verify it before replacing anything. Use the import you tested, or apply the earlier files as a set once you have agreed which points it replaces. Restart with access limited to testers and check both a known balance and whether the plugin can save a controlled new change. ## Sources - [Oxide documentation on data file locations and format changes](https://docs.oxidemod.com/guides/owners/data-files) - [Oxide documentation on plugin configuration](https://docs.oxidemod.com/guides/owners/configure-plugins) ## Related resources - [Which files belong in a Rust server backup?](https://rustsc.com/learn/recovery/what-a-rust-server-backup-needs-to-include/index.html.md) - [Which SQLite files do you need when copying a Rust database?](https://rustsc.com/learn/recovery/copy-rust-sqlite-database-and-wal/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/recover-deleted-oxide-plugin-data/ --- # How to change a restic password without losing your Rust backups [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) Add the new way in, test it on existing backups, then retire the old password. The password that opens your backups and the credentials that reach their storage can expire separately. ## Identify which access is changing This applies to a restic repository you run yourself. Access to the storage gets you to the repository. A repository password lets restic read the backups inside it. Write down which path or storage account and password entry your backup jobs use. Keep the recovery password somewhere you can reach if the Rust host goes down. | Reason for the change | What to verify | | --- | --- | | Switching the storage account or credentials | With the new access, reach the intended repository and restore an existing snapshot. | | Routine replacement of a repository password | Add a new repository key with its own password. From another device using only the new password, restore something from the history you want to keep. | | Suspected exposure of the repository encryption key | Create a new repository with its own encryption keys. Verify required history and new backups there. A password change alone leaves the old encryption keys in use. | ## Make the next backup and read an old one Suppose you created a repository password on the old host and now want one in your recovery vault. Add the new password through restic's key management. Check that you can recover a pre-update snapshot and its expected `.sav` from a separate device. Update your backup job and check that it makes a new snapshot you can read with the new access. Keep a separate, verified copy of important recovery points before revoking anything. Once the old and new points both open using the new credentials, retire the old access and repeat the retrieval check. If you moved repositories because a key was exposed, limit access to the old repository and copies. A replacement key cannot protect a copy someone already obtained. ## Sources - [Restic documentation on repository access and passwords](https://restic.readthedocs.io/en/stable/030_preparing_a_new_repo.html) - [Restic reference on repository encryption and exposed keys](https://restic.readthedocs.io/en/stable/100_references.html) ## Related resources - [Can you get to your Rust backups if the host is gone?](https://rustsc.com/learn/recovery/check-backup-access-with-host-unavailable/index.html.md) - [What can you share from a Rust server backup when asking for help?](https://rustsc.com/learn/recovery/what-to-share-from-rust-backup/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/change-restic-backup-password-without-losing-history/ --- # Can you get to your Rust backups if the host is gone? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) Retrieve a backup from another device without using the Rust host. This tells you whether your separate copy is reachable when the usual login, disk or saved password is gone. ## Rehearse retrieval without touching the live server Leave the server running as usual. Set aside its usual login and local password files for the exercise. Use your written recovery notes and sign in to the separate storage from another device. If the backup is encrypted, check that the password or recovery key is reachable separately. Record where to find it without putting the secret in the notes. 1. Pick a dated copy and retrieve it into a new folder with enough space. For a removable drive, check that another device can mount it and open the files. 2. Open or extract the copy using the tool you can install on a replacement host. Check for the expected server identity and world save plus one file for a feature you depend on. 3. Write down the latest usable date and what you needed to get it. Give a trusted co-owner their own authorized way in if they are expected to recover the server. ## Fix anything that still depends on the original host For example, your backup appears in remote storage but is encrypted with a password saved only on the game host. Move access to a protected place you can unlock separately, then repeat the retrieval. If your newest reachable copy is several days behind the local one, check whether it finished copying and whether your routine moves copies often enough. Keep the working notes when you can get and open the backup independently. Booting it on a separate test server is the next check for whether the world and features come back. ## Sources - [Canadian Centre for Cyber Security guidance on backup access and recovery testing](https://www.cyber.gc.ca/en/guidance/tips-backing-your-information-itsap40002) - [Restic guide to retrieving a saved snapshot](https://restic.readthedocs.io/en/stable/050_restore.html) ## Related resources - [How to prove your Rust server backup can be restored](https://rustsc.com/learn/recovery/prove-a-local-backup-with-a-test-restore/index.html.md) - [Is a Rust server backup on the same disk enough?](https://rustsc.com/learn/recovery/rust-backup-on-the-same-disk/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/check-backup-access-with-host-unavailable/ --- # What to bring when restoring a Rust backup from Windows to Linux [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) Use a clean Linux game install and move the backed-up server data into it. Recreate the launch settings for Linux so the game opens the correct Rust server identity and can write its next save. ## Separate data from the old host's setup Keep a private copy of the Windows launch file or panel settings. It tells you the identity, map settings and other startup values. Install a compatible Rust dedicated server build and matching framework for Linux. Use their Linux startup method. Review the old plugin versions and instructions for any dependencies that also need a Linux version. | From the Windows backup | What to check on Linux | | --- | --- | | Active identity folder | Use the same identity name and capitalization. Preserve the matching map and save file names. | | Custom map and plugin paths | Use paths on the new host. Keep the filename capitalization exact, including plugin config and data references. | | Files the game writes | Make sure the account running Rust on Linux can read its settings and write in its save and plugin data folders. | ## Check the first save as well as the first start If the old identity folder is `Coast` but you pass `+server.identity coast`, Linux can treat those as separate folders. Fix the launch setting in a test install before copying more data. If the game opens the old world but cannot save, check access to the restored folders for the account running it. Recheck with the same account that will run the real service. Keep the Windows data untouched. Start the Linux copy with ports reachable only by testers, Rust+ disabled and any shared plugin databases or webhooks pointed at test services. Join the Linux copy and check a known landmark. Make one small change in the test world. Let the game save and confirm the change survives a restart and that the updated save is in the intended identity folder. ## Move the last live save when the test passes If the Windows server stayed open during testing, it now holds newer play. Arrange a clean stop and take a final backup after the game and other writers exit. Stop the Linux test server and move its test data aside. Restore the final Windows data into an empty destination for the active identity and any plugin data you are moving, so files created during rehearsal stay out of the real world. Keep the Linux launch settings you tested. Set the production connection details and reconnect the integrations you intend to use. Keep the Windows server off and its files intact. On Linux, verify the latest known world change, any affected plugin records and the next save before inviting players to the replacement. ## Sources - [Facepunch guide to Windows and Linux server setup](https://wiki.facepunch.com/rust/Creating-a-server) - [Microsoft documentation on Windows and Linux path capitalization](https://learn.microsoft.com/en-us/windows/wsl/case-sensitivity) ## Related resources - [Why is my Rust world empty after changing the server identity?](https://rustsc.com/learn/recovery/rust-world-empty-after-server-identity-change/index.html.md) - [Move a server to a new host](https://rustsc.com/support/guides/move-to-new-host/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/move-rust-backup-from-windows-to-linux/ --- # Can you restore an old Rust save after a forced wipe? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) A pre-wipe backup preserves the old files. An updated Rust server may require a newer save version, so establish what the running game can load before choosing that point for recovery. ## Check the game version and the map separately Facepunch explains that a forced wipe can change the version number in Rust's save name. Keep the old `.sav` as it is. Renaming it to match the new number cannot make the contents compatible. Also check the map type, size and seed or the custom map file. Save version and map settings are separate checks. | What you need back | Which backup to inspect | | --- | --- | | A base lost after the current wipe | Look for a post-wipe point on the current map from before the base disappeared. | | An old map or world to examine privately | Keep the original matching map and save. Inspect it separately with a compatible game build if you have one. | | Settings that were in use before the wipe | Open the backup in a separate folder and compare the relevant settings with the current ones before applying changes. | ## Choose a point from the right wipe Suppose a server kept the same procedural settings at the forced wipe, then lost a base the following evening. The old map may look familiar, but the pre-wipe point holds the earlier world. Preserve the current files. Find a compatible backup from after the wipe and before the loss. Check for the expected base in a separate install with live integrations disabled before considering an in-place restore. If the only available world copy is from before the forced wipe, leave the current server files in place. You can still open the backup separately to recover the settings you need or keep the files for later inspection. ## Sources - [Facepunch reference for save versions and forced wipes](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Facepunch guide to game branches and map startup settings](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [How to check that blueprints survived a Rust map wipe](https://rustsc.com/learn/wipes/verify-blueprints-after-map-wipe/index.html.md) - [Why is my Rust world empty after changing the server identity?](https://rustsc.com/learn/recovery/rust-world-empty-after-server-identity-change/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/restore-rust-save-after-forced-wipe/ --- # What to keep for Rust+ when restoring the same server [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) For a manual move of the same server, keep its Rust+ identity and pairing data with the world. An independent test or new server should have its own Rust+ identity. ## Keep the Rust+ files with their own server Facepunch identifies `companion.id` as the file Rust+ uses to identify the server. The `player.tokens` files hold players' pairing tokens. Keep them private. When restoring the same server, check that the backup includes these files and that they are from that server. A point from before a player paired may lack that player's current token. Rehearse the move with Rust+ disabled before the test copy first starts. If you edit the test copy’s `server.cfg` yourself, add `app.port -1` or replace the existing value. Confirm the test client’s Rust+ menu shows it is disabled. Keep the original pairing files in your backup. Bring the restored identity online only when the original instance is stopped and you are bringing the same server back. ## Check the app after the real cutover If the game works but Rust+ shows the server as offline, check the companion address and port reported by `app.info`. A move can change where the app needs to connect. Check that the new host exposes the intended Rust+ port and that the app can reach it before you change any saved pairing files. Try the existing pairing with one player. If their pairing is gone after an older restore, ask that player to pair again and check the app can connect. Keep the recovery copy and the original pairing files while diagnosing the issue. ## Sources - [Facepunch guide to Rust+ identity and connection checks](https://wiki.facepunch.com/rust/rust-companion-server) - [Facepunch reference for Rust+ pairing token files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) ## Related resources - [Which files belong in a Rust server backup?](https://rustsc.com/learn/recovery/what-a-rust-server-backup-needs-to-include/index.html.md) - [Move a server to a new host](https://rustsc.com/support/guides/move-to-new-host/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/preserve-rust-plus-pairing-when-restoring/ --- # Which SQLite files do you need when copying a Rust database? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) When manually copying a Rust SQLite database, preserve the database with its matching side files from one stopped capture. For a running database, use a tool that takes a consistent SQLite backup. ## Keep the database and its changes together A matching `-wal` file can contain changes SQLite has already committed that are still missing from the main database. For example, a manual copy of `player.blueprints.18.db` that skips its existing `player.blueprints.18.db-wal` could miss recent blueprint unlocks. Your filename may have a different number. Combining the database from one backup with the `-wal` from another can corrupt the result. A clean shutdown can leave no `-wal` file because SQLite put the changes into the main database and removed the side file. Use the files present after a known clean stop. The absence of a side file from a running copy calls for checking how the copy was made. ## Make and check a working copy If you can stop the writers, stop Rust cleanly and stop any separate service using that database. For a manual filesystem copy, copy the database and the side files that still exist, such as `-wal`, `-shm` or `-journal`, with their names unchanged. If the writers need to stay up, use a SQLite-aware backup tool or the plugin's documented export. 1. Extract the database and its matching files into a new, empty folder. Keep the backup intact, since opening the database can change the working copy. 2. Use your backup tool's database check if it has one, or run `PRAGMA integrity_check` in a SQLite tool on the working copy. The expected result is `ok`. 3. Use a separate Rust instance or the plugin's test environment to check a known record from near the capture time. A readable database can still be missing the data you need. ## Sources - [SQLite documentation on the write-ahead log](https://sqlite.org/wal.html) - [SQLite online backup documentation](https://www.sqlite.org/backup.html) - [SQLite reference for the database integrity check](https://www.sqlite.org/pragma.html#pragma_integrity_check) - [Facepunch reference for SQLite in Rust save folders](https://wiki.facepunch.com/rust/Getting-Started_w-Server) ## Related resources - [Should you stop a Rust server before taking a backup?](https://rustsc.com/learn/recovery/rust-backup-running-or-stopped/index.html.md) - [How to prove your Rust server backup can be restored](https://rustsc.com/learn/recovery/prove-a-local-backup-with-a-test-restore/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/copy-rust-sqlite-database-and-wal/ --- # How often should you back up a Rust server? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) Set the schedule by how much progress players could reasonably lose. Take a separate backup before a major change so you have a nearby point to return to if that change fails. ## Use the gap between successful backups Imagine a building server that gets most of its play on weekend evenings. A daily backup at 06:00 UTC may leave Sunday's evening builds out of a recovery after a late crash. If you want to preserve that session, add a backup after the event or shorten the interval while the server is busy. Check the capture time of the latest usable backup, including the latest one away from the host. A missed scheduled backup can double the gap you thought you had. If a backup failed, check the reason and make a working copy before depending on the schedule again. ## Add a dated copy before a planned change Take an extra copy immediately before a wipe, a new map or a plugin update that changes saved data. Record the change it precedes and verify the copy contains the files you would need to put back. For a change tied to both the world and a plugin database, consider a clean stop so both can be captured in one quiet window. After the next busy week, check two things. Find a backup recent enough for a failure during play and find the particular backup you took before the last change. If frequent copies pushed the named copy out, keep important points separately from the daily rotation. ## Sources - [Facepunch reference for how Rust saves the world](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Canadian Centre for Cyber Security guidance on scheduling and testing backups](https://www.cyber.gc.ca/en/guidance/tips-backing-your-information-itsap40002) ## Related resources - [How many Rust server backups should you keep on the host?](https://rustsc.com/learn/recovery/keep-enough-rust-backups-without-filling-disk/index.html.md) - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/rust-backup-frequency-and-manual-checkpoints/ --- # Which custom map file should you keep with a Rust backup? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) Keep the exact `.map` file that went with the `.sav`, as well as its filename and download URL. The URL can keep working while the file behind it changes. ## Put the map file beside the restore point Keep the exact .map file, its matching .sav, and a small readme with the backup. Add the map filename, download URL, game build and the wipe that first used it. If the download location uses an access link that expires, record where you own the original map file so you can publish a working link when needed. For example, Harbour’s map author sends a winter revision under the same filename as the autumn map. Store the autumn file beside the autumn backup and give the winter revision its own name at a new URL at the next planned wipe. Facepunch describes how the Rust client can reuse a map it has already downloaded by filename. ## Check what a player who has never downloaded it sees First confirm you can open the backup from separate storage and extract both files together. For a restore exercise, put the exact map at a direct download URL and use its original matching filename with the save. Start a private test world using a compatible game build and its own ports. Keep live bots, scheduled jobs and shared plugin data disconnected. Try a client that has joined before and a client on another network that has never loaded this map. If the returning client loads in but the new one cannot download, check the new client's console for the exact map URL. Confirm it opens the map file from their network. Once the new client joins, have them find both a landmark and a known player structure. The landmark checks the map and the structure checks the saved progress. ## Keep a recovery note with the pair Write down the date, filename, backup location and what the new client verified. If they do not see the known structure, keep the test isolated and identify the correct pair before using it to recover the shared world. ## Sources - [Facepunch guide to hosting a Rust custom map](https://wiki.facepunch.com/rust/Hosting_a_custom_map) - [Facepunch FAQ on map filenames and client caching](https://wiki.facepunch.com/rust/FAQ_and_Troubleshooting) ## Related resources - [Why won't my Rust custom map URL load?](https://rustsc.com/learn/configuration/custom-map-url-wont-load/index.html.md) - [Can you restore an old Rust save after a forced wipe?](https://rustsc.com/learn/recovery/restore-rust-save-after-forced-wipe/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/archive-custom-rust-map-for-recovery/ --- # Which bans and staff permissions should you check after a Rust restore? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) An older full backup can also contain older bans, staff assignments and plugin permissions. Record the current decisions before the rollback and check the restored access before reopening the server. ## Save a private list of changes since the backup Before restoring, keep a verified copy of the current state and gather the moderation decisions since the backup date. Check the game's local ban list and in-game staff list, then check the plugin or external service for any access it controls. Use Steam account IDs in your private comparison so you can match players whose display names have changed. Suppose a moderator stepped down on Thursday and a temporary ban ended on Friday. A Wednesday backup might bring back the staff role and the ban. Write down the intended result for each player, including when any still-active temporary ban is supposed to end. ## Apply the decisions you still want With public access still closed, compare the restored game and framework access with your notes. Use the usual ban or permission controls for the affected players. Keep the restored world files and make these decisions one account at a time. For example, check the former moderator's game role and their plugin group memberships, since those can grant access separately. 1. Check that current bans remain in effect and that expired or lifted ones stay lifted. Keep the intended remaining time for temporary bans. 2. Check one active moderator can use the expected staff tools. Check the former moderator's account entry and group memberships so old access stays removed. 3. Reopen the server after checking both the world and the restored permissions. Keep the private comparison with your recovery notes. ## Sources - [Facepunch reference for server bans and admin configuration](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Facepunch guide to inspecting Rust bans](https://wiki.facepunch.com/rust/useful_commands) - [Oxide guide to user and group permissions](https://docs.oxidemod.com/guides/owners/permissions) ## Related resources - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/index.html.md) - [What to save before rolling back a Rust server](https://rustsc.com/learn/recovery/save-current-rust-world-before-rollback/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/check-bans-and-staff-after-rust-restore/ --- # What can you share from a Rust server backup when asking for help? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) Keep the full backup private. Start with the relevant error and the names of the affected files. Share a cleaned copy of a file only when someone needs it to diagnose the problem. ## Give the person helping you a small example Suppose a plugin fails to read its config after a restore. Share the plugin version, the exact error and a copy of the relevant settings with values such as webhook URLs and database passwords replaced. Preserve the same quotes and punctuation so the person helping can see a syntax error. Check nearby log lines for secrets and player information before copying them. | What they need to see | What to send first | | --- | --- | | Whether the right world file was captured | The Rust server identity, map and save filenames, and the backup time. | | Why a plugin could not load its settings | The error and a cleaned copy of the relevant settings. Remove private URLs and tokens. | | Why Rust+ no longer connects | The observed failure and when it started. Keep `companion.id` and player pairing tokens private. | ## Check the outgoing copy separately Extract the archive locally and make a new folder containing only the files you intend to share. Open the outgoing files before sending them. A screenshot can also show an RCON password or player account details. When the problem requires the world file itself, agree on a private transfer with the person helping and share only what they need. If a secret went out already, treat it as exposed. Replace the relevant password or token and check that the intended tools reconnect with the new one. Keep the untouched backup for your own recovery. ## Sources - [Facepunch guidance on keeping the Rust+ identity private](https://wiki.facepunch.com/rust/rust-companion-server) - [Facepunch guide to Rust remote console settings](https://wiki.facepunch.com/rust/Creating-a-server) - [Oxide guide to plugin configuration files and JSON errors](https://docs.oxidemod.com/guides/owners/configure-plugins) ## Related resources - [Get help](https://rustsc.com/support/guides/get-help/index.html.md) - [What to keep for Rust+ when restoring the same server](https://rustsc.com/learn/recovery/preserve-rust-plus-pairing-when-restoring/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/what-to-share-from-rust-backup/ --- # Why is your Rust panel backup download so small? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) A compressed backup can be much smaller than a live server folder. A download of the wrong backup can be small too. Open the archive on a separate drive or device and check for evidence of the right world before treating it as your recovery point. ## Match the downloaded file to the completed backup Compare the server name and creation time in the panel with the item you downloaded. If the panel shows the finished archive size, compare it to your file in the same units. A browser tab closing during download or an archive tool reporting an unexpected end means you need another download before you can use that file. Compare the archive with its listed contents, not the size of the whole game install. The install can include binaries, logs and other worlds. The archive is usually examined as a compressed file and as a list of its uncompressed contents. | What you find | What to do | | --- | --- | | The archive tool cannot list or extract files | Download the same completed backup again and try it in a fresh folder. | | It opens, but you see settings alone | Find the panel’s backup scope and check whether it includes the active save directory. | | It contains an expected save with earlier rotated saves | Check the active save name and the progress you expect for that date. | ## Name the file you would look for on recovery day Use what you know about the server. If Harbour runs a custom map and you expect its Monday evening save, find that save under the intended identity and check the file is nonempty. Note whether the map file, blueprint data and any plugin data you need are included or stored separately. A directory named backup gives you no answer about which world it holds. For an archive that opens and appears complete, extract it without replacing the running world. Keep the original download. A test restore that shows a known Monday structure gives you confidence the smaller file is the right copy. If the archive is missing the save, report the backup name, creation time and missing file to the host while the source files are still available. ## Sources - [Game panel documentation on backup storage](https://nodecraft.com/support/knowledgebase/nodepanel/server-backups) - [Facepunch guide to server files and saves](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [7-Zip documentation on archive compression](https://www.7-zip.org/7z.html) ## Related resources - [Which files belong in a Rust server backup?](https://rustsc.com/learn/recovery/what-a-rust-server-backup-needs-to-include/index.html.md) - [How to prove your Rust server backup can be restored](https://rustsc.com/learn/recovery/prove-a-local-backup-with-a-test-restore/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/rust-panel-backup-download-smaller-than-expected/ --- # Can a Rust backup restore fit into your wipe window? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) Measure one restore of the kind of copy you would use if wipe night goes wrong. Start the clock when you go to fetch the backup. Stop it when a tester can join the recovered world and verify a known piece of progress. ## Use the copy you would actually reach If your recovery route starts with the backup stored away from the host, use that location in the rehearsal. Restoring yesterday’s local file gives you a different time. Choose a copy with a similar world and plugin data size to the one you would expect to recover. Keep it separate from the live game. Prepare an isolated test location and the access you would need, including the backup password if there is one. Use a compatible build, private test admission and separate ports. Keep external plugin data and live notifications disconnected. ## Find which step uses the window Record start and finish times for retrieval, extraction or restore to the spare location, and Rust startup through a successful join. If your tool combines download and extraction, record that as one step. Include any time needed to verify the world is the intended one. | Example rehearsal | Elapsed | | --- | --- | | Get the backup from separate storage | 12 minutes | | Restore into the prepared spare location | 8 minutes | | Load Rust and join to check a known structure | 10 minutes | | Total while the spare location was ready | 30 minutes | ## Decide when the wipe work should stop If you promised to reopen at 21:00 UTC and you observed 30 minutes of restore work after preparing a target, waiting until 20:30 UTC leaves no time for preparation or variation. Use the rehearsal to set an earlier decision point or allow a longer outage. Avoid giving players a restoration promise from a single test. Repeat the slowest part if it depends on a busy network or a growing world. Keep the two readings and where the copy came from in your wipe notes so you can choose a recovery route on the night. ## Sources - [Restic restoring to a separate location](https://restic.readthedocs.io/en/stable/050_restore.html) - [Facepunch guide to server files and saves](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Recovery rehearsal guidance](https://docs.cloud.google.com/architecture/framework/reliability/perform-testing-for-recovery-from-failures) ## Related resources - [How to prove your Rust server backup can be restored](https://rustsc.com/learn/recovery/prove-a-local-backup-with-a-test-restore/index.html.md) - [How to rehearse a Rust wipe before wipe night](https://rustsc.com/learn/wipes/test-a-rust-wipe-plan-before-running-it/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/measure-rust-restore-time-before-wipe/ --- # Did your Rust backup restore go into the wrong world? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) If a second test world suddenly shows progress you meant to put somewhere else, stop changes to both affected worlds. Keep the original backup. Work out which location received the restored files and which location each running instance actually uses. ## Record the selected target and the actual paths Note the target shown in the restore result, its start time and which two worlds were set up. If players can still save to a suspect world, keep it closed using its normal stop process. With the worlds stopped, preserve a separate copy of the current folders before attempting repairs. Ask the host to preserve them if only the host can access those paths. Facepunch documents that two Rust instances can share the installed game and use different server identities. Read the actual startup settings and install location for each instance. Record the identity folder and the game address beside each. The label you see in the browser can differ from the folder name. ## Follow the time and one known piece of progress For example, the panel shows the archive was written under the test identity at 18:40 UTC, and the folder under the practice identity was last written at 17:10 UTC. The timestamps are clues. Check each folder’s save and compare the intended checkpoint details with the archival contents before deciding which was replaced. Verify in a further isolated target where you know the path, port and original source archive. Join that exact address and check a specific structure or blueprint from the dated backup. If two startup entries pointed to one folder, fix the test setup to use separate identities before diagnosing any other discrepancy. Leave the live world stopped until you can identify the correct recovery point and target without guessing. ## Sources - [Facepunch dedicated server guide](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch guide to server files and saves](https://wiki.facepunch.com/rust/Getting-Started_w-Server) ## Related resources - [Where does your Rust server keep its active world?](https://rustsc.com/learn/setup/find-the-active-rust-server-identity-folder/index.html.md) - [Why is my Rust world empty after changing the server identity?](https://rustsc.com/learn/recovery/rust-world-empty-after-server-identity-change/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/rust-restore-changed-the-wrong-world/ --- # A Rust backup is missing from the panel. Can you still use the file? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) If the panel no longer lists a backup you can see in your own folder, keep the file. The listing and the archive can have separate histories. Check what the file actually holds and find a recovery route that accepts it. ## Find out what you still have Copy the candidate archive to separate storage before you change the panel or move any original files. Compare its name, creation time if known, and the Rust identity folder inside. A backup you exported before changing hosts can still be useful after the old panel loses its entry. If the file is visible only on the host, ask whether you can download it while you still have access. Some panels store backups independently of the game files. A compressed archive left in a game folder could have been created manually, and its date alone cannot tell you whether it came from a complete copy. ## Use the matching recovery path Open the archive and look for the active save and a known part of the configuration from the intended day. Do the first extraction to an empty folder. If the panel accepts imports, ask what file formats it expects and whether it can restore to a spare instance. A panel’s built-in restore list may only work with the copies that panel created. If the panel cannot accept the file, retain the original and use the extracted copy in a compatible isolated restore. Example: Harbour’s archive listed in the old dashboard is gone, but the local export opens and a tester can join a private test copy and find Monday’s stone gate. Record that archive and the separate restore route before replacing anything on the shared world. ## Sources - [Example game panel documentation on backup downloads](https://nodecraft.com/support/knowledgebase/nodepanel/server-backups) - [Facepunch guide to server files and saves](https://wiki.facepunch.com/rust/Getting-Started_w-Server) ## Related resources - [Why is your Rust panel backup download so small?](https://rustsc.com/learn/recovery/rust-panel-backup-download-smaller-than-expected/index.html.md) - [How to prove your Rust server backup can be restored](https://rustsc.com/learn/recovery/prove-a-local-backup-with-a-test-restore/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/rust-backup-missing-from-panel-but-file-exists/ --- # What should you check after replacing your Rust server disk? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) Keep the restored server closed to players until you know which drive will receive its next save. A replacement with a different Windows drive letter or a missing Linux mount can leave a startup entry looking in the wrong place. ## Match the launch path to the replacement disk Keep existing copies intact. With Rust stopped, note its install path, identity folder and the backup destination from the startup and backup settings. On Windows compare the drive letter or folder mount with Disk Management. On Linux use findmnt --target with the directory path to see which mounted filesystem contains it. If a directory expected to be on the new disk resolves to the main system disk, arrange the intended mount before copying into it or starting Rust. Restore from a separate readable copy to the confirmed location, using files and a Rust build suited to each other. If you installed the game fresh, compare its actual startup path with the path you restored. Verify that the account running Rust can read and write there. ## Prove one write and one fresh copy Start with private admission and pause unrelated automation while you check the restore. Join the intended world and find a known piece of progress. Observe a game save and check that the save file in the replacement location was updated and that the console recorded success. Also verify that any backup destination was mounted and reachable before running a new backup. If a backup path points back to the replaced disk, select the separate storage you intended and open the first new copy there. Release access once the world and its new save and backup are in the right places. ## Sources - [Facepunch dedicated server guide](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch guide to server files and saves](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Microsoft documentation on drive letters](https://learn.microsoft.com/en-us/windows-server/storage/disk-management/change-a-drive-letter) - [Linux findmnt manual](https://man7.org/linux/man-pages/man8/findmnt.8.html) ## Related resources - [Where does your Rust server keep its active world?](https://rustsc.com/learn/setup/find-the-active-rust-server-identity-folder/index.html.md) - [Why does Rust say the save folder is read-only?](https://rustsc.com/learn/troubleshooting/rust-save-fails-on-a-read-only-filesystem/index.html.md) - [How to prove your Rust server backup can be restored](https://rustsc.com/learn/recovery/prove-a-local-backup-with-a-test-restore/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/restore-rust-after-a-disk-replacement/ --- # What if a Rust restore leaves plugin balances from a later day? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) If a world goes back to Monday while a shop still shows Wednesday’s balance, find where that plugin stores its records. Compare the game copy with the separate data before reconnecting the plugin to players. ## Write down which records survived from each time Check your plugin settings and the author's instructions. Oxide plugins can use local files or a database reached separately. For example, Monday’s world restores the shop building, but the plugin reads balances from a shared MySQL database that never rolled back. Note what modern records would be lost if you restored that entire database to Monday. Keep the current game backup and a separate backup of the current plugin records. Use the database’s own backup and restore method or ask its operator to make the copy. If more than one world uses those records, identify the other worlds before deciding to change any shared data. ## Check a pair of recovery points away from players Restore the game to an isolated test location and use a separate copy of the plugin data with its own access, or keep the plugin disabled until that copy is ready. Confirm the test configuration does not connect to live services or send live notifications. For an example Monday recovery, use known test accounts to compare Monday’s saved world with balances from the proposed data copy. | What you see | Review before opening | | --- | --- | | Known balance and shop both match Monday | Confirm what newer progress the chosen recovery would replace. | | World is Monday, balances are newer | Ask the plugin author about combining or retaining those records safely. | | Data is shared across several worlds | Get a separate export or supported restore scope before replacing shared records. | ## Decide what you can explain to players Keep the shop feature closed if you cannot reconcile its state. Reopen the whole game only if it behaves as intended without that feature, and explain the missing part in your update. When you do restore the plugin data, verify one expected balance and one normal test transaction on the recovery copy before using it on the shared world. ## Sources - [Oxide documentation on database connections](https://docs.oxidemod.com/guides/developers/database) - [MySQL backup and recovery reference](https://dev.mysql.com/doc/refman/8.4/en/backup-and-recovery.html) - [Facepunch guide to server files and saves](https://wiki.facepunch.com/rust/Getting-Started_w-Server) ## Related resources - [Move Rust plugin settings and player data to another server](https://rustsc.com/learn/recovery/move-plugin-settings-and-player-data/index.html.md) - [What to save before rolling back a Rust server](https://rustsc.com/learn/recovery/save-current-rust-world-before-rollback/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/rust-world-restore-with-external-plugin-data/ --- # How to recover a Rust world after its custom map link stops working [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) If the old map link is gone, recover the exact .map file that belongs with the save. Publish it at a new direct download address that a first-time player can reach, and verify those two files together before changing the live server. ## Get the exact map from storage you control Look for the map beside the dated game backup or in the original map files. Compare its revision with the saved world's notes. If you cannot identify the original map, ask the author or the person who prepared that wipe for the exact file. A differently revised map with a similar filename is a new candidate, not a confirmed replacement. Put the recovered file in a web location permitted by the map's sharing terms. Keep the matching filename from the working map and verify that the new URL downloads the map itself from another network. A link that opens a preview page or needs the owner’s browser session will fail for someone without that session. ## Test an unchanged save against the replacement download On an isolated compatible copy of the world, use the new address as server.levelurl. Copy the matching save into the test identity without placing the old map in the test cache. Keep the primary save and archive intact. Separate the test ports and storage and disconnect live plugin services and scheduled work. Start the test game and use its startup output to confirm Rust fetched the replacement URL. Join from a Rust client without that map cached. Check the client console shows the new download URL. Then confirm the intended terrain and a named structure from the saved world. If Rust loads a blank world or mismatched terrain, keep the main server unchanged and check the pairing and game build before proceeding. Once the new link and old world pass, record the replacement address beside the original archive. Use the normal maintenance window to apply it to the intended server and verify a fresh join there too. ## Sources - [Facepunch guide to hosting a custom map](https://wiki.facepunch.com/rust/Hosting_a_custom_map) - [Facepunch custom map troubleshooting](https://wiki.facepunch.com/rust/FAQ_and_Troubleshooting) - [Facepunch guide to server files and saves](https://wiki.facepunch.com/rust/Getting-Started_w-Server) ## Related resources - [Which custom map file should you keep with a Rust backup?](https://rustsc.com/learn/recovery/archive-custom-rust-map-for-recovery/index.html.md) - [Why won't my Rust custom map URL load?](https://rustsc.com/learn/configuration/custom-map-url-wont-load/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/recover-rust-when-the-custom-map-url-is-gone/ --- # Did your Rust backup finish copying over a slow connection? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) Keep the source archive while the transfer finishes. Confirm the copy matches the finished source. Then open or extract it separately and check a file you need for recovery. ## Match the bytes before you start over Wait for the transfer tool to say it finished. Check the exact byte count of the source and destination if both are accessible. If they differ, check whether the tool can resume the same transfer. Keep an incomplete download under a name or in a folder that nobody will mistake for a finished backup. Equal sizes do not prove the files match. If you can compute a SHA-256 value on each side, compare the complete value for the finished archives using the same algorithm. PowerShell's Get-FileHash can compute that value. If the host only offers a downloadable file, ask whether it provides a trusted value for that exact archive. If you cannot verify against the original, keep that uncertainty and do the extraction check. ## Open the copy away from the live game Use the archive tool’s integrity check if available, or extract to an empty location with room for the contents. Find the save for the world and one other item you expect, such as the matching custom map or plugin configuration. A successful file comparison tells you the transfer preserved the archive. A test restore shows whether the archive can bring the game back. If the copy fails verification, leave any previous good copy alone and try a fresh transfer. Write the source date, copy location and last successful check in your recovery notes. ## Sources - [PowerShell file contents verification](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/get-filehash) - [7-Zip archive integrity test](https://7-zip.opensource.jp/chm/cmdline/commands/test.htm) - [Facepunch guide to server files and saves](https://wiki.facepunch.com/rust/Getting-Started_w-Server) ## Related resources - [How to prove your Rust server backup can be restored](https://rustsc.com/learn/recovery/prove-a-local-backup-with-a-test-restore/index.html.md) - [Why is your Rust panel backup download so small?](https://rustsc.com/learn/recovery/rust-panel-backup-download-smaller-than-expected/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/verify-a-rust-archive-copy-on-a-slow-link/ --- # Prove a Rust backup belongs to the right world [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) A healthy archive can belong to the wrong world. Match its origin and date before restoring, then check something only the intended world should contain. Start with a spare destination and keep live files untouched during this check. ## Use three independent clues For example, Alder runs Weekly and Monthly with a similar seed. Two backup names might both say ‘Thursday’. Record the clues from your own inventory. | Clue | What to compare | | --- | --- | | Origin | The named source server, its host and its Rust server identity. The displayed name alone can be reused. | | World details | The backup date and time, expected map or seed and size, and the wipe that was active then. | | Recognizable player state | A location, construction or other agreed marker that existed at the requested time and belongs to this world. | ## Open the strongest candidate in isolation Use your backup tool's read or preview if available. Export or restore to a new destination using the supported procedure. Give the test server its own endpoints and restrict it to testers. Keep live Discord, shared plugin stores and Rust+ out of the test. Start it only after you have checked those boundaries. Join with a trusted tester. Confirm the expected map and marker, such as a staff-built sign that only appeared in Monthly before the last wipe. If the map matches but the marker does not, check another clue from that date or try the next candidate. Similar seeds can regenerate a similar map without your actual progress. ## Record which copy earned approval Write the source, capture time, marker and what progress the selected backup would omit. A private Debian rehearsal backed up several different seeds and correctly refused an in-place restore for the wrong seed. That check distinguishes different maps. Your marker and records help identify worlds that intentionally share a seed. Keep live recovery on hold if the origin or game state is still uncertain. ## Sources - [Facepunch dedicated server identity and map settings](https://wiki.facepunch.com/rust/Creating-a-server) - [Google SRE on checking a hypothesis against observed evidence](https://sre.google/sre-book/effective-troubleshooting/) ## Related resources - [How to prove your Rust server backup can be restored](https://rustsc.com/learn/recovery/prove-a-local-backup-with-a-test-restore/index.html.md) - [Which Rust server backup should you restore after an incident?](https://rustsc.com/learn/recovery/choose-rust-backup-before-an-incident/index.html.md) - [Restore a backup](https://rustsc.com/support/guides/restore-backup/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/prove-a-backup-belongs-to-the-right-rust-world/ --- # Move one Rust world while its neighbour stays open [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) A move is easier to verify when the two worlds have independent addresses and staff can name which one is closed. Rehearse the move with a spare copy first. On the real day, only one version of the moved world should accept players. ## Record both paths before the handoff In this example, Willow Weekly moves to a new host while Willow Monthly stays on the old one. Write the old and new Weekly addresses, the unchanged Monthly address, the two save identities and which work belongs to each host. Keep Weekly's scheduling and announcement changes separate from any jobs still needed for Monthly. Before the scheduled move, prove a supported test restore of Weekly on the destination. Keep that rehearsal off live links. Check the expected game, framework, map and a known world marker. Tell staff what passing looks like and who has authority to reopen. ## Give every step a check Keep the old Weekly instance and its final save available until the destination passes. | When | Weekly | Monthly | | --- | --- | --- | | Close the moving world | Send the notice, stop accepting joins, save and stop Weekly cleanly, then take its final checkpoint. | A helper verifies a player can still join Monthly. | | Bring up the destination privately | Use the proven recovery steps and check the selected checkpoint, current version, world and permissions before public joins. | Keep the usual address and verify no new Weekly job targets Monthly. | | Open Weekly on the new host | Have an outside player verify the new address or DNS record and the expected world. Publish the updated Weekly link and leave the old Weekly closed. | Repeat the Monthly join check and leave its links and jobs active. | ## Set a point to fall back If Weekly fails before players are admitted on the destination, leave the destination closed and reopen the old Weekly using the known final state after checking which jobs and addresses would have to return. If players have already made progress on the destination, close public joins there and decide how to handle that progress before moving back. In a disposable Linux rebuild, a prepared replacement started from the selected world backup after the required framework had been installed. That run exercised one game at a time and did not test public DNS or a neighbouring live world. Verify those two join paths yourself before announcing the move is complete. ## Sources - [Facepunch server identity and settings](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch Rust DNS records](https://wiki.facepunch.com/rust/dns-records) - [Google SRE on assigning incident work](https://sre.google/sre-book/managing-incidents/) ## Related resources - [How to move a Rust server hostname to a new host](https://rustsc.com/learn/hosting/move-your-rust-server-hostname/index.html.md) - [Prove a Rust backup belongs to the right world](https://rustsc.com/learn/recovery/prove-a-backup-belongs-to-the-right-rust-world/index.html.md) - [Move a server to a new host](https://rustsc.com/support/guides/move-to-new-host/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/move-one-rust-world-while-the-other-stays-open/ --- # How to prove your Rust server backup can be restored [Rust server guides](https://rustsc.com/learn/index.html.md) / [Backups and recovery](https://rustsc.com/learn/recovery/index.html.md) Restore your backup to a separate Rust server and join that copy. Seeing a familiar base or learned blueprint in the restored world shows what you could get back if the live server were lost. ## Choose what the backup should bring back Pick a backup and note what existed when it was made. For example, choose one taken after a known base was built but before it was expanded. Write down the landmark next to it and what the base looked like then. Add a learned blueprint or plugin setting if you expect the backup to recover it too. Keep the original backup intact. Restore a copy into a separate server install with compatible game and framework versions and its own ports. Keep those ports reachable only from your test PC or private test network. Leave live integrations and schedules disabled so the copy can't act on the live community. ## Join the restored world and look for the evidence Connect directly to the test server. In the base example, success is seeing the base at the remembered landmark in its earlier form. Check any other data you listed, using the original player's account for their learned blueprints. If you find a fresh world instead, stop the test copy and compare its active server identity and map settings with the backed-up save. A different identity can point the server at another folder. Fix the test copy and try again before counting that backup as usable. ## Sources - [Facepunch reference for Rust server save files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Facepunch guide to local Rust connections](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Back up a server](https://rustsc.com/support/guides/back-up-server/index.html.md) - [Restore a backup](https://rustsc.com/support/guides/restore-backup/index.html.md) --- HTML version: https://rustsc.com/learn/recovery/prove-a-local-backup-with-a-test-restore/ --- # How to keep Windows Update from interrupting your busiest Rust hours [Rust server guides](https://rustsc.com/learn/index.html.md) / [Updates](https://rustsc.com/learn/updates/index.html.md) Set Windows active hours around when players use the server. When an update asks for a restart, pick a time you can save the world and verify the game starts again. ## Use player hours on a dedicated game machine In Windows 11, open Windows Update settings, then Advanced options and Active hours. Set them manually if the host's own activity is a poor guide to when people play. For example, if people play every evening and you rarely use the desktop yourself, set active hours around the evening sessions. Check Windows Update before the next session. When it shows a restart is needed, use a quiet window to save and stop the Rust server, then choose the update restart. Active hours help you avoid inconvenient timing while keeping updates enabled. ## Confirm Windows and Rust both returned After the reboot, check Windows Update and the server console. If you set the game to start automatically, confirm it started without your desktop account signing in. Then join the expected world and check progress from before the restart. Use that routine the next time Windows shows a pending restart. ## Sources - [Microsoft guide to Windows Update active hours](https://support.microsoft.com/en-us/windows/deployment/updates-lifecycle/keep-your-pc-up-to-date-with-active-hours) - [Facepunch console command reference](https://wiki.facepunch.com/rust/useful_commands) - [Microsoft guide to starting a task at boot](https://learn.microsoft.com/en-us/windows/win32/taskschd/starting-an-executable-on-system-boot) ## Related resources - [Start, stop or restart a server](https://rustsc.com/support/guides/start-stop-restart/index.html.md) - [Host offline](https://rustsc.com/support/guides/computer-offline/index.html.md) --- HTML version: https://rustsc.com/learn/updates/windows-update-restarts-on-a-rust-host/ --- # How to put Oxide back after a Rust update [Rust server guides](https://rustsc.com/learn/index.html.md) / [Updates](https://rustsc.com/learn/updates/index.html.md) If all your plugins disappear together after the game updates, first check whether the server is still running Oxide. In the server console, run oxide.version. If it returns a version, investigate the plugins that failed before replacing the framework. ## Pick the release for the host and the game update Read the Oxide.Rust release notes against the Rust update or hotfix you installed. A release for the monthly update can precede a separate hotfix. If the matching build is still pending, keep the planned downtime or run vanilla only if you have checked what the missing plugins would mean for your players. Use the Windows ZIP for a Windows host or the Linux ZIP for a Linux host. In a rental panel with an Oxide installer, use the host's matching install option. ## Keep the existing installation and world Stop the server and save a copy of the Oxide folder and your server data. Extract the framework archive separately, then copy its contents into the existing game root, keeping the archive's folder structure. If you see a new nested server directory alongside RustDedicated, check where you extracted it before starting up. Start with the usual launch settings. Check oxide.version again, then repeat one real player action from an essential plugin. That catches the case where the framework is back and one plugin still needs its own update. ## Sources - [Oxide installation guide](https://docs.oxidemod.com/guides/owners/install-oxide) - [Oxide.Rust release notes](https://github.com/OxideMod/Oxide.Rust/releases) ## Related resources - [Change Oxide or Carbon](https://rustsc.com/support/guides/change-framework/index.html.md) --- HTML version: https://rustsc.com/learn/updates/install-oxide-after-rust-update/ --- # Should you run Oxide or Carbon on your Rust server? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Updates](https://rustsc.com/learn/updates/index.html.md) Base the choice on the features players depend on and the update process you can maintain. For an existing server, a working plugin or extension that the author supports on only one framework may settle the choice. ## If you are starting from scratch For a new server on a rental, check what the host can install and maintain. If the host offers Oxide and your entire list is supported there, you already have a workable choice. If you need a Carbon-only module, check that the host offers Carbon and every other required component works with it. ## If you already run a modded server List the features you need to keep, such as moderation and raid rules. Beside each one write down the plugin and extensions and check the author's support for each framework. For example, if a required raid rule depends on a DLL its author supports only on your current framework, keep that setup until you've found and tested a replacement. ## When both frameworks fit Choose the update routine your team can maintain. Oxide publishes Rust-specific releases with game update notes. Carbon documents when its own updater changes the framework build. In either case decide who checks the framework version and tests your essential feature before players come back. ## Sources - [Oxide Rust releases](https://github.com/OxideMod/Oxide.Rust/releases) - [Carbon game branches and compatibility goal](https://carbonmod.gg/owners/getting-started) - [Carbon auto-updates](https://carbonmod.gg/owners/auto-updates) ## Related resources - [Change Oxide or Carbon](https://rustsc.com/support/guides/change-framework/index.html.md) --- HTML version: https://rustsc.com/learn/updates/choose-oxide-or-carbon/ --- # Rehearse an Oxide-to-Carbon migration before switching live [Rust server guides](https://rustsc.com/learn/index.html.md) / [Updates](https://rustsc.com/learn/updates/index.html.md) Make the first Carbon boot on a copy you can discard. Carbon documents a one-time migration, so use a fresh copy of the original if you need to repeat that first-boot test. ## Write down what the new server must preserve Record one consequential example of each kind of state. A rewards balance for a test player proves more about plugin data than a list of files. One staff action and the same action denied to a regular player give you a check on permissions. Copy the stopped installation, including its world, framework files, plugin settings and state. Give the rehearsal its own ports and storage. Point plugins at test databases and disable live notifications and automated jobs before the first boot. Follow Carbon’s prerequisites on the copy. Turn off any tool that reinstalls Oxide and restore the Rust files Oxide patched. Keep the old oxide folder on the copy for Carbon to import, and keep an untouched backup of the whole pre-switch setup. ## Check the migrated paths and the scheduled jobs After the test boot, check that old Oxide config files reached Carbon's configs folder and that the plugin, data, language and permissions material is present. Inspect the extension list if any plugin needs a DLL. Then run the player and staff checks from your notes. Open the jobs you already run from outside the game. A job that calls an Oxide-prefixed command needs a Carbon equivalent or an intentionally configured alias. Test a harmless read first. Schedule the live move only after the rehearsal gives you the same answers where it counts. ## Sources - [Carbon guide to porting from Oxide](https://carbonmod.gg/owners/oxide-porting) - [Carbon console command reference](https://carbonmod.gg/references/commands/) ## Related resources - [Change Oxide or Carbon](https://rustsc.com/support/guides/change-framework/index.html.md) --- HTML version: https://rustsc.com/learn/updates/rehearse-oxide-to-carbon-migration/ --- # Does your Oxide plugin work on Carbon? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Updates](https://rustsc.com/learn/updates/index.html.md) Confirm the exact thing your players or helpers need from the plugin. Carbon's documentation explains how it supports Oxide plugins and where porting differs. A plugin's loaded status is the beginning of a compatibility check. ## Build an equivalent pair of test worlds Record the Rust build, framework version, plugin version, requirements and settings that you intend to take across. Use separate private test copies with the same test accounts and representative data created for the test. Keep live integrations off. Try the feature once on Oxide so you know what a passing result looks like. ## Keep one result for each point of failure The example uses a staff ability that makes its user invisible. Vanish documents the relevant permission and chat toggle. Use consenting test accounts on the private copy. | What to check | What a pass looks like | | --- | --- | | Startup and dependency | The expected plugin version and each required plugin show as loaded; relevant startup logs show no failed initialization. | | Player-visible feature | With the documented grant, a tester toggles invisibility. A second tester confirms disappearance and reappearance. | | Permission boundary | A regular account without the grant cannot use the ability. An ordinary action, such as moving or joining, still works normally. | | Restart | After a clean restart both the allowed and refused cases still match. For a data-bearing plugin, the test record and customized setting are still present. | ## Keep the blocking row visible If the plugin loads but a feature differs, record that row as failed. Compare one dependency, permission or setting at a time. Keep the current framework for your live world if the affected plugin is essential and you lack a compatible alternative. In one disposable Linux migration, a test plugin carried across a greeting, a language string, a saved counter and a permission. The recorded move exercised that specific test plugin. It did not exercise Vanish with connected players, which is the check to perform if your staff relies on it. ## Sources - [Carbon Oxide porting guidance](https://carbonmod.gg/owners/oxide-porting) - [Oxide dependency requirements](https://docs.oxidemod.com/guides/reviewers/guidelines/dependencies) - [Vanish commands and permissions](https://umod.org/plugins/vanish) ## Related resources - [Change Oxide or Carbon](https://rustsc.com/support/guides/change-framework/index.html.md) - [Rehearse an Oxide-to-Carbon migration before switching live](https://rustsc.com/learn/updates/rehearse-oxide-to-carbon-migration/index.html.md) - [Why did your Rust plugin compile but fail to load?](https://rustsc.com/learn/troubleshooting/rust-plugin-compiles-but-does-not-load/index.html.md) --- HTML version: https://rustsc.com/learn/updates/test-oxide-plugin-compatibility-on-carbon/ --- # Remove a Rust plugin and keep a way to bring it back [Rust server guides](https://rustsc.com/learn/index.html.md) / [Updates](https://rustsc.com/learn/updates/index.html.md) Begin by checking what still uses the plugin. Retire the feature and its live code first. Deal with its old settings and player data after you have verified that the rest of the server works. ## Find incoming dependencies before you unload it Check the author’s listing and review the features you use on the server. For example, Image Library is used by Rust Kits and other plugins. Removing one user of the library is different from removing the library while another menu still depends on it. Plan a stop if the plugin or an accompanying extension needs one. Otherwise unload the plugin with the framework's documented command and put its source outside the plugin folder. An unloaded file left in that folder can load again later. ## Archive by ownership Keep a copy of its exact source file and any settings, player state and translations you may want again. Leave shared files alone. Note the names of plugin-specific grants if you intend to remove them from groups, and review each grant before changing it. A shared group may still serve another plugin. After the next startup, check that the old plugin is absent and try one feature that used to share a dependency with it. Keep the archive until you are comfortable restoring that setup from scratch. ## Sources - [Oxide unload command](https://docs.oxidemod.com/guides/owners/commands) - [Oxide data file ownership and purpose](https://docs.oxidemod.com/guides/owners/data-files) - [Image Library and its consumers](https://umod.org/plugins/image-library) ## Related resources - [Find and manage plugins](https://rustsc.com/support/guides/plugins/index.html.md) --- HTML version: https://rustsc.com/learn/updates/remove-rust-plugin-without-losing-data/ --- # Track Rust plugin versions across marketplaces [Rust server guides](https://rustsc.com/learn/index.html.md) / [Updates](https://rustsc.com/learn/updates/index.html.md) Keep one entry per plugin you run. The fields that matter on update day are where it came from, which version actually loaded and what you have to test if you change it. ## A register entry you can copy For example: WelcomeNotice.cs, version 1.2.0 loaded on Oxide, edited by us, original release linked, working copy in the server backup. Check that a returning player sees the new welcome line. This entry records what runs and one quick test, even if the upstream listing has moved on. Add a field for required downloads if the plugin has any. On GitHub, link to the specific release when possible. On a marketplace, keep the listing and read the author's release notes before downloading. ## On update day Keep a candidate release in the notes while you test it. Once you see it load in the console and your test passes, record the new version and date. If you keep a local patch, record whether you carried it forward. Two files with the same version can still behave differently. ## Sources - [Oxide plugin version in the load result](https://docs.oxidemod.com/guides/owners/install-plugins) - [GitHub releases tied to a tag](https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases) - [Example publisher release history](https://umod.org/plugins/custom-vending-setup/updates) ## Related resources - [Find and manage plugins](https://rustsc.com/support/guides/plugins/index.html.md) --- HTML version: https://rustsc.com/learn/updates/rust-plugin-version-register/ --- # Roll back a plugin update that changed its data files [Rust server guides](https://rustsc.com/learn/index.html.md) / [Updates](https://rustsc.com/learn/updates/index.html.md) A plugin rollback needs compatible code, settings and data. Keep a matched copy from before the update and prove the old plugin can read it. If players have earned progress since that copy, decide what the recovery would cost before using it. ## Look for a conversion before the update Read the author's release notes for changes to stored settings or data. Server Rewards describes an older version change that attempted to convert past data and asks owners to keep a backup. For the version you are considering, identify where the installed plugin stores its state, including any external store it names. Make the rehearsal on a private copy with synthetic data. Record a known value such as a test player's balance. Stop the test server cleanly and save the old plugin, settings, data and required dependencies together. Keep that set outside the active game folder and separate from the copy you will update. ## Prove both directions on the private copy Use separate copies for the post-update investigation and the attempt to go back. 1. Start one copy with the new version. Confirm it finishes loading and compare the recorded test value. Create one new test change to see what would exist only after updating. 2. Return a fresh copy to the old plugin with the old settings, data and required dependency versions. If an external store is involved, use a disposable instance and follow the maintainer's recovery instructions. 3. Start the old copy and check the reported version, the known pre-update value and the normal player action. Record whether the later test change is absent. If the old code cannot read the old copy, stop the rehearsal and ask the maintainer for a supported recovery method. ## Choose an outcome before reopening Take and label the live checkpoint before a scheduled update. Keep player activity paused until you check that conversion succeeded. If a live change has already failed, keep the failed copy and console evidence available for recovery. | What changed since the checkpoint | Decision | | --- | --- | | The server stayed closed while the new version was checked | Use your tested, supported recovery path if the upgraded plugin cannot pass the checks. | | Players earned balances, made purchases or claimed rewards | Record what the old copy would lose. Keep access paused while you decide whether to repair the newer data or accept and explain the agreed loss. | | You cannot verify the storage or a dependent version | Ask the maintainer before any live restore. Keep both copies available. | ## Sources - [Server Rewards migration and backup instructions](https://umod.org/plugins/server-rewards) - [Oxide data files and configuration](https://docs.oxidemod.com/guides/developers/data-storage) - [Oxide plugin loading and reloads](https://docs.oxidemod.com/guides/owners/install-plugins) ## Related resources - [Restore a backup](https://rustsc.com/support/guides/restore-backup/index.html.md) - [What to save before rolling back a Rust server](https://rustsc.com/learn/recovery/save-current-rust-world-before-rollback/index.html.md) - [Which Rust plugin updates belong on force-wipe day?](https://rustsc.com/learn/updates/should-you-update-a-rust-plugin-on-force-wipe-day/index.html.md) --- HTML version: https://rustsc.com/learn/updates/rollback-plugin-update-with-data-conversion/ --- # SteamCMD succeeded. Why is Rust still on the old build? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Updates](https://rustsc.com/learn/updates/index.html.md) Compare the folder SteamCMD updated with the executable path your server launches. A successful download to a spare copy leaves the running installation untouched. ## Write down the update target Read `force_install_dir` in the update script. If it is a relative path, locate it from the working directory SteamCMD uses. ## Write down the executable path Find the path in the active startup script, service or host panel. Resolve relative paths from that launcher’s working directory. In a setup with a staging folder and a live folder, a success message for staging tells you nothing about the live executable. ## Correct the target without switching worlds When the right game instance is stopped, update its actual install folder. Keep the original server identity and startup settings. Launch again, confirm which executable started and check the build or startup output. A successful join should take you back to the existing world. ## Sources - [Facepunch Rust dedicated server setup](https://wiki.facepunch.com/rust/Creating-a-server) - [systemd service reference](https://www.freedesktop.org/software/systemd/man/latest/systemd.service.html) ## Related resources - [Update Rust](https://rustsc.com/support/guides/update-rust/index.html.md) --- HTML version: https://rustsc.com/learn/updates/steamcmd-updated-a-different-rust-folder/ --- # Check the Rust branches when a new build will not connect [Rust server guides](https://rustsc.com/learn/index.html.md) / [Updates](https://rustsc.com/learn/updates/index.html.md) A successful update can put the client and server on different releases. Check which Steam branch each installation uses before changing ports, reinstalling or touching the world. ## Read the selected release on both sides The game you launched and its selected branch can both matter. Facepunch distributes the Staging client as a separate Steam library entry called Rust - Staging Branch. Steam can also offer branch choices in Properties for a library entry. 1. In the Steam library, confirm whether you launched Rust or Rust - Staging Branch. If you changed the branch for that entry, check its Properties as well. 2. On the host, read which branch the SteamCMD script or rental panel requests for the dedicated server. 3. Compare the two selections before redownloading either installation. ## Make the intended installation match For a public server on the normal release, launch the regular Rust library entry on its public branch and let Steam finish any update first. If the server intentionally runs Staging, launch Rust - Staging Branch and try the join there. Verify a fresh join to the expected world before changing the server. ## Sources - [Facepunch Rust dedicated server setup](https://wiki.facepunch.com/rust/Creating-a-server) - [Steamworks branch documentation](https://partner.steamgames.com/doc/store/application/branches) - [Facepunch instructions for launching the separate Staging client](https://rust.facepunch.com/staging) ## Related resources - [Update Rust](https://rustsc.com/support/guides/update-rust/index.html.md) --- HTML version: https://rustsc.com/learn/updates/rust-client-and-server-on-different-branches/ --- # When should you validate Rust server files? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Updates](https://rustsc.com/learn/updates/index.html.md) Validate when SteamCMD reports file problems or the game cannot load a stock file. For a normal update, first check that SteamCMD finished in the right install folder. ## Save the files that matter before validation Stop the game and copy the active world, configuration and any intentionally changed install files to independent storage. Validation checks the installed distribution. It can replace files that differ from Steam’s copy, so note what you need to put back after testing. ## Test the failure that triggered the check Run your SteamCMD update for the correct dedicated server folder with `validate`, following Facepunch’s install example. Read the result, then try one startup of the original server identity. If the same missing-file or startup error returns, keep the new output. That gives you a concrete next thing to investigate instead of repeating validation. ## Sources - [Facepunch Rust dedicated server setup](https://wiki.facepunch.com/rust/Creating-a-server) - [Steam Support on verifying local game files](https://help.steampowered.com/en/faqs/view/21F5-8D5D-0141-7A5E) ## Related resources - [Update Rust](https://rustsc.com/support/guides/update-rust/index.html.md) --- HTML version: https://rustsc.com/learn/updates/when-to-validate-rust-server-files/ --- # How to prepare your Rust server for a seasonal event [Rust server guides](https://rustsc.com/learn/index.html.md) / [Updates](https://rustsc.com/learn/updates/index.html.md) Find the seasonal change in the current Rust release and decide whether your server should use the default event settings or a supported adjustment. ## Start with the event actually announced this year Check the release date and end date if Facepunch gives one. For example, the 2026 Halloween announcement documented halloweendungeon.population as the portal count control. Use the settings named for the release you are running and record the old value before changing it. If you want to adjust an event for your map, try one change on a copy. Decide what you expect a player to see, such as portals appearing during the event. ## Plan the return to normal settings Decide when your changes will end before putting them on the live server. Write down the event end, your own switch-back date if different, and the setting's original value. If someone else is covering maintenance that day, give them the same short list. ## Try a dated change card for a costume fair Suppose Lantern Shore holds a town fair. The operator considers adjusting the portal count in the seasonal world during the event. A separate helper walks the route visitors will actually use. Copy this card for your event and record values from your own test world. | On the card | Lantern Shore example | | --- | --- | | Before the change | Record the current game build and effective portal count setting. Walk from the spawn road to the fair entrance. | | During the fair | Verify the effective temporary value. Observe how portals appear on the test world and check that the arrival route remains usable. | | At the announced end | Restore the recorded setting and have the assigned helper check the route again. Say whether the fair is closed even if the official event is still active. | | After the next startup | Check the effective value again. A startup override can bring back a change you cleared from the running server. | ## After the event Remove the seasonal change from the same place you applied it. If you set it in the startup configuration, remove or restore it there too so the next reboot does not bring it back. Keep any unrelated world settings as they were. ## Confirm the return before posting it Restoring your original setting restores that choice. It does not necessarily remove all event content while Facepunch's event is still active, or erase items players already collected. Use the current release notes to set the right expectation. If the check after startup still shows the temporary value, leave the fair closed and find where the override is applied. Announce normal play when the recorded setting and the player-facing checks agree. Keep the card for your next seasonal event. ## Sources - [Facepunch Halloween event release notes](https://rust.facepunch.com/news/halloween-2026/) - [Official Rust release notes](https://rust.facepunch.com/news/) - [Facepunch guide to creating a server](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Change server settings](https://rustsc.com/support/guides/server-settings/index.html.md) - [Update Rust](https://rustsc.com/support/guides/update-rust/index.html.md) --- HTML version: https://rustsc.com/learn/updates/prepare-rust-seasonal-world-settings/ --- # How to test an existing custom map after a Rust update [Rust server guides](https://rustsc.com/learn/index.html.md) / [Updates](https://rustsc.com/learn/updates/index.html.md) Try the map on the updated server in a test instance. Check places that matter to your players even if the map loads without stopping the game. ## Record a route that worked before the update Pick one important route, such as reaching the loot room through a door and ladder. Record the game build, map filename and version, and what the player had to do. If the game is already updated, use a screenshot or a player's earlier account to establish what they expect without assuming you can still boot the previous build. Read the official release notes for changes relevant to that route. Facepunch documents that a custom map can refer to a game asset that no longer exists. If your map author has already sent a revision, keep both files and give the new one a distinct filename and direct download URL. ## Change one part of the test at a time Use a separate empty test instance. Check the current map with the updated server and client before changing the framework or testing a new map file, if the old setup is compatible. Keep production integrations disconnected. If a route depends on a plugin, verify the matching framework build separately before enabling the plugin on the test. | What happens on the current build | What to try next | | --- | --- | | The old map loads but the ladder is gone | Read the missing asset errors and check the same route on the map author’s revision. | | The route works until the route-control plugin is active | Compare the plugin and framework versions and their startup errors. | | The new map worked for staff, a first-time client cannot join | Check the direct map download from that client’s network. | ## Tell the map author exactly what failed Join from a client that has never cached the revised filename. Follow the route all the way to its intended reward or exit. Record the location and first relevant error if it fails. Keep the existing live map and save intact while you choose a corrected candidate. If the new map works only with a clean world, check separately what players would lose before you put it live. ## Sources - [Facepunch custom map troubleshooting](https://wiki.facepunch.com/rust/FAQ_and_Troubleshooting) - [Official Rust release notes](https://rust.facepunch.com/news/) ## Related resources - [Preview your map](https://rustsc.com/support/guides/preview-map/index.html.md) - [Update Rust](https://rustsc.com/support/guides/update-rust/index.html.md) --- HTML version: https://rustsc.com/learn/updates/check-a-custom-map-after-rust-updates/ --- # Which Rust plugin updates belong on force-wipe day? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Updates](https://rustsc.com/learn/updates/index.html.md) Prepare the game and its compatible framework first. Then decide which plugin changes the world needs in order to reopen. Keep unrelated enhancements for another window so a new gameplay problem has fewer possible causes. ## Give each change a reason to be in the window Take the version you have running and the version you would install. Read the release notes and the dependency list for each. Decide before wipe day what you can hold. | What changed | Decision | | --- | --- | | A fix for a required plugin that fails on the new build | Rehearse the supported release with the new game and framework. Check the essential player action and its dependents. | | Optional feature added to a plugin that still works on the new build | Keep the version that passed your checks. Test the optional feature in another window. | | A plugin needs a dependency whose compatible build is unavailable | Hold the dependant change. If it owns a protection you promised players, keep the world closed until that protection passes. | | An update will convert stored progress | Give it a separate recovery decision. Save the matched files before conversion and rehearse the return on a spare world. | ## Test the break that matters For example, a PvE world needs its advertised building protection before it can reopen. On the test copy, have two ordinary accounts repeat the existing protection check on the new build. Record the running framework and plugin versions and the observed result. Treat untested protection as unavailable when deciding whether to reopen. Do not assume a plugin rollback makes the previous Rust build compatible with current clients. The first recovery choice may be to keep the updated world closed while a compatible plugin is prepared. Put the opening decision and its reason in the staff handoff. ## Sources - [Facepunch on game updates and Oxide](https://wiki.facepunch.com/rust/Creating-a-server) - [Oxide dependency requirements](https://docs.oxidemod.com/guides/reviewers/guidelines/dependencies) - [Google SRE Workbook on staging changes](https://sre.google/workbook/canarying-releases/) ## Related resources - [How to put Oxide back after a Rust update](https://rustsc.com/learn/updates/install-oxide-after-rust-update/index.html.md) - [Roll back a plugin update that changed its data files](https://rustsc.com/learn/updates/rollback-plugin-update-with-data-conversion/index.html.md) - [How to rehearse a Rust wipe before wipe night](https://rustsc.com/learn/wipes/test-a-rust-wipe-plan-before-running-it/index.html.md) --- HTML version: https://rustsc.com/learn/updates/should-you-update-a-rust-plugin-on-force-wipe-day/ --- # Introduce a small Rust plugin change to one world first [Rust server guides](https://rustsc.com/learn/index.html.md) / [Updates](https://rustsc.com/learn/updates/index.html.md) A small welcome-message change is a useful first rollout across several worlds. Rehearse it privately, then open it on one representative world and keep another unchanged while staff watch the same player action on both. ## Pick a first world that can answer the question Choose a world with the same framework, plugin version and relevant settings as the other worlds. It should have players in the hours you can observe. A different framework or ruleset makes it a separate check. Avoid making the first live change to a plugin that controls player protections or rewrites stored progress. ## Compare the same join on both worlds Cedar wants its help message to point to a new community guide. Staff verify the destination and rehearse the exact edit on a private copy first. 1. Record the current line, the source settings file and what prompts the message on each world. 2. Update the message on Cedar Weekly. Have a normal player join at the moment that should show it and follow the link. Have a second tester check the unchanged welcome on Cedar Monthly. 3. Watch the first normal session after the change. Stop widening if the message is missing, points to the wrong place or repeats more often than intended. 4. If a stop condition occurs, put the previous settings back on Weekly and verify the original greeting. Check the intended version and behavior again before scheduling the next world. ## Widen to worlds that match the test Send staff the result, including which version ran and who verified it. Apply the same edit to worlds that share the tested settings and repeat the join check after each. Give worlds with different language files or a different framework a fresh check. A quiet startup alone cannot tell you what players saw. ## Sources - [Google SRE Workbook on comparison groups](https://sre.google/workbook/canarying-releases/) - [Oxide lifecycle and configuration reload](https://docs.oxidemod.com/guides/developers/plugin-lifecycle) ## Related resources - [Install your first Rust plugin and test what it does](https://rustsc.com/learn/setup/first-plugin-download-to-working-feature/index.html.md) - [Change the messages players see from an Oxide plugin](https://rustsc.com/learn/configuration/change-player-facing-rust-plugin-messages/index.html.md) - [Try a management tool update on one Rust host first](https://rustsc.com/learn/management/try-a-manager-update-on-one-rust-host-first/index.html.md) --- HTML version: https://rustsc.com/learn/updates/introduce-a-rust-plugin-to-one-live-world-first/ --- # What to do when a required Rust plugin is no longer maintained [Rust server guides](https://rustsc.com/learn/index.html.md) / [Updates](https://rustsc.com/learn/updates/index.html.md) Start with the features the old plugin enables. A missing update matters more if it owns your economy or protections than if it formats an optional notice. Identify what would fail before you change the live server. ## Draw the shortest dependency list that explains the risk Check the installed version, the publisher's latest supported release and any pinned compatibility note. A quiet release page alone does not establish that a plugin has been abandoned. If there is a specific break, write the first broken game build and the player action you can reproduce. List the plugin's required companions and the features that depend on it. Oxide's review guidance distinguishes optional integrations, required runtime features and dependencies that are necessary even to compile. On a private copy, verify which player step fails without the old component. Keep a record of stored data that would need to move. ## Decide one feature at a time For example, a simple help notice can go away for one wipe. A virtual balance that people earned needs a recovery and player communication decision. | Choice | When it fits | | --- | --- | | Maintain the existing version | The working version still supports your game and someone can own future build and restart checks. Ask the author before adapting code whose terms are unclear. | | Replace it | A supported component covers the required feature and can handle the state you need. Prove the conversion on a fresh private copy. | | Retire the feature | Players can do without it or another supported workflow meets the same need. Explain what stays, what ends and when. | ## Keep the fallback at the failing feature Test the new choice against the same ordinary-player action as the old version. If it changes data, practice going back with the matching old files before releasing. If a critical protection still has no supported replacement, keep that ruleset closed rather than promise a safeguard you cannot demonstrate. ## Sources - [Oxide requirements for plugin dependencies](https://docs.oxidemod.com/guides/reviewers/guidelines/dependencies) - [Google SRE Workbook on limiting rollout risk](https://sre.google/workbook/canarying-releases/) ## Related resources - [Track Rust plugin versions across marketplaces](https://rustsc.com/learn/updates/rust-plugin-version-register/index.html.md) - [Remove a Rust plugin and keep a way to bring it back](https://rustsc.com/learn/updates/remove-rust-plugin-without-losing-data/index.html.md) - [Roll back a plugin update that changed its data files](https://rustsc.com/learn/updates/rollback-plugin-update-with-data-conversion/index.html.md) --- HTML version: https://rustsc.com/learn/updates/when-a-required-rust-plugin-is-no-longer-maintained/ --- # When should you update a Rust server extension by itself? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Updates](https://rustsc.com/learn/updates/index.html.md) An extension can provide shared code for several Rust plugins. Give it its own maintenance window when it can change separately from the game or framework. Use a private restart to test every player or staff feature that depends on it. ## Find out what has to change together Read the extension's version support and installation notes. Oxide describes extension DLLs and recommends stopping the server for a replacement unless the extension explicitly supports another method. Check the extension's own dependencies, and list the plugins that use it. Keep the current extension package and relevant settings available. ## Choose the window from the compatibility notes Keep a version sheet for the game, framework, extension and affected plugins. | Release says | Decision | | --- | --- | | The new extension supports the same game and framework | Rehearse replacing just the extension in a maintenance window. Keep other versions fixed. | | The extension is required for a new game or framework build | Rehearse the documented compatible set together. Do not mix unsupported versions to discover which will load. | | A required dependent has no compatible version | Hold the change or keep the affected feature unavailable until a supported setup passes. | ## Check more than the loaded extension name On a spare host, follow the author's stopped-server replacement procedure and start fresh. Read the extension and plugin load results. Repeat one real action from each affected plugin using test accounts and data. Practice returning to the known working versions on that spare host, then repeat the same actions. Set the live maintenance window only when the tested change and recovery both pass. ## Sources - [Oxide extension lifecycle and updates](https://docs.oxidemod.com/guides/owners/extensions) - [Oxide plugin dependencies](https://docs.oxidemod.com/guides/reviewers/guidelines/dependencies) ## Related resources - [Where do Rust plugin .cs files and extension DLLs go?](https://rustsc.com/learn/setup/plugin-cs-vs-extension-dll/index.html.md) - [Which Rust plugin dependencies should you install first?](https://rustsc.com/learn/setup/install-rust-plugin-dependencies-in-order/index.html.md) - [Roll back a plugin update that changed its data files](https://rustsc.com/learn/updates/rollback-plugin-update-with-data-conversion/index.html.md) --- HTML version: https://rustsc.com/learn/updates/should-you-update-a-rust-server-extension-separately/ --- # What to send your rental host when Rust will not start [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Capture the first useful error from a failed start. Include when it happened and what changed since the last successful boot so the host can match it to the correct attempt. ## Collect one complete attempt From the rental panel, note whether the server stays stopped, starts and exits, or keeps trying to start. Copy the first error and the surrounding console lines. Add the date and time with a time zone, your panel's server name and the last successful start if you know it. A report the host can act on reads “Harbour, 18:10 UTC. The last successful start used a generated world. This was the first start after I changed to a custom map. The console reached the map download and stopped. I’ve attached the lines on either side of the first error.” Substitute your own observations. Remove passwords and private download links. ## Ask for the next check you cannot make yourself If the panel gives you console output but hides the assigned ports or startup command, ask the host to compare the failing attempt with those settings. A useful reply should be able to identify the attempt you described. After you apply the advised fix, watch one complete startup and join to confirm the game is back. ## Sources - [Facepunch guide to creating a Rust server](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch reference for server identity and save files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) ## Related resources - [Server will not start](https://rustsc.com/support/guides/server-will-not-start/index.html.md) - [Get help](https://rustsc.com/support/guides/get-help/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/support-ticket-for-rust-server-startup-failure/ --- # Can RCON start a Rust server that is offline? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) RCON sends commands to a running Rust server. If the game has stopped, start it from your hosting panel or directly on the host. ## Check the panel's server state first If your rental panel shows Stopped, use its Start control. If it shows the game starting, read the startup console and give the world a chance to load. An RCON connection attempt during boot is a poor way to tell where startup is stuck. For example, if a remote console loses its connection when the game stops, check the panel and start the server there. If the panel shows that the process exits again, take the first startup error from the panel console to your host. ## Test the console once the game is reachable Join the game or check that startup has completed. Then connect with your usual RCON client and run a read-only command such as users. If the game can be joined but RCON still fails, check the configured remote console address and credentials separately. You have now narrowed the problem to console access. ## Sources - [Facepunch guide to creating a Rust server](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Start, stop or restart a server](https://rustsc.com/support/guides/start-stop-restart/index.html.md) - [Server will not start](https://rustsc.com/support/guides/server-will-not-start/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-rcon-versus-panel-power/ --- # Why your Rust plugin settings revert when you reload it [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Read the file before editing, right after saving and after the plugin reloads. Note the console events between those reads. That timeline can show whether the edit never reached the active file or whether the plugin wrote a value back. ## Capture three snapshots on a test world Use an easy-to-recognize notice or greeting on an isolated instance. Save the original file. Confirm you are editing the active folder for the framework and that the game's console is open. 1. Before the edit, record the file's full location, its current value and the text the player actually sees. 2. Apply one edit and reopen that exact file from the host or panel. Note whether the new text remains and whether the console already reports a load after the save. 3. Check the file once more after the relevant reload completes and repeat the player action. If the framework already reacted to the save, use that attempt for your timeline. ## Match the rewrite to an event Oxide documents that some plugins write settings while unloading. It also detects changes to watched files. | Observation | Next action | | --- | --- | | The active file never showed the edit | Check which instance and folder the editor saved to, then confirm the active file again. | | The edit vanished on unload | On the test world, use Oxide's unload control, wait until the plugin is unloaded, edit the settings and load it again. Do this with players and other tasks isolated during the test. | | The edit survived unload but changed during load | Check the first configuration warning, the value's type and whether a version migration changed a key. Use the author's expected format. | | The file kept the edit but the player sees the old copy | Check the loaded version and whether the field controls that action or locale. | ## End with the file and player results in agreement A valid edit in the intended file, a clean load and the matching player response give you a result to keep. If the plugin still rewrites the value, send the three snapshots and first related error to the author with sensitive settings removed. In disposable tests, Oxide and Carbon reacted to edits on their own. In a separate configuration test, an invalid value produced different load lines across the two frameworks. Check the concrete error and behavior before assuming the same symptom means the same cause. ## Sources - [Oxide configuration, including save on unload](https://docs.oxidemod.com/guides/owners/configure-plugins) - [Oxide watched files and reload lifecycle](https://docs.oxidemod.com/guides/developers/plugin-lifecycle) - [Oxide load and unload commands](https://docs.oxidemod.com/guides/owners/commands) ## Related resources - [Which Rust plugin JSON file should you edit?](https://rustsc.com/learn/configuration/find-active-plugin-settings-file/index.html.md) - [Which Rust plugin settings should survive an update?](https://rustsc.com/learn/configuration/compare-rust-plugin-defaults-before-keeping-your-settings/index.html.md) - [Find and manage plugins](https://rustsc.com/support/guides/plugins/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/plugin-settings-overwritten-on-reload/ --- # Read the first useful line in a Rust plugin compile error [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Copy the earliest error attached to the plugin you tried to load. Include the file, line and diagnostic code if the framework prints one. Later errors can follow from the first, so give that one your attention before changing several files. ## Decode the first diagnostic The examples below are abbreviated. Keep the unabridged version for the maintainer. | First clue | Check on a spare server | When to stop | | --- | --- | --- | | A named required plugin, type or assembly is missing | Open the plugin's dependency instructions. Check whether the named dependency is the expected version and has a load entry of its own. | If the dependency has its own compile error, resolve that first. | | A namespace already contains a definition, such as CS0101 | Search the active plugins folder for two files containing the same type. A second downloaded copy can carry a numbered filename while keeping the original type. | Keep the original package together if its author intentionally distributes more than one file. Move an identified extra copy outside the active folder. | | A member cannot be found, such as CS1061 | Check whether the plugin author supports this game and framework build. Check the missing member and recent releases for this plugin or its required dependency. | If many unrelated plugins fail together after a Rust update, confirm framework compatibility first. Do not replace the missing code with a guess. | ## Wait for the actual verdict Watch the console after a reload request. In our disposable Oxide and Carbon tests, the request could answer before the compiler printed the error. A test source with the wrong value type produced a named file and location after the request. Check the current plugin list and version at the end of the attempt, then try the player action once. ## Give the maintainer one repairable case Send the plugin version and original download source, the Rust and framework versions, the exact diagnostic and the smallest change that produced it. Say whether a fresh unedited download fails too, if you checked on a clean compatible copy. Remove any credentials or player data from the excerpt. Once the new file compiles and remains loaded, try the same player action as the final check. ## Sources - [Oxide installation and compilation](https://docs.oxidemod.com/guides/owners/install-plugins) - [Oxide on required versus optional dependencies](https://docs.oxidemod.com/guides/reviewers/guidelines/dependencies) - [Microsoft on duplicate definitions](https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/compiler-messages/using-directive-errors) - [Microsoft on a missing member](https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/compiler-messages/cs1061) ## Related resources - [Why did your Rust plugin compile but fail to load?](https://rustsc.com/learn/troubleshooting/rust-plugin-compiles-but-does-not-load/index.html.md) - [Which Rust plugin dependencies should you install first?](https://rustsc.com/learn/setup/install-rust-plugin-dependencies-in-order/index.html.md) - [Find and manage plugins](https://rustsc.com/support/guides/plugins/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/read-rust-plugin-compile-errors/ --- # Is one Carbon plugin slowing down your Rust server? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) If the world pauses when players open a particular menu, record that action on a test copy. A plugin that has accumulated the most time since startup may simply be the one players use most often. ## Give the recording a repeatable job Use the same map, build, plugin settings and player account in both runs. Have a helper stand in the same place. On the first run, leave the menu closed. On the second, let the helper open it the same number of times you wrote down beforehand. Keep unrelated updates and backups outside both recordings. ## Compare the work inside each recording Use a Carbon build that supports c.profile.plugin. In the test server’s admin console, run c.profile.plugin followed by the loaded script plugin name, the duration in seconds and -t for call timing. If Carbon says call tracking is off, enable TrackCalls in carbon/config.profiler.json and restart the test server. Wait until Carbon reports recording has started before the helper opens the menu. The plugin may recompile as the recording starts and ends. Use matching options for both runs. | Observation | What to try next | | --- | --- | | Menu openings coincide with a rise in calls and time for one method. | Repeat the action and save both recordings for the plugin author. | | Both recordings show similar work, but the pause still occurs. | Capture what else the server was doing at that moment. | | The delay appears only while recording detailed timings. | Repeat the player action with profiling stopped before attributing the delay to the plugin. | ## Give the author a case they can repeat Export the two profiles. Include the plugin and Carbon versions, the recorded interval and the exact menu action. Say whether the helper saw the same delay without the profiler running. That lets the author compare like with like, even if their test machine runs at a different speed. ## Sources - [Carbon Mono profiler and recording options](https://carbonmod.gg/devs/features/mono-profiler) - [Carbon single-plugin profiling command source](https://github.com/CarbonCommunity/Carbon/blob/b27f51570ebe53873ff79aea21331290ee2afbd5/src/Carbon.Components/Carbon.Common/src/Carbon/CorePlugin/Core.Commands.Profiler.cs) ## Related resources - [Guides](https://rustsc.com/support/guides/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/measure-one-carbon-plugin-during-a-server-stall/ --- # The Rust process is running, but the game is frozen [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) A running process only proves Rust is still in memory. Try a second way to reach the game before deciding it has frozen. ## Test from two places Ask a player on a different network to join by the known game address. If you also have a game console, try a simple command through a known working console path. If players can still join and move normally while only your remote console fails, troubleshoot that connection before disturbing the game. ## Look for evidence of a stalled game If everyone is stuck and the console has also stopped progressing, record the time and check the host’s CPU, memory and disk activity. Save the last console output. Try the normal stop action if the game can still answer. After any recovery, verify both a fresh join and a console response. ## Sources - [Facepunch Rust dedicated server setup](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch Rust console commands](https://wiki.facepunch.com/rust/useful_commands) ## Related resources - [What a message means and what to do](https://rustsc.com/support/guides/fix-common-problems/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-process-running-but-game-frozen/ --- # Why does Rust keep restarting after a crash? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) If Rust repeatedly exits at the same point in startup, pause automatic retries while you check the first failure. Another attempt will usually repeat the same failure until its cause changes. ## First run and repeat run In a port conflict, the first startup log records a port-in-use error. The service manager announces a restart, then the new game process reports the same error. Read from launch to exit to find the original failure. Check what is already listening or which other game starts first. ## If retries stop On a systemd host, check the unit’s logs to see whether repeated starts reached its limit. The absence of another attempt says little about whether the first error went away. ## Run once after correcting the cause Keep the service stopped with its own control while you correct the failure. Start it manually once, wait for a successful join and verify it stays up before handing recovery back to the service manager. ## Sources - [systemd service reference](https://www.freedesktop.org/software/systemd/man/latest/systemd.service.html) - [systemd journalctl reference](https://www.freedesktop.org/software/systemd/man/latest/journalctl.html) ## Related resources - [What a message means and what to do](https://rustsc.com/support/guides/fix-common-problems/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/automatic-recovery-keeps-restarting-rust/ --- # Rust exits after an update. Was it short of memory? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Check what happened to memory at the time of the exit. An update can make a memory problem visible, but the dates alone do not establish why the game stopped. ## Find the exit and the limit On Linux, look for a kernel out-of-memory entry naming the game. If a container or service has its own memory allowance, check its memory events too. Host memory can look comfortable while a single service has reached its cap. Compare the time with the latest game startup and with an earlier healthy run of the same map. ## Change what the evidence points to If memory really ran out, remove a competing workload or increase capacity for this server before attempting another start. If the first failure instead names a missing file or gives a game error, investigate that. After correcting the cause, check that Rust finishes loading the same world and remains stable through a normal busy session. ## Sources - [Facepunch Rust dedicated server setup](https://wiki.facepunch.com/rust/Creating-a-server) - [Linux kernel control groups and memory events](https://docs.kernel.org/admin-guide/cgroup-v2.html) - [Linux kernel pressure stall information](https://docs.kernel.org/accounting/psi.html) ## Related resources - [What a message means and what to do](https://rustsc.com/support/guides/fix-common-problems/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-closed-after-update-check-memory/ --- # Is high RAM use a problem for your Rust server? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) A large Rust process can run comfortably. Look for declining available memory and pauses under normal load before treating a high usage number as a fault. ## A large working set with smooth play If the game uses more memory after loading a large world and then settles, record the healthy baseline. A large working set with available memory and smooth play gives you a different starting point from a host that slows down with every new workload. ## Falling headroom with pauses On Windows, compare available memory and paging activity alongside the game’s working set. On Linux with pressure information available, look for memory stalls around the player report. Compare CPU and disk activity too. If pausing a competing task reduces the memory stalls and makes the same session smoother, you have evidence that the combined workloads were too much for the host. ## Sources - [Microsoft Windows performance counters](https://learn.microsoft.com/en-us/troubleshoot/windows-server/performance/troubleshoot-performance-problems-in-windows) - [Linux kernel pressure stall information](https://docs.kernel.org/accounting/psi.html) ## Related resources - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/high-memory-use-or-real-pressure/ --- # Is it low client FPS or a slow Rust server? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Start with who feels the problem and what they see. Choppy camera movement on one player's PC points to a different check from delayed interactions across the server. ## Two players, two measurements Both players move the camera and use the Rust client’s `perf 1` overlay to see rendering FPS. The first sees low FPS near a large base, but the second opens doors and moves normally elsewhere. Have the first player repeat the test away from the base. Their original reading measures how fast their PC drew the scene. In a different incident, both players see delayed doors even while camera movement is smooth. Check the server FPS for that time in the host’s monitoring, if available, and compare it with the same server’s normal range. If it fell for both reports, look at what the host was doing then. If server FPS stayed steady, check whether the affected players share a network route or region. After changing a setting or moving a host task, ask the same players to repeat the action that originally showed the problem. Compare the same observation that led to the change. ## Sources - [Facepunch Rust console commands](https://wiki.facepunch.com/rust/useful_commands) - [Microsoft Windows performance counters](https://learn.microsoft.com/en-us/troubleshoot/windows-server/performance/troubleshoot-performance-problems-in-windows) ## Related resources - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/client-fps-or-rust-server-lag/ --- # Why does one Rust server lag while another backs up? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Look at the shared disk, even if the two servers have different folders. A large copy for one server can delay the other when both depend on the same drive. ## Line up the incidents Write down when the lag starts and when the other server’s backup begins and ends. Compare disk wait or latency with a similarly busy period without a copy. If the pauses start and stop with the backup while player counts are similar, you have a specific overlap to test. ## Move one job for the next test Run the backup at a different time while leaving the rest of the setup in place. Check that the backup still completes, and have players repeat an action that used to stall. A recurring lag period after the move suggests a different cause. If moving the job solves the lag, keep the windows separate or consider a backup destination on a different drive. ## Sources - [Linux kernel pressure stall information](https://docs.kernel.org/accounting/psi.html) - [Microsoft Windows performance counters](https://learn.microsoft.com/en-us/troubleshoot/windows-server/performance/troubleshoot-performance-problems-in-windows) ## Related resources - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/one-rust-server-lags-during-another-backup/ --- # Why does Rust say the save folder is read-only? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) A Linux disk can have plenty of free space and still refuse every write. If the first save error says “Read-only file system”, find out how the volume containing the active world is mounted before changing any file permissions. ## Check the filesystem under the save Read the path in the error and locate its existing parent folder. In a terminal, run `findmnt --target . --output TARGET,SOURCE,OPTIONS` from that folder. For a game running inside a container, inspect the mount as the game sees it. A different mount may be visible to the host. Look for `ro` as a complete option. For example, the system drive might be writable while the separate volume under the world folder is read-only. Changing the save folder’s owner cannot make that volume writable. ## Use the exact error to choose the next check Keep a copy of the error and its time. Avoid starting another world over the affected files while diagnosing the storage. | First error | What to inspect | | --- | --- | | Read-only file system | Check the mount options and kernel or hosting-provider storage messages around the failure. | | No space left on device | Check capacity on that specific volume with `df -h .` and inode availability with `df -i .`. | | Permission denied | Check access for the account that runs the game, including its access to the parent folders. | ## Check that the existing world can save again If a previously writable volume changed to read-only unexpectedly, ask whoever manages the disk to check its health before returning it to service. Once they confirm it is writable, watch a normal save of the existing world. Check its file timestamp advances and the original error is absent for that save. ## Sources - [Linux open errors](https://man7.org/linux/man-pages/man2/open.2.html) - [findmnt manual](https://man7.org/linux/man-pages/man8/findmnt.8.html) - [GNU df manual](https://www.gnu.org/software/coreutils/manual/html_node/df-invocation.html) ## Related resources - [Free disk space](https://rustsc.com/support/guides/free-disk-space/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-save-fails-on-a-read-only-filesystem/ --- # Which log explains why a Rust server quit? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Start with the game’s final console or log entries around the exit. Compare those times with the service or host log so the last visible message does not become an accidental diagnosis. ## Build a short timeline Use one time zone for all entries. In this example, a whole group of services returning together is a reason to look for a host boot at 21:07 UTC. | Time (UTC) | Observation | Next check | | --- | --- | --- | | 21:04 | The Rust log falls silent. | Read back to the last game message that describes an action or failure. | | 21:05 | The panel reports the process gone. | Look for a recorded stop or exit at the same time. | | 21:07 | Several unrelated services start again. | Look for a reboot in the host’s system log. | ## Check the host record On a systemd host, inspect the game service’s journal and compare it with kernel messages. On Windows, compare game output with the Application and System logs. If only Rust stopped, read the application or service failure at 21:04 UTC before investigating the later recovery attempt. ## Verify the first event you can explain A save followed by a recorded stop request points to an intentional shutdown. Silence in the game log followed by a new system boot calls for host investigation. A service continuously trying to start after an earlier exit is a consequence. Apply the fix to the earliest supported cause, then check the same log interval during one fresh start. ## Sources - [systemd journalctl reference](https://www.freedesktop.org/software/systemd/man/latest/journalctl.html) - [Microsoft Windows reboot events](https://learn.microsoft.com/en-us/troubleshoot/windows-server/performance/troubleshoot-unexpected-reboots-system-event-logs) ## Related resources - [What a message means and what to do](https://rustsc.com/support/guides/fix-common-problems/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/find-the-log-for-an-unexpected-rust-exit/ --- # Rust startup or remote console failure? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Open the game’s startup output from the host or panel. A remote console that says it is waiting cannot tell you whether the game is still loading, already running or has exited. ## Follow the game through startup If the game is printing new terrain or world-loading messages, let that run continue. If the process exits before loading the world, save the first reported error. Repeatedly reconnecting the console does not move the startup forward. ## Test the console only after the game responds If a player can join the world by the known game address, check the separate remote console address, port and protocol from the PC you usually use to manage the server. Reuse the working game address for player testing and leave its settings alone. Confirm the console is fixed by running a read-only command such as `server.hostname` and checking that the expected name comes back. ## Sources - [Facepunch Rust dedicated server setup](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch Rust console commands](https://wiki.facepunch.com/rust/useful_commands) ## Related resources - [What a message means and what to do](https://rustsc.com/support/guides/fix-common-problems/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-starts-but-remote-console-is-waiting/ --- # Why did a scheduled Rust restart not happen? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Check the scheduler’s last run before triggering the restart again. The schedule may not have fired, its command may have failed, or the game may already have restarted. ## Follow the record in order Check whether the task was enabled and whether the host was awake at its due time. For a systemd calendar timer, check whether it is set to catch up after downtime. On Windows, open the task history or inspect its last run details. If the schedule ran, look for the game’s stop and new startup in its own log. ## Confirm exactly one restart If you find a path error, fix it and check the next due time with the right time zone. If the restart may still be pending, check that before starting one manually. At the next announced window, confirm that the game process starts once and players can reconnect. ## Sources - [systemd timers](https://www.freedesktop.org/software/systemd/man/latest/systemd.timer.html) - [Microsoft Task Scheduler query documentation](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/schtasks-query) ## Related resources - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/scheduled-rust-restart-did-not-run/ --- # Why does Rust+ say your paired server is offline? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) If players can join the game but two paired players see Offline in Rust+, check the server's companion connection. A successful pair can leave an entry in the app even when that connection fails. ## Compare two phones before changing the server Pick the same paired server on both phones and use a second network for one of the checks. If one phone shows the current game time or player count, you have a working companion connection from at least that network. Check the affected phone's network and account first. | What you see | Where to look next | | --- | --- | | The same phone works on Wi-Fi but fails on mobile data | Check that the phone lets Rust+ use mobile data, and try another phone on a separate network. Continue with the server checks if the problem affects both players. | | Neither paired player can open it and the game still works | Read `app.info` and check the startup log for a companion registration or connectivity error. | | One player has an old server entry after a move | Confirm they are opening the active server. Use the current pairing for that server and keep the existing identity files while investigating. | ## Follow the companion port to the process For example, a second game server was set up with its own game ports, but the router still sends the companion port to the first host. Compare the public address and port shown by `app.info` with the router or host panel. If the port is correct and the log reports failed registration, also check if the Rust host can reach `companion-rust.facepunch.com`. If the startup log says Rust+ was disabled after a failed connectivity check, warn players and restart after fixing access so the game can check again. A listen-port change also needs a restart. Open the same paired entry over mobile data and verify it shows live server information. ## Sources - [Facepunch guide to Rust+ connectivity and app.info](https://wiki.facepunch.com/rust/rust-companion-server) - [Facepunch guide to the different Rust server ports](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [How to set up Rust+ on your dedicated server](https://rustsc.com/learn/setup/set-up-rust-plus-on-your-dedicated-server/index.html.md) - [What to keep for Rust+ when restoring the same server](https://rustsc.com/learn/recovery/preserve-rust-plus-pairing-when-restoring/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-plus-paired-server-offline/ --- # Why does Rust+ connect but send no phone notifications? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) When the paired server opens normally, use a known event to test notifications. Start with a teammate joining so you can check delivery separately from any in-game wiring. ## Prove the event first Check that Rust+ is paired to the server you are testing. In the game’s Rust+ menu, check that you opted in to notifications from that server. In the phone app, check the server’s notification switch and the teammate-join setting. Ask an offline teammate to join, then confirm they show as online in the app. Now you have an event with a known time to compare with the phone's notifications. | Result of the join test | Next check | | --- | --- | | The teammate never shows up in the app | Check the active in-game team and the paired server before testing the phone. | | The app shows them online and the alert is in Notification Center or your phone’s notification history | Check whether the phone presents it silently, delays it or hides it on the lock screen. | | The app shows them online and there is no notification | Confirm the game and app notification settings, then check whether the phone allows Rust+ to send notifications. | ## Test with the phone locked On iPhone, open the phone's notification settings for Rust+ and check whether it can show alerts where you expect. Check Focus or Scheduled Summary if delivery is delayed. On Android, check App notifications for Rust+ and whether the relevant alerts are silent. Keep the phone's usual settings when they behave the way the player wants. Lock the phone and repeat one known join with the teammate. A visible alert for that event confirms the path. If teammate alerts arrive but one Smart Alarm stays quiet, test that device and its trigger separately. ## Sources - [Facepunch guide to optional Rust+ teammate notifications](https://rust.facepunch.com/companion/) - [Facepunch explanation of per-server notification opt-in](https://rust.facepunch.com/news/companion-app-update) - [Apple guide to iPhone notification settings](https://support.apple.com/en-us/108781) - [Google guide to Android app notifications](https://support.google.com/android/answer/9079661?hl=en) ## Related resources - [How to test a Rust+ Smart Alarm without waiting for its usual trigger](https://rustsc.com/learn/troubleshooting/test-rust-plus-smart-alarm/index.html.md) - [Why is team chat missing in Rust+ after changing teams?](https://rustsc.com/learn/community/rust-plus-team-chat-missing-after-team-change/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-plus-phone-notifications-missing/ --- # Rust+ says the Smart Switch is on. Why is the light off? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) On in Rust+ describes the Smart Switch state. Check what power reaches the switch and what leaves it before pairing again or changing the rest of the circuit. ## Check one switch and one visible load Try a single in-game light you can see from the switch. Have a player with building privilege operate it in person. Use the Wire Tool to follow the source into the switch's `Power In` and its `Power Out` to the light. `Switch On` and `Switch Off` change the switch state. The circuit still needs power at `Power In`. | What happens with the light | What to check | | --- | --- | | It works when you use the switch in person and in the app | The switch and its remote control work. Check the wiring or power needs of the original load. | | It stays dark even when you use the switch in person | Check the source, the power sockets and the light's required power. | | It works in person, but the physical switch never changes from the app | Check the paired device name against the exact switch. Have someone watch it while you change it from the app. | ## Carry one working check back to the real circuit Suppose the app controls the workshop switch, but adding a second light left the room dark. Check power in and out with the simpler circuit first. Put the original wiring back and read the power where the lights share it. Verify the light follows both an On and an Off from the app after the change. ## Sources - [Facepunch Smart Switch wiring reference](https://wiki.facepunch.com/rust/item/smart.switch) - [Facepunch overview of Rust+ remote device control](https://rust.facepunch.com/news/companion-app-update) ## Related resources - [Why do your Rust base lights go out at night?](https://rustsc.com/learn/troubleshooting/rust-base-lights-go-out-at-night/index.html.md) - [How to test a Rust+ Smart Alarm without waiting for its usual trigger](https://rustsc.com/learn/troubleshooting/test-rust-plus-smart-alarm/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/why-rust-plus-smart-switch-on-but-light-off/ --- # How to test a Rust+ Smart Alarm without waiting for its usual trigger [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Test the Smart Alarm with one deliberate signal. A powered button lets you separate a missing in-game trigger from a problem with the alarm or phone. ## Swap in a trigger you can repeat Use a spare Smart Alarm or make a note of your existing connections before changing them. Pair the alarm from its in-game menu after pairing the server with Rust+. Use a clear name in the app so you can tell this device from a different alarm in the same base. Run the phone test with a paired player who still has building privilege at the alarm. 1. Wire a known in-game power source to a Button, then connect the Button's output to the Smart Alarm's `Power In`. 2. Lock the paired phone and press the Button once. Check for that alarm's message at the time you pressed it. 3. If there is no alert, check that power reaches the alarm during the test. Once the input is confirmed, verify the app shows the paired alarm and that the player has notifications enabled for that server and on their phone. ## Put the original signal back and test it Suppose a pressure pad is meant to announce that someone arrived at the workshop. If the Button produces the alert, restore the pad connection and have a teammate step on it once. If the alert stops, follow that circuit to the alarm's input. When both inputs produce the expected alert, remove any temporary test wiring and leave only the trigger you want. ## Sources - [Facepunch Smart Alarm wiring reference](https://wiki.facepunch.com/rust/item/smart.alarm) - [Facepunch Button wiring reference](https://wiki.facepunch.com/rust/item/electric.button) - [Facepunch notes on Smart Alarm pairing, building privilege and notifications](https://rust.facepunch.com/news/companion-app-update) ## Related resources - [Why does Rust+ connect but send no phone notifications?](https://rustsc.com/learn/troubleshooting/rust-plus-phone-notifications-missing/index.html.md) - [How to set up Rust+ on your dedicated server](https://rustsc.com/learn/setup/set-up-rust-plus-on-your-dedicated-server/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/test-rust-plus-smart-alarm/ --- # Is your Rust Storage Monitor showing the right box? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) A Storage Monitor reads the container it is attached to. Change one count in a known box and look for that exact change on the paired device in Rust+. ## Identify the monitored container in the game Find the Storage Monitor attached to the Large Wood Box or Tool Cupboard you care about. Check that its `Power In` is connected. Match it to its paired Rust+ entry and use a name that identifies the container, such as `West farm seeds`. The Storage Adaptor connects containers to industrial pipes. ## Change one count in a quiet container Suppose two seed boxes have similar names. Record the pumpkin seed count in the first box, put one seed into it and check the app after the device updates. Keep other players or an industrial conveyor from changing that box during the test. If a different entry changes, rename the entry to match the actual container. 1. Remove your test seed and verify the same entry goes back to its earlier count. 2. If the app opens the server and both entries stay unchanged, check the monitor's power and confirm the attached device is the one you paired. 3. If you want an alert, test the notification or attached alarm separately. Seeing live counts verifies the monitor's readout. ## Sources - [Facepunch Storage Monitor container and wiring reference](https://wiki.facepunch.com/rust/item/storage.monitor) - [Facepunch Storage Adaptor industrial connections](https://wiki.facepunch.com/rust/item/storageadaptor) - [Facepunch overview of viewing Storage Monitors in Rust+](https://rust.facepunch.com/news/boat-vendor-update) ## Related resources - [How to test a Rust+ Smart Alarm without waiting for its usual trigger](https://rustsc.com/learn/troubleshooting/test-rust-plus-smart-alarm/index.html.md) - [Why did your Rust Industrial Conveyor stop moving items?](https://rustsc.com/learn/troubleshooting/rust-conveyor-stops-moving-items/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-plus-storage-monitor-wrong-box/ --- # Why won't your Rust CCTV station show a base camera? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Check power at both the CCTV station and the camera. If you can open the station and only one feed fails, compare that camera's identifier to the one saved at the station. ## Separate a station problem from a camera problem Current Rust builds require power at the CCTV station. Use the Wire Tool to check the station's feed as well as the camera's input. If another camera already works at the same station, focus on the missing feed and the power reaching that camera. ## Match the saved identifier to the camera in the world Equip a hammer and use the installed camera's menu to check its identifier. Add that exact identifier at the station and select it. Keep camera identifiers private to the people who should see the feeds. 1. Use a camera aimed at a known spot, such as your garage entrance. Ask a teammate to stand there and verify the live feed shows them. 2. If the wrong area appears, check the selected camera and its direction. Use the camera menu to set the direction if needed. 3. If a feed fails only after dark, check the power again at that time. A midday check can miss a circuit that runs directly from solar power. ## Sources - [Facepunch instructions for camera identifiers and direction](https://rust.facepunch.com/news/cctv-update) - [Facepunch notes on power for the in-game CCTV station](https://rust.facepunch.com/changelist/4034) - [Facepunch item reference for the CCTV station](https://wiki.facepunch.com/rust/item/computerstation) - [Facepunch powered CCTV Camera reference](https://wiki.facepunch.com/rust/item/cctv.camera) ## Related resources - [Why do your Rust base lights go out at night?](https://rustsc.com/learn/troubleshooting/rust-base-lights-go-out-at-night/index.html.md) - [Why does Rust+ say your paired server is offline?](https://rustsc.com/learn/troubleshooting/rust-plus-paired-server-offline/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-computer-station-cannot-show-base-camera/ --- # What does the last death marker on the Rust map show? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) The last death marker shows where the player died. To choose a place to respawn, check their available bags or beds on the respawn screen. ## Identify which point the player is looking at Ask for the marker they see and what they expected to happen when they selected it. If it marks the last death, its position can stay fixed even when the body moves. A named bag or bed is a separate point. Its button or map entry can show a cooldown before the player can use it. | The player says | Check this first | | --- | --- | | The death marker is at the top of the slope | It marks where they died. Compare it with the scene before investigating whether a body or its contents went missing. | | My workshop bag is listed with a timer | The bag is still listed. Wait for its cooldown and check the same option again. | | I cannot find the workshop bag in the list | Check whether the bag is still placed and assigned to that player. | ## Use distinct names for real spawn options For example, a player remembers a marker near the mill and also owns a bag named `Mill`. Ask them to check the named entry on the respawn screen. Rust lets players favourite a bag there to move it up the list. For future tests, have them name a known bag `Mill loft` and check that the matching entry appears in the list before relying on it. ## Sources - [Facepunch explanation of the last death marker and respawn map](https://rust.facepunch.com/news/october-update) - [Facepunch notes on favouriting named respawn points](https://rust.facepunch.com/news/power-trip) ## Related resources - [Why can't you give a friend a sleeping bag in Rust?](https://rustsc.com/learn/troubleshooting/rust-cannot-give-sleeping-bag-to-friend/index.html.md) - [Which Rust map markers can teammates see?](https://rustsc.com/learn/community/which-rust-map-markers-do-teammates-see/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-death-map-marker-versus-respawn-point/ --- # Why is a Rust vending machine missing from the in-game map? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Check whether the shop broadcasts its position, then confirm a buyer on the same server can see its marker and the intended order on the in-game map. ## Check the vending machine with the order Ask the shop owner to check the vending machine's name, order and stock. Then check whether it broadcasts its position. Turning broadcast on makes the shop location public on the game map, so leave it off if the shop is meant to stay private. ## Ask a buyer to check the same shop Say the community market sells seeds from two vending machines at the same base. Use a unique name for the one testing the seed order. Have a buyer open the map at that grid, select the named shop and check what it asks in exchange and how many orders are available. 1. If the marker is missing, check the shop's broadcast setting and grid location. Have the buyer check the map with any search cleared. 2. If the marker is visible and the offer is missing or unavailable, compare the actual order with the stock. The vending machine needs the item in stock to fill the order. 3. If the buyer specifically wants delivery, check the shop's drone access indication on the in-game map and the market terminal's availability before travelling there. ## Sources - [Facepunch release notes for broadcasting a vending machine position](https://rust.facepunch.com/news/devblog-149) - [Facepunch reference for buy and sell orders](https://wiki.facepunch.com/rust/item/vending.machine) - [Facepunch guide to the in-game drone access indicator](https://rust.facepunch.com/news/pivot-or-die) ## Related resources - [Why are shops and events missing from the Rust+ map?](https://rustsc.com/learn/troubleshooting/rust-plus-map-missing-shops-and-events/index.html.md) - [Why did your Rust Industrial Conveyor stop moving items?](https://rustsc.com/learn/troubleshooting/rust-conveyor-stops-moving-items/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-shop-vending-machine-absent-from-game-map/ --- # Why are shops and events missing from the Rust+ map? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Use the in-game Rust map to find vending machines and active event markers. Facepunch stopped sending those markers to Rust+ in the Power Trip update. ## Check what is missing before trying to fix it Older Rust+ instructions may show vending machines, Cargo Ship, helicopters or the travelling vendor on the companion map. The August 2026 release notes record their removal from the app. Seeing one of those in the desktop game and missing it in Rust+ is expected on the updated game. | What you see | What it tells you | | --- | --- | | A known online teammate appears in Rust+ and the game shows a shop the app omits | The app has live information. Check the shop on the in-game map. | | The server is paired but the app cannot load live player or time information | Check the companion connection separately. | | The advertised shop is also missing from the in-game map | Have the shop owner check position broadcast and have a buyer look in the correct grid square. | ## Confirm both views refer to the same server For example, a player reports that the garden shop vanished after updating, but you can see it in the game. Check the app's selected server and a changing value such as its in-game time. If that updates and the shop is visible in the desktop game, tell the player where to check today's market. A re-pair cannot restore a marker the game no longer sends to Rust+. ## Sources - [Facepunch Power Trip notes removing shop and event markers from Rust+](https://rust.facepunch.com/news/power-trip) - [Facepunch overview of live Rust+ server and team information](https://rust.facepunch.com/companion/) ## Related resources - [Why is a Rust vending machine missing from the in-game map?](https://rustsc.com/learn/troubleshooting/rust-shop-vending-machine-absent-from-game-map/index.html.md) - [Why does Rust+ say your paired server is offline?](https://rustsc.com/learn/troubleshooting/rust-plus-paired-server-offline/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-plus-map-missing-shops-and-events/ --- # Why can't you give a friend a sleeping bag in Rust? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Ask the recipient to check who can give them a bag and how many respawn points they already hold. Either can prevent an assignment. ## Check the player setting and the limit separately Rust's Bag Gifting setting lets players allow anyone, allow teammates and friendly contacts, or disable gifts. If the recipient chooses Team, verify the relationship in the game. The server can also limit how many bags and beds count as available respawn points for each player. | What the recipient finds | How to help | | --- | --- | | Gifting is limited to their team or friendly contacts | Check whether the giver is eligible before trying the assignment again. | | They reached the respawn point limit | Let them review their existing points. They can unclaim one they no longer want, or keep them and skip the gift. | | The assignment succeeded and they cannot spot the point | Have them turn on the respawn-point display on their in-game map and check the bag's name and grid square. | ## Verify the recipient can see the right point Suppose a player can give bags to members of their own team but a visitor's assignment fails. Start with the visitor's gifting settings, even if both players use the same base. Once the visitor wants and receives the bag, have them check that `Mill guest` appears at the mill on their map. There is no need to test it by dying. ## Sources - [Facepunch guide to Bag Gifting and respawn point limits](https://rust.facepunch.com/news/bags-to-battles) - [Facepunch guide to joining an in-game team](https://wiki.facepunch.com/rust/teams) ## Related resources - [What does the last death marker on the Rust map show?](https://rustsc.com/learn/troubleshooting/rust-death-map-marker-versus-respawn-point/index.html.md) - [Why can one Rust teammate build at the base while another can't?](https://rustsc.com/learn/troubleshooting/why-rust-teammate-cannot-build-at-base/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-cannot-give-sleeping-bag-to-friend/ --- # Why can one Rust teammate build at the base while another can't? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Have both players check building access at the same spot. The Tool Cupboard controls building privilege in its area, so the new teammate may need authorization there. ## Compare both players at the same spot Ask what they tried to place, where they stood and what message they saw. Stand the authorized builder and the blocked player at the same location and have them compare the building status shown in-game. If the blocked player lacks building privilege there, identify which Tool Cupboard covers that part of the base. A teammate can appear in your roster without being on that cupboard. ## Use the smallest test that shows the difference For example, a visitor can build at the main house but is blocked at the detached workshop. The workshop may be covered by its own cupboard. If the workshop owner wants the visitor to build, have them authorize at that cupboard and retry the same placement preview. 1. Check the building status now shows privilege at the original spot. 2. Check the intended piece can now preview in the correct location. With a test piece, you can verify placement without changing a live structure. 3. If both authorized players are blocked, compare the exact item and position. Look for a placement restriction or obstruction before changing anyone's access. ## Sources - [Facepunch guide to building privilege and Tool Cupboards](https://wiki.facepunch.com/rust/The_Tool_Cupboard) - [Facepunch reference on allowing friends to build](https://wiki.facepunch.com/rust/item/cupboard.tool) ## Related resources - [How can a visitor use one door in your Rust community workshop?](https://rustsc.com/learn/community/give-a-visitor-access-to-one-rust-workshop-door/index.html.md) - [Why can't you give a friend a sleeping bag in Rust?](https://rustsc.com/learn/troubleshooting/rust-cannot-give-sleeping-bag-to-friend/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/why-rust-teammate-cannot-build-at-base/ --- # Why does a Rust planter stay dry with the sprinkler running? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Use one freshwater source, one sprinkler and one planter for the check. Visible spray tells you the sprinkler is active. The planter's water reading tells you what it actually receives. ## Test the water supply without the rest of the farm Trace the hose from the intended freshwater supply. A powered pump can feed sprinklers from fresh water. For a saltwater intake, check that the purifier is powered and the hose feeds the sprinkler from the freshwater side. If you use stored water, verify that the container has some to send. ## Compare the planter with and without the shared load Suppose the first row grew well until you added a second row. Start with one sprinkler and one nearby test planter with a clear path between them. Check the planter's water reading before and after a few sprinkler cycles. If the reading stays flat, verify the source and coverage of that one sprinkler. 1. Once the reading rises, reconnect the other planter area and observe both rows over the same period. 2. If the farther row gets less water, check placement and what the sprinkler can reach. If both are affected under load, check if the source can keep the shared line supplied. 3. Repeat the test with the normal farm connections. Use the readings in each row to decide which change worked. ## Sources - [Facepunch farming guide to freshwater, sprinklers and coverage](https://wiki.facepunch.com/rust/Farming_Basics) - [Facepunch reference for the Sprinkler](https://wiki.facepunch.com/rust/item/electric.sprinkler) ## Related resources - [Why do your Rust base lights go out at night?](https://rustsc.com/learn/troubleshooting/rust-base-lights-go-out-at-night/index.html.md) - [Why did your Rust Industrial Conveyor stop moving items?](https://rustsc.com/learn/troubleshooting/rust-conveyor-stops-moving-items/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-farm-sprinkler-runs-but-planter-stays-dry/ --- # Why do your Rust base lights go out at night? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Find out whether the lamp is running from the solar panel or from a battery. A light that works in daylight can still lose power after sunset. ## Read the circuit in daylight Follow the wires with the Wire Tool. A solar panel's output depends on sunlight. If the light is wired directly to that output, put a charged battery between the source and the light for the test. Connect the panel output to the battery's power input and the battery's power output to one Ceiling Light. Leave the rest of the circuit out of this test. ## Check the same wires after sunset If the lamp goes out immediately, check that the light actually connects to the battery output and that the battery has charge. If it stays on for a while and then goes out, check how much charge remains and how much power the other connected devices use. A charge that gets you through the first part of the night may still run out before dawn. ## Bring back one load and watch what changes Say two new lights were added to the greenhouse and now it goes dark late at night. Try the single-light circuit across one in-game night. Add the second load and check again. If the first setup lasts and the larger one drains the battery, adjust charging or reduce the load. Verify the normal circuit still lights the room just before dawn. ## Sources - [Facepunch reference for solar panel output](https://wiki.facepunch.com/rust/item/electric.solarpanel.large) - [Facepunch reference for battery inputs, output and capacity](https://wiki.facepunch.com/rust/item/electric.battery.rechargable.medium) - [Facepunch Ceiling Light power input and crafting reference](https://wiki.facepunch.com/rust/item/ceilinglight) ## Related resources - [Rust+ says the Smart Switch is on. Why is the light off?](https://rustsc.com/learn/troubleshooting/why-rust-plus-smart-switch-on-but-light-off/index.html.md) - [Why won't your Rust CCTV station show a base camera?](https://rustsc.com/learn/troubleshooting/rust-computer-station-cannot-show-base-camera/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-base-lights-go-out-at-night/ --- # Why did your Rust Industrial Conveyor stop moving items? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) A powered conveyor can sit idle when a filter or destination prevents a transfer. Test one known item along a short path before changing the whole network. ## Check the path from box to box Use two spare storage boxes and a conveyor if the main network holds items you want to leave in place. Check that the Storage Adaptor on the source feeds the conveyor's industrial input and its output goes to the destination. Supply power, turn on the conveyor and try one inexpensive item with no filter to see that it reaches the spare box. ## Check what the filter tells the conveyor to keep Suppose your stone box holds 120 stone and you want it to keep 100. Set a minimum of 100 for stone with space in the destination and no other limits for the test. After the transfer settles, check the source kept 100 and the destination received the excess 20. Use the same kind of before and after count to check the real circuit. | Setting to check | Where to look for the cause | | --- | --- | | Minimum | Check how much of that item is already in the source. This setting leaves a reserve there. | | Maximum | Check how much of that item is already at the destination. | | Buffer | Check whether the source has enough for the required batch size. | ## Verify one transfer on the original route Once the filter does what you expect on the test boxes, check the existing filter and spare space in the actual destination. Adjust only the rule that blocked the transfer. Watch the source and destination counts to check the right items moved and the reserve you want stayed put. ## Sources - [Facepunch Industrial Conveyor electrical and item sockets](https://wiki.facepunch.com/rust/item/industrial.conveyor) - [Facepunch notes on filtering by source minimum, destination maximum and buffer size](https://rust.facepunch.com/news/eye-in-the-sky) - [Facepunch Storage Adaptor item connections](https://wiki.facepunch.com/rust/item/storageadaptor) ## Related resources - [Is your Rust Storage Monitor showing the right box?](https://rustsc.com/learn/troubleshooting/rust-plus-storage-monitor-wrong-box/index.html.md) - [Why do your Rust base lights go out at night?](https://rustsc.com/learn/troubleshooting/rust-base-lights-go-out-at-night/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-conveyor-stops-moving-items/ --- # A player's microphone works elsewhere. Why can't you hear them in Rust? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Have two players stand nearby and listen for the same short voice test. This shows whether everyone misses the speaker or only one listener does. ## Work out which side has the problem Ask the player to check their assigned voice key in Rust and hold it while saying a test phrase. If one listener hears it and the other doesn't, check the affected listener's volume and whether they muted the speaker. Rust's player mute covers both voice and text. Let the listener decide whether they want to change it. ## Check the input device Rust can use Suppose neither listener hears the player but a separate voice app works. Ask the player to open Steam's voice settings and check the selected input and levels. Steam might use a different device, such as the webcam microphone instead of the headset. Speak normally while checking the Steam input level, then select the intended device if necessary. ## Repeat the same test away from the first incident Retest at the same distance with the same listeners after changing the input. If speech still works only outside Rust, compare with another Rust server using the same account and device. A repeat problem on another server gives the player a useful client-side lead. If several players can reproduce it on yours alone, record who heard whom and the time, then check your server's voice-related plugins or rules. ## Sources - [Facepunch microphone input and Steam voice troubleshooting](https://support.facepunchstudios.com/hc/en-us/articles/360019452158-Microphone-not-working) - [Facepunch explanation of local voice and text mutes](https://support.facepunchstudios.com/hc/en-us/articles/10641641796253-Muting-and-Censorship) ## Related resources - [Why is team chat missing in Rust+ after changing teams?](https://rustsc.com/learn/community/rust-plus-team-chat-missing-after-team-change/index.html.md) - [Why does the Rust sign look blank to only one player?](https://rustsc.com/learn/troubleshooting/rust-sign-blank-for-one-player/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-player-microphone-works-elsewhere-not-in-game/ --- # Why does the Rust sign look blank to only one player? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Compare the same sign with another player at the same location. Rust has a client setting that can hide sign artwork. ## Give both players one known sign to look at For example, a board at a trail junction has a painted green circle. Tell both players the grid and the sign you mean. Check the artwork up close on both screens. If one player sees it and the other sees a blank sign, have the affected player look for the sign option under Rust's censorship settings. ## Keep the display choice with the player If the player wants to see signs, they can change the setting and look at the green circle again. If they prefer to keep signs hidden, put essential directions in a text message as well. Give the grid square and the junction's nearest landmark in chat so they can still find it. If both players normally see signs and this one stays blank, try a second known sign before repainting anything. If only the original is affected, confirm the sign's owner and whether it was changed or replaced. Keep the report tied to the exact sign so you can verify the original problem. ## Sources - [Facepunch guide to hiding signs in the Rust client](https://support.facepunchstudios.com/hc/en-us/articles/10641641796253-Muting-and-Censorship) - [Facepunch notes on what the censor signs setting covers](https://rust.facepunch.com/news/arctic-update) ## Related resources - [Which Rust map markers can teammates see?](https://rustsc.com/learn/community/which-rust-map-markers-do-teammates-see/index.html.md) - [A player's microphone works elsewhere. Why can't you hear them in Rust?](https://rustsc.com/learn/troubleshooting/rust-player-microphone-works-elsewhere-not-in-game/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-sign-blank-for-one-player/ --- # Why did your Rust plugin compile but fail to load? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) An Oxide compile message tells you the source file passed the compiler. Keep reading that same startup or reload. A plugin can still fail while it starts, or appear in the plugin list while a particular feature fails. ## Read one attempt from beginning to end Save the console lines from just before you loaded the plugin through the first failure or successful load. Include the plugin name, the version and any later unload on the same attempt. If you started the whole game, keep reading until the server is ready for players. Find the current entry in the framework's loaded-plugin list and compare its version with the file you tried to install. Oxide documents separate stages for preparing the code, loading settings, initializing and registering a plugin. An error in initialization can stop the new code from taking over even if the compiler was happy. ## Follow the first missing result Compare the status you see at the end with the first error for the plugin you just changed. | You see | What to check next | | --- | --- | | A successful compile followed by a config or initialization error | Read the first error for that plugin, including the name of any settings file or missing integration. Compare that file and the named dependency with the author's requirements on a test copy. | | A load message followed by an unload or an older version in the current list | Check the later console lines for the reason, then compare the active file and reported version. An earlier load line can belong to the previous attempt. | | The intended version stays loaded, but its command or feature fails | Try the documented player action once and watch for a new error at that timestamp. Check whether the plugin expects a permission, optional integration or particular game state for that action. | ## Keep a useful result even if the fix needs the author Repeat just the changed test on an isolated server. A clear pass is the intended version staying in the list and an ordinary player getting the intended result. If settings or a dependency are still implicated, send the plugin author the first failure plus a few lines of context, exact versions and the action you tried. Take out passwords and live connection details. In a disposable Oxide test, a plugin compiled successfully and then threw an initialization error. Oxide went back to the prior version and printed a successful load for that earlier version. The log and the current list tell you which code is running. Try the player action separately. ## Sources - [Oxide plugin lifecycle](https://docs.oxidemod.com/guides/developers/plugin-lifecycle) - [Oxide installation and plugin verification](https://docs.oxidemod.com/guides/owners/install-plugins) ## Related resources - [Read the first useful line in a Rust plugin compile error](https://rustsc.com/learn/troubleshooting/read-rust-plugin-compile-errors/index.html.md) - [Which Rust plugin dependencies should you install first?](https://rustsc.com/learn/setup/install-rust-plugin-dependencies-in-order/index.html.md) - [An Oxide plugin loaded. Why is a player denied permission?](https://rustsc.com/learn/community/oxide-plugin-loaded-player-permission-denied/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-plugin-compiles-but-does-not-load/ --- # A Rust reward arrived. Why won’t the shop accept it? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) A Rust plugin can award points successfully while the shop is configured to spend a different balance. Before changing what the item costs, identify what the reward adds and what the affected shop entry expects to debit. ## Follow one transaction on a spare world Use an ordinary test account. Record its balance in each installed currency before triggering a small known reward. Record each again afterwards. For example, if Economics moves from 10 to 15 while Server Rewards stays at zero, write down that you received five Economics units. Open the settings for the shop and the specific category or item that failed. GUI Shop can use Economics, Server Rewards and custom item currency, with overrides in its configuration. Read the world’s own settings to identify that entry’s currency. The number shown on a reward message cannot establish what currency it belongs to. ## Choose the repair that matches the trace Start with the balance and item settings you recorded for the same account. | Observation | Next test | | --- | --- | | Economics rises, but the shop requires Server Rewards points | Test the same item with a small test balance in Server Rewards. Decide whether the shop or reward needs to use the other currency. | | No relevant balance rises | Check the reward plugin's provider settings, the account that earned the reward and the console around the reward event. | | The correct balance rose and covers the cost | Check the item or category restrictions, selected quantity and inventory space. Try a cheap control purchase using the same currency. | ## Close the loop with one purchase On the test copy, repeat the original reward and buy one inexpensive item from the affected shop. Check that only the intended balance falls by the expected amount and that the item arrives. In a disposable Linux Rust run we observed Economics and Server Rewards as separate values. That run did not exercise a GUI Shop purchase, so the shop check belongs in your own rehearsal. ## Sources - [Economics currency and balances](https://umod.org/plugins/economics) - [Server Rewards points](https://umod.org/plugins/server-rewards) - [GUI Shop configuration and currency support](https://umod.org/plugins/gui-shop) ## Related resources - [Which Rust plugin dependencies should you install first?](https://rustsc.com/learn/setup/install-rust-plugin-dependencies-in-order/index.html.md) - [Test Rust kit claims, cooldowns and limits before opening them](https://rustsc.com/learn/configuration/test-rust-kit-redemption-and-cooldowns/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-plugin-balance-changes-but-shop-disagrees/ --- # Why does your Rust plugin work after reload but fail on restart? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) If an Oxide plugin only works after a reload, capture the first failure before fixing it with a second attempt. A reload on an already running server and a clean startup happen at different points in the plugin lifecycle. ## Keep two timelines from the same test instance On an isolated instance with the same versions, start the whole game and save the console from launch until it accepts players. Write down when the affected plugin appears, when its dependencies appear, and when the first error appears. Ask a test player to run the failing action once before reloading anything. Now reload only the affected plugin and repeat the exact action with the same account and settings. Note what changed in the order or in the dependency state. Use a quiet window on the test instance so a scheduled reload or simultaneous update cannot obscure the sequence. ## Read the pair of results Oxide documents that early initialization can happen before dependencies are available. Its later server-initialized stage also runs for a plugin reloaded after startup. | What happened | What to investigate | | --- | --- | | Dependency unavailable on startup, present by the later reload | Send the load order and earliest error to the author. Ask whether the plugin supports the dependency at startup. | | Both versions report loaded, but the same action fails only after startup | Compare the relevant settings, registered permission or prerequisite state at both attempts. Include the first related error after the player action. | | The plugin is absent after start even though it loaded earlier | Check the active file, startup version and any later unload. Fix the startup condition before adding a scheduled reload. | ## Finish with a clean boot Use the author's supported fix on the test instance. Restart cleanly, wait until the world is ready and repeat the action before anyone reloads the plugin. Keep a cold-start success as the result. If you cannot make the action work without manual intervention, keep the existing live setup while the author investigates. ## Sources - [Oxide plugin lifecycle and startup order](https://docs.oxidemod.com/guides/developers/plugin-lifecycle) - [Oxide dependency timing guidance](https://docs.oxidemod.com/guides/reviewers/guidelines/dependencies) ## Related resources - [Which Rust plugin dependencies should you install first?](https://rustsc.com/learn/setup/install-rust-plugin-dependencies-in-order/index.html.md) - [Why did your Rust plugin compile but fail to load?](https://rustsc.com/learn/troubleshooting/rust-plugin-compiles-but-does-not-load/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-plugin-works-after-reload-but-not-after-restart/ --- # Report a Rust plugin bug the maintainer can reproduce [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Tell the maintainer exactly what an ordinary player did and what they saw. ‘It broke after the update’ gives them a time. A minimal sequence and one working comparison give them something to repeat. ## Give the bug a narrow title For example, ‘Member kit deducts points but grants no items after a restart.’ Name the plugin and its exact version, the Rust build, the framework version and any dependencies involved. Note whether you saw the same symptom with the author's unchanged release and your minimal settings on a test instance. If the error only happens on one account, record the role or action history relevant to the issue. Use a synthetic account in the report. Give the maintainer the timing and exact first matching console error, without secrets or anyone's personal data. ## Give the maintainer a sequence they can follow Use a cheap test kit and a small test balance. 1. Start the spare world and join with the test account in the member role. 2. Read the selected balance and leave an empty slot for the kit. Note the kit name and starting balance. 3. Restart the server cleanly, join again and make one claim. Record whether the item arrived and the balance changed. 4. Use another fresh account with the same access on a copy without the restart step. Note that result as the comparison. Say whether you reproduced the failure once or several times. ## Keep the report tied to one defect Separate the expected result from the observed result. A helper who knows the game should be able to follow the report from a fresh test start. Put any unrelated compiler warning in its own investigation. Add a correction in the same thread if a later check changes the result. ## Sources - [uMod maintainer guidance for reproducible reports](https://umod.org/documentation/reporting-issues) - [Google SRE on hypothesis-driven troubleshooting](https://sre.google/sre-book/effective-troubleshooting/) ## Related resources - [Reproduce a Rust plugin issue without sharing player data](https://rustsc.com/learn/configuration/check-per-player-rust-plugin-data-before-sharing-a-copy/index.html.md) - [Read the first useful line in a Rust plugin compile error](https://rustsc.com/learn/troubleshooting/read-rust-plugin-compile-errors/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/report-a-rust-plugin-error-the-maintainer-can-reproduce/ --- # Do two Rust worlds stall when their saves overlap? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Two worlds can pause around the same time for several reasons. Collect one overlap and one quiet comparison from normal play. Observe the natural saves before you change a setting or force additional work. ## Put both worlds on the same timeline Ask a player on each world to report a brief delay in a server action, such as opening a container. Record each time in the same zone. 1. Read each world's actual save times from the console or its active save file timestamps. Give the names and times to staff tracking the incident. 2. Read host disk activity and memory across the same interval. A Linux host may expose I/O pressure under /proc/pressure/io. Use the disk view supplied by your host or Windows monitoring tools if you do not have that file. 3. Mark anything else heavy in that interval, including a backup, scan or second world starting. Compare with an interval where one world saved alone with a similar player load. ## Read the overlap against a comparison A repeated time relationship is evidence for the next test. It does not identify the only bottleneck. | Observed pattern | Next check | | --- | --- | | Both player symptoms line up with the two saves and higher I/O pressure | On spare worlds, arrange non-overlapping save work and repeat the player action with the same conditions. | | The stall appears when neither world is saving | Check other scheduled jobs and whether a console or host measurement changed at the same moment. | | Only one player's local view stutters | Check whether other players can repeat the same server action. Compare their connection and client behavior separately. | ## Keep each world's recovery needs intact If separation improves the comparison on the test host, decide whether you can move unrelated disk work or separate the worlds onto different storage or hosts. Preserve the save frequency you need to recover progress. After one change, repeat the timeline and make sure both worlds still complete normal saves. ## Sources - [Facepunch dedicated server storage guidance](https://wiki.facepunch.com/rust/Creating-a-server) - [Linux pressure stall information](https://docs.kernel.org/accounting/psi.html) ## Related resources - [Why does one Rust server lag while another backs up?](https://rustsc.com/learn/troubleshooting/one-rust-server-lags-during-another-backup/index.html.md) - [Is it low client FPS or a slow Rust server?](https://rustsc.com/learn/troubleshooting/client-fps-or-rust-server-lag/index.html.md) - [Will a second Rust server fit on the same host?](https://rustsc.com/learn/hosting/will-a-second-rust-server-fit-on-one-host/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/two-rust-worlds-stall-when-saving-at-the-same-time/ --- # Why does Rust plugin progress disappear after a restart? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) A plugin can show new progress during play before writing it to storage. Create one unmistakable record on a disposable world and follow it across a clean stop and start. That separates a missing write from a startup that reads elsewhere. ## Follow one change on a fresh test copy Choose a harmless value such as a test account's balance or a test tally. Use the plugin author's instructions to identify its data file or isolated database. Oxide configuration and plugin data are separate. 1. Record the initial in-game value and read the corresponding test data if the tool exposes it. 2. Make one player action that changes the value. Record the new value and the action's time. 3. Wait for the plugin's documented save moment if it has one, then stop the server cleanly. Read the test file or store again and note any console error. 4. Start the same test instance with the same plugin version and read the value through the player's action. Keep the preceding startup log. ## Find which step lost the progress Follow the installed plugin’s own save timing. A file that updates only at a scheduled save may look unchanged during the first part of the test. | Observation | Check next | | --- | --- | | The value never reached storage by clean shutdown | Read the plugin's save instructions and look for its first storage error. Confirm it can write to the expected location or reach the test database. | | The value reached storage and startup shows an older value | Compare the active game folder and plugin storage setting on startup. Check whether the plugin logged a format or schema error. | | The clean check passes and the reported loss followed an abrupt stop | Show the maintainer when the last documented save occurred and whether that interruption could explain the gap. | ## Test a second value after the repair Use the author's supported fix on the same isolated instance and repeat the sequence with a new value. A pass means the written record and the ordinary player's reading agree after a clean restart. Leave the live data untouched while the reason is uncertain. ## Sources - [Oxide plugin data storage](https://docs.oxidemod.com/guides/developers/data-storage) - [Oxide plugin startup and shutdown lifecycle](https://docs.oxidemod.com/guides/developers/plugin-lifecycle) ## Related resources - [How to recover deleted Oxide plugin data](https://rustsc.com/learn/recovery/recover-deleted-oxide-plugin-data/index.html.md) - [Why your Rust plugin settings revert when you reload it](https://rustsc.com/learn/troubleshooting/plugin-settings-overwritten-on-reload/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-plugin-saves-progress-until-the-next-restart/ --- # Why does a Rust plugin run an action twice after reload? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Start with one harmless test event and count the effects. A duplicate can come from two tools reacting to one event, or from a single plugin's repeated work. Fresh-start and after-reload counts help you tell those cases apart. ## Use one test input with a recognizable label For example, a private test server sends a closing reminder twice after a reload. Keep the live channel disconnected. Use console output or a private destination and note the exact time each line appears. Review the plugin, optional framework modules and panel schedules for anything else configured to send the same reminder. ## Change only one condition in each run Use the same test delay or trigger each time. Reset the test before changing the set of tools. | Result | What to try next | | --- | --- | | Two reminders from the first fresh start | On the private copy, run one suspected sender at a time. Give each sender a distinctive message if its settings allow. | | One after startup, two only after reload | Repeat a fresh start and a single reload with just that plugin active. If the duplicate returns, send the author the timeline and the exact reload sequence. | | One immediate reminder and one later copy | Compare their timing against ordinary scheduled jobs and any resend behavior the plugin documents. | ## Prove the count cleared Check the first event after a cold start and another after one reload. The intended action should happen once in both runs. Oxide documents when plugins stop receiving their normal hooks on unload, and Carbon documents repeating timers as a separate mechanism. The logs can show the symptom. The plugin author can confirm why a particular registration or timer repeats. ## Sources - [Oxide lifecycle and unload](https://docs.oxidemod.com/guides/developers/plugin-lifecycle) - [Carbon timer API and repeating timers](https://carbonmod.gg/devs/features/timers) ## Related resources - [Find which Rust plugin handles a chat command](https://rustsc.com/learn/community/find-which-plugin-owns-a-command/index.html.md) - [Report a Rust plugin bug the maintainer can reproduce](https://rustsc.com/learn/troubleshooting/report-a-rust-plugin-error-the-maintainer-can-reproduce/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-plugin-runs-an-action-twice-after-reload/ --- # Why can a Rust player still use a plugin after leaving a group? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Removing a player from a helper group can leave another grant in place. Start with one player and one action, then trace where the permission comes from before editing any other player's access. ## Use the action to find the permission Read the plugin's current help and note the exact grant for the action you want to remove. Test with an ordinary account on a private world. If you use staff authority for the test, the plugin may have a separate administrator bypass. Check the plugin's own documentation for that behavior. ## Work through the remaining access Inspect the user and group permissions with your framework's read controls. Oxide allows permissions to be assigned directly and acquired from more than one group. | What you see | What to inspect next | | --- | --- | | The user has the permission directly | Check why that grant was made. On the test copy, remove that grant alone and retry the action. | | The user belongs to an additional group | Check that group's grants and its parent. Change the player's membership on the test copy only if the other access it provides should end too. | | The default group grants the permission | Compare with a regular account that never had the helper role. Changing the default grant affects every member of that group. | | Your manual changes reappear | Check whether a separate Discord link, access sync or script still assigns them. Correct the source responsible for granting access. | ## Prove the restriction is narrow After adjusting the grant on the test copy, ask the affected account to retry the one action and a second action it should still be able to do. Have a tester who should retain access run the first action too. In a disposable Oxide and Carbon test, a direct grant and a group grant survived a restart while a revoked grant stayed revoked. Repeat your own denial after restart when persistence matters. ## Sources - [Oxide direct grants, group membership and inheritance](https://docs.oxidemod.com/guides/owners/permissions) ## Related resources - [An Oxide plugin loaded. Why is a player denied permission?](https://rustsc.com/learn/community/oxide-plugin-loaded-player-permission-denied/index.html.md) - [Should a Rust moderator have access to one world or all of them?](https://rustsc.com/learn/management/scope-rust-moderators-to-one-world-or-all-worlds/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/rust-plugin-permission-remains-after-group-removal/ --- # Check which Rust worlds actually enforce a ban [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) Once staff have decided where a ban applies, test that the game enforces the same scope. A setting or panel entry gives you the intended result. A fresh join with a test account tells you what the player experiences. ## Write down the expected joins first Use two isolated test worlds with test accounts that can normally join both, and keep production enforcement out of the rehearsal. The example starts with a temporary local test ban already set on Birch Weekly. Birch Monthly should allow the same account. Give each world a distinct join address and keep another regular test account as your comparison. Read any local and shared ban entries that apply to the test account. Label each entry with its owning tool and scope. If you use Facepunch's centralized ban check, it queries the list on a join. An existing session is not proof that a newly added entry was checked. ## Run a fresh join on each world Keep the world name and any refusal text beside the result. Use a fresh connection, including for a test of removal. | Test | Expected result | | --- | --- | | A regular comparison account joins each known address | Both worlds accept the join. Otherwise diagnose that world's access or availability before judging the ban. | | The restricted test account tries Weekly and Monthly | Weekly refuses the join for the test ban. Monthly allows it. | | Remove only the temporary test ban in the tool that owns it and retry | The account joins Weekly again. Monthly still accepts the same join. | | If you also test a shared rule, use a separate clean test account | Both named test worlds enforce it as expected. When you remove the test entry, both worlds return to the baseline. | ## Check the layer that still reports a restriction When the join does not match the expected result, confirm the address and check the local, shared and host records for that test account. If you removed one entry and a different recorded restriction still applies, keep that restriction intact and verify what it covers. Finish when every join agrees with the written scope on the isolated worlds. In a disposable Oxide run, removing managed test bans left unrelated entries from another tool present. That run checked the live game list on one host without connected clients. Use the two join tests to verify the behavior of your own worlds. ## Sources - [Facepunch centralized ban checks at join time](https://wiki.facepunch.com/rust/centralized-banning) ## Related resources - [How to review a ban appeal for your Rust server](https://rustsc.com/learn/community/run-a-rust-community-ban-appeal/index.html.md) - [Handle one conduct incident reported from two Rust worlds](https://rustsc.com/learn/community/handle-a-conduct-incident-reported-from-two-rust-worlds/index.html.md) - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/check-a-rust-ban-on-the-intended-worlds/ --- # Direct join works, but your Rust server is missing from the browser [Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md) If a friend outside your network can join by address, keep that address and game port as they are. The Rust browser uses a separate query port to get server information. ## Start with a clean search Ask the friend who joined to search for a distinctive part of the server name with filters cleared, checking the relevant browser tabs. Use the name shown when they connect so they are looking for the name your server actually presents. If the entry appears, turn filters on one at a time. If applying the wipe schedule filter makes the server disappear, check the advertised wipe tag before changing router settings. ## Check the query port if the listing is still missing Read the query port from your host panel or server startup settings. If you host at home, compare it with the UDP rule on the router and the host firewall. The query rule needs to reach the same machine as the working game rule, on the separate query port. On a rented server, ask the host which public UDP port it assigned for queries and whether it reaches your server. Ask your friend to refresh the browser, find the entry with filters cleared and join from it. That checks both the listing and the route from the listing into the game. Keep the direct join address handy while you investigate a missing listing. ## Sources - [Facepunch guide to creating a server](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch server browser tags](https://wiki.facepunch.com/rust/server-browser-tags) ## Related resources - [What a message means and what to do](https://rustsc.com/support/guides/fix-common-problems/index.html.md) --- HTML version: https://rustsc.com/learn/troubleshooting/direct-join-works-server-missing-from-browser/ --- # Which Rust setting renames the server in the browser? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Use server.hostname to change the name players see. Keep server.identity set to the same value when you want the existing world and its player data to stay in use. ## Change the value that players see Imagine the server identity is coast and you want the listing to say Harbor Builders. Edit server.hostname in the panel or server configuration and leave coast as the identity. If the hostname is set in more than one place, compare the startup settings and server.cfg before applying it. Keep a copy of the previous settings. Use the normal apply or restart method for your host so you can see which hostname the running server actually publishes. ## Check the new name and the familiar world Find the new name in the in-game browser if the server is publicly listed, or check the displayed name after a direct join. Then confirm you are still in the familiar world, for example by visiting an existing base. If the name changed and the world is unexpectedly empty, check which identity and map settings the new startup used. ## Sources - [Facepunch guide to creating a Rust server](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch reference for server identity and save files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) ## Related resources - [Change server settings](https://rustsc.com/support/guides/server-settings/index.html.md) - [Choose a server folder](https://rustsc.com/support/guides/server-folder/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/server-name-versus-server-identity/ --- # Which Rust plugin JSON file should you edit? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Start at the folder used by the running server and check its framework. Oxide usually reads settings in oxide/config. Carbon uses carbon/configs. A server moved from Oxide can still have both directories. ## Follow the active server and plugin version Read the game root in your host panel or launch setup. If you see a current folder and a backup, match the live console's plugin version and filename to the files in that game root. On a rented server, check with the host if their panel maps the default folder somewhere else. Use the plugin's documentation to find the setting. For example, Stack Size Controller's current instructions put individual item stack sizes under IndividualItemStackSize in its config. An old data file or tutorial can describe a previous version that stored them elsewhere. ## Watch where the plugin writes a default file On a test copy, unload the plugin, move the suspected config out of its folder and load the plugin. For a configurable plugin, look for a fresh file with the expected name. Unload the plugin again before putting the saved config back, then load it with the restored settings. If you still see the old value, check the active path and the version again before touching the matching file in another folder. If no config exists on a fresh install, find out whether the plugin provides one and whether the console says it loaded. ## Sources - [Oxide plugin configuration locations](https://docs.oxidemod.com/guides/owners/configure-plugins) - [Carbon's configs directory](https://carbonmod.gg/owners/oxide-porting) - [Stack Size Controller's current configuration format](https://umod.org/plugins/stack-size-controller/) ## Related resources - [Find and manage plugins](https://rustsc.com/support/guides/plugins/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/find-active-plugin-settings-file/ --- # Why a Rust plugin can reject valid JSON [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Run a JSON check first, then compare the edited field with a default config from the same plugin version. A file can parse as JSON while giving the plugin a string where it expects a list. ## Check punctuation separately from the value If the checker reports an error near a closing brace, look at the previous line for a trailing comma. In an example setting, {"Enabled": true,} has invalid JSON punctuation. {"Enabled": true} parses, and its value is a Boolean. The value "true" with quotes parses as text instead. Copy the shape of the default value. If an example field says "Channels": ["general"], adding another value belongs inside the brackets. Changing it to "Channels": "general, trade" produces one string. A checker cannot tell which kind the plugin expects. ## Recover the small edit Save the rejected file separately if the plugin has left it in place. Compare it with the last working copy or a fresh default generated by the same release on a test host. Change only the intended value in that known shape, apply it and watch for a new config error. If the plugin regenerated defaults, bring your settings forward one feature at a time. Start with the change you can observe in game before carrying over the remaining values. ## Sources - [IETF JSON grammar and value types](https://www.rfc-editor.org/info/rfc8259/) - [Oxide configuration troubleshooting](https://docs.oxidemod.com/guides/owners/configure-plugins) - [uMod community example of a config that passes a JSON check](https://umod.org/community/server-info/23077-configuration-keeps-resetting-to-default) ## Related resources - [Find and manage plugins](https://rustsc.com/support/guides/plugins/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/plugin-json-syntax-and-types/ --- # Change the messages players see from an Oxide plugin [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) If the author's settings list doesn't contain the message, check the plugin's language files. A plugin may put its settings, stored state and player-facing messages in three separate places. ## Edit the translation for the language you are testing Open the language file the plugin's documentation names. Better Chat, for example, documents messages under oxide/lang/en/BetterChat.json and chat group formatting in a separate data file. For a built-in response use the language file. For how titles or names are displayed, read the chat group settings. Keep the keys and any replacement fields unchanged. For example, change "Welcome, {0}" to "Good to see you, {0}" while preserving {0}. The plugin fills that part in when it shows the message. ## Make the message appear Keep the previous file, apply the edit using the plugin's instructions and repeat the exact action that triggers the message. Use a test player with the matching language. Check the substituted text as well as your wording. If you still see the old message, check the player language and the file path before editing a second copy or changing plugin code. ## Sources - [Oxide localization guide](https://docs.oxidemod.com/guides/owners/localization) - [Better Chat's configuration and localization examples](https://umod.org/plugins/better-chat) ## Related resources - [Find and manage plugins](https://rustsc.com/support/guides/plugins/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/change-player-facing-rust-plugin-messages/ --- # How to pick a Rust map size for the players you actually get [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Pick the size around the number of players you usually have online. Compare two candidate maps by how people travel between the places they actually use. ## Turn a community complaint into a comparison If regulars say they rarely see anyone, look at how far apart their preferred monuments are and how many routes connect them. If they say every trip passes the same crowded road, compare a candidate with more ways to reach useful landmarks. Seed and terrain shape affect those routes as well as the advertised size. Use a typical busy session as the baseline. A low-population group might prefer shorter trips without wanting everyone to spawn beside the same monument. Compare routes at similar times with the same group. One empty weekday on a large server and one packed wipe evening on a small server tell you little about the effect of size. ## Play one route on each candidate Generate the candidates in a test server. Have the same people travel from a common spawn area to a monument and then a build area on each. Compare where they meet and how long they spend travelling. Check that the host can also run the chosen world with room for saves and backups. ## Sources - [Facepunch guide to creating a server](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch map data reference](https://wiki.facepunch.com/rust/Map_Data) - [Facepunch procedural world configuration](https://wiki.facepunch.com/rust/procedural_generation_customization) ## Related resources - [Preview your map](https://rustsc.com/support/guides/preview-map/index.html.md) - [Read the console and check performance](https://rustsc.com/support/guides/console-performance/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/choose-map-size-for-player-density/ --- # How to check a Rust seed has the monuments your players expect [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Generate the candidate on the build and settings you intend to use. A seed gives you a starting point. The world you generate tells you which monuments actually appeared. ## Sort landmarks by how much they matter For example, make the Train Yard a requirement if your community planned an event there, while treating other landmarks as optional. Keep the seed, world size and any generation settings together when comparing candidates. Changing terrain difficulty or biome settings can remove the conditions a particular monument needs. ## Open the map and visit the location Check the candidate with the same settings you intend to launch. If the monument is missing, change one input or choose a different seed. Keep the candidate only once the place and its approach work for what your group will do there. 1. Open the in-game map and locate the required monument. 2. Travel there from a likely spawn or meeting point. 3. Check the piece of the monument the event uses. If the event needs a specific rail entrance, stand at it and trace where the tracks go. ## Sources - [Facepunch map data reference](https://wiki.facepunch.com/rust/Map_Data) - [Facepunch procedural world configuration](https://wiki.facepunch.com/rust/procedural_generation_customization) ## Related resources - [Preview your map](https://rustsc.com/support/guides/preview-map/index.html.md) - [Wipe your server](https://rustsc.com/support/guides/wipe-server/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/verify-procedural-monuments-before-wipe/ --- # Why did Rust ignore a change to your procedural map settings? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) A change to procedural generation settings usually takes effect when Rust creates the map. Check for an existing map before assuming your new setting did nothing. ## Compare the launch settings and the loaded map Check that the launch settings reference the file you edited through world.configfile and that it lives inside the intended server identity folder. For example, if you set Trails to false and still see the same trails, check whether the old map was already present. Keep that live map and save while you test. ## Generate once in a separate test folder Use a fresh test identity with the intended seed and size and the changed configuration. Look for the expected result there, such as the absence of the trails you targeted. If the clean generation behaves as expected, use the change at your next planned world reset. If it still differs, check the configuration name and values before changing another option. If both versions look the same around the first landmark, check a second area where you know the old world has trails. A valid change may be hard to spot in a place that never had the feature. ## Sources - [Facepunch procedural world configuration](https://wiki.facepunch.com/rust/procedural_generation_customization) - [Facepunch map data reference](https://wiki.facepunch.com/rust/Map_Data) - [Facepunch reference for Rust save files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) ## Related resources - [Change server settings](https://rustsc.com/support/guides/server-settings/index.html.md) - [Preview your map](https://rustsc.com/support/guides/preview-map/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/procedural-config-change-did-not-apply/ --- # How to change Rust biomes without losing safe spawn areas [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Leave space for the terrain Rust uses for player spawns. A world can look good from above and still place a new player somewhere unusable. ## Keep a baseline before changing the mix Generate the original settings and note where new players enter. Then change one biome or terrain difficulty setting in a second test world. For example, if you want more cold terrain, keep enough starting terrain (Tier0) for spawning and check how much usable coastline remains. Facepunch warns that little or no Tier0 terrain can leave a map without spawn points. Keep the seed and size the same for this comparison so you can see what the configuration changed. After checking spawns, visit one monument that matters. Some monuments also need a particular biome or terrain difficulty. ## Join as a new player and try fresh spawns Use a test player with no sleeping bag in that world. Try several fresh spawns and walk inland from the spots you get. Check that you load onto usable ground and can take an early route away from the coast. If spawning fails, revert the last change on the test copy and generate again before using the settings on the live wipe. ## Sources - [Facepunch procedural world configuration](https://wiki.facepunch.com/rust/procedural_generation_customization) - [Facepunch map topology reference](https://wiki.facepunch.com/rust/Topology) ## Related resources - [Preview your map](https://rustsc.com/support/guides/preview-map/index.html.md) - [Change server settings](https://rustsc.com/support/guides/server-settings/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/rust-world-biomes-and-safe-player-spawns/ --- # How to check rail and road routes on a Rust map candidate [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Check whether the rail or road route you need actually runs between its intended stops. Turning a feature on only makes it eligible to generate. ## Name the journey before you choose the seed For example, if you want a train-based event, pick a starting stop and a destination near a useful landmark. Check that AboveGroundRails is enabled if the route needs surface rail. Facepunch's guide lists a 4,250 map-size requirement for procedural above-ground rails. A smaller road-only candidate can be fine for a convoy event. ## Trace it, then travel it Open the map and trace the path between the stops. Load the test world and try the actual journey. If the path exists on paper but does not reach the place you need, compare another seed or revise the event route. Keep the candidate only when someone can make the intended trip in game. Check the return trip if players will be expected to make it. Record any switch or transfer they need so the event instructions match the route you tested. ## Sources - [Facepunch procedural world configuration](https://wiki.facepunch.com/rust/procedural_generation_customization) - [Facepunch map data reference](https://wiki.facepunch.com/rust/Map_Data) - [Facepunch map topology reference](https://wiki.facepunch.com/rust/Topology) ## Related resources - [Preview your map](https://rustsc.com/support/guides/preview-map/index.html.md) - [Change server settings](https://rustsc.com/support/guides/server-settings/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/check-rust-rail-and-road-routes/ --- # How to check buildable space on a Rust map candidate [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Check terrain your players can actually build on. World size alone tells you little about whether a favourite coastline or valley has room for bases. ## Walk the shortlist and try a real footprint For example, a group might want to build near a fishing village but outside monument restrictions. Preview a shoreline with several approaches, then pick a few plausible places near the route rather than judging the whole island from above. Load a test world and attempt the sort of footprint players want to place. Walk the approach and check whether the slope, water or nearby restrictions interfere. Compare the available spots with another seed if the first one has only one usable patch. Announce the candidate after you find room for the activity people asked for. Try the same footprint in more than one spot if the server is for several groups. A hillside with room for one small base may still be a poor choice for a town. Keep a screenshot of the usable sites as a reference for whoever runs the next map vote. ## Sources - [Facepunch map data reference](https://wiki.facepunch.com/rust/Map_Data) - [Facepunch map topology reference](https://wiki.facepunch.com/rust/Topology) ## Related resources - [Preview your map](https://rustsc.com/support/guides/preview-map/index.html.md) - [Wipe your server](https://rustsc.com/support/guides/wipe-server/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/compare-rust-worlds-by-coastline-build-space/ --- # How to write a Rust server description that fits the browser [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Use the first sentence to tell players what they will find when they join. Open your entry in the Rust server browser to see where the important words land. ## Write the part someone needs before joining For a server running standard survival on a small map, try “Standard Rust survival on a small map. Open the website from this listing to see the map and monuments.” Name a gameplay change here if it would surprise someone after joining. Put longer explanations on the page you link. Set the text in your host’s description field or set the variable server.description. For example, in server.cfg use server.description followed by the description in double quotes on one line. If you already set a description on the start line, check that the two places agree before you restart. ## Open the same panel your players will read Ask someone to pick the server in the game browser and read the description before pressing Join. If the last part is missing or hard to read, move the essential words earlier and shorten the text. If it shows the old copy after a refresh, read server.description in the running server console to check whether the game received the change. Try the plain sentence before adding decorative formatting. Keep a version you have already seen display correctly. ## Sources - [Facepunch guide to creating a Rust server](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Which page should you link from your Rust server listing?](https://rustsc.com/learn/configuration/link-a-website-from-your-rust-server-listing/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/write-a-rust-server-browser-description/ --- # How to add a header image and icon to a Rust server listing [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Rust uses two image settings. Use server.headerimage for the header picture and server.logoimage for the smaller server icon. You can set either one on its own. ## Use an address that opens the image itself Open each address in a private browser window. It should load the picture without an account, gallery page or download confirmation. Facepunch recommends a square 256 by 256 PNG or JPG for the icon. Keep the design centred because the icon displays as a circle. | What you want | Value to set | Where to look | | --- | --- | --- | | A header photo | server.headerimage points to the header file. | Open the server details in the Rust browser. | | A small logo | server.logoimage points to the icon file. | Look at the server details. If you pair Rust+, check the icon there too. | ## Check one image at a time Save the addresses where your host keeps the server’s settings and have a player reopen its details. If one picture is missing, compare the saved address with the direct image address first. If both load in a web browser, test each address separately in the game to identify which image needs replacing. ## Sources - [Facepunch guide to the custom server icon](https://wiki.facepunch.com/rust/custom-server-icon) - [Facepunch server settings and header image](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [How to write a Rust server description that fits the browser](https://rustsc.com/learn/configuration/write-a-rust-server-browser-description/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/add-a-header-and-icon-to-your-rust-server-listing/ --- # Which page should you link from your Rust server listing? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Point the listing’s website field at a public page for the server the player selected. On a site with several servers, the most useful destination is the page that tells them what this server is like and how to reach it. ## Pick a page a new player can use If you run separate solo and duo servers, link the duo listing to the duo page. Put the server’s exact browser name near the top so players can tell they are in the right place. Include the rules for that server and a join address they can use later. Facepunch documents server.url as the optional website setting. If you are using server.cfg, use server.url followed by the full HTTPS address in double quotes. If your host offers a website field, use that field and check which server you are editing. ## Test as someone outside your accounts Open the website from the game’s server details. Ask a friend to do the same and tell you which server the page describes. If they land on a sign-in page or an old server, replace the link with the public address for the current server. Leave the website field empty if you have no page players can use. Put the essential details in the listing description. ## Sources - [Facepunch documentation for the server website setting](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [How to write a Rust server description that fits the browser](https://rustsc.com/learn/configuration/write-a-rust-server-browser-description/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/link-a-website-from-your-rust-server-listing/ --- # Which Rust server tags should you show? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Choose the labels a player would use to find your kind of game. The browser displays up to four tags. Spend that space on labels your server can live up to. ## Translate your description into supported labels For example, a server offering standard survival with a focus on roleplay could use vanilla,roleplay. For a training arena use training if it fits what people do there. A custom label such as beginner friendly belongs in the description unless Facepunch documents a matching tag. Use the values from Facepunch’s tag list, separated by commas, in server.tags. Choose at most one from each grouped set. Softcore and Hardcore are both difficulty labels, so using both makes the server harder to find under the intended filter. ## Check the promise behind each tag Look at the entry in the game browser and ask what joining would be like based on the tags shown. If a tag suggests a mode, check the game setting separately. For example, the PvE setting can add its own tag, and the tag by itself is a poor test of damage rules. If a detail has no useful tag, keep it in the first sentence of the description. ## Sources - [Facepunch server browser tag reference](https://wiki.facepunch.com/rust/server-browser-tags) ## Related resources - [What should you check before advertising a Rust server as PvE?](https://rustsc.com/learn/configuration/check-what-pve-means-on-your-rust-server/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/choose-rust-browser-tags-that-describe-your-game/ --- # Should your Rust server be listed under Community or Modded? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Read Facepunch’s Rust-specific plugin guidance before adding something that changes the player experience. Players use the Community and Modded tabs to choose different kinds of servers. ## Walk through what a regular player will see Facepunch directs servers using plugins to the Modded section and describes a narrow allowance for administration plugins that leave gameplay unchanged. It treats changes to gameplay and additions or changes to the in-game interface as Modded cases. | Planned change | What to check | | --- | --- | | A plugin doubles resource gains. | Use Modded. The player gets a different amount for the same action. | | A plugin adds a player-facing in-game menu. | Use Modded. The plugin adds to the game interface. | | A tool only gives staff a way to review reports. | Check that it leaves ordinary gameplay and the player’s interface as they are, then read the admin-plugin allowance. | ## Confirm the tab with a normal client Review the effects from a non-staff account, then look up the running server in the intended tab. If adding the feature changes the kind of game you offer, update the listing and description before inviting players to try it. ## Sources - [Facepunch guidelines for community servers using plugins or mods](https://support.facepunchstudios.com/hc/en-us/articles/360009062817-Guidelines-for-community-servers-using-plugins-mods) ## Related resources - [Which Rust server tags should you show?](https://rustsc.com/learn/configuration/choose-rust-browser-tags-that-describe-your-game/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/choose-community-or-modded-for-a-rust-server/ --- # Why does your Rust server listing show the wrong country? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) A region tag you typed is a label. Rust also detects the location of the server’s public address. Start by finding which of those is wrong. ## Identify the address behind the listing Open the current entry in Rust and confirm it is the server you are checking. Compare the location shown with where the game is hosted. Use the host location, even if you live in a different country or administer the server remotely. If the wrong label is a manually entered region tag, correct or remove that tag in server.tags. Use Facepunch’s documented region values if you set one. ## Route incorrect address data to the right place If the detected country is wrong, use the location correction route in Facepunch’s server guide. For a rental, give the host the public game address, the country the browser shows and the intended host location. Ask them to check the published location of that address. Refresh the listing after the correction and have a player confirm what it shows. If the issue was reported after moving hosts, make sure the player is looking at the new address before asking the host to investigate further. ## Sources - [Facepunch guide to detected server country](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch server browser region tags](https://wiki.facepunch.com/rust/server-browser-tags) ## Related resources - [Which Rust server tags should you show?](https://rustsc.com/learn/configuration/choose-rust-browser-tags-that-describe-your-game/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/fix-the-location-on-a-rust-server-listing/ --- # Should you turn on Premium for your Rust server? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Premium limits who can see and join a Rust server based on the account’s eligible Rust inventory. Keep it off if a friend you want to play with cannot meet that requirement. ## Check the accounts that matter to your server Send your group to Facepunch’s current eligibility guidance. The Premium tag in the game opens the account eligibility panel. Ask people to check their own status. The useful answer is whether their account currently qualifies. For example, if six friends play and one cannot join Premium servers, staying with the standard listing preserves access for all six. Decide based on who needs to get in before changing the running server. ## Test the change from both player perspectives Facepunch documents server.premium 1 for owners who want to opt in. Try it on a separate test server before changing the one people play on. Ask an eligible player to check the Premium label and join. Compare that with what a non-eligible player sees and verify the result against Facepunch’s guidance. If you decide against using it, leave the setting disabled and verify that an account you intend to admit can find and join. ## Sources - [Facepunch announcement and owner setting for Premium servers](https://rust.facepunch.com/news/premium-servers) - [Facepunch Support instructions for checking Premium eligibility](https://support.facepunchstudios.com/hc/en-us/articles/25840924689693-Premium-Servers) ## Related resources - [Which Rust server tags should you show?](https://rustsc.com/learn/configuration/choose-rust-browser-tags-that-describe-your-game/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/decide-whether-to-use-premium-on-a-rust-server/ --- # How many player slots should you set on a Rust server? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Set server.maxplayers to the maximum number of players you intend to have connected at once. Start from a real session you can try with your group. ## Decide what the cap needs to allow Say your usual group has eight players and two friends sometimes join. A cap of ten is a reasonable example if you want room for everyone. If you intend to open the server to more people, test a representative busy session before raising the cap further. A session where everyone idles at spawn tells you they can connect. Have the group do what they will normally do, such as building in separate areas and fighting near a monument, and ask whether movement and interactions stay responsive. ## Verify what the game reports and who gets in Set the positive whole number in your host’s player limit setting or in server.cfg with server.maxplayers. Read the running value after applying it through your normal setup. Ask a player to check the capacity shown in the browser, then confirm the intended group can connect. If players reach the cap while the game still behaves well, try a modest increase and repeat the same kind of session. If play already suffers with the smaller group, keep the lower cap while you check what the host can handle. ## Sources - [Facepunch guide to the Rust player limit](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Why did a Rust setting change back after restart?](https://rustsc.com/learn/configuration/keep-a-rust-setting-after-restart/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/choose-a-rust-server-player-cap/ --- # Why did a Rust setting change back after restart? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) If you changed a variable through the live console, check where your host keeps the settings for the next start. The console can show a successful change while an older value still waits in the startup settings. ## Compare the same variable in every place it is set For example, suppose the running console reports server.maxplayers as 20 and server.cfg also lists 20. If your launcher still passes +server.maxplayers 10, the game starts with 10 on builds that use the startup order Facepunch documents in Soft Refresh. On a rented server, check the panel’s startup value as well as the file. If the host generates that argument, update the panel value. On a self-hosted server, choose one place you control for the setting and remove the conflicting entry if your setup allows it. ## Check the value after a planned start At the next planned restart, type just server.maxplayers in the server console to read it. If the wrong number returns, check that you edited the file under the running server’s identity and that the launcher is using the settings you changed. Leave the same value in the settings your launcher actually uses and read it again after the next planned start. ## Sources - [Facepunch Soft Refresh notes on configuration precedence](https://rust.facepunch.com/news/soft-refresh) - [Facepunch documentation for startup arguments and server.cfg](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Change server settings](https://rustsc.com/support/guides/server-settings/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/keep-a-rust-setting-after-restart/ --- # Which Rust settings affect eligibility for the secure server list? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) When you reuse a launch script from a private test server, check whether it starts Rust with -insecure. Compare the public server’s running encryption setting with Facepunch’s browser requirement. ## Check the two settings that matter here Read the startup arguments for -insecure. Facepunch introduced it in place of the older server.secure variable for choosing an insecure launch. Remove the argument from the startup settings you use for a public secure server. Read server.encryption in the running server console by entering the variable name without a value. Facepunch’s Maintenance update states that at least level 2 is required for a server to be considered secure and appear in the Rust client’s server browser. If your script or config uses a lower value, set the documented level in your persistent settings. ## Check the result from a normal Rust client Restart at a planned time if you changed either value. Read server.encryption again, then have someone open regular Rust and look for the entry. If the settings are correct and the server is still missing, investigate the ordinary listing checks next. ## Sources - [Facepunch Harder Core notes on insecure startup options](https://rust.facepunch.com/news/harder-core/) - [Facepunch Maintenance notes on server browser encryption requirements](https://rust.facepunch.com/news/maintenance) ## Related resources - [Direct join works, but your Rust server is missing from the browser](https://rustsc.com/learn/troubleshooting/direct-join-works-server-missing-from-browser/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/check-secure-listing-settings-on-a-rust-server/ --- # Would Softcore suit the people on your Rust server? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Try Softcore if your group wants to spend less of its play session replacing lost gear. Start by testing what a friend brings back after a death during a normal gathering trip. ## Start the test on a separate world Use a test server with +server.gamemode softcore in its startup settings. Use a second test world with the mode unset for standard survival. Keep the mode change away from a world people already play on because changing modes can clear a player’s state. Facepunch’s Soft Refresh describes automatic recovery of part of your inventory when you die outside a building privilege area. Test in open ground away from cupboards. Bring a few cheap items you can identify, record what you carried and compare what remains after respawning. ## Compare what it takes to get back to playing Have the same person do the route in both modes and say what they had to replace to continue. If the group also cares about gathering speed or what happens to a base while everyone is logged out, make those separate tests before choosing. Facepunch has revised Softcore over time. Base your description on the checks you make on the build you intend to run. ## Sources - [Facepunch wiki on starting a game mode](https://wiki.facepunch.com/rust/server-gamemodes) - [Facepunch Soft Refresh notes on Softcore respawns](https://rust.facepunch.com/news/soft-refresh) - [Facepunch Printed and Polished notes on Softcore revisions](https://rust.facepunch.com/news/printed_and_polished/) ## Related resources - [How to tell if your Rust group will enjoy Hardcore navigation](https://rustsc.com/learn/configuration/test-hardcore-navigation-on-a-rust-server/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/try-softcore-before-choosing-it-for-your-rust-server/ --- # How to tell if your Rust group will enjoy Hardcore navigation [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Hardcore changes how players find their way. Before choosing it for a group, see whether finding a monument and getting home feels like an enjoyable part of the game. ## Try the same route with and without a compass Start a separate test server with +server.gamemode hardcore. Ask two friends to pick a visible landmark from spawn and use terrain to meet there. Have them look at the map before they equip a compass in the belt, then look again with it equipped. Facepunch’s Harder Core update describes the map gradually revealing terrain and showing the player’s position once they equip a compass in their belt. Check the route on the game build your group will actually use. ## Choose based on what the group enjoyed Ask if both players could find the meeting point and retrace the trip to a base. If that took more time than they would want most evenings, keep standard survival for their regular game. If they liked navigating together, set expectations about the map and compass in the description of a new Hardcore server. ## Sources - [Facepunch wiki on starting a game mode](https://wiki.facepunch.com/rust/server-gamemodes) - [Facepunch Harder Core notes on map and compass behaviour](https://rust.facepunch.com/news/harder-core/) ## Related resources - [Would Softcore suit the people on your Rust server?](https://rustsc.com/learn/configuration/try-softcore-before-choosing-it-for-your-rust-server/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/test-hardcore-navigation-on-a-rust-server/ --- # What should you test before running a Rust Primitive server? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Try Primitive on a separate world if your group enjoys the early equipment in Rust. See what a player can craft at a workbench, then try an encounter with that equipment before choosing the mode for your community. ## Test the gear players expect to work toward Start a separate test world with +server.gamemode primitive. Ask a player to open the workbench and look for an expected goal like a crossbow and a weapon they normally aim for later. Compare the available options with what players expect from standard survival. Facepunch’s launch notes describe restrictions across weapons and armour. The list includes bows, crossbows and the Eoka. Check which items the current build offers before naming them in the listing. ## Try the sort of encounter your server is for Give two volunteers a choice of gear available on that test world and try a short skirmish. Ask what each would craft afterward, and whether they’d enjoy that style of fight on a regular server. If you open a Primitive server, name the mode in the description and mention a concrete restriction you checked. Keep the experiment on its own world while you decide. ## Sources - [Facepunch Primitive game mode introduction](https://rust.facepunch.com/news/primitive) - [Facepunch wiki on starting a game mode](https://wiki.facepunch.com/rust/server-gamemodes) ## Related resources - [How to write a Rust server description that fits the browser](https://rustsc.com/learn/configuration/write-a-rust-server-browser-description/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/check-primitive-progression-on-a-rust-server/ --- # How to set up a Rust server for creative building practice [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Use a separate practice server if the goal is to build without gathering first. Rust has built-in creative controls, including a switch for all players and separate switches for individual building effects. ## Turn on the building freedom you need In the practice server console use creative.allusers true to include the whole server and creative.freebuild true to make building blocks free. Leave creative.freeplacement off if the session is supposed to teach placements that also work in survival. Facepunch describes it as bypassing placement checks. If you also want to practise wiring or deployment, read the individual controls in the creative guide and decide whether those rules should match survival. Focus the session on the design you want to build. ## Use an ordinary player for the check Ask a non-admin to join, equip the building tool and place a foundation with no building materials in their inventory. Have them try the same sequence on the survival test setup with materials if they intend to copy the design there. If a part of the build only works on the creative server, note which placement or resource assumption changed. ## Test a base piece where the design gets difficult Imagine Quarry Club practising a two-room workshop that will go on a Survival slope. Mark the chosen terrain on the practice world and build the basic room, then fit the stair landing. Keep free placement off. A snap that works on flat ground does not settle whether an entrance clears the slope at the real site. Have a player build the same small entrance in a Survival test setup with materials and ordinary permissions. Follow the same order, including the step from the door to the landing. If the landing clashes, mark the room as a practice design and change the foundation height or choose flatter ground before publishing a build guide. ## End the practice session deliberately The Creative controls are separate. Keep a before-and-after record so the next group knows what it will find. If you intend a permanently Creative world, keep its published settings and use a separate Survival copy for the reproduction. | Before practice | Before returning the practice world to ordinary play | | --- | --- | | Record the values you changed and who can join. | Restore those original values and recheck the effective settings. | | Put away the builder's resources and label the disposable practice footprint. | An ordinary player should no longer place the free foundation from the opening check if free building was previously off. | | Say whether the practice build will stay for viewing. | Verify the intended placement and resource rules, then either keep the build as agreed or leave the plot clearly marked before reopening. | ## Sources - [Facepunch Creative Mode controls](https://wiki.facepunch.com/rust/creative) ## Related resources - [What should you check before advertising a Rust server as PvE?](https://rustsc.com/learn/configuration/check-what-pve-means-on-your-rust-server/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/set-up-a-rust-creative-building-practice-server/ --- # How to check Tutorial Island on your Rust server [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Enable Tutorial Island if a new player can use what it teaches when they return to your server’s main game. Check the tutorial itself before adding the Tutorial tag. ## Enable the actual tutorial Facepunch documents server.tutorialEnabled true for Tutorial Island. Add the setting to your test server or change it through your host’s settings. Ask a new player to join and look for the prompt. Experienced accounts may need to start the tutorial from Options, so an experienced owner joining without a prompt is an incomplete check. 1. Have the test player enter Tutorial Island. 2. Ask them to try one of its basic tasks, such as crafting or placing a building piece. 3. Check that they can finish the tutorial and reach your server’s main game. 4. Once the path works, add tut to server.tags and verify the listing with the tutorial filter. ## Make sure the lesson matches what players will do If the server is mainly a minigame or changes a core action the tutorial teaches, try that action in the main world before advertising the tutorial. If the introduction does not fit, leave off the tag and use the server description to explain how the first session starts. ## Sources - [Facepunch Tutorial Island instructions for server owners](https://wiki.facepunch.com/rust/Tutorial_Island) - [Facepunch server browser tag reference](https://wiki.facepunch.com/rust/server-browser-tags) ## Related resources - [Which Rust server tags should you show?](https://rustsc.com/learn/configuration/choose-rust-browser-tags-that-describe-your-game/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/enable-and-check-rust-tutorial-island/ --- # Should you change the sleeping bag limit on a Rust server? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Decide how much ground one player should be able to cover with respawn points. A small cap can make players choose between bases, a travel route and staging points near a fight. ## Start with the limit your server already uses Facepunch documents max_sleeping_bags as the control for the per-player limit. Search for max_sleeping_bags in your running server console using find and read the value the game reports. Use that as the starting point when comparing the built-in setting with a lower or higher one. On a separate test world, choose a small cap you can reach without much play. Have an ordinary player put down respawn points up to that cap, then try to add one more. Check what the player sees and whether the existing points are still available on the respawn screen. ## Try one routine that depends on the extra point For example, have the tester set up at a main base, a coast shelter and a regular travel route. Ask which points they would drop first and what that would change on a typical evening. Use the result to decide whether the existing cap already fits. If you keep a custom cap, record the intended value in your host settings and read it again after a planned restart. ## Sources - [Facepunch Bags to Battles notes on respawn limits](https://rust.facepunch.com/news/bags-to-battles) - [Facepunch guide to finding console variables](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Why did a Rust setting change back after restart?](https://rustsc.com/learn/configuration/keep-a-rust-setting-after-restart/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/choose-a-sleeping-bag-limit-for-your-rust-server/ --- # Is Rust decay too fast, or is a base out of upkeep? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Start with the cupboard for the damaged building. A stone base with enough stone may still be short of the metal fragments required for its doors. ## Read the upkeep cost for that structure Ask someone authorised on the cupboard to open it and check the upkeep cost and protection display. Compare each material the cupboard requests with what is actually inside. Facepunch’s cupboard guide gives the example of stone parts and sheet metal doors requiring both stone and fragments. If the complaint is about a separate building beside the base, ask which cupboard serves that structure. Check the small building itself. The main base can be protected while a disconnected building without its own cupboard decays. | What you see | What to check next | | --- | --- | | Stone in the cupboard but no fragments. | Supply the missing material and check the protection display again. | | The main base is fine but a nearby shed is damaged. | Check the shed’s cupboard and upkeep separately. | | Several ordinary bases are hard to maintain with an expected play schedule. | Try the same small build on a test server and measure what its cupboard asks for. | ## Decide from more than one building For an upkeep decision that affects everyone, compare a small starter base and a larger example on the same game mode. Have a player build and stock each one as they normally would, then record the displayed cost. ## Sources - [Facepunch wiki on tool cupboards and decay](https://wiki.facepunch.com/rust/The_Tool_Cupboard) - [Facepunch Devblog 189 on building upkeep](https://rust.facepunch.com/news/devblog-189) ## Related resources - [How to set up a Rust server for creative building practice](https://rustsc.com/learn/configuration/set-up-a-rust-creative-building-practice-server/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/check-rust-upkeep-before-changing-decay/ --- # How to check the built-in team size on a Rust server [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Use the team-size setting if you want Rust’s built-in roster to hold a specific number of people. Test with one more player than the roster should allow. ## Set a roster size on a test server Facepunch documents relationshipmanager.maxteamsize as the team-size variable. For a duo test, set relationshipmanager.maxteamsize 2 in the test server’s settings and check the running value. Use the game mode you actually intend to run because gameplay settings can differ by mode. Have one ordinary player choose Create Team from their inventory and invite a second player. Confirm both appear on the roster. Ask the leader to try adding a third person, then have the second player leave and repeat the invitation. ## Check other actions separately If you care about how many people can share a base, also test authorising at its cupboard. Have the third player walk up to the cupboard and try the authorise action. Check the result separately from the team invitation. Use the result to describe the actual roster size players will get. ## Sources - [Facepunch guide to the team-size variable](https://wiki.facepunch.com/rust/server-gamemodes) - [Facepunch Rust Wiki on teams](https://wiki.facepunch.com/rust/Teams) - [Facepunch Rust Wiki on building privilege](https://wiki.facepunch.com/rust/The_Tool_Cupboard) ## Related resources - [Would Softcore suit the people on your Rust server?](https://rustsc.com/learn/configuration/try-softcore-before-choosing-it-for-your-rust-server/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/check-the-built-in-rust-team-size-setting/ --- # How to test a shorter locked crate timer on a Rust server [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) A shorter locked crate timer changes how much time other players have to arrive after the hack starts. Try that encounter on a test world before changing it on a survival server. ## Measure from the start of the hack Facepunch’s server setup guide shows hackablelockedcrate.requiredhackseconds in server.cfg. Its example value of 600 means ten minutes. Read the value your running server already uses and first test a crate with that value. Start a fresh hack and record the visible countdown. Have a second player begin at a spot where they often are when an event starts. Check whether they can reach the crate while it is still locked. ## Repeat the encounter with one change Use the same kind of crate and starting point for the shorter test. Begin a new hack after the new value is active and compare the timer and the second player’s arrival. Keep the crate’s appearance time separate from how long it takes to unlock. If the change cuts out the part of the encounter you want, keep the original value. If you adopt it, check the game reads the same value after the next start. ## Sources - [Facepunch server configuration example for the crate hack duration](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Why did a Rust setting change back after restart?](https://rustsc.com/learn/configuration/keep-a-rust-setting-after-restart/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/test-a-rust-locked-crate-hack-timer/ --- # What should you check before advertising a Rust server as PvE? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Test the protection you want to advertise with two ordinary players and disposable gear. A PvE browser tag tells people what to expect. Your checks tell you what you can promise them. ## Match your label to the running game Facepunch documents that server.pve applies a PvE browser tag. Check how the server actually shows up in the browser. If you use a plugin to control damage instead, read its setup instructions before changing the built-in setting. TruePVE documents damage rules separately from looting, so a blocked shot or raid does not tell you who can open a box. Write the promise before building the test. A small server might promise ‘No player combat, base raiding or theft in the open world. Scientists and upkeep still matter.’ Each word must survive a realistic interaction. Build a disposable base on a matching test world, stock the cupboard and set up one locked door, an ordinary storage box and a sleeping spot. ## Check the things players expect to keep Keep test staff powers out of both accounts. Let one person act as the base owner and the other as an unrelated visitor. | What you intend to promise | Ordinary-player test and pass condition | | --- | --- | | No player combat in normal play. | Try a direct hit in an open area and check both health bars. When the server promises teammates the same thing, repeat after the accounts join a team. | | Strangers cannot raid a maintained home. | Have the visitor try the test base wall and locked door. Confirm the pieces take no damage from the agreed raid methods. | | A player's sleeper is protected. | Have the owner log out with disposable gear. Have a stranger try the agreed damage and access checks, then have the owner reconnect to confirm their state. | | A stranger cannot take private gear. | Try to open the owner's test box and take spare items from an agreed corpse or dropped bag. Check the visitor and owner separately against the advertised loot rule. | | Monuments still give people a combat challenge. | Ask a player to visit a familiar monument and check that its NPCs can still damage them. Record any places where you advertise a different rule. | ## Turn a failed result into a smaller promise or a repair Imagine Seabank's shot, door and monument checks pass, but the visitor can take cloth from the owner's dropped bag. Hold back the theft claim. Decide whether dropped items are public by design or whether a separate rule needs fixing. If you change loot protection, rerun the box, corpse and bag cases as both an unrelated visitor and an authorized teammate if their access differs. Record the game build, relevant plugin versions and places tried with the result. Put a failed case on the next change checklist. Recheck affected protections after an update or a change to a zone or plugin. ## Publish the same promise in the browser and welcome post For Seabank's example result, the listing could say ‘PvE with protected maintained bases. Dropped bags are public. Scientists and ordinary PvE hazards remain.’ Add the fuller local rules where new players start. If you announce a special combat area, mark its boundary and test entry, exit and actions crossing the edge before making a separate promise. ## Sources - [Facepunch guide to browser tags and server.pve](https://wiki.facepunch.com/rust/server-browser-tags) - [Facepunch Devblog 63 introducing the built-in PvE setting](https://rust.facepunch.com/news/devblog-63) - [TruePVE: damage rules and zone integration](https://umod.org/plugins/true-pve) - [Prevent Looting: container and corpse protection](https://umod.org/plugins/prevent-looting) ## Related resources - [Which Rust server tags should you show?](https://rustsc.com/learn/configuration/choose-rust-browser-tags-that-describe-your-game/index.html.md) - [Should your PvE Rust server add a dueling area or a combat weekend?](https://rustsc.com/learn/community/choose-a-combat-format-for-a-pve-rust-server/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/check-what-pve-means-on-your-rust-server/ --- # Choose one tool to control Rust item stack sizes [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Give stack size to one tool. If Carbon's StackManager module and a plugin both change the same item, a test with both running cannot show which configuration produced the result. ## Decide which settings you need to carry over List a common item, such as wood, and a special case, such as scrap. Write the largest stack your players should be able to form for each. Note any container or inventory rules your setup relies on. Carbon's optional StackManager module has global and per-item settings. A separate plugin such as Stack Size Controller has its own rules and item overrides. Choose the tool that covers the rules you actually use and that you can maintain on your framework. ## Run two clean alternatives Use a disposable Carbon world with the same framework and relevant plugin versions. Record their current settings and keep an original copy of your test items and configuration. 1. Check the optional module and the installed plugins. Read each tool's settings for the same two item names. Keep other stack-changing tools out of the test. 2. Start the copy with only the candidate module active and measure both items. Prepare a fresh copy of the same starting state and repeat with only the candidate plugin active. 3. Try to combine freshly spawned or gathered items past the expected size. Split and move a test stack between a player's inventory and a box. Record the resulting counts. 4. On that copy, try transferring a test stack already larger than the proposed limit. Restart and check the resulting counts once more. ## Use the test to decide when to switch If the expected limit matches but an existing stack behaves badly, hold the change until you know what players need to do with existing items. A fresh wipe is a simpler time to adopt a smaller limit if stored items would otherwise need special handling. Keep the previous settings ready. Open the change to players once one stack controller produces the expected inventory and box behavior after a restart. ## Sources - [Carbon StackManager module](https://carbonmod.gg/owners/modules/optional-modules/stack-manager-module) - [Stack Size Controller by AnExiledDev](https://umod.org/plugins/stack-size-controller) ## Related resources - [Which Rust plugin JSON file should you edit?](https://rustsc.com/learn/configuration/find-active-plugin-settings-file/index.html.md) - [Install your first Rust plugin and test what it does](https://rustsc.com/learn/setup/first-plugin-download-to-working-feature/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/choose-one-source-for-rust-item-stack-sizes/ --- # Check what your Rust gather multiplier actually changes [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) A 2× stone setting for hitting a rock says nothing about picking up stones or running a quarry. Gather Manager gives those paths separate settings. Give the server listing wording that fits the paths you actually test. ## Collect your comparison samples first Use a spare world with Gather Manager as the only rate changer. For stone mining, use the same tool and comparable fresh nodes in both tests. Compare the same part of the mining sequence because the yield can change from one hit to the next. For a ground pickup, start with an empty inventory and take one matching collectible. For a quarry, start with empty output and compare the same completed work under both settings. ## Record what went into the inventory Keep a row for each source. Try the intended multiplier on the disposable world. Record the numbers you actually see rather than assuming each source changed. | Source | Gather Manager setting | Record | | --- | --- | --- | | Stone mining | The stone rate under dispenser | Stone received across the same set of hits. | | Stone collectible | The stone rate under pickup | Stone in inventory after one pickup. | | Mining Quarry | The stone rate under quarry | Stone produced for the selected amount of work. | ## Read a mismatch before adjusting a second setting If a rock gives more on every hit but still runs out sooner than you expected, check yield per hit and total output separately. Gather Manager documents dispenser scaling for how much is available from a node. Review item-specific rates where you use a wildcard because an explicit rate can override it. If a path still looks unchanged, confirm it appears under the expected setting and review other plugins or modules that also affect yields. Then rerun only that row. If mining and pickups match the promise but quarry does not, advertise the measured rule, such as ‘2× mining and pickups; normal quarry output.’ ## Sources - [Gather Manager by Ryan, gathering and dispenser scaling](https://umod.org/plugins/gather-manager) - [Carbon optional modules and gather settings](https://carbonmod.gg/owners/modules/what-are-modules) ## Related resources - [Choose one tool to control Rust item stack sizes](https://rustsc.com/learn/configuration/choose-one-source-for-rust-item-stack-sizes/index.html.md) - [Which Rust server tags should you show?](https://rustsc.com/learn/configuration/choose-rust-browser-tags-that-describe-your-game/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/test-rust-gather-multipliers-by-source/ --- # Test Rust kit claims, cooldowns and limits before opening them [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Choose one small kit and write down who can claim it, what they receive and when they may claim it again. An administrator can set up that kit. A regular account gives you the result your players will get. ## Build one small test kit On an isolated server, create a replenishing kit for a repeated job such as giving rehearsal players tools. Include cheap items that are easy to count. Give one ordinary account the intended permission. Use another ordinary account with no such grant. Leave both accounts at regular player authority so staff privileges cannot explain a successful claim. Rust Kits distinguishes a required permission, an authority level, whether a kit is hidden, cooldown and maximum uses. Write the expected result of a claim separately from whether you expect a title in the menu. If you charge for a kit, use the test copy's currency and record the balance before and after. ## Run the claims in this order Set a limit of two claims for the rehearsal so the use limit cannot explain the first refusal. Start with enough inventory space and, for a kit with a cost, enough test currency to attempt three claims. Choose a cooldown long enough to try again before and after it expires, allowing time for one clean restart. Record each attempt's time. | Try | What a pass looks like | | --- | --- | | Account with the required permission claims once | It receives the exact item counts in the kit. | | Account without the permission tries the same claim route | It receives nothing and loses no currency. | | Allowed account claims again immediately | A kit with a cooldown refuses the second claim. | | Restart while the cooldown is still running and try again | The immediate extra claim is still blocked. If the restart took longer than your test cooldown, rerun with a longer cooldown. | | After the cooldown, claim a second time. Wait for it to expire again and try a third time. | The second claim succeeds. The third claim is refused even after the cooldown, with room and any needed currency still available. | ## Test the way players will actually obtain it If you use an automatic kit at respawn or a kit sold by an NPC, test that route separately. Clear the test inventory between attempts and check what happens when a higher-priority automatic kit is available. Save your observed results beside the kit name. Release it when the allowed and refused claims agree with what you will tell players. ## Sources - [Rust Kits, permissions and redemption rules](https://umod.org/plugins/rust-kits) - [Oxide permission groups and grants](https://docs.oxidemod.com/guides/owners/permissions) ## Related resources - [An Oxide plugin loaded. Why is a player denied permission?](https://rustsc.com/learn/community/oxide-plugin-loaded-player-permission-denied/index.html.md) - [Install your first Rust plugin and test what it does](https://rustsc.com/learn/setup/first-plugin-download-to-working-feature/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/test-rust-kit-redemption-and-cooldowns/ --- # Copy one Rust setting between worlds without changing the save identity [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Copy the setting you wanted, such as the community website address. The destination already has its own launch arguments, world and connections. Use its active configuration as the starting point. ## Find where the destination gets the value Read the setting in the running destination and find where its provider or launch definition sets it. On a self-hosted instance, check both the launch script and the active server.cfg for that Rust server identity. Also check any startup script that generates the file. Write down the source value and the destination's current value before you edit. ## Try the one-line transfer on a copy Choose a visible setting such as server.url. Make a separate test setup based on a saved copy of the destination settings. Give the test its own file paths and ports, restrict its joins and remove live integrations before starting it. 1. Check that the address applies to both worlds. If the source points to a world-specific event or rules page, use the destination's relevant address instead. 2. Save a baseline of the isolated test settings. Change only the chosen value on that test copy and review the difference against the test baseline. 3. Launch the disposable copy the same way the destination launches. Check the setting in the console and, where applicable, in the game client. If the value reverts at startup, find the owner of that value before editing again. 4. Once the test passes and the change is scheduled, apply the same single setting to the destination. Review the live change for any unintended change to identity, map, ports or credentials. Recheck the setting and a familiar landmark or structure in the destination world. ## Stop when the destination looks like a new world If a join lands you on a blank map or an unexpected save, keep the original files. Compare the destination identity and launch record with the details you wrote down. Put back the previous settings and verify you are on the expected world before doing anything else. ## Sources - [Facepunch settings, launch arguments and identity](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch guide to configuration and server saves](https://wiki.facepunch.com/rust/Getting-Started_w-Server) ## Related resources - [Which Rust setting renames the server in the browser?](https://rustsc.com/learn/configuration/server-name-versus-server-identity/index.html.md) - [Why did a Rust setting change back after restart?](https://rustsc.com/learn/configuration/keep-a-rust-setting-after-restart/index.html.md) - [Import or download server settings](https://rustsc.com/support/guides/import-server-settings/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/copy-rust-settings-between-worlds-without-copying-identity/ --- # Reproduce a Rust plugin issue without sharing player data [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Make a new test world and recreate the smallest state that triggers the error. A copy of your production plugin folder may include player histories and private settings that the maintainer needs no access to. ## Work backward from what the bug needs A kit cooldown bug needs a kit, a test account and two claims at known times. It rarely needs the original player's inventory, name or account identifier. Set up a normal test account, create a test kit and give the maintainer the rule and the result. If the error appears only after a restart, restart the test instance before taking the second observation. Use the plugin author's documentation to find the relevant configuration and data. Oxide keeps configuration and stored plugin data in different areas. A plugin can also send requests to configured destinations. Use default files and private test destinations rather than bringing live service details into the reproduction. ## Check what will leave your hands Send a small report by default. When the maintainer needs a file, create a minimal version from the clean test. | Material | Keep in the report | | --- | --- | | Configuration | The few settings that affect the result, with invented names and no live URLs, keys or passwords. | | Console output | The first matching error and its time. Remove player IDs, names, addresses and connection secrets. | | Player state | Test labels and actions. Exclude production saves, player records, bans and permission exports. | ## Verify the report before sending it Repeat the issue using only the steps and files you intend to share. If the synthetic test passes, send the versions and that observation first, and ask what further detail would help. Keep the live files private while the maintainer narrows the case. ## Sources - [Oxide plugin data and configuration storage](https://docs.oxidemod.com/guides/developers/data-storage) - [Oxide web requests and configured headers](https://docs.oxidemod.com/guides/developers/libraries/webrequests) - [uMod issue-report guidance](https://umod.org/documentation/reporting-issues) ## Related resources - [Report a Rust plugin bug the maintainer can reproduce](https://rustsc.com/learn/troubleshooting/report-a-rust-plugin-error-the-maintainer-can-reproduce/index.html.md) - [What can you share from a Rust server backup when asking for help?](https://rustsc.com/learn/recovery/what-to-share-from-rust-backup/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/check-per-player-rust-plugin-data-before-sharing-a-copy/ --- # Test a permanent safe zone on your Rust server [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) A safe-zone name or entry message tells players they crossed a line. Rehearse what they can actually do on both sides. Use a separate map copy and two ordinary testers with expendable items. ## Write the protection you are offering For a protected market, decide whether players may draw weapons, hurt one another, build or deploy items. Zone Manager documents a safe-zone option and separate flags for actions such as building and deployment. List the flags you intend to use. If your market overlaps another zone, record which one you expect to control each action. Put a cheap test structure and landmarks on the copy inside and outside the boundary. Ask testers to approach from different directions, including a path that crosses the apparent edge at a different elevation if the terrain calls for it. ## Walk the market with both testers For actions that might cause damage, use only the test world, gear and structure. | Tester positions | What to observe | | --- | --- | | Both outside, away from other zones | The usual rules apply, giving you a comparison. | | Both inside the market | Weapon and damage results match the market promise. Check building or deployment separately. | | One inside and one outside, then reversed | Test each direction. Record what each player can draw or use and what damage, if any, reaches the other side. | | Inside an overlap, then back outside the smaller zone | The intended rules apply in each area. When both are outside again, the normal rules return. | ## Keep the protection through a restart Zone Manager says a smaller zone normally inherits flags from an enclosing zone. If you use its explicit parent setting, confirm each flag you need in the smaller zone rather than assuming the larger zone still supplies it there. Repeat the boundary walkthrough after a restart. If the observed boundary is unclear, move or simplify it on the test copy until staff can show players where each rule changes. ## Sources - [Zone Manager options, flags and parent-child behavior](https://umod.org/plugins/zone-manager) ## Related resources - [What should you check before advertising a Rust server as PvE?](https://rustsc.com/learn/configuration/check-what-pve-means-on-your-rust-server/index.html.md) - [Run a PvP weekend on your PvE Rust server](https://rustsc.com/learn/community/weekend-pvp-on-a-pve-rust-server/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/test-a-fixed-rust-safe-zone-before-opening-it/ --- # Keep live Discord feeds out of a Rust plugin test server [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) The safest copy for testing a Discord message is a fresh private world with a test-only destination. A copied plugin setting can still point at your live announcement channel. Review the directions messages can travel before starting the test. ## Start from an empty set of external links List what would normally post announcements, relay chat, take commands or grant roles. Check the game plugin, the bot and any rule in your hosting or management tools. Leave those jobs disconnected when you first start the test instance. | Live connection | What to use in the rehearsal | | --- | --- | | Outgoing announcement webhook | Create a webhook for a private test channel if you need to test the outgoing message. Keep its full URL private. | | Bot or two-way chat link | Use an isolated bot and Discord server if the test needs one. Leave inbound commands and role sync off unless they are part of the exercise. | | Live channel IDs, tokens and account links in exported settings | Recreate the minimum config without these values. Read the files you intend to use before starting the feature. | ## Check that one event reaches one destination The example tests only an outgoing status announcement. 1. Verify the test webhook's channel in Discord and enter it in the test plugin settings. 2. Send a synthetic message with a recognizable label such as ‘Birch Test closing check’. Read the intended private channel and the usual live announcement channel. 3. Confirm exactly one copy on the test channel and none on the live channel. Review the source of extra messages before enabling another integration. 4. Remove the test connection when you finish. If you copied any reusable files back to shared storage, check those exports contain no webhook, token or private account link. ## Sources - [Discord webhook setup and channel destinations](https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks) - [Oxide web requests and configured headers](https://docs.oxidemod.com/guides/developers/libraries/webrequests) ## Related resources - [Reproduce a Rust plugin issue without sharing player data](https://rustsc.com/learn/configuration/check-per-player-rust-plugin-data-before-sharing-a-copy/index.html.md) - [What Rust chat should you share in Discord?](https://rustsc.com/learn/community/choose-which-rust-chat-to-share-in-discord/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/keep-live-discord-links-out-of-a-rust-plugin-test-server/ --- # Which Rust plugin settings should survive an update? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Read three copies of the settings before accepting changed defaults. Your current file includes intentional choices and old defaults. A fresh configuration from the new build shows which options the author added, removed or renamed. ## Get each copy from a known version Save the current working configuration before testing any update. Use a fresh private copy of the old build to see its defaults, and a separate copy of the new build to generate new defaults as its author describes. Read the release notes before starting the new version with existing data. Keep the working files untouched during the comparison. ## Read by setting rather than by line number JSON objects can list the same settings in different orders. Compare named settings and values, including their types. | What you find | What to take forward | | --- | --- | | Your old setting differs from the old default and the same option still exists | Check that the difference is intentional. Carry it forward using the new version's expected type and meaning. | | Your setting matched the old default and the new default differs | Decide whether the author’s new behavior suits your world. Avoid silently preserving the old outcome without an owner decision. | | An option disappeared, was renamed or changed type | Use the author's migration instructions. Ask the maintainer if the replacement is unclear. | | An option exists only in the new defaults | Read what it does and check the result that players would see before enabling it. | ## Check a changed rule before copying another Start the candidate on the private world and check it loads. For an example notice setting, join with the matching test account and check the exact text. Read the file back after restart to confirm the intended setting persisted. Stop if the version has rewritten a setting you still need. Keep the saved configuration and the smallest failing comparison ready for the author. ## Sources - [Oxide configuration serialization and file locations](https://docs.oxidemod.com/guides/developers/data-storage) - [JSON objects and values in RFC 8259](https://www.rfc-editor.org/rfc/rfc8259) ## Related resources - [Why a Rust plugin can reject valid JSON](https://rustsc.com/learn/configuration/plugin-json-syntax-and-types/index.html.md) - [Why your Rust plugin settings revert when you reload it](https://rustsc.com/learn/troubleshooting/plugin-settings-overwritten-on-reload/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/compare-rust-plugin-defaults-before-keeping-your-settings/ --- # Check Rust plugin message placeholders after an update [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) A language file can load successfully while a message shows a placeholder or puts values in the wrong order. Use a small action with known values in two supported languages and read what each tester actually sees. ## Choose a message whose values are easy to check For example, a test shop message tells a player how many points remain after a purchase. Use a private world with test balances. Find the entry the current plugin version registers, then compare the same entry in the default language file and your translated file. Oxide stores its default language files under oxide/lang, with a folder for each language. Keep every placeholder the new version expects. A token such as {0} is part of the plugin's formatting. Find what it stands for in the author's documentation or current example before moving it in a sentence. If the new defaults add or change a token, update the translated entry to match the new inputs. ## Observe two languages and two values Have each tester select a locale as supported by the plugin or framework. Keep other permissions and actions the same. | Try | Expected output | | --- | --- | | Default language with the known test balance | The right amount in the expected message, with no unfilled token. | | Translated language with the same test values | The intended translation and the same correct amount. | | One more action with a different value | The text changes only where the new amount belongs. A named placeholder still refers to the expected field. | | Restart and repeat one translated action | The correct language and values appear again. | ## Keep the failing line usable If you get the default language, check how the version chooses a language and whether it found your file and key. If a token appears literally, compare the entry against the current version. Send the maintainer the message key, the two results and the synthetic input values if you need help. ## Sources - [Oxide data storage and language formatting examples](https://docs.oxidemod.com/guides/developers/data-storage) - [JSON strings in RFC 8259](https://www.rfc-editor.org/rfc/rfc8259) ## Related resources - [Change the messages players see from an Oxide plugin](https://rustsc.com/learn/configuration/change-player-facing-rust-plugin-messages/index.html.md) - [Which Rust plugin settings should survive an update?](https://rustsc.com/learn/configuration/compare-rust-plugin-defaults-before-keeping-your-settings/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/test-rust-plugin-language-placeholders-in-game/ --- # Why won't my Rust custom map URL load? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) Open the exact map URL in a private browser window. It should download the map file by itself. A sign-in screen, share page or download button means you need a different link. ## Test the link before changing the live map For example, if your file host opens a page labelled Harbor.map with a Download button, copy the host's public direct-download URL and try that in a fresh private window. Check the result is the map you uploaded. A filename ending in .map can still lead to an error page. Use the direct link in server.levelurl. If you set startup arguments yourself, remove procedural map arguments such as the seed and world size when switching to the custom map. Keep the file at a public address that will still work when new players join. ## Check server startup and a fresh join Start a separate test server on the map before swapping it into the live server. Check its startup console and join with a client that has never downloaded that map. Success means the server opens the intended world and the fresh client gets into it. If the server starts but the client reports a download error, ask the player to check the map URL shown in their F1 console. Try that exact link from their network. If it returns a web page or fails there, fix access to the map file before troubleshooting gameplay or wiping again. ## Sources - [Facepunch guide to hosting custom maps](https://wiki.facepunch.com/rust/Hosting_a_custom_map) - [Facepunch custom map troubleshooting](https://wiki.facepunch.com/rust/FAQ_and_Troubleshooting) ## Related resources - [Preview your map](https://rustsc.com/support/guides/preview-map/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/custom-map-url-wont-load/ --- # Why does my Rust server disappear when I apply a tag filter? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md) If the browser shows your server with filters cleared, start with the tag that makes it disappear. Some tags belong to the same group and Rust expects you to choose one from each group you use. ## Give each group one answer Check server.tags in the server settings. A server tagged both weekly and monthly is giving two answers about its wipe schedule. Facepunch documents that the browser can display one of the tags in a group while searches behave incorrectly. Keep the tag that matches the schedule your players actually get. If the problem is a PvE filter, check server.pve as well. Rust can apply the PvE tag from that setting. Compare what the server is advertising with how the server is actually set up. ## Put the filter back by itself Save the corrected settings and apply them using your host's usual process. Refresh the browser with filters cleared, search for the server name, then select only the corrected tag. For the weekly example, the server should stay visible when you select Weekly. If the single filter works but a combination hides the server, add the other filters back one at a time. That shows which advertised setting to check next. ## Sources - [Facepunch server browser tag groups and settings](https://wiki.facepunch.com/rust/server-browser-tags) ## Related resources - [Change server settings](https://rustsc.com/support/guides/server-settings/index.html.md) --- HTML version: https://rustsc.com/learn/configuration/server-visible-until-browser-tag-filter/ --- # Run a PvP weekend on your PvE Rust server [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) A PvP weekend needs a working finish as much as a working start. Rehearse both on a separate server before inviting your PvE community to fight, and decide whether homes, sleepers and loot will stay protected. ## Give the weekend one clear set of rules Imagine Meadow, an established PvE community using TruePVE. Its first combat weekend runs from Friday at 18:00 to Sunday at 20:00. The server's clock is UTC. Players may fight across the world, but raiding homes and stealing remain against the rules. Existing damage and looting protections must support that promise. There is no new protected-town exception to explain at the boundary. Write that short description before changing the server. If your players want an arena while peaceful building continues elsewhere, use an arena setup instead: the global schedule below changes the whole world's rules. Agree what happens to event loot and destroyed items too. In this example, normal progress carries on after the event; putting protections back does not rebuild anything lost during combat. ## Prepare Meadow's rehearsal copy Use a separate Rust server with its own ports, identity and compatible framework. Copy the community's relevant plugin settings and keep live Discord announcements and other live integrations off. Save the normal TruePVE configuration, its data and any zone or looting-plugin settings before making an event copy. Give the test players disposable gear and build a small test home. This example assumes TruePVE already provides your normal protection with `server.pve false`, as its documentation requires. Keep damage handling on. Clone the working normal ruleset into a ruleset named `weekend`. If its player rule is `players cannot hurt players`, replace that rule with `players can hurt players` in the event copy. Retain its building and locked-door protection, and keep `defaultAllowDamage` false. Flags can override ordinary rules, so verify the result rather than treating that one edit as a complete configuration. TruePVE does not manage looting; retain and test your existing looting plugin's protection. ## Set a start and a return to normal In TruePVE's `Schedule`, set `enabled`, `useRealtime` and `broadcast` to `true`. Replace the entries in the event copy with the two lines below. Meadow runs on UTC. Friday is day 5 and Sunday is day 0. Replace `default` if your normal ruleset has a different name. For the first rehearsal, move the two entries to upcoming times a few minutes apart on the test server. Reload the plugin using your framework's plugin controls and watch the console for successful loading. Check the current rules before the start, during the event and after the end. Schedule selection can take a short time to appear; use the observed change and the player checks before announcing that combat is open or closed. Let TruePVE own these two transitions in this example. If another tool already swaps the same configuration or schedules combat, turn off its competing event changes for the rehearsal and planned event. Keep the saved normal configuration ready for an early finish. | Meadow time | Schedule entry | | --- | --- | | Friday at 18:00 UTC | `5.18:00 weekend Weekend rules switched. Wait for staff to open combat.` | | Sunday at 20:00 UTC | `0.20:00 default Combat is closed. Staff are checking the return to PvE.` | ## Try to break the promise before players do Have two ordinary player accounts run the following checks before, during and after the short event. Use accounts without administrator powers or protection bypasses. Record the actual result beside the expected one. Test an unrelated player against the small home so ownership or team membership cannot make the check look safer than it is. Existing zone mappings need particular attention. In our separate TruePVE rehearsal, two synthetic locations inside the same mapped town selected the town's normal rules during the event. With only one side inside, the resolver selected the global event rules. That was a rule-selection test, not a shot fired across a real boundary. Test both directions with your actual zones before promising a sanctuary; keep combat closed if the promise fails. | Check | Expected outcome | | --- | --- | | Two unrelated players exchange a shot in the open | Player damage is blocked before the event, allowed during it and blocked after it. | | A visitor attacks the test home's wall and locked door | The home stays protected before, during and after combat. | | A player disconnects; the other attacks their sleeper | Normal protection before and after; the exact announced sleeper rule during combat. | | A visitor tries a test box and another player's dropped bag | The looting plugin enforces the promised no-stealing protection, including during combat. | | Players stand together in each existing mapped zone, then shoot across its edge in both directions | Each direction matches the published boundary during combat, with normal protection restored afterward. | ## Announce the rules you just proved Replace the dates in this example before posting it: ‘Meadow combat weekend runs Friday [date], 18:00 UTC to Sunday [date], 20:00 UTC. PvP is allowed across the world once we confirm it is open. Homes and loot stay protected. No raiding or stealing. Event losses stay lost; there is no world rollback at the end. We will confirm the return to PvE here and in game.’ Add the sleeper rule you actually tested and a place to report a problem. Post the same boundaries in Discord and in the game's event messages. Before the start, remind players what they should carry and where to read the full rules. Have a helper watch for protection problems during the opening. If the rehearsal exposed an exception you cannot explain and support, change the event's scope before publishing the invitation. ## Restore peace and close the event At the end, watch the normal rules return and have the same two players repeat the open-world shot and home-protection checks. Verify the looting and sleeper protections you promised too. Publish ‘PvE is back’ after those checks agree. If a protection fails during the event, end combat early: restore the saved normal plugin settings, reload the affected plugins and repeat the checks before reopening peaceful play. For a one-off weekend, put the saved normal configuration back after the scheduled finish and reload it. Check that it contains no enabled event schedule, then verify normal protection once more. The example entries repeat weekly if left enabled. Leave a short staff note with the closing result and any player issue still needing a reply; returning to PvE does not restore lost gear or undo damage. ## What our rehearsal can establish Our disposable Debian test with TruePVE 2.4.8 selected normal, event and normal rules again on a shortened schedule. The event copy kept the same damage rules, so that run verifies switching only. Two players still need to test damage, sleepers, looting and real zone boundaries on your own rehearsal server. ## Sources - [TruePVE: configuration, schedules, flags and zone integration](https://umod.org/plugins/true-pve) - [Zone Manager: zone flags, permissions and boundaries](https://umod.org/plugins/zone-manager) ## Related resources - [Schedule a temporary change](https://rustsc.com/support/guides/temporary-changes/index.html.md) - [Announce or recover a temporary change](https://rustsc.com/support/guides/temporary-change-messages-and-recovery/index.html.md) - [Schedule an in-game Rust event in Discord](https://rustsc.com/learn/community/schedule-a-rust-game-event-in-discord/index.html.md) --- HTML version: https://rustsc.com/learn/community/weekend-pvp-on-a-pve-rust-server/ --- # What should friends agree before starting a private Rust world? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Before anyone rents a server or installs one, agree what you are making together. A friend who spends Sunday building a shop should know whether it can be raided on Monday. Settle when people can play, what others can take and what a late arrival gets. ## Ask what would make the first world worth playing Ask each friend for one thing they want to try: learn a monument, practise a raid, build a village or race another team through progression. Choose an opening aim everyone can describe. You do not need a public-server rulebook for a group that wants to spend an evening learning together. For example, a clan preparing for its next public wipe could agree that practice bases may be destroyed and there is no promise to keep the world. A group building a coastal village might agree that homes and shared supplies are left alone. Let everyone know which kind of world they are joining. ## Work through the friend who misses the opening night Imagine Morgan can join on Friday and Sunday, while Alex plays most evenings. Decide whether Alex may gather and progress between group sessions, what Morgan gets on arriving late, and whether anyone may raid Morgan's base while they are away. Answer for your actual friends before choosing settings or plugins. 1. Agree whether fighting and raiding are part of this world, and where practice damage is allowed. 2. If raids are allowed, say whether an absent player's base is a target. Define how the group agrees a raid, rather than relying on everyone being in voice chat. 3. Choose how a late friend joins: start from scratch, use shared supplies or receive an agreed starter set. Keep the same offer for anyone in that position. 4. Decide who checks shared base upkeep between sessions. The tool cupboard needs the appropriate resources to prevent decay; leaving a base alone is not the same as keeping it intact. 5. Say whether this first world will be kept for another session or treated as disposable practice. If there will be a reset, name what you intend to reset and tell everyone before it happens. ## Turn the answers into a message you can use Here is an example agreement for the village group: “This world is for building together. Gather whenever you like. No player raids or taking supplies from someone else's home. New arrivals can use the shared starter box. Alex checks the village cupboard between sessions. We’ll talk before choosing an extra wipe and give everyone a heads-up when the game requires one.” Treat that as wording to adapt, not a game setting. A written no-raiding agreement asks your friends to cooperate; it does not itself prevent damage. If you want the server to enforce a restriction, check and test the relevant setup before telling people it is protected. Put the agreement in the group chat where everyone can find it. In Discord, pin the message. Keep the current answer in that message when the group changes its mind, so a returning friend does not have to read an evening of discussion. ## Check agreement before spending or starting Ask the friend with the least time to explain what they expect to find when they return. Then ask the keenest raider which base they may attack tonight. If those answers disagree with the message, settle that point before inviting people into the world. You are ready to choose hosting when the group agrees on the purpose, what can happen during someone's absence, and whether this first world is practice or progress to keep. After the first session, ask whether the arrangement made people want to come back. Change the agreement before the next session if it did not. ## Sources - [Facepunch explanation of tool cupboard upkeep and decay](https://wiki.facepunch.com/rust/the_tool_cupboard) - [Discord instructions for pinning a message in a channel or group chat](https://support.discord.com/hc/en-us/articles/221421867-Pin-Messages-FAQ) ## Related resources - [Host Rust at home or rent a server?](https://rustsc.com/learn/hosting/home-network-or-rented-rust-server/index.html.md) - [What should you check before advertising a Rust server as PvE?](https://rustsc.com/learn/configuration/check-what-pve-means-on-your-rust-server/index.html.md) - [What changes at your first Rust force wipe?](https://rustsc.com/learn/wipes/first-force-wipe-versus-elective-wipe/index.html.md) --- HTML version: https://rustsc.com/learn/community/agree-a-first-wipe-with-friends/ --- # Find which Rust plugin handles a chat command [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Start by writing down the command exactly as players type it and what answers. A command in game chat can have a different registration from a command entered in the server console. ## Carbon command lookup To look for /kit, try c.findchat kit in the server console. For a console command, use c.find with its name. Compare what the search returns with the aliases listed in the likely plugins' current settings. ## Oxide settings lookup For the same /kit question, start with the Commands section of each publisher's listing. Rust Kits documents its player chat commands separately from its administrative ones. Search the settings of the plugins that mention the chat name to see which aliases this server enables. ## Identify a collision without disturbing live players On a test copy, try the command as an ordinary player and record the response. Turn off one candidate and try again. If the response changes or the command vanishes, compare that result with its documentation before changing an alias. Give each feature a unique name if its plugin supports that. Retest both names with the same player and tell players which one to use. ## Sources - [Carbon chat and console command searches](https://carbonmod.gg/references/commands/) - [Oxide distinction between chat and console commands](https://docs.oxidemod.com/guides/owners/commands) - [Example Rust Kits command documentation](https://umod.org/plugins/rust-kits) ## Related resources - [Find and manage plugins](https://rustsc.com/support/guides/plugins/index.html.md) --- HTML version: https://rustsc.com/learn/community/find-which-plugin-owns-a-command/ --- # Set up Oxide group inheritance for junior and senior staff [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Put the permissions both staff levels need in a common parent group. Give more sensitive permissions only to the senior group. Oxide's child groups inherit every permission from their parent. ## Draw the relationship before adding permissions Suppose both groups need to read moderation reports and only leads should resolve them. Make a reports group with the read grant, then make leads its child. The leads group adds the resolve grant from the plugin's documentation. A player who should only read reports belongs to reports. In the Oxide server console, the parent relationship in this example is oxide.group parent leads reports. Read the current groups before applying that relationship if you already have a team setup. A group's title and rank are separate settings from its parent. ## Prove both sides of the boundary Use one test member in each group and check the read action on both. Try the resolve action on a test report and verify that only leads can do it. Use regular test accounts without separate grants or native Rust admin status. If a junior test account can resolve, start with oxide.show user followed by its identifier. Look for a direct grant, another group membership or an unexpectedly broad grant in a parent group before changing everyone else's permissions. ## Sources - [Oxide group inheritance and inspection commands](https://docs.oxidemod.com/guides/owners/permissions) - [Oxide permission command syntax](https://docs.oxidemod.com/core/commands/permission) ## Related resources - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/index.html.md) --- HTML version: https://rustsc.com/learn/community/oxide-group-inheritance-for-staff/ --- # How to write Rust server rules players can use [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Write rules around decisions players actually make. On a trio server, the number three is easy to understand. The question that needs an answer is whether a fourth person can defend the base or take an offline teammate’s place. ## Give a rule an example and a boundary Here is sample wording for one trio server. Adapt it to the game you want people to play and check it against the published Facepunch rules before posting. | Rule | Allowed here | Breaks the rule here | | --- | --- | --- | | Up to three people may work together in fights or base defence. | Trading at a shop. | A fourth player guarding your base while your trio raids. | | Use the private report route to raise a complaint about a player. | Discussing whether a published rule needs to change. | Naming a suspected cheater in public and asking others to pile on. | ## Check the cases players will ask about first For the trio example, decide how replacements, shared building access and temporary alliances work. Put those answers by the team limit. For player complaints, name the exact place to report and what someone who can no longer join should use. Ask a friend to read only the posted rules and explain what happens if a regular teammate is offline and a guest joins the next raid. If the friend needs to ask what you meant, edit that part. Give moderators the same copy players can see. ## Sources - [Facepunch Code of Conduct](https://facepunch.com/legal/code-of-conduct) - [Discord guidance on developing moderator guidelines](https://discord.com/safety/developing-moderator-guidelines) ## Related resources - [How to announce a Rust server rule change](https://rustsc.com/learn/community/announce-a-rust-server-rule-change/index.html.md) --- HTML version: https://rustsc.com/learn/community/write-rust-server-rules-players-can-use/ --- # How to announce a Rust server rule change [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) When a squad limit or raid rule changes, say exactly when it starts and what players already on the server need to do. A pinned replacement rule by itself gives returning players no way to tell which version applied to last night’s raid. ## Give teams a decision they can act on For example, say “The next map wipe starts our trio rule. Until the wipe, the current four-person limit applies. After the wipe, up to three players may share a base or fight as a team. See the updated rules for replacements.” Use the scheduled date and time with a time zone if players need advance notice. For a clarification, say which part of the posted rule was unclear and when moderators will start using the revised wording. Keep a private copy of what applied before the change so an appeal about an earlier incident can be checked against it. ## Make the notice and the rules agree Update the main rules page and any shortened copy players see when joining. In each announcement, link to the same rules page and tell staff how to answer the first likely question. For the trio change, that might be what happens when a fourth member connects after wipe. Ask a player who missed the discussion to find the rule and say what applies before and after the change. Fix the wording or link where they got lost. ## Sources - [Discord guidance on developing moderator guidelines](https://discord.com/safety/developing-moderator-guidelines) - [Discord guidance on transparency in moderation](https://discord.com/safety/transparency-in-moderation) ## Related resources - [How to write Rust server rules players can use](https://rustsc.com/learn/community/write-rust-server-rules-players-can-use/index.html.md) --- HTML version: https://rustsc.com/learn/community/announce-a-rust-server-rule-change/ --- # Where should players send reports about your Rust server? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Put one private way to contact your moderators beside your server rules. Facepunch also accepts reports about suspected cheating and abuse through Rust’s in-game tools. Explain both routes so players know where to send a local rule complaint. ## Ask for details that locate the incident Try this prompt. “Tell us the server name, roughly when it happened and your time zone, the player involved, and what you saw. Include a clip or screenshot if you already have one. Keep the report in this conversation.” Add a useful clue for a typical report. For example, ask for the map grid and what each person was doing in a report about a team limit. If someone gives you only a name, ask for the server and time before searching through player records. Keep replies in the same place so another moderator can take over. ## Try it as a new player Ask a friend to start at the public rules and submit a clearly labelled practice report using your community’s route. Check that the moderators responsible for that server can find it and respond. Ask another ordinary member to confirm that they cannot see the report. Try the same journey while outside the game. A player who was kicked or cannot connect still needs to find your contact instructions. ## Sources - [Facepunch reporting tools in Rust](https://support.facepunchstudios.com/hc/en-us/articles/10640775389853-Reporting-in-Rust) - [Discord guidance on confidentiality in moderation](https://discord.com/safety/confidentiality-in-moderation) ## Related resources - [How to triage Rust player reports](https://rustsc.com/learn/community/triage-rust-player-reports/index.html.md) --- HTML version: https://rustsc.com/learn/community/give-rust-players-a-private-report-route/ --- # How to triage Rust player reports [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Start with what is still happening. A report about ongoing harassment may need immediate staff attention. A report about a fight last night can usually wait while you establish who was involved and find the relevant records. ## Make the first decision for each report Use whatever private staff space you already check. Record what the player reported in their own terms, then add what staff confirmed. A short entry such as “Player reports abuse in voice near Outpost. No staff witness. Asked for time and account” gives the next moderator a specific place to start. | What came in | Next check | | --- | --- | | Harassment in public chat that appears to be ongoing. | Check the current chat and apply your published policy to anything you can verify. | | Possible cheating in a fight with no time or location. | Ask for the approximate time and the server. Point the witness to Rust’s in-game reporting tools. | | An old team-limit complaint with a timestamp and clip. | Check which rule applied then and assign one moderator to review the clip. | ## Leave a clear status before moving on Mark the case with the next check and who is doing it. If there is nothing further you can check, record what was missing and close the case without a penalty. An acknowledgement such as “We’ve received this and will review it privately” sets an expectation you can meet. ## Sources - [Facepunch reporting tools in Rust](https://support.facepunchstudios.com/hc/en-us/articles/10640775389853-Reporting-in-Rust) - [Discord guidance on managing moderation teams](https://discord.com/safety/managing-moderation-teams) ## Related resources - [What does a Rust team-limit report actually show?](https://rustsc.com/learn/community/check-a-rust-team-limit-report/index.html.md) - [How to hand over an open Rust moderation case](https://rustsc.com/learn/community/hand-over-an-open-rust-moderation-case/index.html.md) --- HTML version: https://rustsc.com/learn/community/triage-rust-player-reports/ --- # What does a Rust team-limit report actually show? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Four characters standing by a base may be one team, or the fourth may be a stranger who ran up to the fight. Start by writing what the clip shows, then compare it with what your team limit actually prohibits. ## Work through a sample raid report A player on a trio server sends a clip and says “four of them raided us.” The clip starts midway through a fight. Three players move together and a fourth appears, but the recording ends before it is clear who the fourth person is shooting at. Check the server, time and rule in effect. Look for clear account matches in relevant records, if available. Ask for the part of the recording immediately before and after the clip. If it shows the fourth player attacking the raiders, that changes the account of events. If it shows the fourth player repeatedly covering the raiders as they push into the same base, check that staff can identify those accounts and compare their actions with the rule. ## Write what would let another moderator reach the same decision If all you can verify is that four players were present, the example record could read “Four visible near the target base. Fourth player’s role unclear. Asked for the longer clip. No action taken on the team limit.” If you do act after further checks, keep the relevant excerpt and explain the conduct that crossed the published boundary. If two display names are alike, match the account before acting. Steam assigns the account a stable Steam ID while the player may change their displayed name. ## Sources - [Steam Support explanation of Steam IDs](https://help.steampowered.com/en/faqs/view/2816-BE67-5B69-0FEC) - [Discord guidance on developing moderator guidelines](https://discord.com/safety/developing-moderator-guidelines) ## Related resources - [How to write Rust server rules players can use](https://rustsc.com/learn/community/write-rust-server-rules-players-can-use/index.html.md) - [How to triage Rust player reports](https://rustsc.com/learn/community/triage-rust-player-reports/index.html.md) --- HTML version: https://rustsc.com/learn/community/check-a-rust-team-limit-report/ --- # What to do when several Rust players report the same incident [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) If several reports concern the same fight, give one moderator the case. Keep track of who saw what. Five players sharing one clip still gives you one recording of the fight. ## Group by the incident players describe Match the server, time, location and accounts. Two reports about the same name during the same wipe could describe different fights. If the details differ, keep them open separately until someone can explain the difference. Write a short summary for the incident and link to the individual reports in your private staff notes. Identify the original clip and any independent views. For example, a player who saw the fight from outside the base may be able to answer a question that the shared clip leaves open. ## Keep the decision attached to the evidence Have the assigned moderator make one decision about that incident. If a new report adds a different allegation, say what else needs checking. If it only forwards the original clip, record that it was reviewed with the existing incident and acknowledge the player privately. As a check, ask another moderator to name the rule in question, the evidence that was reviewed and the remaining uncertainty from the summary alone. They should be able to do that without counting the reports. ## Sources - [Facepunch reporting tools in Rust](https://support.facepunchstudios.com/hc/en-us/articles/10640775389853-Reporting-in-Rust) - [Discord guidance on confidentiality in moderation](https://discord.com/safety/confidentiality-in-moderation) ## Related resources - [What does a Rust team-limit report actually show?](https://rustsc.com/learn/community/check-a-rust-team-limit-report/index.html.md) --- HTML version: https://rustsc.com/learn/community/handle-duplicate-rust-player-reports/ --- # How to review a ban appeal for your Rust server [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Publish a private appeal route that works for someone who cannot join the game. Use it for bans your own staff issued. Confirm who imposed the restriction before deciding who can review it. ## Give the reviewer the original decision Ask the player to share the server, their Steam ID and the appeal reason through that private route. Let another moderator review the appeal when someone else is available. On a solo server, reopen the evidence and read the player’s account before rechecking your first decision. 1. Find the restriction and confirm the account, affected server and recorded reason. 2. Read the rule that applied at the time and the evidence used to make the decision. 3. Compare the appeal with the evidence and record whether the restriction stays, changes or is removed. 4. Send the player the outcome privately and check that the restriction matches your decision. ## Line up the evidence before comparing stories Suppose a player appealing a ban on Bracken says they were disconnected before a raid. The original case lists 20:16, but the clip has no time zone. A separate staff note identifies a name seen on screen. Ask for the full clip or an original timestamp with its time zone, and check whether records can tie the name to the account in the appeal. | Information | What it establishes | | --- | --- | | The clip shows a breach at the east gate. | The incident happened. Relating it to a particular account needs additional evidence. | | The report calls the timestamp local, and the original reviewer confirms the time zone. | Convert to the same reference as the join records before deciding which connection overlaps. | | After conversion the account in the appeal left before the breach, and the staff note only has a display name. | The evidence does not support keeping this particular local ban. Record why the timing and identity evidence changed the result. | ## Give the player a reason they can understand For example, “We removed the ban. The recording confirmed the raid but did not identify your account as one of the raiders. You can try joining again.” If you keep a temporary ban, tell the player which rule applied and when the ban ends, using a time zone. Keep the reply about the decision and the player’s own account. Keep other reporters’ details in the private case notes. ## Check the decision on the affected world If the appeal is upheld, apply the agreed reversal in the tool that actually enforces the ban. Ask the player to try the affected server and report the exact message if it still rejects them. A separate host or platform restriction can have a different owner. Keep the appeal open until you can explain the remaining result. If you keep the ban, record its duration, scope and plain reason. Check a temporary decision uses the intended end time and that the player's reply says which world or worlds it covers. ## Sources - [Facepunch: reporting in Rust](https://support.facepunchstudios.com/hc/en-us/articles/10640775389853-Reporting-in-Rust) - [Discord guidance on private moderation appeals](https://discord.com/safety/transparency-in-moderation) ## Related resources - [How to correct a moderation mistake on your Rust server](https://rustsc.com/learn/community/correct-a-rust-moderation-mistake/index.html.md) - [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/index.html.md) - [Help a player in game](https://rustsc.com/support/guides/player-actions/index.html.md) --- HTML version: https://rustsc.com/learn/community/run-a-rust-community-ban-appeal/ --- # How to correct a moderation mistake on your Rust server [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) If a moderator banned the wrong account, first remove the restriction from the account that was wrongly affected. Then fix the record staff will use the next time that player is reported. ## Correct every place the decision took effect Match the affected player by Steam ID and find each server or channel where staff applied the decision. Reverse the restrictions from that decision. Check the local ban list for the same Steam ID, and check the Discord account separately if the mistake also affected access there. Add a correction beside the original case note explaining what was reversed and why. Make it clear that the original entry cannot count as a prior offence. If you review the initial allegation again, build the decision from verified evidence about the correct account. ## Reply where the mistake affected the player Tell the player privately what changed. For example, “We matched the wrong account to the report. Your ban was removed. Try joining the server again and reply here if you still cannot connect.” If staff made a public accusation, correct that statement where people saw it. Say that the earlier announcement named the wrong account and has been corrected. Keep private reports and the identity of other people involved out of that message. ## Sources - [Facepunch reference for viewing the game’s ban list](https://wiki.facepunch.com/rust/useful_commands) - [Discord guidance on transparency in moderation](https://discord.com/safety/transparency-in-moderation) - [Discord guidance on managing moderation teams](https://discord.com/safety/managing-moderation-teams) ## Related resources - [How to review a ban appeal for your Rust server](https://rustsc.com/learn/community/run-a-rust-community-ban-appeal/index.html.md) --- HTML version: https://rustsc.com/learn/community/correct-a-rust-moderation-mistake/ --- # What should a Rust moderator tell players about a report? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) A reporter needs to know their concern reached staff. The person who receives a penalty needs to understand the reason and how to appeal. The wider community can usually use a reminder of the rule. ## Use a different reply for each audience Suppose a player reports targeted name-calling in global chat and staff can verify enough to enforce the server’s rule. Put the full decision in the private staff notes, then answer each person in the place they can use. | Who | Example reply | | --- | --- | | Reporter | Thanks for reporting this. We reviewed the chat and handled it privately. | | Player receiving the action | Your chat restriction is for repeated personal insults in global chat. Reply here if you want us to review it. | | Public channel | Keep chat about the game. Send complaints about other players through our private report route. | ## Read the reply as the person who will get it Before sending, check for the reporter’s name, screenshots that reveal bystanders and details from unrelated cases. Remove those if the recipient has no reason to see them. Give the penalised player enough context to identify the incident and challenge the decision privately. ## Sources - [Discord guidance on confidentiality in moderation](https://discord.com/safety/confidentiality-in-moderation) - [Discord guidance on transparency in moderation](https://discord.com/safety/transparency-in-moderation) ## Related resources - [Where should players send reports about your Rust server?](https://rustsc.com/learn/community/give-rust-players-a-private-report-route/index.html.md) --- HTML version: https://rustsc.com/learn/community/share-rust-moderation-decisions-without-exposing-reports/ --- # Who should handle a Rust player report? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Start with where the behaviour happened and which rule it may break. A report can need both a local response and a report to the service that can investigate it. ## Choose who can act on the report Give volunteers this short reference. For cases they cannot resolve within their role, tell them how to reach the person who owns the next decision. | Situation | Route | | --- | --- | | A fourth player may have joined a trio’s raid. | Your Rust moderation team reviews the local team rule. | | A player suspects cheating in a fight. | Ask the witness to use Rust’s in-game reporting tools. Your team can separately review what it can verify on your server. | | An abusive message in Discord appears to break its guidelines. | Report the conduct to Discord. Local moderators can also act on the message in their own community. | ## Make sure one person owns the follow-up When handing off a report internally, say why it is beyond your role, what is still happening and what action you have already taken. For example, “I’ve paused the public discussion. Please review whether the linked message needs a separate Discord report.” Keep private details with the people handling the case. ## Sources - [Facepunch reporting tools in Rust](https://support.facepunchstudios.com/hc/en-us/articles/10640775389853-Reporting-in-Rust) - [Discord instructions for reporting abusive behaviour](https://discord.com/safety/360044103651-reporting-abusive-behavior-to-discord) ## Related resources - [How to triage Rust player reports](https://rustsc.com/learn/community/triage-rust-player-reports/index.html.md) --- HTML version: https://rustsc.com/learn/community/escalate-rust-player-reports-to-the-right-place/ --- # Who handles a report involving a Rust moderator’s own team? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) When your own teammate, rival or raid is part of a complaint, hand the decision to someone who was outside the fight. A clear handoff protects the player and leaves the moderator free to give their own account of what happened. ## Say what happened and who will review it If you were on the raid, send the facts you witnessed and tell the reviewer you were involved. A short message is enough. “This report concerns a raid I took part in. I’ve linked the original report and added my account. Please handle the decision and reply.” Give the reviewer access to the original material and leave space for them to ask their own questions. If a report concerns staff actions, give players a way to reach the owner that works without the moderator being reported. ## Handle urgent behaviour while the case is reassigned If the dispute moves to public chat and a player shares personal information, address that immediate behaviour using the rules. Record what you did and pass the original disagreement to the reviewer. If you run the server alone and the complaint can wait, pause before imposing a lasting penalty. Tell the player who is reviewing it and compare their account with the rule and whatever evidence you can verify. ## Sources - [Discord guidance on confidentiality and conflicts in moderation](https://discord.com/safety/confidentiality-in-moderation) - [Facepunch Code of Conduct](https://facepunch.com/legal/code-of-conduct) ## Related resources - [How to hand over an open Rust moderation case](https://rustsc.com/learn/community/hand-over-an-open-rust-moderation-case/index.html.md) --- HTML version: https://rustsc.com/learn/community/when-a-rust-moderator-should-step-aside/ --- # Onboard your first Rust moderator without sharing your login [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Start your first moderator with their own account and a clear job. Give them a short role sheet, show them where reports go and practise one together. Keep your owner login with you so adding a volunteer does not mean handing over the whole server. ## Copy this role sheet into your staff space These are example duties for a small community. Replace each name and server, then agree which player actions your moderator can take. The labels describe jobs, not permission settings you can copy into every tool. | Job and person | Can handle | Pass to | | --- | --- | --- | | Owner: Rowan. Harbour Trio. | Server changes, staff access and reviews of staff decisions. | An agreed backup contact while unavailable. | | Moderator: Kai. Harbour Trio. | Private player reports, missing evidence and actions named in the staff rules. | Rowan for appeals, unclear rules or reports involving Kai’s own team. | | Event helper: Erin. Saturday build night. | Welcome arrivals, explain the event and post agreed updates. | Kai for conduct complaints; Rowan for changes to the game. | ## Give each person access for their job Use each tool’s individual membership or staff access where available. Give Kai the private report space and the moderation tools you have agreed to use. Erin may need only the event channels. Neither job needs your sign-in, recovery codes or hosting password. Discord roles, Rust game staff and a management tool’s roles are separate. A Discord role called Moderator does not by itself make someone game staff. Discord’s Administrator permission grants all permissions and bypasses channel restrictions, so leave it off for a helper who only needs a few channels. In RustSC, use a separate workspace membership and check the role’s actual permissions. The Moderator role can manage players and bans. A note saying ‘ask me before banning’ does not remove that ability. Use the linked role and access guides to choose what fits your arrangement. ## Rehearse a report before the first shift Use a private practice report for this exercise. Ask the event helper to open the event information from their own account and check that the private report stays out of view. 1. Put the player rules, private report link and owner contact beside the role sheet. Ask Kai to open them using their own account. 2. Send a labelled practice report: ‘Four people raided us. Here is a short clip.’ Leave out the server and time. 3. Have Kai reply: ‘Which server was this on, and what time with time zone? Please send the full clip in this report.’ No real player needs a punishment for the exercise. 4. Add that one raider is Kai’s teammate. Have Kai pass the report to Rowan with the evidence and the next decision. ## Leave a clear end to the shift Once Kai can reply to the practice report and hand it over from their own account, agree when they will be available and who receives unfinished reports. After the first shift, read one reply together and ask what was difficult to find or decide. Update the same role sheet so the next volunteer starts with the answer. ## Agree what the volunteer owns by the end of week one Rowan and Kai fill in a first-week sheet together. If the role technically lets Kai do more than the sheet says, check whether a narrower supported role fits. The duty agreement tells everyone who decides. The permission check tells you what the account can do. | Duty | Check from Kai's account | Owner at the end of week one | | --- | --- | --- | | Acknowledge reports on Harbour Trio. | Kai opens a private test report and replies using a practice account. Erin cannot see it. | Kai during the named shift. Rowan owns the alternate shift. | | Pass a proposed ban for review. | Kai sends Rowan the rule and the minimum facts in private. Rowan confirms receipt. | Rowan decides bans under this first-week agreement. | | Ask for a server restart after maintenance. | Kai can reach Rowan by the agreed contact. Verify the role's actual restart permissions separately. | Rowan makes any restart decision. | ## Set a review date on the sheet Record the day you will revisit the roles and one change you expect to consider. On Sunday, Rowan and Kai review a practice reply and discover that Kai knows how to post it but did not know which person covers Rowan's absence. Write the backup's name next to the escalation path. Close the first week by asking Kai to describe their next shift and who owns each decision they cannot make alone. ## Sources - [Discord guidance on training new moderators](https://discord.com/safety/training-and-onboarding-new-moderators) - [Discord documentation on roles and the Administrator permission](https://support.discord.com/hc/en-us/articles/214836687-Discord-Roles-and-Permissions) ## Related resources - [What access does your Rust moderator actually need?](https://rustsc.com/learn/community/choose-access-for-a-rust-moderator/index.html.md) - [How to hand over an open Rust moderation case](https://rustsc.com/learn/community/hand-over-an-open-rust-moderation-case/index.html.md) - [Understand workspace roles](https://rustsc.com/support/guides/workspace-roles/index.html.md) - [Give someone access to only some servers or hosts](https://rustsc.com/support/guides/limited-access/index.html.md) - [Run a shadow shift for a new Rust moderator](https://rustsc.com/learn/community/run-a-shadow-shift-for-a-rust-moderator/index.html.md) --- HTML version: https://rustsc.com/learn/community/onboard-a-first-rust-server-moderator/ --- # What to check when a Rust server moderator leaves [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Before someone leaves the moderation team, list the places they used to do the job. Their Rust staff assignment, community chat roles and hosting access each need their own check. ## Keep the team’s work reachable Ask for open cases and the next step on each. Assign a new contact for each case, and check that the new contact can reach the notes and evidence. If access must end immediately, use the records already available to the owner and assign a new contact as soon as possible. 1. On every game server they helped run, remove their Rust staff role and any staff permissions granted by a plugin, whether given directly or through a framework group. 2. Remove their staff roles and any individual access to restricted community channels. 3. Remove their individual access to the hosting panel, moderation tools and any team records. 4. Replace shared credentials they could still use and update the tools that rely on them. ## Walk through a friendly departure Say Kai is stepping down from staff on Harbour Trio but will keep playing. Rowan confirms which staff duties end on Sunday. A private case still needs an evidence reply and a named helper must take over the Sunday report check. | Place to check | Harbour Trio's closeout | | --- | --- | | Open case and rota | Rowan assigns Sam the unfinished case and next shift. Sam confirms access to the notes and the next player reply owed. | | Rust and framework roles | Rowan checks the game staff list and both direct and group-based staff access on every affected world. Kai keeps ordinary player access. | | Discord and private records | Rowan removes staff roles and any separate channel or shared-document grants. Kai stays in the ordinary community channels. | | RustSC and hosting tools | Rowan checks memberships and roles in each place Kai used. Where a shared login is being retired, a remaining staff member checks the tools that depend on it after replacement. | ## Verify the remaining access Use the account lists to check the former moderator’s Rust role and any plugin permissions that still apply. In Discord, check direct channel access as well as roles. Confirm a remaining moderator can handle a test report. If the former moderator is staying as a player, compare their remaining access with what an ordinary player receives. ## Have the new moderator take the next action Ask Sam to open a practice report and state the next step on the unfinished case. From the owner side, reread the former staff assignments and check for permissions still inherited through a different role. If the team can arrange a cooperative, ordinary-player check, ask Kai only to confirm access they should retain. End the handoff when Sam can do the agreed work and Kai's remaining grants match the ordinary role. ## Sources - [Facepunch documentation on Rust game staff access](https://wiki.facepunch.com/rust/Creating-a-server) - [Oxide documentation on direct and inherited plugin permissions](https://docs.oxidemod.com/guides/owners/permissions) - [Discord documentation on roles and channel permissions](https://support.discord.com/hc/en-us/articles/214836687-Discord-Roles-and-Permissions) ## Related resources - [How to check a Rust moderator’s access after a role change](https://rustsc.com/learn/community/verify-a-rust-moderator-access-change/index.html.md) - [Understand workspace roles](https://rustsc.com/support/guides/workspace-roles/index.html.md) - [How to hand over an open Rust moderation case](https://rustsc.com/learn/community/hand-over-an-open-rust-moderation-case/index.html.md) --- HTML version: https://rustsc.com/learn/community/remove-rust-server-staff-access-when-someone-leaves/ --- # What access does your Rust moderator actually need? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Start with the work you want a person to do. A volunteer who responds to player reports may be able to do the entire job in a private report space. Decide separately who should need access in the game, the hosting panel or Discord. ## Tie each grant to a specific task Use these sample assignments to make a short list for your own team. Include the server or Discord channels the person covers. | Job | Access to consider | Decision to keep with the owner | | --- | --- | --- | | Collect missing details on reports. | Read and reply in the private report space. | Whether to apply a lasting server ban. | | Keep community chat readable. | Moderate the channels they cover and refer larger cases to the owner. | Changes to staff roles or community-wide settings. | | Handle Rust player actions during a shift. | Use a tool that allows the specific actions on that server, if available. | Granting broader game staff or host control. | ## Write down where their job ends If the tool only offers broader access than the volunteer needs, keep those actions with the owner and tell the volunteer how to reach you. Check the proposed role against another server or private channel the volunteer should not be able to open. ## Sources - [Discord documentation on roles and channel permissions](https://support.discord.com/hc/en-us/articles/214836687-Discord-Roles-and-Permissions) - [Facepunch documentation on Rust game staff access](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [How to check a Rust moderator’s access after a role change](https://rustsc.com/learn/community/verify-a-rust-moderator-access-change/index.html.md) --- HTML version: https://rustsc.com/learn/community/choose-access-for-a-rust-moderator/ --- # How to check a Rust moderator’s access after a role change [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) After changing staff access, verify it from the member’s side. Seeing a role in your owner account tells you that it was assigned. The useful check is what the person can actually see or do. ## Check both sides of the change Write one expected success and one expected restriction before you begin. For example, a moderator for your trio server can read and reply to a practice report for that server. They should be unable to open the staff notes for your second server. Use Discord’s View Server As Role to preview channel visibility for the relevant roles. With the member’s cooperation, also check their real view because they may have other roles or a permission set for them individually. Use a labelled practice item to check a task without affecting real players. ## Trace unexpected access to its source If the member sees a restricted channel, check their other roles and individual access to that channel. In Discord, Administrator bypasses channel restrictions. For changes in Rust, check the account’s game staff entry and any relevant plugin permissions granted directly or through a group. Record which account and server or channel you checked and what you found. If you change another permission, repeat the same allowed and restricted checks. ## Sources - [Discord guide to viewing a server as a role](https://support.discord.com/hc/en-us/articles/360055709773-View-Server-As-Role-Permission-Guide) - [Oxide documentation on direct and inherited plugin permissions](https://docs.oxidemod.com/guides/owners/permissions) - [Discord documentation on roles and channel permissions](https://support.discord.com/hc/en-us/articles/214836687-Discord-Roles-and-Permissions) ## Related resources - [What access does your Rust moderator actually need?](https://rustsc.com/learn/community/choose-access-for-a-rust-moderator/index.html.md) --- HTML version: https://rustsc.com/learn/community/verify-a-rust-moderator-access-change/ --- # How to hand over an open Rust moderation case [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Before you log off, give one moderator the open case, the action already taken and the next decision. A forwarded screenshot alone leaves them guessing whether staff have already replied or restricted anyone. ## Make the handover usable on its own Here is a sample handover. “Trio server, 12 November around 20:15 UTC. Player reports a fourth raider. The clip shows four figures and leaves the fourth person’s role unclear. Asked for a longer clip in the original report. No restriction applied. Please review the reply and decide whether the rule was broken.” Link the original report and any relevant evidence the reviewer can access. If you took a temporary action, give its end time and zone. If the player is waiting for an update you promised, write down when you said you would reply. ## Keep one owner and one reply Ask the next moderator to acknowledge the case in the staff space. They can check that they can open the evidence, take ownership and reply in the existing conversation. If no one can take it, mark it for the owner with the remaining action and any deadline. ## Sources - [Discord guidance on managing moderation teams](https://discord.com/safety/managing-moderation-teams) - [Discord guidance on confidentiality in moderation](https://discord.com/safety/confidentiality-in-moderation) ## Related resources - [How to triage Rust player reports](https://rustsc.com/learn/community/triage-rust-player-reports/index.html.md) --- HTML version: https://rustsc.com/learn/community/hand-over-an-open-rust-moderation-case/ --- # Which Discord channels does a small Rust community need? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Start with a public place for current rules and announcements, a place for players to talk and one private way to contact staff. Give a new joiner the same path to ask a question as a player who already knows the owner. ## Name the channel for what a player does there A welcome message can point players to the rules and tell them how to report a problem. Use one place for the current information so you can correct an outdated link or rule once. | Place | Use it for | | --- | --- | | Rules and announcements | Current team rules, server information and notices. | | General chat | Looking for teammates, questions about the server and ordinary discussion. | | Private contact | A report or appeal visible only to the people handling it and the person submitting it. | | Staff notes | Restricted decisions and handovers for the moderators responsible. | ## Walk through the public and staff views Ask a friend with ordinary member access to locate the rules and use your private contact route. Check that the friend cannot open the staff notes or see other players’ reports. With a staff account, find the practice report and reply in the same place. ## Sources - [Discord documentation on roles and channel permissions](https://support.discord.com/hc/en-us/articles/214836687-Discord-Roles-and-Permissions) - [Discord guidance on confidentiality in moderation](https://discord.com/safety/confidentiality-in-moderation) ## Related resources - [Where should players send reports about your Rust server?](https://rustsc.com/learn/community/give-rust-players-a-private-report-route/index.html.md) - [What Rust chat should you share in Discord?](https://rustsc.com/learn/community/choose-which-rust-chat-to-share-in-discord/index.html.md) --- HTML version: https://rustsc.com/learn/community/organise-discord-channels-for-a-rust-community/ --- # What Rust chat should you share in Discord? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Treat a relay into Discord as a change in who can read a message. A player who types in Rust global chat may expect the people in the game to see it. A linked Discord channel may be visible to people who have never joined the game. ## Set the audience before connecting chat If you want to share game chat, start with a named Discord channel and the Rust global channel. Decide who can see the Discord channel and whether messages go back into the game. Keep team chat, reports and staff discussion out of the relay. Put the boundary where people type. For example, “Rust global chat is mirrored to #game-chat. People with access to that channel can read it.” If Discord replies go back into the game, say so in the Discord channel. ## Check the relay with harmless sample messages With a test server or consenting players, send separate labelled messages in global chat and team chat. Check that only the intended global message appears in Discord. Use ordinary member access to check who can see it. If you expect replies to go into the game, post a labelled reply and check the destination there too. If the audience or direction differs from what you advertised, pause the relay while you correct it. ## Sources - [Facepunch Rust Wiki on global and team chat](https://wiki.facepunch.com/rust/global_text_chat) - [Discord documentation on roles and channel permissions](https://support.discord.com/hc/en-us/articles/214836687-Discord-Roles-and-Permissions) ## Related resources - [Which Discord channels does a small Rust community need?](https://rustsc.com/learn/community/organise-discord-channels-for-a-rust-community/index.html.md) --- HTML version: https://rustsc.com/learn/community/choose-which-rust-chat-to-share-in-discord/ --- # How to help Rust players recognise real staff messages [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Publish one place where players can verify a staff message. If someone with a familiar display name sends a private link or demands an account code, the player can start from the contact route they already know. ## Make your verification message easy to follow Post a short note beside the rules. “Check staff requests through the private contact link on this rules page. We never ask for your password or sign-in code. If a message says to verify your account through a new link, contact us here first.” Use the same channel for official moderation replies and show the staff roles players should expect to see there. In Rust, check accounts by Steam ID when names are similar. Display names can change. ## Respond to an impersonation report Ask the player where the message appeared and which account sent it. Compare it with your actual staff list. If it was a Discord message, ask them to use the in-app reporting options for deceptive impersonation. If it was in Rust, point them to the in-game report tools. If other players received the same message, post a brief warning in the official channel that describes what to look for. Leave the suspicious link out of the warning. ## Sources - [Discord Community Guidelines on deceptive impersonation](https://discord.com/guidelines) - [Steam Support explanation of Steam IDs](https://help.steampowered.com/en/faqs/view/2816-BE67-5B69-0FEC) - [Facepunch reporting tools in Rust](https://support.facepunchstudios.com/hc/en-us/articles/10640775389853-Reporting-in-Rust) ## Related resources - [Which Discord channels does a small Rust community need?](https://rustsc.com/learn/community/organise-discord-channels-for-a-rust-community/index.html.md) --- HTML version: https://rustsc.com/learn/community/help-rust-players-recognise-real-staff-messages/ --- # What to say when a Rust raid argument takes over global chat [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Keep your first reply short enough to read while chat is moving. Tell players which behaviour needs to stop and where to send the complaint. ## Say what needs to stop in the channel For a raid dispute with personal insults, try “Stop the personal insults. If you think the raid broke a rule, send the details to staff through the report link in the rules.” Use the server’s wording for the rule and move on once the message is clear. For a heated discussion about the rules that has stayed civil, tell players where to send their feedback. For an ongoing clear violation, follow the action your rules set out. Record the relevant lines and any action staff took in the private case notes. ## Give players an immediate way to get some distance A player can select a name in Rust text chat to mute that person for themselves. Facepunch says this covers text and voice. If the player is being targeted, explain that option and give them the private report route so the team can look into what happened. Check whether the behaviour stopped. Follow up on any report in private and use the original context if the dispute comes back. ## Sources - [Facepunch guide to muting and censorship](https://support.facepunchstudios.com/hc/en-us/articles/10641641796253-Muting-and-Censorship) - [Facepunch Code of Conduct](https://facepunch.com/legal/code-of-conduct) - [Discord guidance on developing moderator guidelines](https://discord.com/safety/developing-moderator-guidelines) ## Related resources - [Where should players send reports about your Rust server?](https://rustsc.com/learn/community/give-rust-players-a-private-report-route/index.html.md) - [What should a Rust moderator tell players about a report?](https://rustsc.com/learn/community/share-rust-moderation-decisions-without-exposing-reports/index.html.md) --- HTML version: https://rustsc.com/learn/community/calm-a-rust-global-chat-argument/ --- # Where should your Rust players look when Discord is down? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Pick one place players can reach outside Discord. For a few friends, that can be the group chat you already use. If you run a public server with a website, put a short join page there so someone arriving for the first time can still find the game. ## Make the second route easy to find in advance Put the plain Rust join instruction and the place you’ll post event changes on the fallback page or in the group chat. Test that a player can open it without signing into Discord. For a public world, Facepunch documents a website setting and a description on the server connection window. Use the website field for a page players can reach, and tell regulars where to find it before Discord goes down. Ask someone to try joining Rust with Discord closed. If a link or invite sends them straight back into Discord, give them the game address and the event details at the fallback destination itself. ## Confirm what is still working Check Discord’s status page and ask a player to try the usual Rust join line. When the world is playable, post a short note in the fallback location, such as ‘North Pier is open. Find the build tour at the boathouse at 19:00 UTC. We’ll coordinate in game today.’ If the event depends on voice and you have no other way to run it, post the revised details in the same place. When Discord returns, copy the final event decision back there so people returning through the original announcement can catch up. ## Sources - [Discord service status page](https://discordstatus.com/) - [Facepunch server website and description settings](https://wiki.facepunch.com/rust/Creating-a-server) - [Google SRE guidance on communications during a service outage](https://sre.google/sre-book/emergency-response/) ## Related resources - [Keep one current Rust join post in Discord](https://rustsc.com/learn/community/one-current-rust-join-post/index.html.md) --- HTML version: https://rustsc.com/learn/community/keep-rust-players-informed-when-discord-is-down/ --- # Keep one current Rust join post in Discord [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Pin one join message and send its link whenever someone asks where to play. If the host changes the game port, edit that message. A player coming back through an old conversation will land on the current instruction. ## Put the player’s choices on separate lines Give each game server its own short block. Name it exactly as it appears in Rust and state what distinguishes it in player terms, such as ‘Evening Builds, PvE’ or ‘Harbour Solo, PvP’. Then give the browser tab and the full F1 `connect ADDRESS:PORT` instruction on a separate line so players can copy it easily. Have someone use that exact line and confirm which world they reach. Rustafied’s server directory offers an example of one place to look up several worlds. For a group with one server, a single pinned message is enough. ## Replace the routes people already use Find the old pinned address, the welcome message and any stock reply that contains a copy of the join line. Replace those copies with a link to the current post. If you have an old launch message you want to keep, add a note at the top pointing to the current post. Open the link as a regular Discord member. From a phone, check that reaching the message takes one tap and that players can tell which line belongs to which server without reading the rest of the channel. ## Sources - [Discord pinned messages and jumping to the original post](https://support.discord.com/hc/en-us/articles/221421867-Pin-Messages-FAQ) - [Facepunch instructions for connecting by address](https://wiki.facepunch.com/rust/Creating-a-server) - [Rustafied’s server directory](https://www.rustafied.com/server) ## Related resources - [What address should friends use to join your Rust server?](https://rustsc.com/learn/hosting/which-address-should-friends-use/index.html.md) --- HTML version: https://rustsc.com/learn/community/one-current-rust-join-post/ --- # Turn repeated Rust questions into answers players can find [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Start with the last few questions you answered twice in Discord. Give each answer a title in the words the player used, such as ‘Which world is open for build practice?’ One clear answer players can find saves a volunteer from sending the same reply on every shift. ## Turn the reply into a short reference Copy the question without the player’s name. Put the next action in the first sentence. If the question is about where to join, link to your join post so the answer survives an address change. If it is about a temporary event, link to that event and remove the reference from the active list when the event ends. Pin the answers in a small Discord server. If you already use a Community server and answers have ongoing discussions, use a forum channel with a simple tag such as ‘Joining’ or ‘Events’. Discord forum search and tags let players find an existing answer before opening another post. ## Try it on the next person who asks Send the answer link to the next player who asks. If they still need a follow-up, add the missing step to the answer while you have it in front of you. For example, if ‘Join the practice server’ sends players to your regular PvP world, add the exact practice server name and link to its connection block. Give each changing answer a maintainer. When practice night moves, the person who changes the event should also check the question players use to find it. ## Sources - [Discord forum channels, search and tags](https://support.discord.com/hc/en-us/articles/6208479917079-Forum-Channels-FAQ) - [Discord pinned messages](https://support.discord.com/hc/en-us/articles/221421867-Pin-Messages-FAQ) - [Rustafied player FAQ](https://www.rustafied.com/faqs) ## Related resources - [Keep one current Rust join post in Discord](https://rustsc.com/learn/community/one-current-rust-join-post/index.html.md) --- HTML version: https://rustsc.com/learn/community/turn-repeat-rust-questions-into-discord-answers/ --- # How to share Rust announcements with another Discord server [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) For regular shared notices, let your partner follow a dedicated Discord Announcement channel. Each community can receive the same published post while keeping conversations and local updates in its own channels. ## Send one test from the source to the destination Use a Discord server with Community enabled for the source Announcement channel. Give it a clear purpose, such as joint events and changes that affect both communities. Have someone in the other Discord select Follow and choose the destination channel. Ask them to confirm whether it should appear in their general updates or a channel specifically for partner events. Post a test, then use Publish. A message that stays unpublished only appears in the source channel. Have your partner check the delivered copy as a reader would, including whether its links open for people who have yet to join the source Discord. ## Agree on corrections before the first real post Edit the original when meeting instructions change. Discord updates the published copy in following servers. For a last-minute cancellation, publish a short new notice too so people have a fresh message to read. Discord removes role mentions such as `@everyone` from followed posts. If the partner wants to notify its event group, let them choose when to tag it locally. For a one-off event, give your partner a short announcement and a link they can test before sharing. ## Sources - [Discord publishing and editing Announcement posts](https://support.discord.com/hc/en-us/articles/360032008192-Announcement-Channel-FAQ) - [Discord Channel Following and destination setup](https://support.discord.com/hc/en-us/articles/360028384531-Channel-Following-FAQ) ## Related resources - [Run one Rust event with another community](https://rustsc.com/learn/community/one-rust-event-two-communities/index.html.md) --- HTML version: https://rustsc.com/learn/community/share-rust-updates-with-partner-discords/ --- # What to put in a new Rust server launch announcement [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) A player reading your launch post should be able to decide whether the server suits them and know where to look when it opens. State the format, the planned opening time and the link you’ll update when players can join. ## Describe the first playable evening Use the exact server name, region, play style and any team-size expectation that would change a player’s choice. Say whether existing worlds in the community will carry on as usual. In Rustafied’s original EU Main announcement, the team named the new world and separately explained that its existing EU server was being renamed and would carry on with its map and progression. For example, write ‘Harbour Solo opens Saturday at 19:00 UTC. It’s an EU vanilla PvP server for solo players. Evening Builds stays open as usual. We’ll post the join details in #join-rust when Harbour Solo is ready.’ Give the calendar date in a real post so a forwarded screenshot still makes sense. ## Send players to the current status Have one person publish the opening message after a regular player reaches the correct world. If the opening slips, edit the launch post and send a short update where you first announced it. Give a time for the next update when you can commit to one. An opening message can be one sentence. ‘Harbour Solo is open now. Use the Harbour Solo block in #join-rust.’ Keep the join instruction there so anyone who finds the launch announcement later has a current address. ## Sources - [Rustafied’s EU Main launch and EU Medium rename announcement](https://www.rustafied.com/updates/2016/8/29/an-exciting-week-ahead) - [Facepunch server browser information and joining instructions](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Keep one current Rust join post in Discord](https://rustsc.com/learn/community/one-current-rust-join-post/index.html.md) --- HTML version: https://rustsc.com/learn/community/write-a-rust-server-launch-announcement/ --- # What to do when a shout-out fills your Rust server [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) When a creator sends a crowd to your Rust server, first find out whether the people already inside can play. A full, playable world calls for a queue message. A world that players cannot load into needs a status update and a closer look before you send more people there. ## Check the game and Discord separately Ask one player already inside if movement and interactions are working. Ask someone at the door what they see when they try to join. Compare that with your player count and the slot limit. A working world with a queue can stay on the current settings. Facepunch documents `server.maxplayers` as the player cap and notes that more players increase CPU demands. If Discord is filling up with the same question, answer it in one visible post and have a helper point people there. If game joins are failing, pause further promotion and say which world is affected. Keep a known working alternative in the post only if players can join it and its play style is clear. ## Give the creator a line they can repeat For a full world, try ‘Harbour Solo is full and people are still playing. Use the normal join post for the queue. We’ll update #updates if we open more space.’ For a broken join, replace that instruction with when and where people should check again. Review the rush after it passes. If players inside were fine but the queue stayed long at several busy sessions, choose a capacity change you can test. If the queue cleared when the stream ended, keep the working limit and save the status message for the next rush. ## Sources - [Facepunch player slots and server requirements](https://wiki.facepunch.com/rust/Creating-a-server) - [Discord pins for keeping a message easy to find](https://support.discord.com/hc/en-us/articles/221421867-Pin-Messages-FAQ) ## Related resources - [What to tell players when your Rust server goes down](https://rustsc.com/learn/community/rust-outage-status-post/index.html.md) --- HTML version: https://rustsc.com/learn/community/rust-server-fills-after-a-shout-out/ --- # What to tell players when your Rust server goes down [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) As soon as you can confirm the player-facing problem, post it in the place your players already check. A message saying which Rust world is affected and when you’ll check in again gives players something to act on while you investigate. ## Post the symptom you have confirmed Name the affected world and describe what players see. If they can load into another one, name it explicitly. Give a time for your next message that you can keep even if you have nothing new to report. Anyone working on the server should know who is sending the updates. Try ‘Harbour Solo is refusing new joins. Evening Builds is reachable. We’re checking Harbour Solo and will post another update here at 20:30 UTC.’ If it is still down then, say so and give the next check-in. Keep follow-ups together so a player who missed the first post can catch up. ## Check from the player’s side before posting the all-clear Ask someone on a normal game client to connect using the join method in your announcement. If they load into the world but can’t move or interact, keep the update open and post that joining has improved while play is still affected. When the check passes, say which world is playable again and what players should do. For example, ‘Harbour Solo is open again. Rejoin using the usual address in #join-rust.’ Remove any pin that would lead late readers to the old outage message alone. ## Sources - [Google SRE guidance on incident communications and current state](https://sre.google/sre-book/managing-incidents/) - [Facepunch Rust client connection instructions](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [How to hand over a Rust server outage to another helper](https://rustsc.com/learn/management/hand-over-a-rust-server-outage/index.html.md) --- HTML version: https://rustsc.com/learn/community/rust-outage-status-post/ --- # Schedule an in-game Rust event in Discord [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Choose Somewhere Else when the actual event takes place inside Rust. Use the location and description to send players to the right game world. Players who select Interested can get a notification when you start the Discord event. ## Put the join path in the event Give the event a name that makes the activity clear, such as ‘Harbour Boat Race’. Include the exact server name, a link to the join instructions, a map grid or landmark, and when arrivals should be ready. If voice is useful for coordination, give the voice channel separately. Someone who only opens the event should still be able to find the course. 1. Open the Discord server menu, choose Create Event, then select Somewhere Else. 2. Set the time and enter the server name or a link to the join post as the location. Add the in-game meeting details in the description. 3. Create the event and ask a player to open it and find both the Rust join instructions and the meeting point. ## Start the event when the world is ready Open Events, find the entry and use Start Event when players can follow the posted instructions. If you are running late, update the time and post the change where you shared the original link. For people outside your Discord, use the event invite if you want them to be able to join the Discord server as well. A direct event link requires them to be in the server and able to see it. ## Sources - [Discord Scheduled Events, external locations and link types](https://support.discord.com/hc/en-us/articles/4409494125719-Scheduled-Events) - [Facepunch direct join in the Rust client](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Will enough players show up for your Rust event?](https://rustsc.com/learn/community/rust-event-attendance-before-you-commit/index.html.md) --- HTML version: https://rustsc.com/learn/community/schedule-a-rust-game-event-in-discord/ --- # Will enough players show up for your Rust event? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Pick a minimum turnout from the activity itself. If your boat race only works with two crews on the water, count confirmed crew members before doing the setup. Treat Discord’s Interested count as a list of people who want a reminder. ## Ask about availability before asking for a commitment Offer two times the host can make and ask players to vote for every slot they can attend. Discord polls can accept several answers from one voter. Once you pick the slot, ask for a confirmation in the event thread with a reply deadline. For team activities, ask each captain for a count of people who have actually said yes. Confirm the format after the deadline. ‘We need two crews of three for the race. Reply by Friday evening with your crew count. With fewer people, we’ll run timed practice laps on the same course.’ Choose counts and a deadline that suit your event. ## Make low turnout an ordinary decision Tell people which format is happening in the event description and the signup thread. If you reach the minimum, say when crews need to be on the water. If you switch to the smaller version, update the description before pressing Start Event so anyone arriving from the reminder sees the new schedule. If the same slot repeatedly falls short, ask whether the start time, format or prep work makes it difficult to attend. Use the answers to choose the next test. ## Sources - [Discord polls with multiple answers](https://support.discord.com/hc/en-us/articles/22163184112407-Polls-FAQ) - [Discord Scheduled Events and the Interested reminder](https://support.discord.com/hc/en-us/articles/4409494125719-Scheduled-Events) ## Related resources - [Schedule an in-game Rust event in Discord](https://rustsc.com/learn/community/schedule-a-rust-game-event-in-discord/index.html.md) - [How to run signups for a Rust event with limited spots](https://rustsc.com/learn/community/rust-event-spots-and-waitlist/index.html.md) --- HTML version: https://rustsc.com/learn/community/rust-event-attendance-before-you-commit/ --- # How to run signups for a Rust event with limited spots [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Work out what limits your event before you promise a spot. A public server may have no spare game slots even when there’s room in your boat race or build tour. Count what the whole server can support and what the activity can handle. ## Count the space the event actually has For a build tour, walk the route with the guides and decide how many people can follow the briefing and stay together. Leave room for the guides and anyone already playing in the world when you compare that number with your game’s slot limit. If regular players can fill the server, explain that an activity spot depends on getting into the game. Rustafied’s published Charitable Rust schedule in 2020 gave players separate server entries for different parts of its event. For a small group, a second run on the same course may be simpler than a second server. ## Give signups a cut-off and a substitute list Ask players to reply with the name you can use to find them in-game and the session they want. Post confirmations and the waitlist in the signup thread. Confirm one person at a time from the waitlist when someone drops out, and say when they need to reply. Try ‘The first tour has eight places. Check in with the guide by 19:00 UTC. At 19:05 we’ll offer unclaimed places to the waitlist in signup order.’ If the game itself is full, tell the next person to join the queue and offer the later run if one is available. ## Sources - [Facepunch server player capacity](https://wiki.facepunch.com/rust/Creating-a-server) - [Rustafied’s Charitable Rust event server checklist](https://www.rustafied.com/updates/2020/11/21/charitable-rust-is-today) - [Discord threads for event signups](https://support.discord.com/hc/en-us/articles/4403205878423-Threads-FAQ) ## Related resources - [Will enough players show up for your Rust event?](https://rustsc.com/learn/community/rust-event-attendance-before-you-commit/index.html.md) --- HTML version: https://rustsc.com/learn/community/rust-event-spots-and-waitlist/ --- # Help late players catch up at a Rust community event [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Write down where a late player should go before you start the event. The original meeting grid can stop being useful the moment a build tour sets off. A named regroup point or next round gives them a way in without making everyone repeat the opening briefing. ## Choose a catch-up point that suits the format For a tour, pick a second landmark you know the group will pass. For a round-based event, leave one place near the start where players can wait for the next round. Describe what to bring and how to get there from a normal spawn, especially if the route passes through regular PvP areas. Open the in-game map with G on the default controls and check the landmark and grid in the actual world. If the meeting point is a player build, describe how to recognise it from a named landmark, since someone joining late might never have seen the build. ## Send one live instruction during the event Ask a helper to post where late players should go as the group leaves the start. Try ‘The tour has left the boathouse. Meet the guide at the Lighthouse in H12 for the next stop. If you miss us there, the next tour starts at 21:00 UTC.’ If the route changes, edit that instruction or post the replacement in the same event thread. When there’s no next round, say the activity is finished and give the next gathering if there is one. ## Sources - [Facepunch guide to opening the Rust map and finding monuments](https://wiki.facepunch.com/rust/map) - [Discord threads for keeping event instructions together](https://support.discord.com/hc/en-us/articles/4403205878423-Threads-FAQ) ## Related resources - [Schedule an in-game Rust event in Discord](https://rustsc.com/learn/community/schedule-a-rust-game-event-in-discord/index.html.md) --- HTML version: https://rustsc.com/learn/community/help-late-players-join-a-rust-event/ --- # Run one Rust event with another community [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Agree on one Rust world and one place to read the current event details before either Discord announces the event. Each community can introduce it in its own voice while sending players to the same time, joining instructions and fallback. ## Agree which jobs each community owns Have the game host verify the world, its meeting point and playable capacity. Give each Discord one contact who can publish changes and answer their own members. If there is a separate livestream, name where that will happen as well. Facepunch’s 2023 Charitable Rust announcement illustrates the value of naming the official stream even when multiple creators are taking part. If you use a Discord event as the shared reference, check what members of the partner Discord can see. Use an Event Server Invite when they are welcome to join the hosting Discord. If partners will stay in their own Discords, share a page they can open or put the essential details in both posts. ## Test the two announcements together Swap drafts and have one person from each side follow the other post. Both should reach the same game world and see who to ask if the meeting point changes. Agree on one person to call a delay or cancellation, then have each Discord contact acknowledge that they posted it. The shared brief can fit on one screen. Include the playable world, start time, join path, gathering point, who calls changes, and the channel each community will use for updates. ## Sources - [Facepunch coverage of Charitable Rust’s 2023 event and central stream](https://rust.facepunch.com/news/community-update-256) - [Discord event invites and direct event links](https://support.discord.com/hc/en-us/articles/4409494125719-Scheduled-Events) ## Related resources - [How to share Rust announcements with another Discord server](https://rustsc.com/learn/community/share-rust-updates-with-partner-discords/index.html.md) --- HTML version: https://rustsc.com/learn/community/one-rust-event-two-communities/ --- # How to tell players your Rust server is closing [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Say which Rust world is closing and give the last date and time people can join it. If your other worlds will stay open, name them. Retirement can look like an outage to someone coming back weeks later, so leave the answer where they used to find the address. ## Give players time to finish what matters to them Post the decision where the people on that world will see it and mention it in-game if you expect regulars to miss Discord. Offer a last gathering or a chance to capture screenshots if you can support it. In 2023 Rustafied tied the closure of its BR servers to the arrival of the January game update and discussed changes to its other servers separately. An example notice is ‘North Pier closes Sunday at 21:00 UTC. Join before then to visit your builds one last time. Our Discord stays open. Evening Builds is a separate world where members can start again.’ Include the date and explain what will happen to progress if you offer another world. ## Check the old links after closing Replace the closed world’s join block with the closure date and any suggested next step. Update event invitations, profile links and partner posts that still send people there. If the Discord will close too, give that its own date so players have time to reach each other. Open the old welcome link the next day as a member. It should lead to the closure notice or the world that remains open. Where a partner shared the address directly, ask them to update their old post too. ## Sources - [Rustafied’s public closure notice for its BR servers](https://www.rustafied.com/updates/2023/1/5/hello-2023) - [Discord pinning and finding a message later](https://support.discord.com/hc/en-us/articles/221421867-Pin-Messages-FAQ) ## Related resources - [What to do with Discord after your Rust community winds down](https://rustsc.com/learn/community/wind-down-a-rust-community-discord/index.html.md) --- HTML version: https://rustsc.com/learn/community/tell-players-a-rust-server-is-closing/ --- # What to do with Discord after your Rust community winds down [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) After the last Rust session, ask whether people still want a place to meet. If someone wants to keep hosting game nights, agree who will look after the Discord. If the group is ending, set a date to close it so members can exchange contact details and keep the memories they want. ## Decide who will look after the space If the group will keep meeting, agree who’ll take responsibility and review the events and links that still point to the old Rust world. For a permanent handoff, confirm the exact account with the new owner before choosing Transfer Ownership from the Discord member list. Discord Support cannot reverse a completed transfer. Ask the new owner to confirm they can see the ownership controls, then announce the handoff. If you just want to leave the old notices available for a while, put the final message at the top of a channel members can see. Remove any old invitation you posted elsewhere that still promises an active Rust server. Check the remaining notice as a member who missed the last session. ## Give members a last day to collect what they want Use a dated post to say what happens to the Discord and where friends can regroup. Invite people to download their own clips and screenshots before that date. If you assemble a farewell album, keep copies of the images outside the old server and share only material people meant to make public. Deleting the Discord server is permanent. Before using Delete Server, ask a member to open the regroup destination and any shared album without using links to messages or files in the old server. If something still relies on that server, copy it to its new home and check it again. ## Sources - [Discord ownership transfer instructions](https://support.discord.com/hc/en-us/articles/216273938-How-to-Transfer-Ownership-of-a-Discord-Server) - [Discord server deletion and what members lose](https://support.discord.com/hc/en-us/articles/213595197-How-do-I-delete-a-server) - [Discord invite management](https://support.discord.com/hc/en-us/articles/208866998-Invites-101) ## Related resources - [How to tell players your Rust server is closing](https://rustsc.com/learn/community/tell-players-a-rust-server-is-closing/index.html.md) --- HTML version: https://rustsc.com/learn/community/wind-down-a-rust-community-discord/ --- # Why is team chat missing in Rust+ after changing teams? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Open the correct paired server in Rust+ and check which team the paired player belongs to in the game. Rust+ sends text to that in-game team chat. ## Check the team in the game first Ask the player to open their inventory and check the teammates shown there. After an invite, the new member still has to join the team. If the player switches between accounts or between two servers, confirm the running game and the paired entry belong to the same Steam account and server. Suppose a player left the builders' team and received an invite to a new one, but has yet to accept it. Opening the same server in Rust+ cannot finish the in-game invite. Ask them to accept it in the game and verify a teammate sees their name in the roster. ## Send a short test in each direction Use a neutral phrase that both people can recognize. Have the teammate in Rust select Team in the in-game text chat. With default controls, Tab switches chat channels while the chat box is open. 1. Send a test line from the game's Team chat. Check it appears under Team for that server in Rust+. 2. Reply from Rust+ and have the teammate check the in-game Team channel for the reply. 3. If the pair's live server information also fails, check the companion connection. If the game chat works and the app is connected, record which direction failed and which account and team you verified. ## Sources - [Facepunch guide to making and joining a Rust team](https://wiki.facepunch.com/rust/teams) - [Facepunch explanation of Rust+ team chat](https://rust.facepunch.com/companion/) ## Related resources - [Why does Rust+ say your paired server is offline?](https://rustsc.com/learn/troubleshooting/rust-plus-paired-server-offline/index.html.md) - [Which Rust map markers can teammates see?](https://rustsc.com/learn/community/which-rust-map-markers-do-teammates-see/index.html.md) --- HTML version: https://rustsc.com/learn/community/rust-plus-team-chat-missing-after-team-change/ --- # Which Rust map markers can teammates see? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Use a marker placed by the in-game team leader when everyone needs the same meeting point. Use a ping for something nearby that teammates only need to notice briefly. ## Choose how to share the location A player can place and label personal markers on the map. The team leader's markers also show to teammates, alongside their own. Rust pings are short-lived callouts that team members can share using supported gear such as binoculars. | What you want players to find | Use this | | --- | --- | | A rally point the team will use throughout the session | A labelled map marker from the team leader. | | Your own route back to a project | A personal marker if you are a regular team member. If you lead the team, use a private note for a location you want to keep to yourself. | | A landmark someone needs to look at right now | A short ping with the relevant in-game tool. | ## Confirm visibility from the receiving side For a building session, ask the leader to place a marker on the road junction and label it `MILL`. Ask one teammate to open their map and check the label and grid square. If they cannot see it, check the active team for both players and have them compare the current map markers. A regular member placing their own copy of the marker only proves it appears on that player's map. ## Sources - [Facepunch guide to map markers and pings](https://rust.facepunch.com/news/make-your-mark) - [Facepunch guide to Rust in-game teams](https://wiki.facepunch.com/rust/teams) ## Related resources - [Why is team chat missing in Rust+ after changing teams?](https://rustsc.com/learn/community/rust-plus-team-chat-missing-after-team-change/index.html.md) - [What does the last death marker on the Rust map show?](https://rustsc.com/learn/troubleshooting/rust-death-map-marker-versus-respawn-point/index.html.md) --- HTML version: https://rustsc.com/learn/community/which-rust-map-markers-do-teammates-see/ --- # How can a visitor use one door in your Rust community workshop? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) For a workshop where guests can use the public room while the rest of your base stays private, put a Code Lock on the guest entrance. Give the visitor its guest code. Keep a separately locked door between that room and the private area. ## Walk the route before inviting anyone Build a small example on a practice world. Stand outside as a visitor would. Trace every route from the front door to the furnaces and from the furnaces to your storage. An open side entrance defeats the room layout even if the front lock works perfectly. On the workshop’s Code Lock, set a main code you keep and a different guest code for that entrance. Close and lock the door. Use distinct codes for the private area. Keep both codes out of your public server description and screenshots. ## Check from an ordinary player’s account Ask a player who has never used the main code to try the guest entrance. Someone already authorised as an owner cannot demonstrate the guest experience. | Try as the visitor | What should happen | | --- | --- | | Use the workshop’s guest code. | The visitor can open and close that door. | | Open the lock controls. | The guest cannot change the main code, unlock the lock or remove it. | | Walk from the furnaces toward private storage. | The separately locked door still blocks entry. | ## Describe the actual access in the invitation “Come through the courtyard door to use the public furnaces” gives a guest a destination they can recognise. If the visitor reaches private storage during the rehearsal, fix the route or the second lock before sharing the workshop entrance. ## Use a temporary visit to test the whole route Mo could write to a Long Ear Foundry visitor privately, ‘Use the courtyard entrance Saturday from 18:00 to 20:00 UTC. I will meet you by the public furnaces. The inner door is for staff.’ Share the guest code separately. Give each person their role for the test. | Player | What to verify | | --- | --- | | Visitor who received the guest code | Can enter the furnace room and leave by the same door. The inner door and stock stay private. | | Unrelated passerby with no code | Cannot open the closed courtyard door. A steward watches the door while visitors go through if other people might follow. | | Workshop owner | Can still lock the courtyard and reach private storage independently. | ## Prove the visit is over from the guest's side At the announced end, close the guest route and end temporary access. If you clear or change a guest code, ask someone who already used it to try the closed door again. Also ask a fresh passerby to try. If the former guest can still enter, keep an independently locked barrier across the route and leave the public room closed. Rehearse replacing the guest entrance's lock on the test setup before applying the change to the real entrance. With the real entrance closed again, verify that the former guest and a fresh passerby cannot use it and that the owner can still open and secure it. Check the owner's private door too. Confirm those results before taking down the barrier or reusing the public room. Remove the old invitation and post that the visit has ended. ## Sources - [Facepunch introduction to guest codes](https://rust.facepunch.com/news/devblog-149) - [Facepunch Code Lock item reference](https://wiki.facepunch.com/rust/item/lock.code) ## Related resources - [Why can one Rust teammate build at the base while another can't?](https://rustsc.com/learn/troubleshooting/why-rust-teammate-cannot-build-at-base/index.html.md) - [Open your Rust builders' town for a guided tour](https://rustsc.com/learn/community/run-a-guided-rust-builders-town-tour/index.html.md) --- HTML version: https://rustsc.com/learn/community/give-a-visitor-access-to-one-rust-workshop-door/ --- # Should your PvE Rust server add a dueling area or a combat weekend? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Choose the smallest area where the fight belongs. Use a dueling area when some players want a fight and others want to keep building. Consider a combat weekend when players actually want combat to change the whole world's routine. ## Decide what the player who sits out can do Ask a builder, a fighter and a newcomer to describe their Saturday. A rule works when all three can say where they can play, what they risk and how to get back to ordinary PvE. | Format | Player's way to opt out | What you must prove | | --- | --- | --- | | Keep PvE everywhere | Carry on with normal routes and play. | There is no temporary player combat exception. | | Offer a dueling area | Stay outside the marked arena and keep ordinary access to roads, shops and home. | The entry, exit and both directions across the boundary behave as described. | | Hold a combat weekend | Avoid the server or use any explicitly tested peaceful option. | The announced protections for homes, sleepers and loot hold during combat, and normal play returns at the end. | ## Try the arena against an ordinary route Imagine Reedbank, whose players want fair duels beside the town in G8. The first proposed ring sits across the bridge that builders use to reach the recycler. Move the ring off the bridge or keep the event private. Putting a warning on the bridge still makes the arena a condition of the usual trip. Put one ordinary account in the ring and another outside. Try an agreed test hit each way. Swap accounts and repeat after the fighter walks out and after a reconnect. If you use TruePVE with Zone Manager, check the mappings and any separate zone flags. A person standing inside a marked zone cannot establish how attacks crossing its edge behave. Record both directions separately. If only one direction protects the player outside, move the ring or keep it closed until both sides match the published rule. ## Put losses on the invitation Describe gear and loot before choosing a format. For Reedbank's first event, use loose practice gear and leave ordinary inventories and homes out of it. Check what happens when someone drops a bag or disconnects. TruePVE deals with damage. Where you promise restrictions on looting, prove those separately. A world-wide event needs a public start, a tested end and a way to close early. A post saying ‘PvE returns Sunday’ should also tell players whether event losses stay lost. If staff cannot describe that evening to a newcomer in one message, run the smaller event first. ## Make the opening decision Read the proposed announcement to someone outside the crew and ask them to name the safe route, the loss they can take and the time when peace returns. If they can explain it and the corresponding ordinary-player tests pass, publish. Otherwise move the boundary, narrow the rules or keep the server PvE for this round. ## Sources - [TruePVE: damage rules and zone integration](https://umod.org/plugins/true-pve) - [Zone Manager: flags and zone settings](https://umod.org/plugins/zone-manager) ## Related resources - [Run a PvP weekend on your PvE Rust server](https://rustsc.com/learn/community/weekend-pvp-on-a-pve-rust-server/index.html.md) - [What should you check before advertising a Rust server as PvE?](https://rustsc.com/learn/configuration/check-what-pve-means-on-your-rust-server/index.html.md) --- HTML version: https://rustsc.com/learn/community/choose-a-combat-format-for-a-pve-rust-server/ --- # Open a trading market on your PvE Rust server [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Open one stall first. Your first successful market visit starts at a clear approach, ends with the advertised goods and gives the visitor access only to the part of the stall needed for the sale. ## Give the seller and buyer different routes For example, Bo stocks cloth from a locked room at Lark Market. Jules approaches from the riverside path, buys from the public face of the vending machine and leaves by the same path. A sign gives the scrap cost and says where to queue. There is no need for the public to go through the stock entrance. Ask someone who did not build the stall to follow that route without Bo's help. If they stop at the wrong door, move the sign first. If the stockroom door is making the public frontage look like an entrance, mark it as staff access and test the front again. ## Run one normal transaction and three awkward ones Use disposable stock, a regular vendor account and two ordinary visitors. Note where money and goods actually end up. | Run | What Lark needs to see | | --- | --- | | Jules buys one stack of cloth. | The listing matches what changes hands and Jules can leave without passing through the stockroom. | | Casey tries the stockroom and its cupboard while Bo restocks. | The door stays closed to Casey. Bo can restock without leaving the stockroom open to the queue. | | The last stack sells while Casey is approaching. | Casey can see whether the listing is out of stock or closed, and nobody promises a trade from the locked overflow box. | | Casey orders by drone, if Lark advertises it. | A buyer at an available market terminal can find this stall, place the test order and collect the cloth. | ## Decide how to handle a lost sale Facepunch introduced marketplace delivery for reachable vending machines. Try from the actual terminal on your server before promising drone orders. If Bo's covered stall fails that test, Lark advertises walk-up sales and keeps a sign at the public face. If Casey says a trade consumed payment but provided no goods, have them give staff the time, stall and listing. Check what happened before offering a private remedy. A damage rule and a storage rule do different jobs. If Lark relies on a looting plugin, run the storage check with the roles and exceptions actually used on the server. Keep the queue off the restock route even if the test account cannot open the box. ## Close without leaving a confusing listing At the end, finish the last agreed sale, mark the market closed where it was announced, and have Bo secure unsold stock. Send Jules back on foot to confirm what the next buyer sees. If accepting remote orders outside staffed hours is part of your offer, say which stalls remain available and test a normal off-hours purchase. ## Sources - [Facepunch: the original Rust marketplace and drone delivery](https://rust.facepunch.com/news/softcore-gamemode-update) - [Facepunch: trading and stock access at a vending machine](https://wiki.facepunch.com/rust/item/vending.machine) - [Prevent Looting: container and corpse protection](https://umod.org/plugins/prevent-looting) ## Related resources - [How can a visitor use one door in your Rust community workshop?](https://rustsc.com/learn/community/give-a-visitor-access-to-one-rust-workshop-door/index.html.md) - [Why is a Rust vending machine missing from the in-game map?](https://rustsc.com/learn/troubleshooting/rust-shop-vending-machine-absent-from-game-map/index.html.md) --- HTML version: https://rustsc.com/learn/community/open-a-pve-rust-trading-market/ --- # Teach your Rust server's roleplay in one first encounter [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Give a new player one thing they can do as soon as they reach town. Explain how to pause the scene in the same place you explain how to begin it. ## Start at the dock, with one decision Picture a newcomer arriving at the public dock of Alder Port with starter gear. The host is a ferrymaster who needs help reading a notice. The player can agree to deliver it, ask where to find the market or take the road out. Any of those choices is a complete first encounter. Put the actual rules on a short welcome card in the join post and at the dock. ‘Play a character here if you want to join a scene. To pause, say “out of character” in voice or type OOC in chat. The road to town is open to everyone. Ask a steward privately if another player keeps you in a scene after you ask to leave.’ ## Play it once without your most experienced regular Have one volunteer run the dock and someone who has never read the lore walk up. On the first pass, the ferrymaster asks for a long character backstory before sharing the notice. The newcomer goes quiet. Replace that opening with a line someone can answer immediately: ‘Taking a parcel to the market or just passing through?’ On the second pass the newcomer types ‘OOC I need to go’. The ferrymaster pauses and points out the road in plain words. A second helper takes over the parcel for the next scene. Check that other players know to stop the scene too, even if their characters are supposed to insist. ## Keep a genuine rule issue outside the story Give the steward a short answer for a player who says someone pursued them after they withdrew: ‘You're out of the scene. Send me the place, time and what happened through the private report route.’ Leave any staff response out of character. A scene leader can stop the activity while a moderator checks the report. ## Publish the short version first The join post needs the dock location, the first invitation and the pause words. Put the full town history in a separate reading link. Ask another newcomer to show you where they would start, how they could pause and how they would leave. If they cannot show all three after one read, change the card before opening the dock. ## Sources - [Facepunch: Community Server and Hosting Guidelines](https://facepunch.com/legal/servers) - [Discord: developing moderator guidelines](https://discord.com/safety/developing-moderator-guidelines) ## Related resources - [How to write Rust server rules players can use](https://rustsc.com/learn/community/write-rust-server-rules-players-can-use/index.html.md) - [Where should players send reports about your Rust server?](https://rustsc.com/learn/community/give-rust-players-a-private-report-route/index.html.md) --- HTML version: https://rustsc.com/learn/community/write-a-first-roleplay-encounter-for-your-rust-server/ --- # Run a shadow shift for a new Rust moderator [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Pair a new moderator with someone who explains their decisions. Use practice cases first so the trainee can try a response without affecting a real player. ## Prepare the shift with a clear job Say Nia already knows the rules at Mallow Creek and has agreed to cover player reports on Saturday. Her mentor Dev gives her the current rule page and a private practice thread. They agree that Nia can write a draft reply but Dev is responsible for any real decision during the exercise. Have both people read the same facts and write their own next action before discussing either answer. Include at least one case where a sensible response is to gather more information. ## Work three cases in the order they arrived For each case, Nia records what she observed, what she would do next and what she would tell the player. | Case Mallow Creek rehearses | What the mentor looks for | | --- | --- | | Two names, one clip of an argument, no server name. | Ask which world and when. Acknowledge the report without attributing the voice to either person. | | A clear chat threat under the community's safety rules. | Use the agreed urgent route, preserve the relevant message privately and use the separate platform reporting route when appropriate. | | An otherwise clear rule complaint about Nia's regular teammate. | Hand it to an uninvolved moderator without taking a position about the teammate in the report thread. | ## Practice the missed part once more Nia correctly routes the urgent case, but writes the teammate's name in public chat while looking for another moderator. Dev explains that a private handoff reaches the same person without identifying anyone to the whole server. Nia repeats the case using a private note with the time, rule and assigned reviewer. Give the volunteer a brief record after the shift. In this example, Nia can acknowledge normal reports and request missing facts independently. Dev is still the reviewer for contested decisions, and another mentor handles cases involving Nia's teammates. Review those boundaries after a later shift together. ## Check the volunteer can begin a real shift Hand Nia a fourth synthetic report without instructions about which part is missing. Ask her to talk through where she would send the private note and who owns it if Dev is offline. When she can run the agreed routine and name the escalation route, publish her coverage in the staff schedule. ## Sources - [Discord: training and onboarding moderators](https://discord.com/safety/training-and-onboarding-new-moderators) - [Discord: confidentiality in moderation](https://discord.com/safety/confidentiality-in-moderation) - [Facepunch: reporting in Rust](https://support.facepunchstudios.com/hc/en-us/articles/10640775389853-Reporting-in-Rust) ## Related resources - [Onboard your first Rust moderator without sharing your login](https://rustsc.com/learn/community/onboard-a-first-rust-server-moderator/index.html.md) - [Who handles a report involving a Rust moderator’s own team?](https://rustsc.com/learn/community/when-a-rust-moderator-should-step-aside/index.html.md) --- HTML version: https://rustsc.com/learn/community/run-a-shadow-shift-for-a-rust-moderator/ --- # Which rules should all your Rust worlds share? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Share the conduct rules you can apply consistently everywhere. Publish play rules beside each world's name and join information so players can see what changes when they move between worlds. ## Read the rule from three worlds Imagine a community with Meadow PvE, Ridge Trio and Loft Build. A ban on harassment applies across all three. A player limit on teams belongs beside Ridge Trio. The building lanes and test plots belong beside Loft Build. Meadow has its own definition of protected homes and public trade. For each proposed shared rule, ask two questions. Does the same action warrant the same response on all worlds? Can any moderator explain how to report it? If the answer depends on the map, game mode or event, write a short world rule naming its scope. ## Write rules in the order a player sees them Make the shared rules easy to find from every world card. Give scoped exceptions the same name in the browser description, join post and community rule page. | Where it appears | Example | | --- | --- | | Community conduct | Keep reports private and do not harass players or staff on any world. | | Meadow PvE join post | Player combat is closed outside named events. See Meadow's home and loot protections before joining. | | Ridge Trio join post | Read the Ridge team rule before joining a group. Normal combat is part of this world. | | Loft Build join post | Use a marked test plot and keep roads and neighboring plots clear. | ## Try a rule change with an ordinary player Say a new weeknight duel opens on Meadow. Update only the Meadow card and add the dates and arena location. Ask a regular Ridge player who has never visited Meadow to explain what is allowed before and after duels, and whether the Loft building rules changed. Check that the public listing still describes the actual world fairly. If another moderator would treat a report as a community-wide conduct issue, give them the name of the common rule and a private reporting path. If the report describes only a local play rule, send it to that world's staff. Publish the split when a player can pick the right rule and the staff member can name whoever owns the reply. ## Sources - [Facepunch: Community Server and Hosting Guidelines](https://facepunch.com/legal/servers) - [Discord: developing moderator guidelines](https://discord.com/safety/developing-moderator-guidelines) ## Related resources - [How to write Rust server rules players can use](https://rustsc.com/learn/community/write-rust-server-rules-players-can-use/index.html.md) - [How to announce a Rust server rule change](https://rustsc.com/learn/community/announce-a-rust-server-rule-change/index.html.md) - [Server groups reference](https://rustsc.com/support/guides/reference-server-groups/index.html.md) --- HTML version: https://rustsc.com/learn/community/choose-shared-rules-for-multiple-rust-worlds/ --- # How should PvE players share a Rust monument? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Pick a rule a player can follow from the moment they arrive. At a crowded PvE monument, ‘don't steal’ needs to say who can start the encounter, who can help and who may take the reward. ## Choose either a turn or shared play Suppose two groups on Bracken reach Oil Rig just after the first starts the locked crate. Facepunch's Oil Rig introduction describes the crate as the trigger for a Heavy Scientist encounter. The volunteer sees a dispute over who was first to arrive, who started the crate and whether a group that helped gets a share. A staffed group may use turns for that one encounter. In Bracken's example the first group to start the locked crate holds the current turn, and additions need the group's agreement. A quieter server could instead run a shared fight with a clearly stated loot split. Either choice should give somebody who arrives halfway through a next action. ## Read three situations against the proposed rule Ask two ordinary groups for a quick run. Let them describe what they would do before any staff member explains it. | Situation | Bracken's rule in practice | | --- | --- | | Both groups arrive before the crate starts. | Agree who will start before opening it. If there is no agreement, ask a steward before claiming a turn. | | A group returns after leaving mid-encounter. | An active group can finish the encounter. A group that leaves and gives up its turn can rejoin if invited. | | Someone fires during the fight without being invited. | Help alone does not grant a loot claim. Tell the group how to ask to join next time. | ## Keep the sign and enforcement consistent Write the rule in two or three lines next to the monument instructions in your welcome post. If the game or a plugin grants access differently from the house rule, tell players what they should do when the game permits the wrong action. A PvE damage plugin does not settle who owns a crate. Try the scenario with one volunteer pretending to join halfway through. The first group can say who may collect the reward and the second group knows where to wait or how to ask. Rework the rule if their answers disagree on when a turn begins. ## Sources - [Facepunch: the Oil Rig encounter](https://rust.facepunch.com/news/oilrig-update) - [TruePVE: damage rules and zone integration](https://umod.org/plugins/true-pve) ## Related resources - [What should you check before advertising a Rust server as PvE?](https://rustsc.com/learn/configuration/check-what-pve-means-on-your-rust-server/index.html.md) - [How to write Rust server rules players can use](https://rustsc.com/learn/community/write-rust-server-rules-players-can-use/index.html.md) --- HTML version: https://rustsc.com/learn/community/share-a-rust-pve-monument-with-other-groups/ --- # Judge a Rust building contest players want to enter again [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Publish the building conditions and scoring before anyone places a foundation. Judges should score the job you asked entrants to do, under the conditions every entrant actually had. ## Give every builder the same footing For a challenge called Stoneworks, ask builders to create a public shelter with a clear entrance, a place to wait and an exit. Organizers mark plots on comparable ground and use the same Creative settings for all participants. If the footprint is meant to transfer to Survival, keep ordinary placement checks in the practice setup and verify that claim separately. Give each entrant the same start and finish window and answer rule questions in the shared event thread. If someone asks whether an attached staircase counts toward the footprint, publish the answer where the next entrant can see it too. ## Score the same work independently Stoneworks awards up to two points in each category. A judge writes one observation per category before seeing the other judge's sheet. | Category | Covered shelter | Round shelter | | --- | --- | --- | | Arrival and exit | 2. Both routes are visible from the path. | 2. The doors are signposted and the path is clear. | | Usable waiting space | 2. Visitors can wait inside without blocking the entrance. | 1. The waiting bench crowds the door. | | Fits the brief | 1. The footprint stays inside the plot, but the shelter is open along one edge. | 2. The shelter fits the plot and meets the cover requirement. | ## Resolve equal scores with the published rule Both entries score five. Stoneworks published ‘Usable waiting space’ as the tie-break category, so Covered shelter takes first place. If the judges disagree on whether an edge counts as covered, return to the written brief together and apply that reading to every entry. Keep a joint place if you have no announced way to break a remaining tie. Tell the entrant one thing that earned points and one observation they could act on. Before publishing the result, ask a third person to pick the winner from the sheet alone. If they need an extra unwritten rule, resolve that with the judges before naming a winner. ## Sources - [Facepunch: Creative Mode](https://wiki.facepunch.com/rust/creative) - [Discord: Scheduled Events](https://support.discord.com/hc/en-us/articles/4409494125719-Scheduled-Events) ## Related resources - [How to run signups for a Rust event with limited spots](https://rustsc.com/learn/community/rust-event-spots-and-waitlist/index.html.md) - [How to set up a Rust server for creative building practice](https://rustsc.com/learn/configuration/set-up-a-rust-creative-building-practice-server/index.html.md) --- HTML version: https://rustsc.com/learn/community/judge-a-rust-building-contest/ --- # Run a tool-lending bench for new PvE Rust players [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Start with items you can afford to lose and a person who can receive them back. The bench is a place for a short handoff. Keep the main stock in a room only the stewards can enter. ## Set up the handoff in sight of the path For a tool loan at Sedge Camp, a steward could bring an ordinary hatchet and pickaxe to an outside bench. A newcomer can borrow one set for their first gathering trip. The steward hands the tools directly to the named borrower and checks that they picked up the right items before leaving. A Tool Cupboard controls building privilege around a base. Keep cupboard authorization separate from a tool loan. If your server also protects storage, prove the protection with an unrelated account rather than relying on the borrower to stand behind the correct door. ## Keep one small loan record The record belongs with the stewards. The sign at the bench needs only the borrow and return hours, the contact and the policy for a missing item. 1. Write the player name, items, expected return and steward who handed them over. 2. When a player returns a tool set, check it against the entry before putting it back into circulation. 3. If a player cannot catch the steward, agree a later handoff in private. Avoid leaving a pile of supplies on the path. ## Close a late loan before the next shift Sedge's borrower returns the hatchet but lost the pickaxe. Sedge treats a first low-value loss as part of the programme. The steward records the hatchet returned and the pickaxe lost, then closes the entry. They speak privately with a player if the pattern recurs. A missing entry alone needs a check with the previous steward before anyone draws that conclusion. Ask another helper to run the next handoff with just the sign and loan record. An ordinary borrower should collect and return a complete set without seeing the private box. If the helper needs a staff code to give somebody a tool, move the handoff outside the workshop. ## Sources - [Facepunch: Tool Cupboard, decay and building privilege](https://wiki.facepunch.com/rust/the_tool_cupboard) - [Prevent Looting: container and corpse protection](https://umod.org/plugins/prevent-looting) ## Related resources - [How can a visitor use one door in your Rust community workshop?](https://rustsc.com/learn/community/give-a-visitor-access-to-one-rust-workshop-door/index.html.md) - [What should you check before advertising a Rust server as PvE?](https://rustsc.com/learn/configuration/check-what-pve-means-on-your-rust-server/index.html.md) --- HTML version: https://rustsc.com/learn/community/start-a-rust-pve-tool-lending-bench/ --- # Interview two Rust moderator volunteers for the same job [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Interview for the work you need covered. Ask each applicant the same short questions and say how often the shift happens before they decide whether to take it. ## Describe one real vacancy Suppose the Brook community needs someone to catch the first reports on Sunday after its regular building event. The job is to acknowledge reports in private, gather missing details and pass contested cases to the owner. Tell applicants which hours are actually useful, which duties are occasional and who covers when they are away. ## Give both candidates the same situations Explain that there is no real case behind the examples. Read each answer in light of the advertised job. | Prompt | What the answer can show | | --- | --- | | A report names no world or time. Write your first reply. | They can ask for the missing facts without blaming anyone. | | Your usual teammate is in the clip. Who gets the report? | They can hand a conflict to another person and keep the case private. | | You can cover Sunday once a month. What should we offer? | They can be honest about a recurring commitment and suggest a useful smaller role. | ## Match the answer to the vacancy Kira would ask for the world and time and is available every other week. Amari knows the usual players well and can cover most Sundays, but wants to ask the whole Discord who appears in the clip. Brook talks through the privacy concern with Amari before offering a report role. It can offer Kira the alternate weeks she actually named, with a named backup or an advertised gap. Tell each volunteer which duty you are offering and whether there is a practice shift. Give people room to decline without explaining their personal calendar. Measure the decision against whether the named Sundays now have feasible coverage. A friendly conversation and a popular applicant are both useful, but the roster still needs people who can be there. ## Sources - [Discord: developing moderator guidelines](https://discord.com/safety/developing-moderator-guidelines) - [Discord: managing moderation teams](https://discord.com/safety/managing-moderation-teams) ## Related resources - [Onboard your first Rust moderator without sharing your login](https://rustsc.com/learn/community/onboard-a-first-rust-server-moderator/index.html.md) - [Run a shadow shift for a new Rust moderator](https://rustsc.com/learn/community/run-a-shadow-shift-for-a-rust-moderator/index.html.md) --- HTML version: https://rustsc.com/learn/community/interview-a-rust-moderator-volunteer/ --- # Get two Rust moderators to apply the same rule consistently [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Find a rule your moderators read differently. Give them the same two invented cases, collect their decisions separately and change the staff example that leaves too much to guess. ## Pick a pair with one meaningful difference Pinebridge's market rule says ‘Keep the public road clear.’ Case A shows a player placing a foundation across the entire ramp for a storage extension. Case B shows a booth on the edge of the road with the ramp and exit still usable. Both pictures are staged on a test world and come with the same time and location context. Ask the moderators to write what they can see, the words in the rule they rely on, what they would ask the builder to do and when they would escalate. Collect the answers before they compare notes. ## Find the point where judgment split In this example both moderators would ask the first builder to reopen the ramp. They disagree on the booth. | Reading | Next move | | --- | --- | | One moderator treats any footprint over the painted line as a violation. | Check whether the boundaries were published and explain the line if the community wants a fixed boundary. | | The other looks only at whether players can pass. | Specify the actual passage players must keep usable if that is the outcome the community wants. | ## Test the clarification on a third case Pinebridge chooses passage. It adds a staff example: ‘Both ends of the ramp and the doorway to the recycler must stay usable. Ask the builder to move an obstruction and show the blocked route.’ It also adds both examples to the staff note so the next volunteer can see the difference. Give both moderators a third picture of a queue blocking the doorway with no building piece in the way. If one sends a builder warning and the other asks a steward to move the queue, the examples still leave a gap. Clarify when to direct people and when to address a structure. End the exercise when both can name the next action and the evidence behind it. ## Sources - [Discord: developing moderator guidelines](https://discord.com/safety/developing-moderator-guidelines) - [Discord: managing moderation teams](https://discord.com/safety/managing-moderation-teams) ## Related resources - [How to write Rust server rules players can use](https://rustsc.com/learn/community/write-rust-server-rules-players-can-use/index.html.md) - [Run a shadow shift for a new Rust moderator](https://rustsc.com/learn/community/run-a-shadow-shift-for-a-rust-moderator/index.html.md) --- HTML version: https://rustsc.com/learn/community/calibrate-rust-moderators-on-one-rule/ --- # Lay out a Rust village with private plots and open paths [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Lay out the route to the market and neighboring houses before allocating plots. A rectangle on a map is only a proposal until ordinary players can build within it and walk past it. ## Mark the route people use every day Imagine two homes beside a river in Fern Village. The expected visitor path turns past the west plot to reach a bridge. Draw the route from both directions and mark each proposed home entrance. Keep wall lines and doors out of the bend. A player following the path should have somewhere to go while a door is open. ## Walk the outline with two builders and a visitor On a disposable setup, place example foundations and cupboards in both plots. Facepunch explains that tool cupboards affect building close to the base. A mark on the map does not decide where a builder has privilege. Have each resident try intended placements at the front and sides, with their own cupboard access. Record the pieces or spots that fail. Fern's west builder can place the main rooms but cannot place an exit landing after the east cupboard is added. Move the plot edge and test again before assigning either lot. Repeat the walking route with both doors, a visitor and the stairs in place. ## Hand out a plot card people can recognize Name the plot after a visible landmark. Give the builder the marked bounds and the path they must keep open. | Example plot field | Fern Village | | --- | --- | | Plot | West Bridge, entrance faces the river | | Shared space | The bend beside the bridge stays walkable from both directions | | Steward contact | Ask the town steward before moving a boundary or adding a wall along the route | ## Leave the shared route visible after move-in When the first two homes go up, a steward and someone new walk the route once more. If the newcomer takes a private staircase to reach the bridge, correct the markers or the layout. Open more plots when each resident can reach their own entrance and the newcomer can find the bridge unaided. ## Sources - [Facepunch: Tool Cupboard, decay and building privilege](https://wiki.facepunch.com/rust/the_tool_cupboard) - [Facepunch: Community Server and Hosting Guidelines](https://facepunch.com/legal/servers) ## Related resources - [How to check buildable space on a Rust map candidate](https://rustsc.com/learn/configuration/compare-rust-worlds-by-coastline-build-space/index.html.md) - [How to write Rust server rules players can use](https://rustsc.com/learn/community/write-rust-server-rules-players-can-use/index.html.md) --- HTML version: https://rustsc.com/learn/community/lay-out-a-rust-village-with-private-plots/ --- # Save the story of your Rust roleplay town before wipe [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Save the places and moments people will ask about next wipe. Make something they can browse even after the map and its signs are gone. ## Choose the tour you would give a player next month Maple Pier's steward picks the ferry steps, the market and the noticeboard. For each, choose a wide view that explains the location and a second view that shows a detail somebody remembers. The old noticeboard has a sign thanking players for saving the market. Ask the author whether to include it and how they want to be credited. Capture before the teardown starts. Put the world name, wipe or season, in-game location and an approximate date alongside each image. Introduce the archive as a record of this town, so readers can tell which buildings belong to the old map. ## Write captions that outlive the grid reference Store one gallery link where people already follow town news. Keep individual image names simple enough for another steward to update. | Image | Example caption | | --- | --- | | 01-ferry-steps | Maple Pier, spring wipe. Ferry departures moved here after the first storm-night event. | | 02-market | Looking from the river entrance toward the public cloth stalls. The shutters closed after the final Saturday trade. | | 03-noticeboard | Original thank-you sign after the market rebuild, shared with its author's permission. | ## Review the album as a visitor Facepunch's video FAQ discusses ownership of recordings. Ask your own community about names, signs and identifying chat before publishing the album. Crop a private message or use a cleaner angle if the picture would expose somebody who was merely passing by. Ask a newcomer to open the link and tell you where the town started, what changed and when this season ended. Fix the order or captions if they need the stewards to fill in the story. Post the finished link beside your existing wipe announcement so returning players can find both the old town and the new join details. ## Sources - [Facepunch: Rust support and video FAQ](https://rust.facepunch.com/support/) - [Facepunch: Community Server and Hosting Guidelines](https://facepunch.com/legal/servers) ## Related resources - [What should your Rust wipe announcement say will reset?](https://rustsc.com/learn/wipes/announce-what-a-rust-wipe-resets/index.html.md) - [What to put in a new Rust server launch announcement](https://rustsc.com/learn/community/write-a-rust-server-launch-announcement/index.html.md) --- HTML version: https://rustsc.com/learn/community/archive-a-rust-roleplay-town-before-wipe/ --- # Record and check a Rust demo for your community showcase [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Record a short take and play it back before spending the evening filming. The file is a Rust demo. Review your eventual video separately for the framing, sound and details the audience will see. ## Make a short take where you can try again To rehearse the Tern Bridge showcase, have one volunteer walk from the lane to the bridge. The camera operator wants a wide arrival and a closer view of the crossing. Try the wide one first. 1. Open the Rust client console and enter `record tern-bridge-wide`, or open the recorder with `demo.recorder` and name the take there. 2. Walk the route. Reopen the recorder with `demo.recorder`, then end the take using its recording controls. Return to the main menu and look for the take in Rust's demo browser, or check the local `demos` folder. 3. Play it from the browser or with `demo.play tern-bridge-wide`. Check the opening, crossing and end. Record the close view after the wide one plays. ## Inspect playback before gathering the group The wide recording in this example opens a few seconds after the volunteer has started walking. Retake it with the operator already recording and enough time to see the sign before the action starts. Use a fresh take name so both recordings remain easy to identify. The Facepunch demo reference documents client recording and local playback. Its section on Full Server Demos describes an older system, which the game's change log says was removed. This job uses a short local take from the recording player's client. ## Review the actual clip you will give players Capture the chosen playback in your usual video recorder and open that export. Watch from the beginning with sound on, look at the borders of the frame for chat or overlay text and check that the route is clear at ordinary playback speed. Replace the take if it reveals a private door or an identifiable player you did not want on screen. Write the world and build title in the accompanying post and tell viewers whether they can visit it. Ask one viewer to locate the bridge in the clip and listen for any line you meant them to hear before you publish. ## Sources - [Facepunch: recording and playing Rust demos](https://wiki.facepunch.com/rust/Demos) - [Facepunch change log: removal of Full Server Demo support](https://rust.facepunch.com/changes/2) ## Related resources - [What to put in a new Rust server launch announcement](https://rustsc.com/learn/community/write-a-rust-server-launch-announcement/index.html.md) - [Save the story of your Rust roleplay town before wipe](https://rustsc.com/learn/community/archive-a-rust-roleplay-town-before-wipe/index.html.md) --- HTML version: https://rustsc.com/learn/community/record-a-rust-demo-for-a-community-showcase/ --- # Run a Rust roleplay ferry that can finish on foot [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Give a ferry event the same arrival point even if the boat stays ashore. Use a short crossing you can rehearse, with a shore host to tell people when to board or take the foot route. ## Give the passengers a route before they board For example, the pilot at Brine Dock runs across one bay and the shore host waits beside a blue sign. The first boat goes only after the host counts available seats and tells the pilot who is aboard. The sign also gives the land meeting point, the town bell beside the market. Facepunch documents player-made boats in the Naval update. Rehearse the actual boat you intend to use in your world. ## Walk one full trip and one failed departure Start with disposable gear and volunteers who were not involved in choosing the route. | What happens | What the shore host does | | --- | --- | | The boat is ready and the first passengers are present. | Guide them to the marked boarding point. The pilot confirms everyone is ready before moving. | | A player reaches the blue sign after departure. | Tell them when the next crossing is or take them to the bell along the footpath. | | The pilot cannot launch. | Post the foot-route switch in the event post and guide people from the same blue sign. The next scene still starts at the bell. | ## Put boarding and the fallback in the invitation Brine posts ‘Meet at the blue sign at the public dock. Bring disposable gear. If the ferry stays ashore, follow the host to the town bell.’ On the first run, a late player keeps waiting at a second dock. Give the sign a grid reference and a landmark visible from the approach before publishing. At the second rehearsal someone new follows either route and reaches the same scene without a private escort from the organiser. Ask the shore host to close the trip by updating the event post with the change or completion. If players could still be waiting on the wrong shore, leave a steward there until the group is accounted for. ## Sources - [Facepunch: player-made boats in the Naval Update](https://rust.facepunch.com/news/naval/) - [Discord: Scheduled Events](https://support.discord.com/hc/en-us/articles/4409494125719-Scheduled-Events) ## Related resources - [Help late players catch up at a Rust community event](https://rustsc.com/learn/community/help-late-players-join-a-rust-event/index.html.md) - [Teach your Rust server's roleplay in one first encounter](https://rustsc.com/learn/community/write-a-first-roleplay-encounter-for-your-rust-server/index.html.md) --- HTML version: https://rustsc.com/learn/community/run-a-rust-roleplay-ferry-with-a-backup/ --- # What should a Rust event host be able to decide? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Give the host control of the event they are running. Write down who handles player conduct and server changes so a disputed round reaches the correct person without stopping the whole night. ## Put a real dispute on the job sheet Say a player at Birch Arena crosses the start line before the bell and claims another player disrupted the heat. The host can rerun the heat from the written contest rules. If someone reports harassment, the host passes that part privately to a moderator. Define those paths before deciding which accounts or permissions the host needs. ## Match each action to the person who needs it Write one result a volunteer should be able to produce on event night. | Decision | Birch assigns it to | Practical check | | --- | --- | --- | | Pause or rerun a heat | Event host | Post a ruling and start the next heat in the event space. | | Investigate a conduct report | Moderator | Open a private report and acknowledge it without copying it to the event channel. | | Change game settings or restart | Server operator | Receive a clear request with the affected world and decide whether a change is needed. | ## Remove access that the exercise does not use Discord roles can add access to individual channels. Give the event host the event space they need. In a Rust management tool, check the actual role capabilities rather than using the job title as a permissions checklist. If they can keep score and post a rerun through Discord, that job may need no management access at all. Simulate the dispute with ordinary accounts. The host posts the new start in public and hands the conduct part to the moderator privately. If the host needs live player controls just to stop a heat, see whether event boundaries or a separate steward can meet the need before granting additional access. ## Sources - [Discord: roles and permissions](https://support.discord.com/hc/en-us/articles/214836687-Discord-Roles-and-Permissions) - [Discord: developing moderator guidelines](https://discord.com/safety/developing-moderator-guidelines) ## Related resources - [What access does your Rust moderator actually need?](https://rustsc.com/learn/community/choose-access-for-a-rust-moderator/index.html.md) - [Understand workspace roles](https://rustsc.com/support/guides/workspace-roles/index.html.md) --- HTML version: https://rustsc.com/learn/community/decide-what-an-event-host-can-settle-in-rust/ --- # Review a report that a Rust moderator misused staff powers [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Have an uninvolved lead review the staff action and the underlying player complaint separately. A player can have broken a rule and still be entitled to a fair review of how staff responded. ## Capture what the report can show Suppose a player on Longford reports that a moderator moved them away from a build contest after an argument. The clip shows the player in a different place after a cut and the moderator's name nearby. Ask for the world, time with time zone and the original sequence. Preserve relevant history available to the reviewer. Record unavailable evidence as unavailable. Tell the moderator privately what action is being reviewed and ask them to describe what they did and under which rule. Let a different lead take the case if the usual reviewer was involved. Keep the reply to the initial player short and give them a time when they can expect an update. ## Separate the observations from the decision Say Longford's reviewer gets the full clip and a staff note that agrees with it on the time and the action. | Question | Finding and next move | | --- | --- | | Did the moderator move the player? | The moderator confirms it in their note, and the sequence matches. Record the evidence supporting that finding. | | Was it an agreed event action? | The staff guide allows a reset after a heat. This happened during a personal argument outside the course. The lead addresses the staff action separately. | | Was the player's original conduct a violation? | The clip does not establish the player's alleged conduct. Keep that question open only if another proportionate evidence check is available. | ## Give both people a private outcome Tell the player what the lead found about their concern and what remedy is relevant. Tell the moderator which duty or access has changed, who is responsible for it and when it will be reconsidered. If evidence could not establish who acted, record the unresolved point and avoid filling it with assumptions. Close the review when the staff decision has an owner, both people received their own reply and the lead verified any agreed access change. General wording about the event can go in a public update if players need it. Leave private statements and identifying evidence in the restricted case record. ## Sources - [Discord: managing moderation teams](https://discord.com/safety/managing-moderation-teams) - [Discord: confidentiality in moderation](https://discord.com/safety/confidentiality-in-moderation) - [Facepunch: reporting in Rust](https://support.facepunchstudios.com/hc/en-us/articles/10640775389853-Reporting-in-Rust) ## Related resources - [Who handles a report involving a Rust moderator’s own team?](https://rustsc.com/learn/community/when-a-rust-moderator-should-step-aside/index.html.md) - [How to correct a moderation mistake on your Rust server](https://rustsc.com/learn/community/correct-a-rust-moderation-mistake/index.html.md) - [Help a player in game](https://rustsc.com/support/guides/player-actions/index.html.md) --- HTML version: https://rustsc.com/learn/community/review-a-rust-moderator-staff-powers-report/ --- # Offer a starter kit without making it the best way to gather [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Stock a kit for the first trip out of spawn. Choose when a player should qualify, then run the same claim as a newcomer, a returning player and a player who has just died. ## Tie the contents to a first task Suppose you run Mossfield PvE and want late arrivals to reach the village and gather their first wood. You offer a small bag of basic supplies via an explicit claim. There are no components or stockpiles worth repeatedly claiming. If the first task can be supported by a guide and a loaned tool, try that before adding a kit. Gameplay-changing kits affect which browser category you can use. Facepunch lists Rust Kits as an example of a gameplay-modifying plugin. Check your advertised category and use the plugin's own guide for its supported controls. ## Prove the actual claim rule The Rust Kits documentation describes per-wipe maximum uses, cooldowns and access restrictions. Decide whether your promise is once per wipe or once per player across wipes. Those are different policies. | Account and action | Mossfield example expectation | | --- | --- | | Eligible newcomer claims before gathering. | Gets one starter bundle. | | Same player claims again after respawn. | The second claim is refused under the one-per-wipe policy. | | Existing account that already claimed during this wipe tries again. | The existing claim stays spent. | | Returning account tries after the next map wipe. | The result matches the reset rule you actually selected and rehearsed. | ## Write the promise at the place people claim For a one-per-wipe configuration that passed, Mossfield writes ‘One starter kit per player each wipe. Ask a steward if yours was already used.’ If you want an account lifetime limit, check that the mechanism and wipe routine support it before publishing that line. Leave automatic kits off if the test shows an unexpected respawn grant. Use ordinary player accounts on a test world. Record what was received and whether each repeat attempt was refused. Open the offer when the wording, the actual reward and the reset behavior agree. ## Sources - [Facepunch: guidelines for community servers using plugins or mods](https://support.facepunchstudios.com/hc/en-us/articles/360009062817-Guidelines-for-community-servers-using-plugins-mods) - [uMod: Rust Kits claims, cooldowns and usage limits](https://umod.org/plugins/rust-kits) ## Related resources - [Should your Rust server be listed under Community or Modded?](https://rustsc.com/learn/configuration/choose-community-or-modded-for-a-rust-server/index.html.md) - [Run a tool-lending bench for new PvE Rust players](https://rustsc.com/learn/community/start-a-rust-pve-tool-lending-bench/index.html.md) --- HTML version: https://rustsc.com/learn/community/offer-a-pve-rust-starter-kit-once/ --- # Host a Rust creator shoot without filming live players [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Set up the part of the scene you can control. Use volunteers who know what will be recorded, a short route and an alternate angle that leaves unrelated players and private locations out of the shot. ## Give each volunteer the shot and the audience in advance Say a creator asks for a flyover and a close walk through Willow Workshop. The owner arranges a private rehearsal area where the volunteer builders can be filmed with the door closed to normal traffic. The note says where the finished clip will appear, which builder names will be shown by agreement and who to tell if someone wants to sit out. Facepunch's creator FAQ addresses recorded videos. Your shoot still needs its own agreements about people and private details that could appear. Avoid relying on hidden overlays at the last moment. Pick a route that keeps a private base or travel path behind the camera. ## Break the shoot into two crew assignments Give someone other than the camera operator the job of watching the staging area. | Shot | What the crew checks | | --- | --- | | Outside approach | Line up on the marked approach. Confirm the background contains only the intended exterior and no private base markers or live players. | | Workshop interior | Use the closed entrance and wait for the volunteer host. Confirm names, signs and any recorded speech only include what was agreed. | | Fallback | Shoot the building from the fence without people in frame if the indoor route cannot stay clear. | ## Rewatch the export as the audience will see it In the Willow example, a spectator steps in during the approach take. The crew moves to the fallback angle and reshoots instead of trying to repair several frames and an audible name. Play the export at normal speed, then pause at both ends and during the move. Ask a builder to confirm the public view is what they agreed to. Publish the clip only after the operator can identify the permitted names, which world or site it promotes and whether visitors can go there. Give the creator the verified join post separately if the area shown is for filming only. ## Sources - [Facepunch: Rust support and video FAQ](https://rust.facepunch.com/support/) - [Facepunch: recording and playing Rust demos](https://wiki.facepunch.com/rust/Demos) ## Related resources - [Record and check a Rust demo for your community showcase](https://rustsc.com/learn/community/record-a-rust-demo-for-a-community-showcase/index.html.md) - [Run one Rust event with another community](https://rustsc.com/learn/community/one-rust-event-two-communities/index.html.md) --- HTML version: https://rustsc.com/learn/community/host-a-rust-creator-shoot-without-filming-players/ --- # Write a staff conduct agreement your Rust players can use [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Publish the standard players can hold staff to. Give the staff team a companion note explaining what to do when their duties conflict with their own play. ## Put the promise where players already read the rules A public entry for Fox Hollow could read ‘Staff play by the same rules as everyone else. We use staff tools only for agreed duties. Report staff conduct through this private route. Another lead will take the case when the usual contact was involved.’ Make the reporting route available to someone who cannot join the game. ## Write the matching actions in the staff space The private wording puts an owner against each promise without posting case evidence or staff-only access details. | Situation | Staff agreement | | --- | --- | | A moderator sees a report about their usual team. | Pass it to an uninvolved lead and keep the report in the private case space. | | A staff tool is needed to run a named event. | Write down which action the event permits and whether someone has to log the use. | | A player complains about a person assigned to receive reports. | Give the player the backup route and tell the backup lead to acknowledge receipt. | ## Test the agreement before asking people to sign up Ask a regular player to find the report destination and explain what staff may do during a casual game. Ask two moderators to read the same event exception and say what they would write down after applying it. If players can understand the promise but staff cannot agree on the action, keep the public line clear and add an example to the staff note. Get current staff to accept the same standard, including the owner when they play. Put the date and next review beside the agreement so an event exception cannot turn into a permanent staff privilege without anybody noticing. ## Sources - [Discord: developing moderator guidelines](https://discord.com/safety/developing-moderator-guidelines) - [Discord: confidentiality in moderation](https://discord.com/safety/confidentiality-in-moderation) ## Related resources - [How to write Rust server rules players can use](https://rustsc.com/learn/community/write-rust-server-rules-players-can-use/index.html.md) - [Review a report that a Rust moderator misused staff powers](https://rustsc.com/learn/community/review-a-rust-moderator-staff-powers-report/index.html.md) --- HTML version: https://rustsc.com/learn/community/write-a-rust-staff-conduct-agreement/ --- # What should you take off an overloaded Rust volunteer's plate? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Ask which job is hard to keep doing and remove a specific responsibility. A smaller shift or a real break is easier to use when everybody knows who will handle the work now. ## Ask about the job in private Say Lee still enjoys hosting Saturday build tours at Rowan Point and is also answering report pings most nights. The lead asks ‘Which of shop tours, Sunday reports and after-hours pings would you like to keep for now?’ Lee asks to keep the tour and step away from reports for two weekends. Agree what taking the job off means. Lee no longer watches the queue, gets no report pings and does not need to find cover. They can still play normally. The lead checks whether a notification role can be separated from any access needed for Saturday's tour. ## Give the team the handoff they need Share duties and hours with the staff group. Keep Lee's reasons private unless Lee asks to share them. | Duty | Cover for the next two weekends | | --- | --- | | Saturday tours | Lee hosts as usual and passes conduct concerns to a moderator. | | Monday report catch-up | Sam checks the queue and takes unresolved cases. | | Off-hours | Players can leave a private report. Advertise the next review window if no one is reading overnight. | ## Check whether the smaller job feels smaller Unassign Lee from reports that have already been handed over and check the next duty reminder goes to Sam. At the end of the second weekend ask privately whether the new split is working and whether Lee wants to keep it. A volunteer may choose to step back further. Arrange cover before telling people an old shift will resume. The handoff is complete when Lee can ignore a report without anyone waiting for them to act and the team can name who receives that report instead. ## Sources - [Discord: understanding and avoiding moderator burnout](https://discord.com/safety/understanding-and-avoiding-moderator-burnout) - [Discord: managing moderation teams](https://discord.com/safety/managing-moderation-teams) ## Related resources - [Make a Rust server staff rota people can stick to](https://rustsc.com/learn/management/make-a-rust-server-staff-rota/index.html.md) - [Reduce the Discord pings your Rust volunteers have to answer](https://rustsc.com/learn/management/reduce-rust-volunteer-pings/index.html.md) --- HTML version: https://rustsc.com/learn/community/reduce-one-rust-volunteers-workload/ --- # Run one events calendar for several Rust worlds [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Start with the names players see when they join. Keep a shared events calendar where each entry says which world it belongs to, when it starts and who is running it. ## Sort the conflict before publishing the calendar Suppose Loft Build offers a showcase at 18:00 UTC and Ridge Trio wants a tournament at the same time. Ellis is needed to open both. Keep the showcase at 18:00 and move the tournament after Ellis's duties finish, or find a separate tournament host before posting. Let each world confirm who can handle late arrivals. ## Make each public entry stand on its own Use one live entry per event and a shared list pointing to those entries. Discord Scheduled Events can describe an event somewhere outside a Discord voice channel. | Public entry | First details from the shared list | | --- | --- | | Loft Build • Workshop showcase | Saturday 18:00 UTC, Loft Build, meet at the blue workshop door. Ellis opens the door. | | Ridge Trio • Tournament check-in | Saturday 20:00 UTC, Ridge Trio, meet at the published starting grid. Bea checks arrivals. | ## Check from outside the staff room Ask a member who normally plays only Ridge where they would go for the Loft showcase. Share the event as an ordinary member would see it. Discord direct event links depend on the viewer's access, so test the actual link for the audience you expect to follow it. Link the world’s current join post where it can be opened. If Ellis drops out, update the affected loft entry and the shared calendar link. Let the other entry stand if it is still staffed. The check passes when people can find the correct time, world and starting point from each entry without asking a moderator. ## Sources - [Discord: Scheduled Events](https://support.discord.com/hc/en-us/articles/4409494125719-Scheduled-Events) - [Discord: managing moderation teams](https://discord.com/safety/managing-moderation-teams) ## Related resources - [Schedule an in-game Rust event in Discord](https://rustsc.com/learn/community/schedule-a-rust-game-event-in-discord/index.html.md) - [Which rules should all your Rust worlds share?](https://rustsc.com/learn/community/choose-shared-rules-for-multiple-rust-worlds/index.html.md) --- HTML version: https://rustsc.com/learn/community/run-one-event-calendar-for-your-rust-worlds/ --- # Why did a player take damage on your PvE Rust server? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Reproduce the reported interaction with disposable gear. Find out whether the same player takes the same kind of damage in the open, inside the affected area and across its edge before changing a rule for the whole world. ## Write down the exact symptom Suppose a visitor loses health while stepping beside a motorized vehicle at Willowbank's market exit. The original report calls it PvP but does not show an attack. Record the world, location, time, who controlled the vehicle and the player's state. Separate damage to the visitor from damage to the vehicle. Use a test copy and volunteers without staff immunity. Record the game and plugin versions as well as the local rules that should apply. Start with a direct test hit in the normal area to see whether ordinary player combat is blocked at all. ## Change one part of the test at a time If you use TruePVE, its rules and flags can apply differently depending on damage source and zone mappings. Zone Manager also has separate protection settings. | Compare | What to check next | | --- | --- | | The ordinary hit damages the player everywhere. | Check the active global damage handling and loaded ruleset before touching a zone. | | The ordinary hit is blocked in open terrain but counts across one side of the edge. | Check the local zone mapping and flags. Repeat with the attacker and target on opposite sides in both directions. | | An ordinary hit is blocked and health drops only beside the moving vehicle. | Reproduce with and without the vehicle on the same route. Check what the active rules cover for the object that actually lost health. | ## Fix the specific gap or tell players how to avoid it If the vehicle case reproduces away from the edge, Willowbank moves the pedestrian route away from moving vehicles while it works out what covers the damage. If the failure follows the edge, close the affected path until both crossing tests pass. Keep the unaffected rules in place. Repeat the exact original interaction and one nearby interaction that was already working. When the result matches both promises, share the reopened route with players. If the result still differs, say which area is affected and where to send another report. ## Sources - [TruePVE: damage rules and zone integration](https://umod.org/plugins/true-pve) - [Zone Manager: flags and zone settings](https://umod.org/plugins/zone-manager) ## Related resources - [What should you check before advertising a Rust server as PvE?](https://rustsc.com/learn/configuration/check-what-pve-means-on-your-rust-server/index.html.md) - [Should your PvE Rust server add a dueling area or a combat weekend?](https://rustsc.com/learn/community/choose-a-combat-format-for-a-pve-rust-server/index.html.md) --- HTML version: https://rustsc.com/learn/community/diagnose-unexpected-player-damage-on-a-pve-rust-server/ --- # Open your Rust builders' town for a guided tour [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Give players a tour they can walk without your building access. Start from a public landmark, keep the doors simple and name the last place a late visitor can join. ## Walk the route in arrival order For a three-stop tour of Chalk Wharf, have the town greeter start at the bridge lantern, take the group to the waterwheel overlook and finish at the public courtyard. Each stop has something to notice or try. The route stays clear of occupied houses and their cupboards. ## Assign each position before making the event public Give an ordinary visitor the directions. Keep the builders in their usual roles during the rehearsal. | Stop | Tour instruction | What staff verify | | --- | --- | --- | | Bridge lantern | Meet here first. Bring only what you need for the walk. | A player coming from the road can see the lantern and join the group. | | Waterwheel overlook | Wait on the terrace while the builder explains the design. | Everyone can pass without a guest code or building privilege. The route works when another player is standing there. | | Public courtyard | Finish and take pictures here. Late visitors can go straight here. | The exit is visible from inside. Only the agreed doors and spaces are accessible. | ## Have a fallback for the door that stays shut The test visitor finds the courtyard door locked when the builder logs out. Chalk Wharf moves the finish into the open garden or assigns someone to receive visitors on both sides of the door. Try that change with the guest who previously got stuck. Revise the public event text with the actual finish point. At the end, have the greeter walk the route once more to see if anyone missed the group or cannot leave. Tell late arrivals the tour has ended and which spaces remain public. The route is ready for another session when a guest can discover the meeting point and exit unaided. ## Sources - [Facepunch: Tool Cupboard, decay and building privilege](https://wiki.facepunch.com/rust/the_tool_cupboard) - [Discord: Scheduled Events](https://support.discord.com/hc/en-us/articles/4409494125719-Scheduled-Events) ## Related resources - [Help late players catch up at a Rust community event](https://rustsc.com/learn/community/help-late-players-join-a-rust-event/index.html.md) - [How can a visitor use one door in your Rust community workshop?](https://rustsc.com/learn/community/give-a-visitor-access-to-one-rust-workshop-door/index.html.md) --- HTML version: https://rustsc.com/learn/community/run-a-guided-rust-builders-town-tour/ --- # Clear a Rust report backlog after wipe weekend [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Clear the oldest visible blockage by giving each report one owner and one next step. Start with cases that still affect players, then check what needs a reply from the previous wipe. ## Take one snapshot of the waiting reports Say Ash Dock starts Monday with a report that someone is still posting abuse, two reports of the same access issue at the old spawn and a separate appeal about a ban that still applies. The shift lead gives each matter an owner and keeps the original messages linked privately. Check which cases still need design or moderation work. Wiping the map can remove a damaged structure or change a location. It does not decide an appeal or make an ongoing conduct report irrelevant. ## Work three different queues without creating more threads Use the existing case space and follow your published moderation rules. | Case | Next step and owner | | --- | --- | | Current abusive messages | Rin checks the still-active incident and applies the agreed response. Keep relevant evidence private. | | Two reports of the old spawn gate | Oli checks the new spawn, links the old reports and replies that the affected layout is gone if the new gate is usable. | | Local ban appeal | Pat keeps the appeal open and gives the player a private next update. The world reset leaves that separate decision with Pat. | ## Leave fewer cases waiting on someone nobody named Close the reports whose factual question has been answered and send a short private reply where useful. For each still open, record who will take the next action, when the reporter last heard from staff and the missing fact. Useful handoffs say ‘Pat is comparing the full clip to the join time’ rather than ‘someone look at this’. Ask the next volunteer to read the live queue and name the urgent case and the oldest untouched appeal without reading the whole weekend's chat. If they cannot, make the current priority and next owner easier to find. ## Sources - [Discord: transparency in moderation](https://discord.com/safety/transparency-in-moderation) - [Facepunch: reporting in Rust](https://support.facepunchstudios.com/hc/en-us/articles/10640775389853-Reporting-in-Rust) ## Related resources - [How to triage Rust player reports](https://rustsc.com/learn/community/triage-rust-player-reports/index.html.md) - [How to hand over an open Rust moderation case](https://rustsc.com/learn/community/hand-over-an-open-rust-moderation-case/index.html.md) - [Review F7 reports and find events](https://rustsc.com/support/guides/review-player-reports/index.html.md) --- HTML version: https://rustsc.com/learn/community/clear-a-rust-player-report-backlog-after-wipe/ --- # Hold a short staff debrief after a rough Rust wipe [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Pick one handoff or message that failed and examine how it happened. End with one change someone can check at the next wipe. ## Put three moments on one timeline Suppose Greywater's owner finished post-wipe world checks at 19:08 UTC, a moderator left at 19:10 and the next volunteer repeated ‘still down’ at 19:15. Ask what each person actually saw and where they looked. Keep this discussion about the shared sequence. A separate lead can review a specific conduct concern in private if needed. ## Find the step that would have changed what players heard The team finds two pinned posts. The person coming on shift saw the older one first. | Moment | What the team can fix | | --- | --- | | 19:08, a fresh join works. | The operator writes the confirmed result and time in one shared status post. | | 19:10, the shift ends. | The outgoing volunteer tells the incoming person where to check the current result. | | 19:15, the player reply is written. | The incoming volunteer reads the one post before sending a status update. | ## Write one test for next time Assign Ivy to update and pin one status post before the next wipe. Eli, who just came on shift, should be able to find it and repeat the current status and time from that post. Set the date for that check now. Leave other suggestions in the notes until the team knows if the one change worked. End by asking someone who missed the discussion to name the change, the owner and the moment to verify it. If the note says only ‘communicate better’, replace it with the action people actually agreed to take. ## Sources - [Discord: managing moderation teams](https://discord.com/safety/managing-moderation-teams) - [Discord: developing moderator guidelines](https://discord.com/safety/developing-moderator-guidelines) ## Related resources - [How to hand over a Rust server outage to another helper](https://rustsc.com/learn/management/hand-over-a-rust-server-outage/index.html.md) - [What to tell players when your Rust server goes down](https://rustsc.com/learn/community/rust-outage-status-post/index.html.md) --- HTML version: https://rustsc.com/learn/community/debrief-with-rust-staff-after-a-rough-wipe/ --- # Resolve a disagreement between your Rust moderation leads [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Keep one decision in force while you resolve the disagreement. Name the person who owns that decision and give the other lead a private place to explain what they see differently. ## Keep the immediate duty separate from the policy question Say Mat wants to permanently ban a player from Amber Bay after repeated event disruptions. Iona thinks the last warning never reached the player and wants a temporary action while they review. Players are waiting at the event gate. The owner assigns Iona the event response under the existing rules and schedules a separate private review of any ongoing restriction. Have both describe the case using the same facts. Ask which part they agree on and which missing fact would change the response. Keep player replies with the named reviewer so two staff messages cannot give two outcomes. ## Hear the leads before writing a wider rule Iona reads the warning record and Mat describes prior incidents. They find that the rule says ‘after a warning’ but does not say how the warning reaches the player. The owner asks what evidence of delivery they can realistically check. They agree the event lead can end immediate disruption and the reviewer can consider a longer restriction once the documented warning is confirmed. In the staff note, replace the vague instruction with the agreed action, who has it and the boundary between event response and case review. If the wider lead remit was part of the conflict, record who can decide it during the owner's absence. ## Read the agreement back on a different case Give Mat and Iona a new example with a clear warning and an event about to start. Each should identify the immediate event owner, the later restriction reviewer and who communicates the result. Revisit the staff note if they still give the player two possible answers. After the test, tell the team what changed without airing the original argument. ## Sources - [Discord: managing moderation teams](https://discord.com/safety/managing-moderation-teams) - [Discord: developing moderator guidelines](https://discord.com/safety/developing-moderator-guidelines) ## Related resources - [How to correct a moderation mistake on your Rust server](https://rustsc.com/learn/community/correct-a-rust-moderation-mistake/index.html.md) - [Get two Rust moderators to apply the same rule consistently](https://rustsc.com/learn/community/calibrate-rust-moderators-on-one-rule/index.html.md) --- HTML version: https://rustsc.com/learn/community/resolve-a-disagreement-between-rust-moderation-leads/ --- # Tell players when one of your Rust worlds is taking a break [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Say which world is paused and which are open. Give people who usually play the paused world one next update and a clear choice if they want somewhere else to play now. ## Publish a short sequence from the affected world's post Suppose Cliff Builds is pausing while the operator decides what its next season will look like. North PvE remains open. The same headline and dates appear wherever Cliff's regulars get notices. | When | Example message | | --- | --- | | Before the pause | Cliff Builds pauses Sunday after the open house. We will post its next update on Thursday at 19:00 UTC. | | When the pause starts | Cliff Builds is paused. North PvE is open at its usual address. It has its own rules and world progress. | | At the next decision | Cliff Builds remains paused this week. We will share the next opening date here when it is agreed. The other worlds follow their usual schedule. | ## Keep the optional alternative in its own terms Open the current North PvE join post using an ordinary account. Check that its world name, rules and progress expectations are accurate. Say plainly what happens to a player's Cliff work during the pause. If the team has agreed only to keep the existing world offline, avoid telling players they can carry buildings or inventories over. If you extend the pause, update the same post where returning Cliff players already look. Ask a player who missed the first message to read the current one and identify the paused world, one open option and the date of the next update. Revise if they think the entire community has closed. ## Sources - [Facepunch: Community Server and Hosting Guidelines](https://facepunch.com/legal/servers) - [Discord: managing moderation teams](https://discord.com/safety/managing-moderation-teams) ## Related resources - [How to tell players your Rust server is closing](https://rustsc.com/learn/community/tell-players-a-rust-server-is-closing/index.html.md) - [Which rules should all your Rust worlds share?](https://rustsc.com/learn/community/choose-shared-rules-for-multiple-rust-worlds/index.html.md) --- HTML version: https://rustsc.com/learn/community/announce-a-temporary-pause-on-one-rust-world/ --- # How should you reclaim an abandoned plot in a Rust village? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Use the absence policy players saw when they took the plot. Try a private contact, give a clear deadline and spell out what the next resident can build or use before handing it over. ## Check the claimed plot before assuming it is empty Suppose the mill plot at Mossbridge has an apparently abandoned workshop and a locked cupboard. The steward finds the resident's name in the plot record, the season's original published absence rule and a recent message saying the resident was travelling. An empty cupboard or decaying wall can show what needs attention. It cannot tell you whether somebody gave notice. If you have no rule the previous resident saw, agree a voluntary handback or publish a rule for future claims. Put uncertain access or ownership in the staff notes before anyone attempts to change the building. ## Use a notice that gives the player a real choice In this example, the published rule allows a private notice before reclaiming a plot. The steward sends the resident the claim name, date, time zone and contact. | Resident's reply | Steward's next move | | --- | --- | | I am returning this weekend. | Check the published terms, agree a return date and keep the plot reserved if the agreement allows it. | | I am finished with this plot. | Agree which belongings they want to collect and when the next resident can view the space. | | No reply by the notice date. | Check the notice actually went to the correct contact and follow the published process with a second steward. | ## Hand over the space the next owner can actually use List whether the plot is empty or includes agreed shared structures and which paths remain public. Have the next owner walk the boundary and try the intended access using their own account. Cupboard authorization, an old door and the name on the claim sheet can each tell a different story. Resolve those differences before confirming the handoff. Finish when the former resident has had the agreed chance to respond, the town knows the current plot steward and the new resident can use the agreed space without relying on old codes. ## Sources - [Facepunch: Tool Cupboard, decay and building privilege](https://wiki.facepunch.com/rust/the_tool_cupboard) - [Facepunch: Community Server and Hosting Guidelines](https://facepunch.com/legal/servers) ## Related resources - [Lay out a Rust village with private plots and open paths](https://rustsc.com/learn/community/lay-out-a-rust-village-with-private-plots/index.html.md) - [How to announce a Rust server rule change](https://rustsc.com/learn/community/announce-a-rust-server-rule-change/index.html.md) --- HTML version: https://rustsc.com/learn/community/return-an-abandoned-plot-to-your-rust-village/ --- # Pair a new PvE Rust player with a guide for one session [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Offer a guide after a new player reaches your world. Pick one task they want to learn and a meeting place they can find from the public directions. ## Let the newcomer pick the first job For example, a volunteer named Zed could meet Asha at the public lantern on Oak Lane's spawn road. Zed asks whether Asha wants to build a first shelter, find water or locate the market. Asha picks the shelter. Facepunch's Tutorial Island teaches the game's basics on a separate island on compatible servers. The volunteer session starts when Asha is on the main map and can use Oak Lane's local routes. ## Show one action, then give the player a turn Use supplies the player can afford to lose and a place where the activity fits the server's rules. 1. Walk from the lantern to a marked practice spot and point out the route back. 2. Demonstrate one action the player asked about. Let them repeat it before adding more instructions. 3. Let Asha identify the next thing to gather and how to find the practice spot again from the lantern. ## Close the session with something the player can do Asha can place a sample foundation but cannot remember the way from the lantern. Zed walks back with them and lets Asha lead the return. The finished session is Asha placing the foundation once and pointing to the correct road from the lantern. Give them the short town guide and which channel or steward can answer later questions. Keep the guide's shift time explicit and keep mentoring optional. If the guide cannot make the meeting, tell the player where they can start on their own. Do not make a newcomer wait for a particular volunteer to join your normal world. ## Sources - [Facepunch: Tutorial Island](https://wiki.facepunch.com/rust/Tutorial_Island) - [Discord: training and onboarding moderators](https://discord.com/safety/training-and-onboarding-new-moderators) ## Related resources - [How to check Tutorial Island on your Rust server](https://rustsc.com/learn/configuration/enable-and-check-rust-tutorial-island/index.html.md) - [Run a tool-lending bench for new PvE Rust players](https://rustsc.com/learn/community/start-a-rust-pve-tool-lending-bench/index.html.md) --- HTML version: https://rustsc.com/learn/community/pair-new-rust-pve-players-with-a-volunteer-guide/ --- # Bring a Rust moderator back after a long break [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Give a returning moderator the changes that affect their next shift. Agree what job they want, then practice a case under the rules they will use now. ## Compare the old job with the one they want back Suppose Kim is returning to Salt Quarry as a moderator. A second world has opened and appeals now go to another lead. Kim wants one evening of normal reports on the original world and no appeal duty. Send Kim the latest player rules, report link and shift contact. Mark only the differences that affect their new work. ## Walk through what changed before restoring access Keep this practice case separate from real reports. | Change since Kim left | Return check | | --- | --- | | The quarry's second world has its own local rules. | Kim identifies which rule page and person apply to a report from the other world. | | Appeals go to a separate lead. | Kim hands off a practice appeal in private and knows who confirms it was received. | | The named duty is one world on one evening. | The owner checks the roles assigned in each tool against the duty. Kim can reach the agreed reports and other assignments remain with their owners. | ## Make the first evening a supported shift If Kim cannot reach the private report space, check the intended world scope and role using your actual tool. Add only the documented access needed for the duty. A game staff role and a Discord role can be separate even when they share a name. If the tool lets you scope this duty by world, ask Kim to confirm from their own account that the other world's private queue stays out of reach. If it cannot scope that queue, check the account's effective access as owner and choose a narrower task or a different route for it. Ask another lead to help with work outside the current remit. After the shift ask Kim which change was hard to remember. Update the short return note and verify Kim can name the next shift, the applicable world and the appeal contact without reading the archive. ## Sources - [Discord: training and onboarding moderators](https://discord.com/safety/training-and-onboarding-new-moderators) - [Discord: roles and permissions](https://support.discord.com/hc/en-us/articles/214836687-Discord-Roles-and-Permissions) ## Related resources - [How to check a Rust moderator’s access after a role change](https://rustsc.com/learn/community/verify-a-rust-moderator-access-change/index.html.md) - [Understand workspace roles](https://rustsc.com/support/guides/workspace-roles/index.html.md) --- HTML version: https://rustsc.com/learn/community/bring-a-rust-moderator-back-after-a-break/ --- # Give a Rust volunteer their first lead shift [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Give the acting lead a defined shift and the authority needed to keep volunteers working. Write down which changes still wait for the owner and who is next if someone needs an immediate answer. ## Name the decisions, not just the title For example, Jo can move a report to another moderator and approve a short pause to the evening event during Cairn Coast's Sunday shift. Jo cannot revise the player rules or change staff access. The owner names a backup reachable during the shift and an exact time when the owner takes decisions back. ## Ask three volunteers to make practice requests Jo should see the same staff reference and contact list they will have on Sunday. | Request | What Jo does | | --- | --- | | A volunteer cannot finish a report. | Assign it to a named available moderator, who confirms receipt. | | An event argument is getting in the way of play. | Pause the event if needed and assign the conduct report separately using the existing escalation route. | | Someone needs broader staff access for a future duty. | Record the request with the work it would enable and pass it to the owner at handback. | ## Keep people from making the same decision twice Post the shift window privately, name Jo as the active lead and tell staff where to leave anything Jo cannot decide. Give Jo only the access the actual duty uses. Much of this lead job can be done in a private staff channel without changing server administration. At the end, Jo gives the owner the open decisions, their current assignees and any player update owed. The owner confirms receipt. The rehearsal passes if a volunteer can tell who owns a pending request before and after that handback. ## Sources - [Discord: managing moderation teams](https://discord.com/safety/managing-moderation-teams) - [Discord: developing moderator guidelines](https://discord.com/safety/developing-moderator-guidelines) ## Related resources - [Hand one Rust maintenance window to a helper](https://rustsc.com/learn/management/delegate-a-rust-maintenance-window/index.html.md) - [Make a Rust server staff rota people can stick to](https://rustsc.com/learn/management/make-a-rust-server-staff-rota/index.html.md) --- HTML version: https://rustsc.com/learn/community/give-a-rust-volunteer-the-first-lead-shift/ --- # Handle one conduct incident reported from two Rust worlds [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Give the shared conduct question one reviewer. Let each world handle its own play rule, with a clear record of which decision applies where. ## Record where each part happened Suppose a player on Shoreline's Ridge Trio world reports a suspected team-size breach. Later, a volunteer on Loft Build receives a report that a player followed someone there to harass them about the same match. Use the reports to establish the place, time and action. Keep an uncertain account match open for checking rather than merging people who use similar names. ## Give each question a rule and an owner One reviewer can coordinate the answers while the world steward confirms the relevant local facts. | Question | Scope and decision owner | | --- | --- | | Did the Ridge team break Ridge's group rule? | A Ridge steward checks the event and decides any local action. | | Did someone violate the community's common harassment rule on Loft? | An uninvolved reviewer checks the linked conduct report against the common policy. | | Does the resulting action apply on every world? | Apply the published scope of the rule and the evidence. Record why a world-specific or common response fits. | ## Check what each world has to do before closing Tell each reporter enough about their own report to understand its outcome. Keep the other world's evidence in the restricted case space unless a reviewer needs it for the decision. If your rule gives a common response, verify the action actually applies on the named worlds using their tools. If the action is local, confirm the other world has received only the relevant update. Ask the next on-duty moderator to identify which rule applied, which world is affected and who handles a follow-up. If they give a wider answer than the recorded action, correct the handoff and the private player reply before closing. ## Sources - [Facepunch: reporting in Rust](https://support.facepunchstudios.com/hc/en-us/articles/10640775389853-Reporting-in-Rust) - [Discord: confidentiality in moderation](https://discord.com/safety/confidentiality-in-moderation) ## Related resources - [What to do when several Rust players report the same incident](https://rustsc.com/learn/community/handle-duplicate-rust-player-reports/index.html.md) - [Which rules should all your Rust worlds share?](https://rustsc.com/learn/community/choose-shared-rules-for-multiple-rust-worlds/index.html.md) - [Review F7 reports and find events](https://rustsc.com/support/guides/review-player-reports/index.html.md) --- HTML version: https://rustsc.com/learn/community/handle-a-conduct-incident-reported-from-two-rust-worlds/ --- # Help players choose the right world in your Rust community [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) A player who wants a monthly world should be able to choose it without knowing your staff's nicknames. Give each listing and join link the same recognizable name, then get a new player to try both routes. ## Put the player decision before the address Harbor runs two worlds for different kinds of play. An example join note might look like this. Replace the labels and rules with what your community offers. | World | For players who want | What to copy into your post | | --- | --- | --- | | Harbor Weekly | PvP and a fresh world each week | Actual next wipe date and time, region, player cap and the join link for Harbor Weekly. | | Harbor Monthly | PvE building across the month | What damage and looting are allowed, actual next wipe, region and the join link for Harbor Monthly. | ## Make the browser and join note agree Read the live server name in the Rust browser before you publish. Check the wipe and mode tags are accurate for that world. Facepunch groups some tags as mutually exclusive, so give each world the correct cadence and mode. In Discord, pin the chooser in the player join channel and update the same message when an address changes. ## Give the note to one player who has never joined Ask them to pick the world where they could build peacefully for a month. Watch which entry they select and ask them to say the world name they see after joining. Repeat with a weekly PvP player. Fix any matching names, wrong addresses or unclear rules, then have them follow the corrected route without staff help. ## Sources - [Facepunch server browser tags](https://wiki.facepunch.com/rust/server-browser-tags) - [Discord pinned messages](https://support.discord.com/hc/en-us/articles/221421867-Pin-Messages-FAQ) ## Related resources - [Keep one current Rust join post in Discord](https://rustsc.com/learn/community/one-current-rust-join-post/index.html.md) - [Which Rust server tags should you show?](https://rustsc.com/learn/configuration/choose-rust-browser-tags-that-describe-your-game/index.html.md) - [What should you check before advertising a Rust server as PvE?](https://rustsc.com/learn/configuration/check-what-pve-means-on-your-rust-server/index.html.md) --- HTML version: https://rustsc.com/learn/community/help-players-pick-the-right-world-in-your-rust-community/ --- # An Oxide plugin loaded. Why is a player denied permission? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md) Once the server console confirms the plugin loaded, check the player and the particular command they tried. A plugin can be ready while its commands are still restricted to certain players. ## Find the permission for the command Look up the command in the plugin author's documentation. In the server console, run oxide.show perms to check that the permission listed by the author is registered. If it is missing, check the installed plugin version and review its console messages before trying to grant it. Run oxide.show user followed by the affected player's Steam ID. Check their group membership as well. If access should come through a group, use oxide.show group followed by the group name and check any parent groups. ## Grant the action to the people who need it If one player needs access, use oxide.grant user followed by their Steam ID and the exact permission. For example, if a sample plugin had separate townmarket.use and townmarket.admin permissions, give a player townmarket.use when their job is simply to open the market. Use the actual permission from your plugin. If the same command belongs to an existing staff role, grant it to that group and confirm the player is a member. Have the affected player run the original command again and check that it opens or performs the action they asked for. Testing with your own admin account would only check your access. ## Sources - [Oxide owner guide to permissions](https://docs.oxidemod.com/guides/owners/permissions) - [Oxide permission command reference](https://docs.oxidemod.com/core/commands/permission) ## Related resources - [Groups and permissions](https://rustsc.com/support/guides/player-permissions/index.html.md) --- HTML version: https://rustsc.com/learn/community/oxide-plugin-loaded-player-permission-denied/ --- # How to bring your Rust server back after a power cut [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Automatic recovery has two parts. The host must power on when power returns, and the operating system must start your server when it boots. ## Set what the host does when power returns Check the manual for your host or its motherboard for its power recovery setting. Some hosts offer a choice such as power on or restore the last power state. Choose the behaviour you want for your dedicated host. If the host stays off after an outage, an operating system startup task has no chance to run. ## Check Rust starts before anyone logs in Use one startup method that launches the intended server. On Windows, use a Task Scheduler boot trigger if you use a scheduled task. On a Linux host using systemd, enable the configured server service. Run a planned reboot while you can reach the host. Leave it at the sign-in screen and have a client connect to the expected world. A planned reboot checks the server startup part. Separately, check the firmware behaviour during planned downtime on a spare host with similar hardware if available. Avoid pulling power during a live game just to test recovery. ## Sources - [Example Dell firmware manual for power recovery](https://dl.dell.com/manuals/common/dell-emc-remote-wake-up-config-dell-client-cmd-suite.pdf) - [Microsoft guide to starting a task at boot](https://learn.microsoft.com/en-us/windows/win32/taskschd/starting-an-executable-on-system-boot) - [systemd documentation for services started at boot](https://www.freedesktop.org/software/systemd/man/latest/daemon.html) ## Related resources - [Host offline](https://rustsc.com/support/guides/computer-offline/index.html.md) - [Start, stop or restart a server](https://rustsc.com/support/guides/start-stop-restart/index.html.md) --- HTML version: https://rustsc.com/learn/management/rust-server-start-after-power-returns/ --- # How to choose a host reboot window around two Rust worlds [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Put both worlds’ events on one clock. A quiet moment on the first world can be the start of the second world’s busiest session. ## Lay out one evening before choosing a time Suppose Harbour has a backup booked for 19:00 UTC, Valley opens a fresh map at 20:00 UTC, and you can reach the host until 22:30 UTC. Ask each world’s helper when their work will finish. A booking marked “start” tells you little about when the host will be free. | Candidate | What conflicts | Decision | | --- | --- | --- | | 19:00 UTC | Harbour begins copying its world. | Leave the host running until the backup finishes. | | 20:00 UTC | Valley players are arriving for the new map. | Keep the launch window clear. | | Later that evening | Both jobs have finished. You still need someone available to rejoin. | Agree on a time with the helper or choose another evening. | ## Publish one window both communities can use Write the start time, time zone and both world names in the notice. Include where players will hear that each world has reopened. Keep a copy beside the host’s maintenance entry so a helper sees the same schedule players see. Check both calendars once more before sending the notice. If a wipe or backup moved, choose a fresh window and replace the announcement in both places. Leave enough time for someone to check each world before their shift ends. ## Sources - [Facepunch console command reference](https://wiki.facepunch.com/rust/useful_commands) - [Microsoft guide to starting a task at boot](https://learn.microsoft.com/en-us/windows/win32/taskschd/starting-an-executable-on-system-boot) - [systemd documentation for services started at boot](https://www.freedesktop.org/software/systemd/man/latest/daemon.html) ## Related resources - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/index.html.md) - [Start, stop or restart a server](https://rustsc.com/support/guides/start-stop-restart/index.html.md) --- HTML version: https://rustsc.com/learn/management/choose-a-maintenance-window-for-host-reboot/ --- # How to restart a Rust server without losing the latest save [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Warn your players first, then let Rust save and exit normally. Wait for the game process to finish before starting it again. ## Give the world time to save Use your host panel’s normal stop action if it performs a graceful shutdown. If you run the dedicated server console directly, `quit` saves and closes the game. Facepunch also documents `sv quit` for an administrator using the in-game console. Watch the console through shutdown. A process you end in Task Manager or kill immediately may leave recent progress unsaved. ## Check the first join after restart Keep the same server identity and world settings. After startup, join and check one known change from just before the restart, such as a recently placed object. If the world is empty or the change is missing, stop and confirm which save loaded before allowing more play. ## Sources - [Facepunch Rust dedicated server setup](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch Rust console commands](https://wiki.facepunch.com/rust/useful_commands) ## Related resources - [Start, stop or restart a server](https://rustsc.com/support/guides/start-stop-restart/index.html.md) --- HTML version: https://rustsc.com/learn/management/restart-rust-without-losing-the-latest-save/ --- # Should you restart Rust or reboot the host? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Restart the game for a game-only change. Reboot the host when maintenance needs the operating system to restart or a host-wide fault calls for it. ## Changed one game setting? Restart that game If two game servers share one host and you change the launch arguments of one, restart only that game. Afterward its process should have a new start time while system uptime continues. Players on the other server should stay connected. ## Windows asks for a reboot? Close both games first Before applying a system update that explicitly needs a reboot, tell players on both servers, stop both normally and confirm they have exited. When the host comes back, check that Windows booted again and each intended game started. Check the System log if the timing is unclear. Join each affected server before reopening it. ## Sources - [systemd service reference](https://www.freedesktop.org/software/systemd/man/latest/systemd.service.html) - [Microsoft Windows reboot events](https://learn.microsoft.com/en-us/troubleshoot/windows-server/performance/troubleshoot-unexpected-reboots-system-event-logs) ## Related resources - [Start, stop or restart a server](https://rustsc.com/support/guides/start-stop-restart/index.html.md) --- HTML version: https://rustsc.com/learn/management/restart-rust-or-reboot-the-host/ --- # Track disk space as your Rust world grows [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Measure the free space on the drive that holds the active world before and after a routine save. Repeat at similar points in the wipe cycle so one busy save does not become a long-term estimate. ## Track the drive and the world separately Find the active world through the server identity in the startup settings. On Linux, `df -h` against that folder shows the space left on its filesystem, while `du -sh` against the folder estimates the space its files occupy. Measure the backup destination separately, especially when it sits on another drive. ## Work out the room a backup needs This backup used another 8 GB at its peak and left 5 GB of new files behind. Use the peak when checking whether the next job fits, then leave extra room for growth. A growing server can need more room next time. If the drive loses room faster than the active world grows, measure the other directories before removing saves. After making room, watch one complete save and backup and check the space left afterward. | When you looked | Free space | | --- | --- | | Before the backup | 30 GB | | Lowest reading during the backup | 22 GB | | After the backup finished | 25 GB | ## Sources - [Facepunch Rust dedicated server setup](https://wiki.facepunch.com/rust/Creating-a-server) - [GNU df manual](https://man7.org/linux/man-pages/man1/df.1.html) - [GNU du manual](https://man7.org/linux/man-pages/man1/du.1.html) ## Related resources - [Free disk space](https://rustsc.com/support/guides/free-disk-space/index.html.md) --- HTML version: https://rustsc.com/learn/management/measure-rust-save-growth-before-disk-fills/ --- # What to do when Rust logs fill the drive [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Identify which logs are growing before deleting anything. The combined size matters, but the fastest-growing file tells you what is likely to fill the drive again. ## Measure the game and host logs separately Compare the size of the game’s log folder and any framework log folder, then repeat after a busy period. On Linux, if the game logs to systemd, `journalctl --disk-usage` reports how much the journal uses. Journal retention settings apply to the journal itself. A separate framework log file needs its own retention setting. ## Keep an example of the repeating problem If one error repeats, save a short excerpt with its times before moving closed logs to a separate drive. Leave the active world and current log in place. Adjust retention in the software that owns the files. Confirm the next busy session produces readable new logs and that the drive is no longer losing space at the old rate. ## Sources - [GNU du manual](https://man7.org/linux/man-pages/man1/du.1.html) - [systemd journal storage settings](https://freedesktop.org/software/systemd/man/latest/journald%40.conf.html) - [systemd journalctl reference](https://www.freedesktop.org/software/systemd/man/latest/journalctl.html) ## Related resources - [Free disk space](https://rustsc.com/support/guides/free-disk-space/index.html.md) --- HTML version: https://rustsc.com/learn/management/rust-disk-filling-with-logs/ --- # Schedule a Rust restart in your players’ time zone [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Choose whether the restart should stay at the same clock time for your players or at the same UTC time year-round. Most community announcements are easier to keep when the scheduler follows the players’ local time. ## Check which time zone the schedule uses Use a named zone such as `Europe/London` if the scheduler accepts one. On a Linux host using systemd, calendar expressions can include a zone. For an existing Windows scheduled task, check its trigger and any offset in the start time. Remote panels may show a different time zone from your game host. ## Check a date after the clocks change Compare two dates in the scheduler’s next-run preview or equivalent calendar calculation. In this example, both should land at 05:00 in London. Use a time outside the clock change itself so it does not fall in a skipped or repeated hour. | Season | London time | UTC | | --- | --- | --- | | Winter | 05:00 | 05:00 | | Summer | 05:00 | 04:00 | ## Sources - [systemd calendar and time zone syntax](https://www.freedesktop.org/software/systemd/man/latest/systemd.time.html) - [systemd timers](https://www.freedesktop.org/software/systemd/man/latest/systemd.timer.html) - [Microsoft Task Scheduler trigger time](https://learn.microsoft.com/en-us/windows/win32/taskschd/trigger-startboundary) ## Related resources - [Schedule a restart or update](https://rustsc.com/support/guides/schedule-tasks/index.html.md) --- HTML version: https://rustsc.com/learn/management/schedule-rust-restart-in-player-time-zone/ --- # How to reboot a host running several Rust servers [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Warn all affected communities, stop each game cleanly, then reboot the host. If the worlds compete for memory or disk during startup, bring them back one at a time. ## Before the warning Write down which servers are running and how each starts after reboot. If you need a staged startup, use the service manager or panel to choose that order before you reboot. ## During shutdown Check for a game restart or update already due in the same window and move it if it could interfere. Once players have received the warning, save and stop each game normally. Wait until all have exited before rebooting. ## Bring back one world, then the next Wait for the first server to load its expected world and accept a connection. Check whether enough RAM and disk bandwidth are available before starting the next. ## Before reopening to players Confirm that each game is on its own expected save and that any restart you moved has a sensible next run. Join each world once. If a world failed to load, keep that one closed and record its last startup message while the others stay up. ## Sources - [Facepunch Rust console commands](https://wiki.facepunch.com/rust/useful_commands) - [systemd service reference](https://www.freedesktop.org/software/systemd/man/latest/systemd.service.html) - [Linux kernel pressure stall information](https://docs.kernel.org/accounting/psi.html) - [Microsoft Windows reboot events](https://learn.microsoft.com/en-us/troubleshoot/windows-server/performance/troubleshoot-unexpected-reboots-system-event-logs) ## Related resources - [How to choose a host reboot window around two Rust worlds](https://rustsc.com/learn/management/choose-a-maintenance-window-for-host-reboot/index.html.md) - [Start, stop or restart a server](https://rustsc.com/support/guides/start-stop-restart/index.html.md) --- HTML version: https://rustsc.com/learn/management/reboot-a-host-with-several-rust-servers/ --- # Replace a Rust restart script one job at a time [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Read what the old script does before switching it off. One loop may handle launching, restarts after an exit and updates, and each job needs a clear owner. ## Find what the old script actually runs Write down the executable path, game options and server identity, then check whether a scheduled task or service launches the script. If the script jumps back to an update or launch step after the game exits, it can try to start the game while the new tool is trying to do the same job. ## Hand over the next scheduled job first Test on a spare copy first. Give the new tool one scheduled restart and check that only one process starts. If the old script automatically launches the game whenever it exits, disable that loop before the new tool takes over. If you cannot disable it separately, rehearse the launcher and restart together before switching them on the live server. In the announced live window, verify one stop, one new start and a join to the original world. Leave independent jobs where they are until you can verify each transfer. Test crash recovery on a spare copy and confirm a deliberate stop stays stopped. ## Sources - [Facepunch Rust dedicated server setup](https://wiki.facepunch.com/rust/Creating-a-server) - [systemd service reference](https://www.freedesktop.org/software/systemd/man/latest/systemd.service.html) ## Related resources - [Move a server you already run into RustSC](https://rustsc.com/support/guides/move-existing-server/index.html.md) --- HTML version: https://rustsc.com/learn/management/replace-an-old-rust-restart-script-safely/ --- # What to tell players in Discord and in Rust chat on wipe day [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Put the full wipe notice in the place players check outside the game. Keep the in-game message short so people who are playing know what is about to happen. ## Give the two messages different jobs In Discord, put the date, time, reset scope and where to look for reopening in one post. For example, tell people the map resets at the announced time, learned items carry over if confirmed, and updates will appear in that thread. In game chat, warn people shortly before you stop the server. Say that the map wipe is about to start and tell them where to check whether the server is back. If timing changes, update the pinned post first and give current players the revised message. ## A short game warning you can reuse “Map wipe at 19:00 UTC. Finish what you’re doing. Check our Discord wipe post for reopening.” Send the same warning on each planned wipe so someone who joins late can still see what is about to happen. ## Check what a player can find Ask a staff member to read the community post as someone who is offline and to watch the warning in game as someone online. Have them find the same current notice in both places. Send the reopening message once a player can join the new world. ## Sources - [Facepunch console command reference](https://wiki.facepunch.com/rust/useful_commands) - [Facepunch reference for Rust save files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) ## Related resources - [Messages, restarts and wipes: what players see](https://rustsc.com/support/guides/player-messages/index.html.md) - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/index.html.md) --- HTML version: https://rustsc.com/learn/management/rust-wipe-messages-for-discord-and-game-chat/ --- # How to announce a Rust wipe across time zones [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Open the next run of the job that will perform the wipe. Use its actual date and time to write the announcement. A Discord timestamp shows that instant in each reader’s local time, and a plain UTC time travels with the message. ## Write a wipe announcement Enter the agreed time in UTC. Discord will show it in each reader’s time zone. **Worked example** For 18:00 UTC on 1 January 2027, copy this message: Map wipe at `` (2027-01-01 18:00 UTC). Blueprints carry over. ## Start with the full date from the wipe job For example, Friday 11 December 2026 at 00:30 UTC falls on Thursday evening for a player at UTC−05:00. Write the date, time and zone together even if you normally tell regulars the weekday alone. For a local recurring schedule, check the next date in its named time zone. When clocks change, the UTC hour can move while the local hour stays the same. | UTC | At UTC−05:00 | At UTC+10:00 | | --- | --- | --- | | Friday 11 December at 00:30 | Thursday 10 December at 19:30 | Friday 11 December at 10:30 | ## Write the Discord notice and the UTC fallback Discord uses seconds since the Unix epoch. For the example above, use in a regular Discord message. The capital F asks Discord to show the full date and time. A copyable message is “Harbour map wipe at (Friday 11 December 2026, 00:30 UTC). Blueprints stay.” Replace the server, timestamp and what resets before sending. Paste the timestamp as ordinary text in a private test message. Ask a player in another zone to read back the weekday and hour they see. Copy the plain UTC part into places that do not display Discord timestamps, such as game chat. ## Check the two places that can get out of step Compare the test message with the scheduler’s next run. If you also display Rust’s in-game countdown, compare that separately. Facepunch’s PrintWipe output shows the next timer date, which can come from an override. The announcement and the countdown need to agree with the job that will actually reset the world. For a recurring wipe, generate a fresh timestamp from the next run before reposting. If a clock change leaves the game timer or the scheduler showing a different instant, correct the schedule or countdown before posting the new date. ## Sources - [Facepunch wipe timer reference](https://wiki.facepunch.com/rust/server-wipe-timer) - [IANA time zone database and daylight saving changes](https://www.iana.org/time-zones) - [Discord timestamp styles](https://docs.discord.com/developers/reference#message-formatting) ## Related resources - [Schedule a wipe](https://rustsc.com/support/guides/schedule-wipe/index.html.md) - [Messages, restarts and wipes: what players see](https://rustsc.com/support/guides/player-messages/index.html.md) --- HTML version: https://rustsc.com/learn/management/plan-a-rust-wipe-across-time-zones/ --- # How to hand over a Rust server outage to another helper [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Before you step away during an outage, leave the next helper one message with the affected world, the last player-visible result and the next task. Get their reply before they take over so two people don’t work on the same restart or tell players different things. ## Put the handoff in the order they’ll use it Start with what the players are seeing and when you verified it. Link to the relevant host ticket or evidence and write the last action and its result. State the next action, who should do it and when you promised to post again. Keep the handoff in the shared incident thread so a third helper can catch up. | Field | Example handoff | | --- | --- | | What players see | Harbour Solo joins time out. Two friends tried at 21:05 UTC. | | Last action | Asked the rental host to check the connection. Ticket linked in this thread. | | Next action | When the host replies, ask Erin to try the usual join line. Post the result in #updates at 21:30 UTC. | | Taking over | Kai has the server from 21:15 UTC and will post the 21:30 update. | ## Make the transfer visible Ask the incoming helper to reply with what they will do first. If they are still travelling or cannot check until later, agree who is covering the gap. Update the thread with the name of whoever is currently handling it. If nobody can take it, tell players when you’ll be back to check. Leave an unresolved host ticket and the last tested result in the thread so you can pick up where you stopped. ## Sources - [Google SRE guidance on a shared incident record and acknowledged handoff](https://sre.google/sre-book/managing-incidents/) - [Discord threads for following a single conversation](https://support.discord.com/hc/en-us/articles/4403205878423-Threads-FAQ) ## Related resources - [What to tell players when your Rust server goes down](https://rustsc.com/learn/community/rust-outage-status-post/index.html.md) --- HTML version: https://rustsc.com/learn/management/hand-over-a-rust-server-outage/ --- # Make a Rust server staff rota people can stick to [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Arrange cover around when people already want to be online. Name one person for each covered window and write down when nobody is available. A two-person team can cover busy evenings without promising someone is always watching Discord. ## Build one week from confirmed hours Ask each helper when they can reliably read messages and what they can handle in that window. Use the times players most often need a response, such as the hour around a regular event or a peak evening. Give the date, start and end time, time zone and duty in the pinned staff post. Mark any time someone can only read messages as updates-only coverage. | Example window | Contact | What they’re covering | | --- | --- | --- | | Friday, 19:00 to 22:00 UTC | Kai | Join checks and player updates | | Saturday, 18:00 to 21:00 UTC | Erin | Event arrivals and server checks | | Sunday evening | No cover | Messages picked up Monday | ## Make swaps explicit Use the same post for swaps. A helper writes the window they need covered, someone accepts, then the person making the rota updates the name. Until someone accepts, mark the window as open so everybody sees the gap. After the first week, ask which slots actually generated work and which were hard to cover. Use that evidence to move a slot, shorten it or leave it open. ## Try a swap that only covers part of a shift Erin drops out of Saturday's 18:00 to 21:00 UTC event cover. Kai can handle join checks until 19:30, and you cannot find someone for the rest. Update the pinned rota in two parts so nothing appears covered just because somebody briefly accepted. | Window | Rota entry | What staff check | | --- | --- | --- | | 18:00 to 19:30 UTC | Kai, join checks and public updates | Kai confirms they know who owns urgent issues and where ongoing reports belong. | | 19:30 to 21:00 UTC | Uncovered | Name the next report review window. Leave one person responsible for checking it then. | | Next review window | Erin, review messages from Saturday | Erin acknowledges the assignment and finds any open items from Kai. | ## Tell players what response is available Use the player-facing post for the useful part: ‘Staff can help with joining until 19:30 UTC Saturday. You can leave a private report after that. We will check again at [date and time].’ Keep the reason someone dropped out in staff discussion. Before the event, ask a helper looking only at the rota to say who checks joining at 19:15 and who picks up a report at 20:00. The second answer should be the next review slot, with its named owner. Correct the pinned rota if either person relies on a private swap reply. ## Sources - [Google SRE examples of rotations, handoffs and escalation](https://sre.google/workbook/on-call/) - [Discord pinning for a shared current roster](https://support.discord.com/hc/en-us/articles/221421867-Pin-Messages-FAQ) - [Discord: managing moderation teams](https://discord.com/safety/managing-moderation-teams) - [Discord: understanding and avoiding moderator burnout](https://discord.com/safety/understanding-and-avoiding-moderator-burnout) ## Related resources - [What should your Rust server helper cover this weekend?](https://rustsc.com/learn/management/weekend-rust-server-cover/index.html.md) - [What should you take off an overloaded Rust volunteer's plate?](https://rustsc.com/learn/community/reduce-one-rust-volunteers-workload/index.html.md) --- HTML version: https://rustsc.com/learn/management/make-a-rust-server-staff-rota/ --- # What should your Rust server helper cover this weekend? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Before you leave for the weekend, ask your helper to work through the brief you will leave behind. They should be able to join the right Rust world, tell players what they confirmed and find the person who can deal with trouble. Name the hours they have agreed to cover so a volunteer evening does not become an all-weekend promise. ## Fill in one weekend brief Copy this example into the private staff space and replace its details. Use links to the current join post, event instructions and support contact. Ask each named person to confirm their part before you leave. | Brief | Example to replace | | --- | --- | | World and cover | Harbour Solo. Kai covers Saturday, 18:00 to 21:00 UTC. Sunday has no cover. | | Planned activity | Build night on Saturday at 19:00 UTC. Use the pinned event post. | | Helper’s job | Check joins, answer event questions and post confirmed updates in #updates. | | Technical contact | Rowan handles server changes. If unavailable, use the host’s agreed support route and keep the ticket reference here. | | When to contact the owner | Players cannot join, the world looks reset unexpectedly or a complaint concerns staff. | | Handback | Post open reports, support tickets and the next decision here before Monday’s handback. | ## Try the brief while you can still help Ask Kai to start from the brief using their own accounts. Have them open the public join post, connect to the named server and confirm they reached the expected world. They should also find the event post and the place for player updates without asking you for a link. Then give a spoken practice scenario: ‘A player says the server is down.’ Kai should explain how they would try joining, check for an existing staff update or support ticket, and contact the named person. Keep this part an exercise; there is no need to stop the game or file a real ticket. If Kai cannot open the support page with their own access, put a reachable person in that step. If nobody can make server changes during the gap, say that in the brief and leave technical work for the owner. ## Practise one player update Have Kai draft an update in the private staff space. For example: ‘I couldn’t join Harbour Solo at 20:10 UTC. Rowan is checking it. I’ll post again at 20:30 UTC.’ Name a contact only after they have taken the issue, and choose an update time Kai can keep. An unsuccessful join attempt alone does not tell them why the server is unavailable. You are ready to leave when Kai can show the join result, find the contact and draft the update from the brief alone. Fix any missing link or access and repeat the affected step. ## Move optional work away from the gap Review planned events and changes together. If Kai can host build night as a player but cannot update plugins, keep build night and move the optional plugin work to a covered window. Tell players when messages outside the covered hours will be picked up. At handback, Kai leaves the last confirmed result, links to any open report or ticket, and the next decision for the owner. ‘No open reports or tickets; Saturday event finished’ is enough when nothing needs follow-up. Review the remaining items together before closing the weekend thread. ## Sources - [Facepunch Rust join instructions](https://wiki.facepunch.com/rust/Creating-a-server) - [Google SRE guidance on shared records and incident handoff](https://sre.google/sre-book/managing-incidents/) - [Discord guidance on moderation team availability and duties](https://discord.com/safety/managing-moderation-teams) ## Related resources - [Make a Rust server staff rota people can stick to](https://rustsc.com/learn/management/make-a-rust-server-staff-rota/index.html.md) - [How to hand over a Rust server outage to another helper](https://rustsc.com/learn/management/hand-over-a-rust-server-outage/index.html.md) --- HTML version: https://rustsc.com/learn/management/weekend-rust-server-cover/ --- # Reduce the Discord pings your Rust volunteers have to answer [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Ask volunteers which messages interrupted them while they were playing, working or asleep. Pick the most common interruption and ask what someone actually needed to do. The fix may be a clearer join post or a scheduled reply window instead of another person watching chat. ## Read a week of pings by the action they required Take a few real examples from the last week. For each, note who was asked, what they did and whether waiting would have changed the outcome. ‘Can’t find the practice world’ usually needs the join link. ‘When is the next tour?’ can wait for the event host. Several players getting disconnected from the same world merits a timely server check. | Common interruption | Where it goes next week | | --- | --- | | Same join question in several DMs | Put the current join post in the channel header or a pin and link to it. | | Request to repeat Saturday’s event | Reply in the event thread during the next planning session. | | Several people suddenly cannot play | Ask the named helper for the current window to check the affected world. | ## Make the urgent route easy to hear Agree which channel carries requests that need immediate attention during covered hours. Helpers can set Discord notification overrides for that channel and read the others when they have time. Send a test message during a covered window and confirm the person who should get it actually sees it. Check a week later whether the same helper still gets most of the messages directly. Move the answer they keep typing to the place where the questions start. ## Sources - [Discord per-channel notification overrides](https://support.discord.com/hc/en-us/articles/215253258-Notifications-Settings-101) - [Google SRE guidance on actionable on-call work](https://sre.google/sre-book/being-on-call/) ## Related resources - [Turn repeated Rust questions into answers players can find](https://rustsc.com/learn/community/turn-repeat-rust-questions-into-discord-answers/index.html.md) --- HTML version: https://rustsc.com/learn/management/reduce-rust-volunteer-pings/ --- # How to take a break when you run a Rust server alone [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Decide before you leave whether the world will stay open between now and your return. For a short break, an established group may be happy to play without live support. For a longer break with nobody available to check it, a planned pause gives everyone a date to work with. ## Decide what the group can count on Look at the activities already in the calendar. Keep only those that can happen with the people who will actually be there. If the server stays up, explain that replies will wait until you return and say where to leave a join problem. If you pause it, give the last playable time and the date you’ll post your next update. A short notice might read ‘North Pier stays open while I’m away. I’ll check #rust-chat on Monday evening. Saturday’s build tour is cancelled.’ Update the Discord event as well so a player opening it from the calendar gets the same answer. ## Agree what happens while you’re offline Ask regulars to put join problems in one thread with the time and what they saw. An individual player may still be able to join from a different network, so ask the group to say whether the problem affected anyone else. That gives you something specific to check when you get back. On return, use the usual join instruction, load into the world and post the result in the same place you announced the break. If the pause lasts longer than planned, edit the pinned notice and give a new check-in date. ## Sources - [Discord editing and cancelling Scheduled Events](https://support.discord.com/hc/en-us/articles/4409494125719-Scheduled-Events) - [Facepunch Rust client join methods](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [What should your Rust server helper cover this weekend?](https://rustsc.com/learn/management/weekend-rust-server-cover/index.html.md) --- HTML version: https://rustsc.com/learn/management/take-a-break-from-running-your-rust-server/ --- # Compare Rust server managers with one real job [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Pick the job you would buy a tool to make easier. Run it from start to finish on your own spare server. If the job is ‘get a stopped Rust server back online from my phone,’ opening the console or seeing the server’s name only gets you part of the way. ## Write down the start and the finish For a Sunday morning recovery, start with a spare Rust world deliberately stopped, the host online, and you away from the desktop. Finish when a second person can load into the right world. Use the same account role, phone and starting conditions in each test, including a run with your existing tools. The game’s remote console only answers while Rust can receive the connection. If you need to start a stopped game, check what access the candidate needs to reach the host or rental panel. A demo only counts once you can give the tool the access it needs. ## Mark the steps you cannot leave to someone else Write a single must-have before starting. For example, “I must be able to start the stopped world and confirm a player can join without calling someone at home.” Keep optional conveniences, such as viewing more of the startup log on the same screen, in a separate column. | Phone recovery test | Must-have result | Extra steps | | --- | --- | --- | | Current dashboard | Started and Mo joined | Opened console on a separate screen | | Tool A | Started and Mo joined | Read startup output in the same screen | | Tool B | Could see that Rust was stopped | Needed a second person to start it | ## Decide from the missing step In this example the current dashboard and Tool A both pass the must-have. If the extra console screen is hard to use on your phone, repeat that part at the next rehearsal and decide whether Tool A saves enough effort to change tools. Tool B may work for a different job, such as reading the console while Rust is running. Leave one line for each test with the server type, connection you used and a visible result. If you move hosts or change a required account role later, repeat the same job and compare with that record. ## Sources - [Facepunch Rust server startup and remote console settings](https://wiki.facepunch.com/rust/Creating-a-server) - [Google Cloud guidance on testing recovery scenarios](https://docs.cloud.google.com/architecture/framework/reliability/perform-testing-for-recovery-from-failures) ## Related resources - [Will a Rust management tool do the same jobs on both your hosts?](https://rustsc.com/learn/hosting/test-a-rust-management-tool-on-different-hosts/index.html.md) - [What can you still do when your Rust dashboard is unavailable?](https://rustsc.com/learn/management/manage-rust-without-the-usual-dashboard/index.html.md) --- HTML version: https://rustsc.com/learn/management/compare-rust-server-managers-with-one-workflow/ --- # Try a Rust manager beside the tools you already use [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Start on a spare server with the same kinds of tools you already use. Leave the new manager’s game-changing features off, connect it and see what it can read. Keep one tool in charge of each scheduled action until you deliberately move that job. ## Write down what should stay put Before connecting, note the game’s visible name, current startup options, world and next planned action in your existing manager. Ask the candidate what the connection step changes on the host and which features start working on their own. Make the first check about whether you can see today’s setup intact. After connecting, check that the game is still running and recognises the same world. If the new tool shows a setting as unavailable, leave its value alone and read it from the tool you already use. ## Check across a normal cycle Watch your next planned action run once on the spare server, then compare the next run displayed in both tools. If the old tool sends Friday’s notice, you should see one notice. If the new tool sets up a second schedule, turn that schedule off and check the next run again before considering a live connection. Write down which actions you want to move and who owns them today. That lets you try the dashboard’s day-to-day value while keeping control of when anything changes in the game. ## Sources - [Facepunch’s Rust startup configuration and server identity reference](https://wiki.facepunch.com/rust/Creating-a-server) - [Google SRE on learning from a limited release before making it broader](https://sre.google/workbook/canarying-releases/) ## Related resources - [What still runs after you disconnect a Rust manager?](https://rustsc.com/learn/management/find-rust-jobs-before-disconnecting-a-manager/index.html.md) --- HTML version: https://rustsc.com/learn/management/try-a-rust-manager-with-your-current-tools-running/ --- # Which jobs can your management tool do on vanilla Rust? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Test the jobs you care about on a spare vanilla Rust server before deciding whether to add anything to the game. A host panel can start Rust and the game’s native console can send a chat message. A tool’s other features may still depend on extra game software. ## Test one host job and one in-game job Start the spare game through the management tool, if it offers a start action, and have a player join. From the tool, then send a harmless announcement and have the same player confirm it appeared. Facepunch documents a native `say` command. If a tool offers its own announcement feature, test that feature before assuming it uses the native command. Write down any prerequisite shown for each job. A host connector and a plugin installed into the running game are separate choices. A setup that needs one can still work without the other, depending on the job. ## Ask for proof of the job that matters most If you want game chat in a Discord channel, send a unique line as a normal player and see whether it reaches the right channel. Ask the provider exactly what that job needs if it doesn’t work with your setup. Compare that answer with the choice you are making. If an optional job needs a plugin and you want to keep the game vanilla, you can still choose the tool for the host jobs you proved. ## Sources - [Facepunch dedicated server startup and optional framework setup](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch native Rust server commands](https://wiki.facepunch.com/rust/useful_commands) ## Related resources - [Try a Rust manager beside the tools you already use](https://rustsc.com/learn/management/try-a-rust-manager-with-your-current-tools-running/index.html.md) --- HTML version: https://rustsc.com/learn/management/test-manager-jobs-on-vanilla-rust/ --- # What can you still do when your Rust dashboard is unavailable? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Practice using a route that works without your usual dashboard. For a server at home, sign in directly to your host. For a rental, try your provider’s panel. Check the game from a player’s side first so you know whether the outage affects Rust or only the way you manage it. ## Test with the dashboard closed Keep the normal dashboard closed for the rehearsal. Join a spare game using the public game address. Then use your independent route to find out what is running and where you can read the latest output. Try a planned stop and start and ask a friend to join again. If your second route needs a link or sign-in you normally open inside the dashboard, put it somewhere you can reach without the dashboard. If the rental panel itself is the only route, identify the host’s support contact and write the information they need to find the server. ## Check what the missed action does when the site returns During a real outage, write down any manual action you took and what happened. Look at the dashboard history before sending another start or restart after it returns. A game that already recovered may only need a fresh status check. Keep a three-line fallback with the player join path, the independent management or support path, and where to say the action was completed. ## Sources - [Facepunch connecting directly to a Rust game server](https://wiki.facepunch.com/rust/Creating-a-server) - [Google Cloud testing recovery paths and dependencies](https://docs.cloud.google.com/architecture/framework/reliability/perform-testing-for-recovery-from-failures) ## Related resources - [What to tell players when your Rust server goes down](https://rustsc.com/learn/community/rust-outage-status-post/index.html.md) --- HTML version: https://rustsc.com/learn/management/manage-rust-without-the-usual-dashboard/ --- # Can your activity history tell you who restarted Rust? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Have a helper restart a spare game using their own account. Then check what you can see as the owner. You want to know which Rust server was affected, who requested the restart, when it happened and whether the game came back. ## Create two changes you can distinguish Have your helper restart the spare game and write down when the action was sent. Set up a separate scheduled restart on that game. Look up both changes afterwards and confirm you can tell which was requested by a person and which came from the schedule. If you try a request for a time when the server cannot act, check whether the tool shows the outcome or only that it accepted the request. The OWASP logging guidance lays out the information that makes a record usable. For this job, you need the time, the action, the actor and the outcome. The game console can show that startup happened. Individual accounts in a management tool give you a way to check who asked it to happen there. ## Trace one record from request to player join Open the helper’s entry and use the nearest matching startup in the game console. Once a normal player can join again, compare the start and finish with what the activity entry actually says. Record any gap in your notes so a future helper knows which view to check first. If the host panel stays in use, repeat the lookup after a restart from that panel. You may need that panel’s own records to answer who acted there. ## Sources - [OWASP guidance on recording who did what and the outcome](https://cheatsheetseries.owasp.org/cheatsheets/Logging_Cheat_Sheet.html) - [Facepunch startup and server console reference](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Hand one Rust maintenance window to a helper](https://rustsc.com/learn/management/delegate-a-rust-maintenance-window/index.html.md) --- HTML version: https://rustsc.com/learn/management/tell-who-restarted-rust-from-activity-history/ --- # Hand one Rust maintenance window to a helper [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Hand over the whole job for one maintenance window. Show the helper where to warn players, which world to work on and how to check the game afterward. Agree what they should do if the game fails to come back. ## Give them a short brief they can run alone For example, ‘On Saturday at 08:00 UTC, restart Evening Builds. Give players the warning in #updates first. Ask Mo to join after the restart. Put the result in the staff thread. If Mo can’t join, post that we’re checking and send me what Mo saw.’ Put the date and world name in the brief and give the helper the exact places they need to open. Ask them to follow the same steps on a spare server with their own account. The rehearsal should include posting the warning, choosing the right target and asking someone to connect. Watch for any step that still needs you at the keyboard. ## Give them a stopping point if the work changes Agree which changes are theirs to make. If they were briefed to restart a world and the result calls for changing settings or rolling anything back, ask for the last confirmed result and take the next decision together. That gives the helper something useful to do while they wait for you. Ask for a one-line report in the same thread after the window. ‘Restarted Evening Builds at 08:00 UTC. Mo loaded in at 08:06 UTC.’ If something remains open, add who is taking it next. ## Sources - [Google SRE guidance on operational roles and acknowledged handoff](https://sre.google/sre-book/managing-incidents/) - [Facepunch Rust player connection checks](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Can your activity history tell you who restarted Rust?](https://rustsc.com/learn/management/tell-who-restarted-rust-from-activity-history/index.html.md) --- HTML version: https://rustsc.com/learn/management/delegate-a-rust-maintenance-window/ --- # How to hand a running Rust server to a new owner [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Make a list of what keeps the same Rust world running. The next owner needs a way to manage the game, pay for or operate the host, and maintain any name players use to find it. Ask them to demonstrate those routes while you are still available to fix gaps. ## List the things someone has to keep current Record who controls the rented or self-managed host, management workspace, domain if you use one, and player announcements. Ask the provider whether their account or server can be transferred. Agree who will pay for each service from the handover date and how the new owner will reach support. Record the game name and the world it should load. Facepunch describes the server identity as the folder name for that server’s files. When the new owner first opens the panel, have them confirm the existing installation and world they are taking over. ## Have the new owner do one complete shift Ask them to find the upcoming schedule, show who holds the hosting account and arrange a test join. Use a planned quiet window or a spare instance to work through a start and stop. The new owner should be able to finish the check under their own account. Agree who posts the change to players and who picks up outstanding work. When the new owner is ready, update the contact list and retire your old account access through the services that issued it. ## Sources - [Facepunch server identity and connection details](https://wiki.facepunch.com/rust/Creating-a-server) - [Google Cloud guidance on documenting recovery roles and dependencies](https://docs.cloud.google.com/architecture/dr-scenarios-planning-guide) ## Related resources - [Put your Rust server’s operating details on one page](https://rustsc.com/learn/management/write-a-rust-server-operator-card/index.html.md) - [What to do with Discord after your Rust community winds down](https://rustsc.com/learn/community/wind-down-a-rust-community-discord/index.html.md) --- HTML version: https://rustsc.com/learn/management/hand-rust-server-ownership-to-a-new-owner/ --- # Put your Rust server’s operating details on one page [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Write the page you would want to open on a phone when someone says the game is down. Use the player-facing world name and link to the places you actually use. Keep one card per world, even when several worlds share a host. ## Write the answers in the order you need them Put the public join post first. Next put the host or panel link, the server identity if your setup exposes it, and the location of the upcoming schedule and latest console output. Add the person to ask about the host and the place players read status updates. Store passwords in the account or password manager you already use and refer helpers to that separately. | Field | Example card for Evening Builds | | --- | --- | | Player join | Evening Builds, see its block in #join-rust. | | Host and world | Open the game panel for Workshop Host. Select Evening Builds. | | Regular jobs | The panel lists the Sunday restart. Our event reminders live in Discord. | | Help and updates | Host support is linked in the panel. Players check #updates. | ## Have someone use it without you Ask a helper to find the next expected restart and the latest game output from the card. Add the missing link if either search takes them into the wrong world. Write the card’s owner and the last time someone followed it. Check it again when you change host, rename a world or move a scheduled job. ## Sources - [Facepunch Rust server identity, ports and log options](https://wiki.facepunch.com/rust/Creating-a-server) - [Google Cloud guidance on practical recovery procedures](https://docs.cloud.google.com/architecture/dr-scenarios-planning-guide) ## Related resources - [How to hand a running Rust server to a new owner](https://rustsc.com/learn/management/hand-rust-server-ownership-to-a-new-owner/index.html.md) --- HTML version: https://rustsc.com/learn/management/write-a-rust-server-operator-card/ --- # What does ‘online’ mean in your Rust management tool? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Find out what the status tells you to do. A host can be up while Rust is still starting, and a recent game query can show a browser listing without proving a player can enter. Try each condition on a spare world before using the status to decide whether someone needs to investigate. ## Compare three points in a normal restart Check what the tool shows with the game stopped and the host still reachable. Start the game and check again while the console is still showing startup. When a friend loads into the world from their usual client, record whether the tool’s status changed and what it called each state. The Facepunch server guide distinguishes game traffic from the query port used by the server browser. For a report that players can’t join, a real join is the check that answers their question. ## Ask how the display handles lost contact Ask the provider whether it shows a last-known status or a distinct unknown state when the tool can no longer reach the host. Look for when the status was last updated. During a real loss of contact, check the game from a normal client and note whether the label helped you choose the right next action. Add the result to the team’s notes. For example, ‘Green says the game process is up. For a join complaint, test from the usual join post.’ Base the note on what you actually observed. ## Sources - [Facepunch game and server-query ports](https://wiki.facepunch.com/rust/Creating-a-server) - [Google SRE distinction between internal signals and user-facing checks](https://sre.google/sre-book/monitoring-distributed-systems/) ## Related resources - [What can you still do when your Rust dashboard is unavailable?](https://rustsc.com/learn/management/manage-rust-without-the-usual-dashboard/index.html.md) --- HTML version: https://rustsc.com/learn/management/test-what-online-means-in-a-rust-dashboard/ --- # Which Rust server job should you automate first? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Start with a task you already repeat the same way. A reminder for a regular build night is easier to leave with a schedule than a decision about whether to restart a world where players report lag. Write down what someone should see when the job succeeds and what you’ll do if it misses its time. ## Use the last few times the job happened For each run, note what made you start, what you did and where you saw the result. If the time and message were predictable, try scheduling that reminder. If you changed the time or wording after asking players a question, let the schedule remind you to make the decision yourself. Google’s SRE guidance calls out repetitive manual work that can be automated. For one Rust server, the test is what work you’ll still need to do after setting it up. A schedule that needs rewrites every time may leave you with more work than the original message. ## Choose a task you can see from the player side Send a scheduled test reminder to a place where only your helpers will see it. Check the time, wording and whether it was sent once. Then try a run at the actual time with the real audience and retire the old reminder when the new one works. If the job still needs someone to make a decision, simplify the step that repeats. For example, put a build night in Discord’s event list and let attendees mark it as Interested. The host can start the event and send the notification once the world is ready. ## Sources - [Google SRE guidance on recognising repetitive work that is worth automating](https://sre.google/sre-book/eliminating-toil/) - [Discord native Scheduled Events and start reminders](https://support.discord.com/hc/en-us/articles/4409494125719-Scheduled-Events) ## Related resources - [Should a missed Rust job run when the host comes back?](https://rustsc.com/learn/management/check-what-rust-schedules-do-after-an-outage/index.html.md) --- HTML version: https://rustsc.com/learn/management/pick-your-first-rust-server-automation/ --- # Should a missed Rust job run when the host comes back? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Decide what a late run should mean before the first outage. If an early-morning restart would land in a busy afternoon, you may want to skip it. If a housekeeping job can still help later in the day, running it once when the host returns may suit you. ## Find the setting that handles missed time Read the scheduler’s policy for an offline host and for an offline game. Windows Task Scheduler has a setting for starting a timed task after its scheduled time has passed. A systemd calendar timer can catch up with `Persistent=` enabled. A game panel may have its own rule. Check the scheduler that actually owns this job. Write the decision beside the job. ‘Skip the early restart if the host missed its window. The next regular run stays on the calendar.’ If the tool can only catch up, choose a different route for a job that would disrupt players later in the day. ## Rehearse a missed run without restarting your live world Use a spare host or scheduler and a harmless task whose output you can recognise. If the real job must handle a missed run because its host was powered off, reproduce that on the spare host. 1. Schedule a test job that leaves a timestamp you can check later. 2. Keep the spare host off while the scheduled time passes, then turn it back on. 3. Compare when the job ran, if at all, with the intended catch-up rule. Check that the next regular run remains in place. ## Sources - [Microsoft Task Scheduler StartWhenAvailable setting](https://learn.microsoft.com/en-us/windows/win32/taskschd/taskschedulerschema-startwhenavailable-settingstype-element) - [systemd calendar timers and missed runs with Persistent](https://www.freedesktop.org/software/systemd/man/devel/systemd.timer.html) ## Related resources - [Pause a Rust automation and know when it will come back](https://rustsc.com/learn/management/pause-a-rust-automation-with-a-return-date/index.html.md) --- HTML version: https://rustsc.com/learn/management/check-what-rust-schedules-do-after-an-outage/ --- # Pause a Rust automation and know when it will come back [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) If a normal restart clashes with a tournament, give the exception a start and end. Keep the usual schedule available to restore. The next helper should be able to tell at a glance which run was skipped and who will put it back. ## Put the exception beside the schedule Write down the usual time and next run before changing anything. If your tool can skip one occurrence, check that the following occurrence remains scheduled. If it can only switch the whole job off, name the helper who will switch it back on and give them a reminder at a specific time. An example is ‘Skip Saturday’s 19:00 UTC restart for the race. Mo will re-enable the job after the race and confirm next Saturday is still at 19:00 UTC.’ Add the actual dates so another helper can check your work. ## Check warnings and missed runs before resuming Find out whether the player warning is part of the restart or runs separately. If it has its own schedule, skip the warning for the same occurrence. Before turning either back on, check whether the scheduler can catch up on a missed action. If that would send an old notice or trigger a restart immediately, set the next run explicitly before you leave it unattended. Check the newly displayed date and time against the original schedule. Tell the helper who owns the next window that the normal schedule is back. ## Sources - [Microsoft Task Scheduler enabled and catch-up settings](https://learn.microsoft.com/en-us/windows/win32/taskschd/taskschedulerschema-settingstype-complextype) - [systemd rules for persistent timers and manual activation](https://www.freedesktop.org/software/systemd/man/devel/systemd.timer.html) ## Related resources - [Should a missed Rust job run when the host comes back?](https://rustsc.com/learn/management/check-what-rust-schedules-do-after-an-outage/index.html.md) --- HTML version: https://rustsc.com/learn/management/pause-a-rust-automation-with-a-return-date/ --- # When should automatic Rust recovery send you an alert? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Write down the alert you’d want if the game stays down and the note you’d want if it comes back by itself. Then test both routes. A short interruption that ends with players able to join may only need a record. A world players still can’t enter needs someone to check it. ## Compare a recovery notice with a failed recovery Use your monitoring tool’s test mode or a spare server to check whether a recovered problem and an ongoing outage reach different destinations. One example is to keep ‘Evening Builds recovered’ in a log channel and send ‘Evening Builds still can’t accept joins’ to whoever agreed to cover that evening. Ask the recipient to name the first thing they would check. LinuxGSM’s monitor is an example of a tool that can check a game and attempt a restart. Read your own tool’s event definitions. A restart attempt and a player being able to join again are different observations. ## Give repeat notices an owner Check what happens if the same spare game stays down through the next check. If the host and management tool both send a ping about the same outage, choose one alert the helper will act on and keep the other as history where the tools allow it. Confirm the alert includes the world name and enough context for the helper to try a join or check the game without opening every server. ## Sources - [Google SRE guidance on actionable alerts and signals people see](https://sre.google/sre-book/monitoring-distributed-systems/) - [LinuxGSM monitor command behavior](https://docs.linuxgsm.com/commands/monitor) ## Related resources - [What does ‘online’ mean in your Rust management tool?](https://rustsc.com/learn/management/test-what-online-means-in-a-rust-dashboard/index.html.md) - [Reduce the Discord pings your Rust volunteers have to answer](https://rustsc.com/learn/management/reduce-rust-volunteer-pings/index.html.md) --- HTML version: https://rustsc.com/learn/management/decide-when-rust-recovery-should-alert-you/ --- # Test a bulk Rust action before using it on every server [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Pick an action that’s easy to see in each world. A short chat message lets you check which servers received a bulk action without restarting any of them. Include one spare world you intend to reach and one you intend to leave out. ## Check the selection before sending Give the spare worlds distinct names. Select one and read the final target list or confirmation. If you selected a group, check which worlds it contains at that moment. Send a unique test message and open both game views to see where it appeared. Facepunch documents `say` as a server command that sends a message to the in-game chat. For the next run, include both spare worlds and stop one before sending. Record what the tool shows for the world that received the message and the world where it could not be delivered. ## Find where the next action belongs You want enough detail to continue on the one world that still needs the job. If the tool only shows one overall result, check its per-server histories or keep that action individual. Before using a bulk restart or setting change, check that the preview names the exact worlds you meant to touch. ## Sources - [Facepunch game chat broadcast command reference](https://wiki.facepunch.com/rust/useful_commands) - [Google Cloud guidance on testing how systems fail and recover](https://docs.cloud.google.com/architecture/framework/reliability/perform-testing-for-recovery-from-failures) ## Related resources - [Should you retry a Rust panel action after a timeout?](https://rustsc.com/learn/management/retry-a-rust-panel-action-after-a-timeout/index.html.md) --- HTML version: https://rustsc.com/learn/management/test-bulk-actions-across-rust-servers/ --- # What happens when two helpers restart the same Rust server? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Use a spare game to find out whether a second restart request will wait, be declined or cause another interruption. Ask two helpers to use their normal controls so the test reflects the paths they would actually take. ## Send the second request while the first is visibly underway Have one helper start a planned restart. Once the game has started shutting down or loading, have the second send the same request from their own account. Keep the spare game console open and note exactly what each helper’s activity view says. Count the stop and start cycles from the game output, then check that the world has settled and a player can join it. Schedulers can handle overlap in different ways. Microsoft documents options to run a new instance in parallel, queue it, ignore it or stop the existing instance. Find out what your management tool does on the action you’ll use. ## Make it clear who is doing the job Repeat the check from both the panel and separate manager if staff use both. A tool’s overlap handling may only see the requests it received. If both routes can act at once, agree that the helper who starts the restart posts the world and time in the staff thread. The second helper checks for that message and the current game state before acting. ## Sources - [Microsoft’s example of common overlapping task policies](https://learn.microsoft.com/en-us/windows/win32/taskschd/taskschedulerschema-multipleinstancespolicy-settingstype-element) - [Google SRE guidance on assigning operational work during an incident](https://sre.google/sre-book/managing-incidents/) ## Related resources - [Should you retry a Rust panel action after a timeout?](https://rustsc.com/learn/management/retry-a-rust-panel-action-after-a-timeout/index.html.md) --- HTML version: https://rustsc.com/learn/management/test-two-simultaneous-rust-restart-requests/ --- # Should you retry a Rust panel action after a timeout? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) A timeout tells you that the screen didn’t receive an answer in time. The restart or other action may already be underway. Open the activity view and look for the first request before deciding whether to send it again. ## Read the outcome before pressing the button again Find the action for the specific world and time. If it is waiting or running, follow that entry. If the tool shows it completed, confirm the game or setting has reached the intended state. If it clearly failed before starting, fix any stated problem and try once when the next attempt is appropriate. If the entry is missing or unclear, look at the game output or host panel. A Rust server loading levels after a stop is evidence that something may already be happening. If you can’t tell, give the game a chance to settle and ask the host or tool provider what it received. Microsoft’s retry guidance describes why a service can finish work even if its reply never reaches the caller. ## Leave a short note when handing it over Write the world, the time you sent the request and what you last confirmed. For example, ‘Restart requested for Evening Builds at 20:00 UTC. Dashboard timed out. Console still shows the world loading. Check for a player join before sending another restart.’ Whoever takes over can pick up the check without repeating the action. ## Sources - [Microsoft Azure Architecture guidance on retries and lost replies](https://learn.microsoft.com/en-us/azure/architecture/patterns/retry) - [Facepunch Rust startup and log reference](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [How to hand over a Rust server outage to another helper](https://rustsc.com/learn/management/hand-over-a-rust-server-outage/index.html.md) --- HTML version: https://rustsc.com/learn/management/retry-a-rust-panel-action-after-a-timeout/ --- # Try a management tool update on one Rust host first [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) If your management tool has an update you install on each host, start with one that uses the features you need to check. For example, use a spare home instance for your local start and stop routine. Check a rental separately if you manage it through a different connection. ## Pick the results that let you continue Record the manager version you already use and check how its publisher says to return to it if necessary. Pick a few tasks that must work on the first host. For example, read current game output, send a harmless message and review the next scheduled run. If you depend on the tool to start a stopped game, do a test start too. Before applying the update, see whether it requires stopping the game or changing host settings. Use a quiet window or the spare host if it does. This rehearsal is for the management tool. Keep the game version steady so you can tell what changed. ## Wait for one regular job if it matters Check the updated host through a normal use of its most important scheduled job before moving to the others. If you see an unexpected stop, missing schedule or a setting changed on the wrong world, pause the rollout. Use your known working host route while you check the update or ask for support. ## Sources - [Google SRE limited rollout and evaluation guidance](https://sre.google/workbook/canarying-releases/) - [Facepunch distinction between dedicated server startup and game updates](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Will a Rust management tool do the same jobs on both your hosts?](https://rustsc.com/learn/hosting/test-a-rust-management-tool-on-different-hosts/index.html.md) --- HTML version: https://rustsc.com/learn/management/try-a-manager-update-on-one-rust-host-first/ --- # What still runs after you disconnect a Rust manager? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Identify where jobs run before you disconnect the old manager. Stopping a dashboard connection may leave a job running on the host. Conversely, a job that only lived in the dashboard may stop sending its player notices as soon as the connection goes away. ## Make a list of jobs and where they run Read the old dashboard schedules, the host’s own scheduler and any rental panel schedules. Check jobs that start or stop Rust, send messages or check whether it has crashed. LinuxGSM, for example, documents its monitor as an automatable command, and systemd timers can activate their own services independently. Each job on your list needs an owner after the change or a decision to retire it. Ask the old tool’s publisher what disconnecting or uninstalling does to jobs it installed on the host. Use its documented removal path. Check a spare host first if you need to know what it will leave behind. ## Watch for both missing and duplicate work After you switch, check the next planned run for a moved job. It should appear in the new place with the expected result. For a retired job, check that the old place shows it disabled and that its next former run does not send anything. Keep the owner and next check beside each open item until you can account for it. ## Sources - [LinuxGSM monitor as a separate scheduled command](https://docs.linuxgsm.com/commands/monitor) - [systemd timer-to-service activation rules](https://www.freedesktop.org/software/systemd/man/devel/systemd.timer.html) ## Related resources - [What schedule details should you keep when changing Rust tools?](https://rustsc.com/learn/management/keep-your-rust-schedules-when-changing-tools/index.html.md) --- HTML version: https://rustsc.com/learn/management/find-rust-jobs-before-disconnecting-a-manager/ --- # What schedule details should you keep when changing Rust tools? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Save more than the displayed next run. A recurring job needs a time zone, the worlds it affects, the actions it performs and what it does when the scheduled time is missed. A separate warning deserves its own line in the record. ## Make a schedule record you can read without the old tool If the current tool can export schedules, read the downloaded file and check which details it includes. Fill in any missing information from the schedule view. If there’s no export, record these fields once for each job you still need. | Field | Example | | --- | --- | | World and action | Restart Evening Builds. | | Repeat time and time zone | Saturday at 08:00 in Europe/London. | | Warning | Post the notice to #updates before the restart. Keep its text with the schedule. | | Missed run | Skip it if the host misses its window. | | Next check | Compare the next date in both schedules and check the first run next week. | ## Rebuild from the record while the old schedule is visible In the new tool, compare the next two dates in the time zone you intend, especially around a clock change. Check that the warnings, execution order and missed-run behavior match what you promised players. Set up the replacement with the old job still visible. Before the new job’s first live run, turn off the old copy so only one sends a notice or acts on the game. ## Sources - [systemd calendar timing and missed runs](https://www.freedesktop.org/software/systemd/man/devel/systemd.timer.html) - [Microsoft settings for starting after a missed time](https://learn.microsoft.com/en-us/windows/win32/taskschd/taskschedulerschema-startwhenavailable-settingstype-element) ## Related resources - [What still runs after you disconnect a Rust manager?](https://rustsc.com/learn/management/find-rust-jobs-before-disconnecting-a-manager/index.html.md) --- HTML version: https://rustsc.com/learn/management/keep-your-rust-schedules-when-changing-tools/ --- # Can you open a Rust management tool’s export somewhere else? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Pick one record you would want to carry away, such as the name and outcome of a planned maintenance job. Make a sample record on a spare server. Export it and open it in a separate app before relying on the tool to keep that history. ## Choose the smallest record worth keeping Write down the fields you expect. For example, for scheduled jobs you might need the world name, the job, the next run with its time zone and whether the job is active. For a finished job you may want the outcome and when it ran. Ask which of those the export actually contains. Use invented names and ordinary test activity. You can verify that a CSV preserves commas by naming the sample world “Harbour, Practice”. It should display in one field when you open the file with the right delimiter. You can leave player details and staff notes out of this test. ## Try the result outside your normal account Open the downloaded file in a local spreadsheet or text editor. Check that the sample name, status and date survived and make sense without the original dashboard. If the time is stored as a number or without a zone, ask for the format before relying on it. If the export is a link that still needs the tool account, ask how to save a copy you can open separately. Name which job the export covers in your buying notes. A sheet you can read may be enough for reference when leaving. If you need to import it directly into another tool, try that separately with the same sample row. ## Sources - [IETF reference for CSV fields and escaping](https://datatracker.ietf.org/doc/html/rfc4180) ## Related resources - [What schedule details should you keep when changing Rust tools?](https://rustsc.com/learn/management/keep-your-rust-schedules-when-changing-tools/index.html.md) - [Compare Rust server managers with one real job](https://rustsc.com/learn/management/compare-rust-server-managers-with-one-workflow/index.html.md) --- HTML version: https://rustsc.com/learn/management/test-a-rust-manager-export-before-paying/ --- # Do you need the Rust console or the host panel away from home? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Choose the job first. Reading a new console message needs a connection to the running game or a tool that shows its output. Starting a stopped server needs access to the host or rental panel that can start it. ## Write down what you intend to finish remotely Suppose Kai covers a Saturday while you are out. If their job is to check a message from players, they may only need a tool that can read recent output. If their job is to bring a closed world back, they need access that can reach the host while Rust is stopped. A tool that can send a console command while Rust is running does not establish that ability. If the owner should decide any restart, agree on that handoff and leave the helper with the reading access they need. Check whether the available remote console access also permits commands before giving it to someone whose job is only to read. ## Test it as you will use it Use the actual phone or laptop and connect from outside the home network. As the helper, find a named line you recognise from a spare running server. If power control is in scope, start a deliberately stopped spare world through the agreed route and have a second person confirm they can join. Write down the button or location that worked and who takes over if it fails. If the only working path needs the owner’s account, ask the owner to retain that job or check whether the host offers an individual account with the required access. ## Sources - [Facepunch dedicated server guide](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch console command reference](https://wiki.facepunch.com/rust/useful_commands) ## Related resources - [Can RCON start a Rust server that is offline?](https://rustsc.com/learn/troubleshooting/rust-rcon-versus-panel-power/index.html.md) - [What can you still do when your Rust dashboard is unavailable?](https://rustsc.com/learn/management/manage-rust-without-the-usual-dashboard/index.html.md) --- HTML version: https://rustsc.com/learn/management/choose-console-or-panel-for-rust-admin-away/ --- # Can you do your Rust admin work on your phone? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Test the job you would actually do away from a desktop. Open a spare world’s recent messages on your own phone with Wi-Fi off. Find the right server, read a full line and hand off the result. ## Choose one piece of information to find Ask a helper to put a harmless message in the test server’s output and note its time and world. Open the tool in the browser or app you would carry. Confirm you are looking at that world, find the message and read the time and end of the line. Send the result to your helper and compare it with their note. Repeat with your normal phone text size and portrait orientation. W3C’s guidance explains why well-wrapped text helps users read on narrow screens. If the interface uses a wide table, check whether expanding one row gives you all the details without losing the server name. ## Check how the screen resumes Put the phone to sleep, then return and look for a second known message. If the tool is still showing an old view, check how you get to current output and whether it explains that the connection was lost. Decide whether you can reliably do the reading job as part of your normal day. For a phone you also use for owner actions, test those separately on a spare world. A readable console tells you that you can check what happened. You still need to verify any controls you intend to use. ## Sources - [W3C guidance on reflow on narrow displays](https://www.w3.org/WAI/WCAG22/Understanding/reflow.html) - [Facepunch dedicated server guide](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [What can you still do when your Rust dashboard is unavailable?](https://rustsc.com/learn/management/manage-rust-without-the-usual-dashboard/index.html.md) - [Do you need the Rust console or the host panel away from home?](https://rustsc.com/learn/management/choose-console-or-panel-for-rust-admin-away/index.html.md) --- HTML version: https://rustsc.com/learn/management/test-a-rust-tool-on-your-phone/ --- # How much of your week will a Rust management tool take? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Write down work that falls to you in an ordinary week. Measure it in your current setup and in the spare setup you are evaluating. Include the checks and handoffs that still need a person. ## Count hands-on time separately from waiting If a backup runs while you are doing something else, put the time you spend starting it, finding its result and opening the copy in the hands-on column. If you have to stay available for an update to finish, record that waiting separately. Compare the same finished job in both setups. | Example | Current hands-on work | Other setup | | --- | --- | --- | | Check backups, twice a week | 5 minutes per check | 3 minutes per check | | Prepare the weekly restart notice | 8 minutes | 4 minutes | | Give a helper their weekend notes | 7 minutes | 7 minutes | | Weekly total | 25 minutes | 17 minutes | ## Include the work you only do when switching Estimate the separate work to transfer settings, check accounts and teach your helper. If that takes 80 minutes and you save 8 minutes a typical week, you will spend ten weeks catching up on time. That arithmetic assumes the same tasks recur. If you will stop running the server sooner, an immediate feature you need could still decide the choice. Write the existing approach and its best replacement on one line each. Before changing tools, repeat one weekly job and include any work the first check missed, such as signing in twice or consulting the host panel. ## Sources - [Facepunch dedicated server guide](https://wiki.facepunch.com/rust/Creating-a-server) - [systemd reference for timer-controlled jobs](https://www.freedesktop.org/software/systemd/man/latest/systemd.timer.html) ## Related resources - [Compare Rust server managers with one real job](https://rustsc.com/learn/management/compare-rust-server-managers-with-one-workflow/index.html.md) - [What schedule details should you keep when changing Rust tools?](https://rustsc.com/learn/management/keep-your-rust-schedules-when-changing-tools/index.html.md) --- HTML version: https://rustsc.com/learn/management/check-hours-to-run-rust-tools-before-switching/ --- # What will a Rust management tool tell you when a wipe fails? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Ask for a safe demonstration using a disposable world. You want an answer to three questions after something stops: which world, which change and where to see what happened. Check the tool can still show you that after you close and reopen it. ## Pick a failure that costs you nothing Ask the seller for a demonstration of a rejected wipe or use a new test world containing no progress to preserve. If the workflow supports custom maps, you could ask them to demonstrate what appears when a test map cannot be downloaded. Facepunch documents distinct connection and file failures for custom maps. A completed attempt to change the world with a failed return to play is a useful example to ask about. Write down the expected failure and the world you intend to use. Keep live worlds, live integrations and recurring wipe jobs out of the exercise. If the tool says it accepted the request, wait for a final result or check the host state before doing anything again. ## Read the result as the next person on duty Close and reopen the tool. Find the attempted wipe by world name and time. Check whether you can tell if it stopped before changing the world or after making part of the change. If the result points to a startup log, open it and find the relevant line. Join the test server if it is actually accepting players. Keep a note such as “Dunes, 18:10 UTC. New map URL set, startup failed retrieving the file. Panel shows the failed start. The previous test map is still in our separate copy.” If the demonstration only gives you a generic failure, ask where else you would verify which files and settings changed. Decide if you can use that fallback during your real maintenance window. ## Sources - [Facepunch custom map troubleshooting](https://wiki.facepunch.com/rust/FAQ_and_Troubleshooting) - [Facepunch wipe timer reference](https://wiki.facepunch.com/rust/server-wipe-timer) - [Guidance on exercising a recovery failure scenario](https://docs.cloud.google.com/architecture/framework/reliability/perform-testing-for-recovery-from-failures) ## Related resources - [A Rust wipe stopped halfway. What should you check first?](https://rustsc.com/learn/wipes/check-an-interrupted-rust-wipe-before-retrying/index.html.md) - [Should you retry a Rust panel action after a timeout?](https://rustsc.com/learn/management/retry-a-rust-panel-action-after-a-timeout/index.html.md) --- HTML version: https://rustsc.com/learn/management/test-how-a-rust-manager-shows-failed-wipes/ --- # Open a Rust practice world alongside your survival server [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Set up a clean practice world when players want to test a build beside a survival season. Carry over only what the practice session needs, then confirm that every change you make belongs to the practice world. ## Give Birch Practice its own home Birch Survival is already live. Birch Practice will open for one building session and get a fresh procedural map. Make a new server in your host panel or use a separate game folder and launch definition on a full host. Give it a distinct name, its own Rust server identity, available ports and a separate log. Record which joining address goes with each name before starting Practice. Keep Practice private to the testers while you check it. If you reused a launch template, inspect its save location, port settings, administrator list and logs before starting. Leave out Survival saves, player data, staff grants and any copied Rust+ identity. Start with new settings and leave live Discord feeds, bots and other automation unconnected. ## Send two testers to the right worlds Ask a regular player to join both from the same addresses players will receive. In Practice, provide a building tool and enable only the creative settings needed for the session. Leave placement checks in effect if players want layouts that also work in survival. | Test | Expected result | | --- | --- | | Read the server name and find a familiar landmark on Survival | The usual world and player progress are present. | | Open Practice and place a foundation with no building materials | The practice rule allows it, while a Survival player still needs materials. | | Restart Practice and join both worlds | The Practice foundation reappears in Practice, and Survival has stayed open. | | Check who can use an admin-only action and where messages go | A normal tester has their expected access and there are no Practice messages in live announcements. | ## Close the practice session cleanly Tell testers when Practice ends and whether you will keep its designs. Save or export any agreed material from Practice using that world's name. Stop only Practice, check Survival still accepts a join, and remove the temporary Practice link from the announcement. ## Sources - [Facepunch server settings and identity](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch private server guide](https://wiki.facepunch.com/rust/Creating_a_hidden_whitelisted_server) - [Facepunch Creative Mode controls](https://wiki.facepunch.com/rust/creative) - [Facepunch on protecting the Rust+ identity](https://wiki.facepunch.com/rust/rust-companion-server) ## Related resources - [How to assign ports to a second Rust server on one host](https://rustsc.com/learn/setup/allocate-ports-for-a-second-rust-server/index.html.md) - [How to set up a Rust server for creative building practice](https://rustsc.com/learn/configuration/set-up-a-rust-creative-building-practice-server/index.html.md) - [Where does your Rust server keep its active world?](https://rustsc.com/learn/setup/find-the-active-rust-server-identity-folder/index.html.md) --- HTML version: https://rustsc.com/learn/management/open-a-rust-practice-world-without-copying-the-main-world/ --- # Which settings should your Rust worlds share? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Two worlds can share a standard welcome message and still play by different rules. Put the settings you maintain into a short sheet. Decide which ones follow a community decision and which belong to one world before you save a template. ## Start with the reason each setting exists Imagine Ridge runs a monthly survival world and a weekly practice world. The same support staff cover both. Practice offers different building rules and keeps a shorter season. | Choose one owner for | Ridge example | How to know | | --- | --- | --- | | A community default | The address for private player reports | Changing it should send players from either world to the same current destination. | | A world choice | Wipe schedule, map size, difficulty and player cap | A player sees and experiences the rule that belongs to the named world. | | An instance value | Save identity, endpoints and per-world credentials | A change or restart targets the intended world alone. | | Player state | Maps, progression, plugin data and staff grants | Each record stays where its players and access rules expect it. | ## Give exceptions a reason and a person Next to each shared setting, note who can change it, which worlds should receive it and what staff should check on each. Write out valid exceptions, such as ‘Practice players use a separate report channel during staff-run sessions.’ Keep passwords and connection secrets in the appropriate private controls. The shared sheet only needs to say where to manage them. ## Try one harmless choice before adopting the sheet Ask a helper to find where they would change the player help link. Have them name the expected value in each world, including any exception, and check what the player sees. If they cannot tell who owns it or what applies to which world, fix the sheet before copying more settings. ## Sources - [Facepunch dedicated server settings](https://wiki.facepunch.com/rust/Creating-a-server) - [Oxide configuration and player data storage](https://docs.oxidemod.com/guides/developers/data-storage) ## Related resources - [Copy one Rust setting between worlds without changing the save identity](https://rustsc.com/learn/configuration/copy-rust-settings-between-worlds-without-copying-identity/index.html.md) - [Put your Rust server’s operating details on one page](https://rustsc.com/learn/management/write-a-rust-server-operator-card/index.html.md) - [Change server settings](https://rustsc.com/support/guides/server-settings/index.html.md) --- HTML version: https://rustsc.com/learn/management/choose-what-rust-worlds-should-share/ --- # Should a Rust moderator have access to one world or all of them? [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Give a helper access where they work. A Friday moderator on your weekly world and an owner who covers emergencies on both worlds have different jobs. Verify the scope on both worlds before relying on the setup. ## Write the smallest useful scope Name the person, the world and a specific action. For example, Mina handles reports on Juniper Weekly. Lee is on call for Weekly and Monthly. | Job | Give access to | Verify | | --- | --- | --- | | Read incoming reports | The relevant Discord channel or management view | Mina can open a Weekly report and cannot open Monthly's private staff queue. | | Use an in-game plugin action | The relevant game's supported permission | Mina can use the named helper action on Weekly and cannot use it on Monthly. | | Carry out a server-wide emergency action | Both worlds for the named on-call responder | Lee can reach both worlds under Lee's own login. Test the read path first and rehearse any disruptive action on a spare world. | ## Check each place that can grant the action Review access in the management tool, hosting panel, Discord and game separately. Oxide permissions can come from a direct grant or a group. A Discord role controls Discord permissions unless you have deliberately set up a connection that changes game access. Note any shared group or automated role mapping before changing a single server's grants. On a spare setup, have the helper try the same harmless read or staff command on both worlds. Use the helper's own accounts. If the other world unexpectedly allows the action, check its direct grants, groups and shared tooling. Keep existing world owners in place while you verify. ## Tell the helper who covers the gap Leave a line in the rota that names the worlds and who to contact for the other one. If the moderator later moves worlds, revisit the allowed action and its denial on the old world together. A read-only ordinary action gives you a fresh check without disrupting play. ## Sources - [Oxide owner guide to permissions](https://docs.oxidemod.com/guides/owners/permissions) - [Discord roles and channel permissions](https://support.discord.com/hc/en-us/articles/214836687-Discord-Roles-and-Permissions) ## Related resources - [What access does your Rust moderator actually need?](https://rustsc.com/learn/community/choose-access-for-a-rust-moderator/index.html.md) - [Understand workspace roles](https://rustsc.com/support/guides/workspace-roles/index.html.md) - [Keep player permissions the same across servers](https://rustsc.com/support/guides/sync-player-permissions/index.html.md) --- HTML version: https://rustsc.com/learn/management/scope-rust-moderators-to-one-world-or-all-worlds/ --- # Work out which Rust worlds are affected before restarting [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) When an outage report says ‘Rust is down’, find the world and the failed action first. Compare the same action on another world. A management dashboard, a browser listing and a player join can fail separately. ## Check each named world once Write the time and use the same outside network for both worlds where possible. If you cannot reach a console, mark it unchecked. A blank cell should never be read as a failure. | Read-only check | If it fails | | --- | --- | | Direct join to the documented game address | Check another world and, if available, ask a second network to test the affected address. | | Rust browser listing with the usual filters | If direct join works, investigate discovery or filters first. | | Existing private console or hosting panel shows the current game | If a tester can play, keep the game running while you check the management route. | | Host reachable through the existing provider or local controls | If both of its worlds fail from several networks, check host or network status before treating the games as separate crashes. | ## Name the affected world in the update For example, ‘Harbor Weekly direct joins fail from two networks. Harbor Monthly still accepts joins. Weekly is missing from the list; Monthly appears normally.’ Give staff the time and one next observation. If both worlds share a host, say that too. Keep a working world open while the checks point to a narrower failure. ## Confirm the user-facing result before closing the incident When the failed path returns, repeat the original test from the outside network and verify the comparison world still works. Update the incident with the action that now passes. If the evidence still only proves a management panel failure, tell players about the game connection you actually tested. ## Sources - [Facepunch game, browser and console endpoints](https://wiki.facepunch.com/rust/Creating-a-server) - [Google SRE effective troubleshooting](https://sre.google/sre-book/effective-troubleshooting/) ## Related resources - [Direct join works, but your Rust server is missing from the browser](https://rustsc.com/learn/troubleshooting/direct-join-works-server-missing-from-browser/index.html.md) - [How to hand over a Rust server outage to another helper](https://rustsc.com/learn/management/hand-over-a-rust-server-outage/index.html.md) - [If something is not working](https://rustsc.com/support/guides/not-working/index.html.md) --- HTML version: https://rustsc.com/learn/management/check-which-rust-worlds-are-affected-before-restarting-anything/ --- # Retire one Rust world while keeping your community open [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Close the named world and give players a clear route to the one that stays. Keep the closing work in the retiring world's own schedule, backup and joining details so its neighbours can continue normally. ## Tell players which world is closing For example, ‘Birch Practice closes on Sunday at [time and zone]. Birch Survival stays open at its usual address. Practice builds won’t transfer. Keep the same community Discord for Survival news.’ State what is happening to progress and what people should do if they saved a design or had an open moderation issue. Update the pinned chooser, website and any automated join notice that mentions the retiring world. Leave a dated close note where somebody may still follow an old link. ## Close and verify one world Prepare an inventory of the jobs and destinations before the closing window. Identify any job that more than one world shares. | Close the retiring world | Verify what stays | | --- | --- | | Stop public joins and save the final world through your normal safe stop | Follow the surviving world's normal join address from outside and check it is still open. | | Make and label a final archive with the name, capture date and expected map | Keep the surviving world's backup arrangements in place. Use a spare destination for any archive check. | | Remove the closed world's recurring jobs and announcements using the owning tools | Read the next surviving wipe, backup and any shared announcement. Keep shared credentials or feeds that still serve a live world. | | Retire the old join address when you control it | Confirm you removed only the retiring world's record. If both worlds share an address, preserve what the remaining world needs. | ## Leave a short close record Write where the archive is, which world it belongs to and who can retrieve it. Ask a player to use the updated chooser to find and join the remaining world. The close is complete when the link and staff rota point to a live world and there is no remaining job targeting the closed one. ## Sources - [Facepunch dedicated-server identity and configuration](https://wiki.facepunch.com/rust/Creating-a-server) - [Facepunch Rust DNS records](https://wiki.facepunch.com/rust/dns-records) - [Discord pinned messages](https://support.discord.com/hc/en-us/articles/221421867-Pin-Messages-FAQ) ## Related resources - [How to tell players your Rust server is closing](https://rustsc.com/learn/community/tell-players-a-rust-server-is-closing/index.html.md) - [Help players choose the right world in your Rust community](https://rustsc.com/learn/community/help-players-pick-the-right-world-in-your-rust-community/index.html.md) - [Prove a Rust backup belongs to the right world](https://rustsc.com/learn/recovery/prove-a-backup-belongs-to-the-right-rust-world/index.html.md) --- HTML version: https://rustsc.com/learn/management/retire-one-rust-world-without-closing-your-community/ --- # Help staff target the right Rust world before a restart [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Two worlds with similar names are easy to mix up in a busy window. Give helpers two clues they can check before touching server controls. For example, use the public name and player address, then compare the world shown in the console or panel. ## Choose a name people can read over voice chat At Cedar, the two names are Cedar Weekly and Cedar Monthly. Keep the same wording in the browser, staff handoff and the place a helper selects the server. | Place | What the helper should see | | --- | --- | | Player listing and join post | The world name and its actual join address. | | Staff handoff | The same name, the host where it runs and which world will stay open. | | Management view or terminal | The selected world or service, checked with a read-only status or console view before any disruptive action. | ## Run one handoff without restarting a game Give a helper a paper exercise for Cedar Weekly with both worlds running. 1. Ask them to name the world that should eventually restart and the one that should remain open. 2. Have them read the selected server name and address back to a second person, or compare it with the inventory if working alone. 3. Open only the selected world's read-only details. If its name, host or joining address disagrees with the handoff, leave the controls alone and correct the label or instruction. 4. Repeat with the other world and the other role. Record both checks as a dry run so nobody expects a restart. ## Use the same clues on the actual day Keep names stable across maintenance windows, especially if a world moves hosts. Update the handoff if a port or address changes. Before a restart, have the operator say the selected world and intended player impact. Afterward, have a player confirm the intended world returned and the other stayed reachable. ## Sources - [Facepunch server names, identity and game ports](https://wiki.facepunch.com/rust/Creating-a-server) - [Google SRE on incident handoff and named roles](https://sre.google/sre-book/managing-incidents/) ## Related resources - [Put your Rust server’s operating details on one page](https://rustsc.com/learn/management/write-a-rust-server-operator-card/index.html.md) - [Test a bulk Rust action before using it on every server](https://rustsc.com/learn/management/test-bulk-actions-across-rust-servers/index.html.md) - [Find and select servers in a workspace](https://rustsc.com/support/guides/find-a-server-in-your-workspace/index.html.md) --- HTML version: https://rustsc.com/learn/management/label-two-rust-worlds-so-staff-restart-the-right-one/ --- # What to check before sharing your new Rust server address [Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md) Hold the announcement until someone outside the new host's network can join the intended world. A server that accepts connections can still be running with fresh world data or missing settings. ## Choose what needs to arrive on the new host Write down the current server identity, map or map URL, game version and the player data or plugins you intend to keep. Back up the settings and data before the move. If you are keeping the live world, stop the old server for the final copy so players cannot make more progress there while you move it. On the new host, use the intended identity folder and map settings. For a move mid-wipe, pick an existing base or landmark and an account with a known learned blueprint. If the move coincides with a planned wipe, record which progress you expect to reset so the tester knows which changes to expect. ## Send the join instruction to one tester first Ask someone outside the host network to paste the exact new connect instruction into F1. Have them check the expected world and one thing you meant to carry over, such as that blueprint. If you advertise the server through the browser, have them find it there and join from the entry as well. Once the checks pass, replace the join instruction in your Discord pins and other places players look for it. If a check fails, hold the announcement and keep the old server data available while you correct the copy or connection. ## Sources - [Facepunch reference for server identity and save files](https://wiki.facepunch.com/rust/Getting-Started_w-Server) - [Facepunch game connection and query settings](https://wiki.facepunch.com/rust/Creating-a-server) ## Related resources - [Back up a server](https://rustsc.com/support/guides/back-up-server/index.html.md) - [Restore a backup](https://rustsc.com/support/guides/restore-backup/index.html.md) --- HTML version: https://rustsc.com/learn/management/before-sharing-a-new-server-address/