Which plugins a Rust server needs at launch

1. Choose a small starter set

Server Info and Welcome do not change gathering rates or the economy. They make useful first loading checks. Download the free files from their resource pages after signing in with RustMods ID.

2. Prepare the server and selection criteria

• Check that Oxide works: oxide.version should return its version.
• Back up oxide/plugins, oxide/config, oxide/data and the current world saves.
• Read the selected release description: compatibility, dependencies, commands, permissions and changelog.
• Choose a testing window and record existing console errors. Install one plugin at a time.

If Oxide is not installed, start with this guide ↗

3. Install one file at a time

Extract the downloaded ZIP. Put the .cs file in oxide/plugins and keep the README for reference. The config appears after a successful load. An example JSON file does not need to replace a config you have already customised. The paths below assume a standard Oxide installation.

oxide/plugins/RustModsServerInfo.cs
oxide/config/RustModsServerInfo.json
oxide/plugins/RustModsWelcome.cs
oxide/config/RustModsWelcome.json

If loading fails, check the first console error. Fix it before adding another plugin. Enter console commands in the server console or RCON; commands starting with a slash belong in game chat.

4. Configure Server Info

Download RustMods Server Info ↗

Edit the relevant fields in oxide/config/RustModsServerInfo.json. This is a fragment: merge its values into the existing config and keep the other settings. Replace the date, time zone, rates and rules with your own. The wipe field displays text; it does not schedule a wipe.

{
  "Wipe information": "Friday 18:00 UTC",
  "Rates information": "Vanilla",
  "Show map seed": false,
  "Custom lines": ["Rules: no cheating; respect other players."]
}

oxide.reload RustModsServerInfo

/serverinfo

Check the response as a regular player: the name, player count, rules and wipe description should match your server. If you change Primary chat command or Secondary chat command, use the new command name.

5. Add Welcome

Download RustMods Welcome ↗

This is a complete example of oxide/config/RustModsWelcome.json for version 1.0.0. Translate the message text if needed, keeping the field names and {name} and {server} tokens. The reference to /serverinfo assumes Server Info is already installed with its default commands.

{
  "Prefix": "<color=#ff6b2d>[RustMods]</color>",
  "Delay before welcome messages (seconds)": 2.0,
  "Enable /welcome command": true,
  "Broadcast player joins to everyone": false,
  "Join broadcast message": "{name} joined the server.",
  "Welcome messages": [
    "Welcome, {name}! You are playing on {server}.",
    "Type /serverinfo for server details.",
    "Type /welcome to read this again."
  ]
}

oxide.reload RustModsWelcome

/welcome

Reconnect next: the welcome should arrive after the configured delay. Join broadcasts are disabled in this example, so every connection does not add a message to everyone else’s chat.

6. Add Auto Restart when you need it

Open RustMods Auto Restart ↗

On a first installation, place a config with an empty schedule before uploading RustModsAutoRestart.cs. If the plugin is already running, unload it first with oxide.unload RustModsAutoRestart. Merge the following fields into an existing config while keeping its other values. For a new file, these fields disable the schedule and the remaining settings use their defaults.

{
  "Daily restart times (24h HH:mm)": [],
  "Save server before restart": true
}

Once the config is ready, upload the .cs file; use oxide.load RustModsAutoRestart for an already unloaded plugin. An administrator can check its state with the command below.

/rmar status

Enable the schedule only after checking automatic startup in an agreed maintenance window. Use HH:mm in the server’s local time. Avoid overlapping countdowns in the hosting panel and another plugin.

7. Grant only the access you need

Group commands are part of Oxide. Reading Server Info and using /welcome in these versions are available to regular players. The rustmodsserverinfo.admin permission allows config reloading with /serverinfo reload; Rust administrators also have access. This example creates a separate information editors group.

oxide.group add infoeditors
oxide.grant group infoeditors rustmodsserverinfo.admin
oxide.usergroup add STEAM64_ID infoeditors
oxide.show group infoeditors

Check that /serverinfo reload works for an editor and is denied for a regular player. Remove the test access with the commands below. Auto Restart’s rustmodsautorestart.admin permission allows control over server shutdown; an information editor does not need it.

oxide.usergroup remove STEAM64_ID infoeditors
oxide.revoke group infoeditors rustmodsserverinfo.admin

8. What to add after the first launch

Give each addition one clear task and a result you can check. If two plugins change the same action, investigate compatibility first. Installing more files does not by itself make the server easier to play on.

RustMods catalogue ↗

Browse additional plugins on uMod ↗

9. Roll back one step if an error appears

• Copy the first console error and record the change that preceded it.
• Unload the affected plugin, then move its .cs file from oxide/plugins to a backup folder outside the loading directory.
• Restore the previous config from a backup. Do not delete oxide/data at random: it may contain plugin saves.
• Before loading a previous version, check that its data and config formats are compatible.

oxide.unload RustModsWelcome

Unloading does not reverse changes already written to the world, economy or permissions. Those changes require a data recovery plan prepared in advance.

10. Check before inviting players

• A regular player receives the correct /serverinfo and /welcome responses.
• After reconnecting, the welcome arrives once and contains current rules.
• A regular player cannot use /serverinfo reload; an editor can.
• Selected settings survive a server restart and no new compilation errors appear.
• If installed, Auto Restart’s schedule, time zone and startup through the panel have been checked separately.
• A backup, version list and recent change notes are available.

Invite your first players and collect specific feedback: what is unclear on arrival, which command is missing and where the rules disagree with the settings. Use those observations to choose the next addition.