
Reproduce a Rust plugin issue without sharing player data
Make a new test world and recreate the smallest state that triggers the error. A copy of your production plugin folder may include player histories and private settings that the maintainer needs no access to.
Work backward from what the bug needs
A kit cooldown bug needs a kit, a test account and two claims at known times. It rarely needs the original player's inventory, name or account identifier. Set up a normal test account, create a test kit and give the maintainer the rule and the result. If the error appears only after a restart, restart the test instance before taking the second observation.
Use the plugin author's documentation to find the relevant configuration and data. Oxide keeps configuration and stored plugin data in different areas. A plugin can also send requests to configured destinations. Use default files and private test destinations rather than bringing live service details into the reproduction.
Check what will leave your hands
Send a small report by default. When the maintainer needs a file, create a minimal version from the clean test.
| Material | Keep in the report |
|---|---|
| Configuration | The few settings that affect the result, with invented names and no live URLs, keys or passwords. |
| Console output | The first matching error and its time. Remove player IDs, names, addresses and connection secrets. |
| Player state | Test labels and actions. Exclude production saves, player records, bans and permission exports. |
Verify the report before sending it
Repeat the issue using only the steps and files you intend to share. If the synthetic test passes, send the versions and that observation first, and ask what further detail would help. Keep the live files private while the maintainer narrows the case.