What reviewers check in a Rust plugin: the rules we use, with sources. Feedback wanted. Pinned
-
We've put up two pages that we wish had existed when we started: a list of every doc and tool we actually use for Rust modding (Oxide, Carbon, hooks, Harmony, decompiling, server setup, code-analysis rules), and the rules a plugin gets checked against before it's listed here, each one with a link to where it comes from.
https://directory.mixapps.store/guides/rust-modding-resources
https://directory.mixapps.store/guides/plugin-review-rulesMost of the rules come straight from the Oxide and Carbon developer docs. A few are ours, and they're marked as ours. We learnt three of them the hard way this week: Harmony through AutoPatch not a manual instance, no reflection because the assemblies are publicised at runtime, and no ContainsKey before Remove.
If you think a rule is wrong, missing, or marked wrong, say so here. If you've got a link that belongs on the resources page, post it and we'll add it. The same checks will run on uploads here soon, so you'll see the findings on your own file before anyone else does.
Reply
Sign in with Steam to post Reading is open to everyone. We keep only your SteamID, nothing else from Steam. Your posts show under a random name like "Player K7Q2M".
