Oxide Sync is live: your plugins install and update themselves →
Rustplugins.store

Review guidelines

What we check before a plugin goes live

Every new plugin and every update is reviewed by a person before Oxide Sync installs it on anyone's server. These guidelines are what we check. If something isn't covered here, we use the same test: would a server owner be comfortable running this on a live server?

New plugins are usually reviewed within one to two business days; updates are usually faster.

Code safety

Every build is read before it reaches a server. Server owners trust us to install code on live servers, so this is the strictest part.

Required

  • Readable C# source. We review the same file buyers receive.
  • Network calls go through Oxide’s webrequest API and are to services the listing names (for example a Discord webhook the server owner configures).
  • Anything the plugin sends off the server (telemetry, logs, player data) is described in the listing and can be turned off in the config.
  • Files are only written inside the plugin’s own oxide/data or oxide/config entries.
  • Permissions are registered with permission.RegisterPermission and only granted by the server owner.

Not accepted

  • Obfuscated, minified or encrypted code, or large encoded blobs that hide what runs.
  • Downloading, compiling or loading code at runtime (Assembly.Load, remote scripts, plugin installers).
  • Backdoors: hidden commands, hard-coded SteamIDs with special access, or code that grants admin, ownerid, groups or permissions on its own.
  • Licence checks, “phone home” DRM or kill switches. Oxide Sync handles licensing.
  • Starting processes, raw sockets or HttpClient/WebClient, deleting or editing files outside the plugin’s own data.
  • Code copied from another author without permission, or from a plugin whose licence doesn’t allow resale.

The build

We load every build on a test server.

Required

  • A single .cs file with a class deriving from RustPlugin or CovalencePlugin.
  • An [Info("Name", "Author", "1.2.3")] attribute whose version matches the version you upload.
  • It compiles and loads on current Rust and Oxide (and Carbon, if you tick it) with no errors.
  • A default config is generated on first load, with sensible values.
  • Required dependencies are declared in the listing, and the plugin fails gracefully (a clear console message) when one is missing.
  • A new version number for every build. Versions can’t be re-uploaded.

Not accepted

  • Builds that throw on load, spam the console, or noticeably hurt server performance under normal use.

The listing

Buyers decide from your listing, so it has to be accurate.

Required

  • A short store description saying what the plugin does.
  • Documentation: installation, every config option, commands and permissions.
  • A square icon, and screenshots or a short clip of anything with UI.
  • The right category, frameworks and tags.
  • Only features that exist in the build you submit.

Not accepted

  • Other people’s trademarks, art or names in a way that suggests endorsement.
  • Links that move buyers to buy elsewhere, or contact details asking for payment outside the store.
  • Misleading claims, fake reviews or keyword stuffing.

Pricing

You set your own prices.

Required

  • Paid plugins need a connected Stripe account before you can submit them.
  • Prices for the 3-server and unlimited tiers, if offered, should be higher than the single-server price.
  • Free plugins must be fully usable: no paid unlock inside the plugin.

Content and Rust’s rules

Plugins have to be fine to run on a public Rust server.

Required

  • Respect Facepunch’s server owner rules and Rust’s terms.

Not accepted

  • Plugins built to cheat, exploit bugs, harass players, or collect players’ personal data without the server owner disclosing it.
  • Gambling with real money or items that can be traded for real money.
  • Hateful, sexual or illegal content.

Support and updates

Selling a plugin is a commitment to the people who bought it.

Required

  • Reply to support tickets in your developer console, ideally within 3 business days.
  • Ship fixes after Rust force-wipe updates within a reasonable time, or tell us if you can’t.
  • Use the changelog field: buyers see it when an update installs.
  • Use beta channel and staged rollouts for risky changes.

Review outcomes

Approved

The listing goes live and the builds you submitted are released with the rollout you chose. You get a message in your console (and Discord, if set).

Changes requested

You get specific notes. Fix them, save, and press Resubmit. There’s no limit on resubmissions.

Build rejected

Your listing stays live on the previous version. Upload a fixed build with a new version number.

Removed

For serious problems (malicious code, stolen work) we unlist the plugin and may suspend the account. Existing buyers keep their last safe version.

Disagree with a decision? Reply in the note when you resubmit, or open a support ticket. A different reviewer will take another look.

Ready to submit?

Apply with your store account. See the developer terms for commission and payouts.

Apply to sell