If oxide.version returns “unknown command,” or a .cs file in oxide/plugins never appears in the console, Oxide/uMod is either not installed, not supported by the host, or not loading correctly. Verify the server build and host support first, then check the plugin’s exact path and filename, read the first error in the console or oxide/logs, and only afterward investigate dependencies, permissions, extensions, or configuration.
Godlike.Host offers hosted Rust servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
Start with the fastest diagnosis
Run oxide.version in the Rust server console or in chat. A working installation responds with the installed Oxide/uMod version. An “unknown command” response means the command handler is absent; plugins cannot load until the framework itself is installed and active.
As an Amazon Associate I earn from qualifying purchases.
| What you see | Most likely cause | First action |
|---|---|---|
oxide.version is an unknown command |
Oxide/uMod is missing, failed to load, or the host does not support it | Confirm host support for Oxide 2.0 or higher and reinstall the build intended for that Rust server |
| The plugin file remains silent | Wrong directory, wrong extension, renamed file, or framework not running | Place the original .cs file in oxide/plugins (or the host’s equivalent umod/plugins) and watch the console |
| Console reports a compile error | Syntax error, outdated API, incompatible Rust/Oxide version, or missing dependency | Fix the first compiler error shown in the console or oxide/logs, then reload the plugin |
| A configurable plugin has no JSON file | The plugin failed before configuration was created, or it is not configurable | Check oxide/logs; do not assume the absence of a file is itself a configuration problem |
A .dll extension fails after upload |
Extension lifecycle, compatibility, dependency, or permission issue | Stop the server before replacing the DLL, then restart and inspect extension-related log entries |
Do not change several things at once. The first framework or compiler error usually explains the later “plugin not found” messages.
1. Confirm that the host and server actually support Oxide/uMod
uMod’s installation guidance is explicit: the server provider must support Oxide 2.0 or higher; otherwise plugins will not load or do anything. This is a hosting capability, not a setting inside an individual plugin.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
Check the command before checking the plugin
- Open the game-server console supplied by your host, or join the server with permission to issue administrative commands.
- Enter
oxide.version. - Record the exact response. A version response confirms that the framework is visible. “Unknown command” does not indicate a bad plugin; it indicates that the command is unavailable because Oxide/uMod is not loaded.
If the command is unknown, verify that the server is a Rust build for which the host offers Oxide/uMod support. Some control panels expose a separate “modded,” “uMod,” or “Oxide” installation choice rather than enabling it automatically. Select the provider’s current Rust-compatible build, reinstall it according to the host’s procedure, and restart the server if the panel requires a restart. Do not continue debugging plugin code until oxide.version works.
Check whether an update removed the framework
Rust updates can leave a previously installed framework incompatible or absent. After an update, compare the framework version shown by oxide.version with the Oxide/uMod build offered for the current Rust server. If the framework no longer starts, reinstall the matching build instead of copying old plugin files into a vanilla server.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
When to change hosts
If the provider does not support Oxide 2.0 or higher, no plugin-side fix can compensate. Move the server to Rust server hosting with uMod support, or use the provider’s supported modding option. Ask support to confirm that the framework is installed on the actual instance you are running, not only on a template or staging server.
2. Put the plugin in the exact directory with its original name
Ordinary Oxide/uMod plugins are C# source files ending in .cs. The usual location is oxide/plugins; some hosts present the same location as umod/plugins. A file in a download folder, a web root, or a similarly named directory will be ignored.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
Upload and verify the file
- Download the plugin’s original source file, not a web page saved with a
.htmlextension and not a compressed archive left unopened. - Upload the file to the live server’s
oxide/pluginsdirectory. If the host uses aumodtree, use its documented equivalent. - Keep the filename and the
.csextension unchanged. Do not add.txt, change capitalization, or append a version number to the filename. - Wait for the server console to report that Oxide detected and compiled the plugin. Oxide’s installation guidance says plugins are detected and compiled automatically, so a normal plugin update does not require shutting down the server.
- If nothing appears, verify that the file was uploaded to the instance and game server you are actually running, then inspect the logs before uploading another copy.
On case-sensitive Linux filesystems, oxide/plugins, Oxide/plugins, and oxide/Plugins are different paths. Use the exact directory shown by the host’s file manager or installation documentation.
Recognize files that are not ordinary plugins
- Plugin: a
.csfile inoxide/plugins; the framework compiles it and can normally reload it while the server is running. - Extension: a compiled
.dll, normally placed inRustDedicated_Data/Managed; it follows a different compatibility and restart process.
Renaming a DLL to .cs, or placing a plugin source file in the managed-DLL directory, does not convert one type into the other.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →3. Read the console and oxide/logs in the right order
The server console is the first place to look immediately after uploading a plugin or restarting. Oxide/uMod also writes detailed records under oxide/logs. Search for the plugin filename, its class name, and the first exception or compiler message.
Fix the first error, not the last symptom
- Open the newest server console output or log file.
- Find the first error emitted while the framework starts or while the plugin is detected.
- Copy the complete message, including the line number, missing type, or dependency name.
- Correct that specific issue, remove the failed plugin copy if necessary, and let the framework detect it again.
- Only after the first error is gone should you investigate subsequent warnings.
A later message such as “plugin failed to load” is often a consequence of an earlier compile error. Changing permissions, configuration, and Rust versions simultaneously can hide the original cause.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
Common compile-error patterns
- Syntax or compiler errors: the source contains invalid C# or was damaged during download or editing. Replace it with a clean original file before attempting manual edits.
- Missing type or namespace: the plugin expects a library or another plugin that is not installed, or it targets an API removed from the current Rust/Oxide combination.
- Method or hook not found: the plugin may target an older Rust server API. Obtain a version maintained for the current server and framework rather than suppressing the error.
- Runtime exception after compilation: the plugin compiled but failed during initialization. The stack trace in
oxide/logsnormally identifies the configuration value, dependency, or hook that triggered it.
4. Check Rust, Oxide, and plugin compatibility
A plugin can be in the correct directory and still fail because its code targets a different Rust or Oxide/uMod API. Compatibility is a three-way relationship: the running Rust server build, the installed framework build, and the plugin release.
Use a controlled compatibility check
- Record the Rust server version from the host panel or startup console.
- Record the output of
oxide.version. - Check the plugin’s stated supported Rust/Oxide versions and release date.
- Read the first compatibility or missing-API error in
oxide/logs. - Install a plugin release intended for the current combination, or update the framework using the host’s supported package.
Do not assume that a plugin that worked last month will continue working after a Rust update. Conversely, replacing a stable framework with an unrelated build can break several plugins at once. Keep a copy of the last known-good plugin and configuration so you can restore them after a controlled update.
5. Separate missing dependencies from a broken plugin
Some plugins require another plugin, a library, or an extension. The log usually names the missing component. Install dependencies in the same oxide/plugins directory when they are plugins, and follow the dependency’s own installation instructions when it is an extension or library.
Dependency troubleshooting sequence
- Read the error for the exact dependency name and required version.
- Confirm that the dependency file exists in the expected directory and has not been renamed.
- Load or reload the dependency first.
- Reload the dependent plugin with
oxide.reload PluginName. - Recheck the console for a new first error; a missing dependency message should disappear when the dependency is available and compatible.
A dependency can itself fail to compile. Treat its first error as the root problem rather than repeatedly reloading the plugin that depends on it.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
6. Treat extensions differently from plugins
Extensions are compiled DLLs, generally stored in RustDedicated_Data/Managed. They are loaded by the server process rather than compiled by Oxide from a source file. Their replacement lifecycle is therefore different.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Item | Plugin | Extension |
|---|---|---|
| File type | C# source, .cs |
Compiled library, .dll |
| Typical directory | oxide/plugins or host equivalent |
RustDedicated_Data/Managed |
| How it loads | Oxide detects and compiles it | Server process loads the library |
| Replacement lifecycle | Usually detected without shutting down | Stop the server, replace the DLL, then restart |
| Primary failure evidence | Plugin compiler/runtime entries | Extension startup, dependency, permission, or compatibility entries |
Stop the server before replacing an extension unless the host explicitly documents a safe hot-swap method. A DLL held open by the server may not be replaced cleanly, and restarting is required for the process to load the new library.
What to check when an extension fails
- Whether the DLL is built for the current Rust and framework versions.
- Whether another extension or plugin supplies a required dependency.
- Whether the server account can read the file.
- Whether two extensions provide conflicting versions of the same library.
- Whether the extension’s error appears before ordinary plugin loading in the startup log.
7. Check Linux permissions and file integrity
On Linux servers, the account running RustDedicated must be able to read the plugin and traverse every parent directory. A file uploaded by a different account can have restrictive permissions even when it is visible in a control panel.
Permission checks
- Confirm that the server process owns the file or has read access.
- Confirm that the process can access
oxide/plugins,oxide/config, andoxide/logs. - Ensure the filename contains no hidden extra extension such as
Plugin.cs.txt. - Replace a zero-byte or partially uploaded file with a fresh copy.
- After changing permissions, restart only when the host requires it; ordinary plugin detection should occur while the server is running.
Do not make every server file world-writable as a shortcut. Grant the minimum read/write access required by the account that runs the server, then use the console to verify detection.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
8. Validate configuration before reloading
Configurable plugins normally create a JSON file in oxide/config using the plugin’s filename. A plugin that is not configurable may legitimately create no configuration file. If a configurable plugin creates none, uMod’s guidance is to inspect oxide/logs because the plugin may have failed during initialization.
Recommended Free Tools
Edit JSON safely
- Stop editing while the plugin is writing its configuration.
- Make a backup of the existing file.
- Preserve double quotes around property names and string values.
- Remove trailing commas and comments; standard JSON does not allow them.
- Keep numbers, booleans, arrays, and objects in the types the plugin expects.
- Save the file, then reload the plugin with
oxide.reload PluginName. - Read the console immediately. A JSON parse error identifies the configuration file and usually a line or character position.
Use the plugin name without .cs in the reload command. If the reload reports that the plugin is not loaded, return to the compile and dependency errors rather than repeatedly editing JSON.
Recover from a bad configuration
- Move the suspect JSON file out of
oxide/configwhile the server is stopped only if your host requires a stop for file operations. - Start the server or reload the plugin so it can generate a clean default configuration.
- Reapply settings one group at a time, reloading after each valid change.
- When the plugin works, keep the known-good JSON as a backup.
9. A complete recovery procedure
Use this sequence when you want a repeatable fix rather than isolated guesses.
- Confirm the framework: run
oxide.version. If it is unknown, resolve host support and reinstall Oxide/uMod before touching the plugin. - Identify the live instance: verify that the panel, file manager, and console refer to the same Rust server.
- Install a clean plugin file: upload the original unchanged
.csfile tooxide/pluginsor the host’s equivalent. - Watch detection: wait for the automatic compile/load message instead of assuming the upload succeeded.
- Read the first failure: inspect the console and newest file in
oxide/logs. - Resolve compatibility: compare Rust, framework, and plugin versions; replace outdated code with a compatible release.
- Resolve dependencies: install and load required plugins or libraries before the dependent plugin.
- Check permissions: make sure the RustDedicated account can read the file and its directories.
- Handle extensions separately: for a DLL, stop the server, replace the file in
RustDedicated_Data/Managed, and restart. - Restore configuration: validate JSON, reload with
oxide.reload PluginName, and confirm a clean console response.
10. Prevent the next Oxide loading failure
- Keep a text record of the Rust server version and
oxide.versionoutput after every planned update. - Back up
oxide/configand the last known-good plugin files before updating Rust or Oxide. - Install one plugin at a time and wait for its console result; this makes the first error attributable.
- Do not rename plugin files or change their extensions to make them “match” a configuration name.
- Keep extensions and ordinary plugins in their separate directories and follow the extension’s restart requirement.
- After every configuration edit, validate JSON and use
oxide.reload PluginNamerather than restarting blindly. - When contacting a host or plugin author, include the Rust version,
oxide.versionoutput, exact filename and path, the first console error, and the relevantoxide/logsexcerpt.
When the evidence points outside the plugin
If oxide.version remains unknown after a supported framework reinstall, the problem is at the host or installation layer. If the framework responds but a clean, compatible .cs file produces no detection message, the problem is usually the instance path, filename, permissions, or an incorrect host mapping. If detection occurs and compilation fails, the log’s first compiler or dependency error is the actionable item. If a DLL fails while ordinary plugins load, use the extension directory and restart lifecycle rather than applying plugin troubleshooting steps.
Quick Recap
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.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors
