Free tools Windows power users keep installed
One-click scans. No signup required.
On an Oxide or uMod Rust server, reload one plugin from the server console or an authorized RCON terminal with oxide.reload PluginName. Replace PluginName with the plugin’s exact name. If your installation documents the uMod namespace, the equivalent form is umod.reload PluginName. A reload applies source or configuration changes while the game server keeps running; a full restart is still the safer recovery when initialization repeatedly fails.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Rust servers with free DDoS protection and up to three free backups a day.
The reliable process is: back up the plugin and its configuration, confirm the name and dependencies, make the edit, issue the framework command, inspect the response and logs, then test the affected feature. The sections below show the exact commands, framework differences, failure diagnosis, and the point at which a restart is preferable.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key... | $25.00 | Buy on Amazon |
| 2 |
|
Rust Video Game Notebook | $15.00 | Buy on Amazon |
| 3 |
|
Rust Game Props Large Furnace (S) | $14.99 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What “reload” does on a Rust server
A plugin reload asks the server mod framework to apply a plugin again without stopping the Rust server process. It is intended for routine source edits and configuration changes when you want to avoid disconnecting players. The command must be entered in the game-server console or through an authenticated RCON session that is allowed to run server commands; entering it in a player chat box, a host control-panel search field, or a normal operating-system shell will not work.
Reloading is not a guarantee that every change is safe to apply live. A plugin can fail to compile, lose a dependency, reject malformed JSON, or require the clean startup sequence that only a complete server restart provides. Treat the console response and log entries as the authority on whether the operation succeeded.
#1 Best Overall
- Inspired by the Rust Video Game – These cards replicate the iconic keycards found in Rust (Red, Blue, Green).
- High Quality PVC Plastic – Printed on both sides, durable and water-resistant. Not a sticker.
- Great Rust Gift Idea – Perfect for fans of Rust, whether for cosplay, loot-themed gifts, or collection.
- Wallet-Size Replica – Standard 3.375x2.125 inches, 30 mil thick—fits in any wallet.
- NOT a sticker*
Commands and namespaces
Use the namespace exposed by the framework installed on your server. OxideMod’s command documentation lists the primary form, wildcard form, and aliases at its plugin-command reference. uMod’s command guide documents a separate umod.reload syntax for the running game-server terminal at the uMod commands guide.
| Command | Use | Where to run it | Important qualification |
|---|---|---|---|
oxide.reload PluginName |
Reload one plugin | Rust server console or authorized RCON | Use the plugin’s exact name. |
oxide.reload * |
Reload every loaded plugin | Rust server console or authorized RCON | Affects the whole plugin set; avoid casually on a busy production server. |
o.reload PluginName |
Alias for the Oxide reload command | Rust server console or authorized RCON | Use the full form when documenting procedures so the namespace is unambiguous. |
plugin.reload PluginName |
Another Oxide alias | Rust server console or authorized RCON | It still requires the exact plugin name. |
umod.reload PluginName [PluginName] [..] |
Reload one or several plugins in the uMod command syntax | Running game-server terminal | Confirm that this namespace is supported by your installation before using it. |
For a normal single-plugin change, start with oxide.reload PluginName. The uMod configuration documentation specifically instructs administrators to reload a changed plugin configuration from the server console with the oxide.reload command: uMod plugin configuration documentation. The existence of both oxide and umod forms means you should check the command guide shipped with, or maintained for, your server framework rather than assuming that one namespace works everywhere.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Prepare before issuing a reload
1. Identify the exact plugin name
Use the name shown by the framework’s plugin list or by the plugin file, and copy it exactly into the command. Do not substitute a display title, a shortened nickname, or the filename of a different revision. A name mismatch commonly produces a “not found” response even when the file is present.
2. Check dependencies
Read the plugin’s installation notes and confirm that its required libraries or companion plugins are installed and loaded. A reload can expose a missing dependency immediately, especially after you have updated several files. If the dependency itself is being changed, plan the order in which the related plugins will be reloaded.
3. Back up the current files
Make a copy of the plugin source and its configuration before editing. Keep the backup outside the live plugin directory or give it a non-loading extension so the framework cannot mistake it for another plugin. This gives you a known-good version to restore if compilation or configuration parsing fails.
4. Decide whether the change is source or configuration
A source edit may require compilation and can fail on a syntax or API error. A JSON configuration edit normally needs the same plugin reload, but it can fail if a comma, quote, brace, data type, or setting name is invalid. Preserve the file’s encoding and structure while making the smallest change possible.
Safe single-plugin reload: exact procedure
- Back up the live files. Copy the plugin file and its configuration, noting the time and version you are about to change.
- Confirm the operating context. Open the Rust server’s local console or an authenticated RCON terminal with permission to execute framework commands. Do not send the command as an in-game chat message.
- Verify the name and dependencies. Check the loaded-plugin listing and the plugin’s documentation. Make sure every required companion plugin is available before applying the edit.
- Edit the source or JSON configuration. Save the change to the live file only after checking the syntax. For a configuration-only change, follow the plugin’s documented setting names and value types.
- Run the framework command. Enter
oxide.reload PluginName, substituting the exact plugin name. If your installation’s command guide explicitly uses the uMod namespace, useumod.reload PluginNameinstead. - Wait for the complete response. Do not assume success because the command was accepted. Read the console output until the framework reports that the plugin loaded or identifies an error.
- Inspect the server log. Look for compiler diagnostics, missing-dependency messages, permission or registration errors, and configuration parsing failures. Record the first meaningful error rather than chasing later cascade messages.
- Test the changed behavior. Use the affected chat command, console command, permission, or in-game feature with a controlled test account. Verify both the intended result and a normal unaffected path.
- Restore or restart if necessary. If the reload fails, restore the backed-up file and try once after correcting the reported issue. If the plugin continues to fail or requires a clean initialization, stop the server and perform a full restart instead of repeatedly reloading it.
How to verify that a reload really worked
A successful command entry is not the same as a successful plugin load. Verification has three layers:
- Framework response: The console should identify the requested plugin and report its load or reload result. An unknown-command response points to the wrong namespace or terminal.
- Log output: Compilation errors normally include a file and line reference; dependency failures identify the missing component; configuration errors point to malformed or unsupported data. Save the relevant lines before making another edit.
- Functional test: Exercise the feature that changed. A plugin can load while a particular permission, command path, or setting remains incorrect, so test the behavior rather than relying only on a green-looking console line.
If the plugin has an administrative command, run it from the same context players will use. If it is controlled by permissions, test with an account that has the intended permission level; testing only as an owner can hide an authorization mistake.
Rank #2
Reloading configuration files safely
uMod’s configuration guidance says that after changing a plugin configuration file, you reload the plugin in the server console with oxide.reload. That makes a reload appropriate for many settings changes, but it does not make malformed data acceptable. Keep a copy of the previous JSON, validate punctuation and value types, and change one setting group at a time so an error is easy to isolate.
When a configuration reload reports a parse error, stop testing the feature. Restore the last valid JSON, reload the plugin again, and confirm that it returns to its previous behavior before attempting a corrected edit. If the plugin creates a default configuration after a failed load, compare that generated file with your backup before copying values back; blindly overwriting it can discard newly introduced settings.
Oxide and uMod command differences
Administrators often encounter both names because documentation and server installations do not always present the same command namespace. The operational questions are the same—what command is exposed, what plugins are compatible, how dependencies are handled, and where errors are logged—but the spelling entered at the console can differ.
| Area | Oxide-style command set | uMod-documented form | How to decide |
|---|---|---|---|
| Single reload | oxide.reload PluginName |
umod.reload PluginName |
Use the namespace accepted by your running framework. |
| Multiple or all plugins | oxide.reload * is documented for all plugins; aliases include o.reload and plugin.reload |
umod.reload PluginName [PluginName] [..] is documented for one or more named plugins |
Prefer named reloads unless you have a reason to affect the entire set. |
| Compatibility | Depends on the plugin’s supported framework and game-server API | Depends on the plugin’s supported framework and game-server API | Read the plugin’s stated requirements; a command namespace alone does not make an incompatible plugin work. |
| Dependency handling | Errors appear during the reload response or in logs | Errors appear during the reload response or in logs | Resolve the first missing or failed dependency before repeating the reload. |
| Downtime | A named reload avoids a full process restart when it succeeds | A named reload avoids a full process restart when it succeeds | Use a restart when clean initialization is required or failures persist. |
The command references do not establish that every plugin accepts every namespace. If oxide.reload returns an unknown-command error, consult the command guide for the framework actually running and try its documented equivalent, not a random variation.
What to do when a plugin will not reload
“Unknown command” or no response
Check that you are connected to the game-server console or an authorized RCON endpoint, then verify the namespace. A terminal connected to a host machine is not automatically the Rust server console. If the server uses the uMod command set, try the documented umod.reload form; if it uses Oxide commands, use oxide.reload or its documented aliases.
“Plugin not found”
Recheck the exact name, including spelling and punctuation, against the loaded-plugin listing and the live plugin file. Make sure the file is in the framework’s plugin directory and has not been left with a temporary extension. If the plugin has not loaded once, a reload command may have nothing to target; correct the file or install the missing dependency first.
Compile or syntax error
Read the first compiler message and its line number. Restore the backup if the edit is substantial, then correct one error at a time. A reload cannot repair a source file that no longer compiles. After saving the correction, issue a new named reload and verify that the previous error has disappeared from the log.
Missing dependency or incompatible API
Install or restore the required companion plugin and confirm that its version supports the current Rust server and framework. Reloading the dependent plugin before its prerequisite is available will continue to fail. If the prerequisite itself cannot load, treat that as the primary problem.
Rank #3
- Acrylic Painting Pla Plastic
Configuration parse or validation failure
Replace the edited JSON with the last known-good backup, reload, and then reapply the setting carefully. Check quotes, commas, braces, arrays, and whether the value type matches the plugin’s documented example. Do not delete an error message and assume the setting was accepted.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchThe plugin loads but the feature still fails
Confirm that you tested the correct command or in-game path, then check permissions and the plugin’s own settings. A successful reload only establishes that the framework accepted the plugin; it does not prove that every user has the required permission or that the edited option applies to an existing object.
When to use oxide.reload *
OxideMod documents oxide.reload * as a way to reload all plugins. It can be useful after a coordinated batch of compatible edits, but it expands the failure surface: a single broken file, missing dependency, or invalid configuration can produce errors across a long console stream, and every plugin is reinitialized at once. On a busy server, prefer one named reload at a time so players experience the smallest possible change and you can associate each log entry with a specific edit.
Before using the wildcard, back up every affected plugin and configuration, confirm that the framework accepts the wildcard syntax, and plan a test for the features most important to the server. If any plugin fails, stop issuing additional reload commands until you have identified whether the problem is isolated or shared.
Reload versus a full server restart
A reload is the lower-downtime option when one plugin has a valid source file or configuration and can initialize cleanly while the server is running. A full restart is the correct recovery when the plugin repeatedly fails to load, when dependencies must be loaded in a clean sequence, or when the plugin documentation requires startup initialization that a live reload does not reproduce.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesFor a restart, announce the maintenance window to players, save the server state according to your hosting setup, stop the process cleanly, replace or restore the files, start the server, and watch the startup log from the beginning. Then test the plugin as you would after a reload. Do not keep issuing reload commands indefinitely against a plugin that is producing the same error; repeated attempts can make diagnosis harder and leave the server without the intended feature.
Quick operator checklist
- Exact plugin name copied from the server’s loaded-plugin information.
- Current plugin file and configuration backed up.
- Required dependencies present and compatible.
- Source or JSON edit saved with valid syntax.
- Authorized server-console or RCON session open.
- Correct namespace selected:
oxide.reloador the documentedumod.reloadform. - Console response read to completion.
- Logs checked for compilation, dependency, permission, and configuration errors.
- Changed command or in-game behavior tested with an account that matches the intended permission level.
- Backup restored or a full restart scheduled if the plugin will not initialize reliably.
Official command references
For syntax that may change with framework updates, consult the current documentation before standardizing a procedure for staff:
Quick Recap
- OxideMod plugin commands — reload syntax, wildcard behavior, and aliases.
- uMod plugin configuration — reload guidance after configuration edits.
- uMod commands guide — the
umod.reload PluginName [PluginName] [..]terminal form.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
