
Track Rust plugin versions across marketplaces
Keep one entry per plugin you run. The fields that matter on update day are where it came from, which version actually loaded and what you have to test if you change it.
A register entry you can copy
For example: WelcomeNotice.cs, version 1.2.0 loaded on Oxide, edited by us, original release linked, working copy in the server backup. Check that a returning player sees the new welcome line. This entry records what runs and one quick test, even if the upstream listing has moved on.
Add a field for required downloads if the plugin has any. On GitHub, link to the specific release when possible. On a marketplace, keep the listing and read the author's release notes before downloading.
On update day
Keep a candidate release in the notes while you test it. Once you see it load in the console and your test passes, record the new version and date. If you keep a local patch, record whether you carried it forward. Two files with the same version can still behave differently.