How we verify plugins

The short version

Every plugin the generator gives you, and every code sample on this site, is compiled by a real C# compiler against the same assemblies a Rust server loads. If it does not compile, we do not call it compiled. Today that covers 736 of 736 hook examples, 170 of 170 plugin recipes, the fixes on our 62 error pages and the full plugins inside our 25 guides.

What we compile against

• Rust dedicated server 2635.289.1 (Steam build 26139947): the managed assemblies are downloaded from Steam (app 258550, the official dedicated server) the same way a server host gets them.
• Oxide.Rust 2.0.7839: the official release, overlaid on the server files exactly like a real install, including Oxide's patched game assemblies.
• The same compiler settings Oxide uses on a live server: Roslyn 4.5 (C# 11), Oxide's default assembly references, its compile-time "publicizer" that exposes private game members, and the // Reference: and // Requires: rules.
• Oxide's loader checks: the file name must match the plugin class, and only extensions a standard server has are allowed.

The assemblies are used only as compile references inside our build service. They are never published or sent to anyone.

What happens when code does not compile

The generator reads the exact compiler errors (code, line and column), fixes the plugin and compiles again, up to three rounds. For the content on this site we did the same, and wrote the page's explanation against the final code, not the first draft.

Safety checks

Before you get a plugin, a static check blocks code that grants admin rights or permissions to hard-coded SteamIDs, registers hidden commands, sends network requests you did not ask for, touches files outside Oxide's data and config folders, loads code through reflection, or contains obfuscated content.

Every Rust update, again

Facepunch ships an update every month and Oxide follows. Our build service checks for new Oxide.Rust releases every day. When one appears it downloads the new assemblies, recompiles every example on this site and every plugin saved by subscribers, publishes a monthly update report of the hooks that were added, changed or removed, and flags any plugin the update broke so it can be repaired.

What compiling does not prove

Compiling proves the code is valid C# for the current Rust and Oxide: every type, method and hook signature exists. It does not prove the plugin behaves exactly as you imagined on your server. Test new plugins on a staging server or at a quiet time, and use chat edits to adjust them.

Questions or a mistake?

Email support@rustplugingenerator.com. If you find an error on a page we fix it and recompile.