Since the latest update yesterday, I've experienced this situation twice, once running the Rust Oxide plugin version 2.0.4714 and once with version 2.0.4715. Everything is running fine, nothing buggy, and then all of Oxide just reloaded. There are no scheduled commands and no one entered a o.reload * command. This is what the oxide log looks like:

21:25 [Info] [FancyDrop] xxxxxx (xxxxxxxxxxxxxxxx) looted his Drop at: (-986, 13, -1539) grid area: G24
21:26 [Info] Loading Oxide Core v2.0.3988...
21:26 [Info] Loading extensions...
21:26 [Info] Loaded extension CSharp v2.0.4037 by Oxide Team and Contributors
21:26 [Info] Loaded extension Rust:IO for Oxide v2.17.0 by playrust.io / dcode
21:26 [Info] Loaded extension MySql v2.0.3758 by Oxide Team and Contributors
21:26 [Info] Loaded extension Rust v2.0.4714 by Oxide Team and Contributors
21:26 [Info] Loaded extension SQLite v2.0.3760 by Oxide Team and Contributors
21:26 [Info] Loaded extension Unity v2.0.3772 by Oxide Team and Contributors
21:26 [Info] Latest compiler MD5: 8ce6d27e7718e3d164766bba8833537a
21:26 [Info] Local compiler MD5: 8ce6d27e7718e3d164766bba8833537a
21:26 [Info] Using Covalence provider for game 'Rust'
21:26 [Info] Loading plugins...​

Not sure if there's an error in one of the plugins I'm running potentially causing issues, but just didnt know if there have been any reported stability issues with the newest builds of Oxide.

Oxide core doesn't reload, it is only loaded on server start. The command "o.reload *" only applies to plugins. I would assume some plugin is messing with it, as it would only ever be called when the server itself is initialized, once.

Hmm, yea I can double check any possible plugin errors. But all that code for the oxide core reloading was done in the middle of the the server already up and running with people on doing things. Nothing out of the ordinary happened either time. Just super odd. It's possible one of the plugins I'm running still needs to be updated since the Aug. 6 update, but I'll dig around and see what I can find. So it seems even more suspicisous that something is causing the entire platform to reload.

This is the only location where Oxide is initialized, when Rust starts and sets up the server initially:


That "Interface.Initialize()" is the trigger to tell Oxide to load. If a plugin calls that manually, it's possible that it would be causing that, or if the plugin calls the method where it is hooked, but more likely the former.

Great info! I'll dig around and make sure nothing is calling that hook by mistake.