Reloading plugins will not restart your server.
Fixed Plugins not loading on startup after update (dependency mismatch)
Discussion in 'Rust Discussion' started by inuques, Feb 2, 2017.
-
Wulf Community Admin
-
Same issue as everyone else, plugins werent loading on server start, manually loaded a load of em.
For some other reason whatever it was had unexpected restart
Manually reloaded those plugins again
Reluctant to restart just to show the compiler thing because I have people on.
you want me to try oxide.reload *
?? -
go to your plugins and set a dot in front of the name of PlayerManager.
It will prevent it from being set into the loading queue.
The do "reload *" and all plugins will load
(i did it that way) -
-
Wulf Community Admin
Okay, so I believe I found the cause (at least one of them). Any plugins referencing something from Rust that uses Newtonsoft.Json (ex. Facepunch.ObjectList) will cause errors due to a dependency mismatch. Ideally the plugin would not be calling this directly in the game, but to resolve it try the DLL below by placing it under RustDedicated_Data/Managed while the server is offline (likely won't work while online).
Attached Files:
-
-
-
-
Wulf Community Admin
-
Logs :
Attached Files:
-
-
Wulf Community Admin
-
Copy to /games/rust/RustDedicated_Data/Managed/Newtonsoft.Json.dll
Offline Server....
New logs :Attached Files:
-
-
-
Wulf Community Admin
-
-
-
Wulf is goin the extra mile tonight, praise wulf
-
Beautiful update. Now the server is found with 0 plugins and me with an offline server
-
Here you go
Attached Files:
-
-
Wulf Community Admin
Pushed a new build (2.0.3012) that includes the updated Newtonsoft.Json.dll. This is the same version that comes with Rust, just bundling it as sort of a hack to get around a limitation with our current build process. Just to clarify, the error is coming from one plugin erroring because of a DLL dependency mismatch, where the plugin is trying to use something from Rust's Assembly-CSharp.dll that requires a specific version of Newtonsoft.Json.dll.
Because plugins are compiled in a single batch (all at once) on startup and not individually, the compiler couldn't figure out how to handle the error and so the rest of the plugins errored as well, though they weren't actually at fault in most cases. Ideally this would not happen, but it was case where we did not see it during testing due to not running any of the affected plugins that were triggering it. -
My server is up to date but:
Code:10:22 [Error] Error while compiling Compiler v1.0.0.94 disconnected.
Attached Files:
-