I have updated to the latest version of Oxide and none of my plugins are working. I have tried to update twice in the last 20 minutes to ensure that I had the latest version and they still did not work. I tried restarting the server, which is not required as I use LGSM, but the plugins are still not working. The server was updated to the newest version of Rust this morning when it came out and restarted then as well. My players are getting upset that they do not have their plugins. What is going on?
Oxide not workingNot An Issue
I'm not aware of any issues, and there were no changes with Oxide this update, so it sounds like you do not have Oxide installed. You can verify with the oxide.version command.
Well, the server has the oxide folder and I have had plugins working until this morning so unless Rust removed oxide that was not the issue, but I re-installed Oxide, and LGSM told me it was already installed.
After all of that, I go into the RustAdmin console and type oxide.reload all and get absolutely nothing and I still have no plugins working in the game.
Rust updated twice today, which you'd need to reinstall Oxide after each game update.
I just verified that I am on the latest version of Rust and I did reinstall Oxide per your suggestion and nothing is still working. I am going to restart the server one more time and hope Oxide decides to start up as I can find no reason for it to not be working. Since one of the questions I have noticed you ask when discussing reinstalling Oxide is if it asks about overwriting files, yes it did ask and I did say yes.
Oxide wouldn't just not start, it is loaded when the server starts when it is installed. If it doesn't load, it isn't installed. Make sure you don't have any update steps that are running that would remove it each start.
It is finally working after reinstalling it, and updating it and restarting my server multiple times even after all of that. I have never had to do this much work to get Oxide working again. I do not know what the problem was but it is working again now.
As for Oxide "just not start" I have had it where it quit on update before but usually on server restarts it fixes it, or a second restart. This is the first time I have had to go through this much work to get it to "repair" and work again. I have spent two hours now trying to get this working. According to the server it was already installed. Regardless of the fact that I could not get any reply as to what version it was, I have had that happen numerous times before when Oxide quit working but as I said a restart fixed it if oxide.reload all did not.
I love the work you guys do and all of the plugins that you make possible but not everything is "If it doesn't load, it isn't installed."
It isn't really possible for it to work that way, sorry, but it's simply not possible. It either loads or it isn't installed, which you can see from your server log. If there is an error during start, it would be in the logs, but there is no conditional loading.
Oxide is loaded by replacing game files with patched ones, so it is either installed or it isn't. Those files being replaced means it is installed and you would see that it is when the server starts.
Wheter plugins load or not is another thing, but all indications in your messages show that it wasn't installed each time. In the future though, I would suggest checking the server log.
Also, a folder existing doesn't mean it is installed, just that it once was as those files are not removed by the server. The only relevant indication here is your logs and Oxide functionality. The game has to be physically modified for Oxide to load, and if it isn't then it won't load as nothing was modified for it to load.
If the method you use to start or update the server doesn't successfully replace the files from the game with the modified ones, Oxide will not load as there is nothing there to tell it to load.
If you update the server with Steam for a game update, that would remove and replace the modified files necessarily for loading Oxide.
Also, always make sure the server is shutdown before installing or updating, as that can prevent a proper install if those files are in use and fail to be replaced.
I hope that helps clarify it.
Locked automatically