Skip to main content

Where do Rust plugin .cs files and extension DLLs go?

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

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details