1. Community
  2. Game Support
  3. Reign of Kings
Oxide not loading/showing log outputFixed
Posted 4 years ago
Last updated 3 years ago
#1
There seems to have been some sort of change with how oxide is being loaded now.
It seems on the latest release, the compiler is no longer being loaded when running ROK.exe and only gets loaded when using the server.exe (basically a console viewer) to start the rok.exe
Before the latest update, the compiler would load up with rok.exe without an issue.
I am not sure if this was intentional or not, just wanted to bring it to your attention.
Posted 4 years ago
Last updated 3 years ago
#2
There hasn't been any changes made to how it loads, or really anything this update. The update only patched for the RoK changes, which didn't even touch any of our files, only the game's DLLs. I tested it before release as well, and it loads up the same way it has for the past few years.

Regardless of how you start the server though, the Compiler is started by Oxide, not the server itself.

Without really any details though and not being able to reproduce the issue, there isn't much for us to go on to help you.
Posted 4 years ago
Last updated 3 years ago
#3
I am running the latest version of reign of kings and the latest oxide. If I start the server using only the rok.exe, the compiler.exe does not open up and oxide does not get loaded. If i open the server using the server.exe, the compiler.exe does open up and oxide will load up. 
Iv never used the server.exe to load up a reign of king server before and had no issue with oxide in the past.
Can you confirm if you encounter the same thing?
Posted 4 years ago
Last updated 3 years ago
#4
In response to zack ():
I am running the latest version of reign of kings and the latest oxide. If I start the server using...
I've tested both ROK.exe and Server.exe, both startup fully and both show Oxide and plugins loading. As I mentioned, no changes were made to how Oxide is loaded, the updates didn't really change anything.
Posted 4 years ago
Last updated 3 years ago
#5
Alrighty then, thanks for your time.
Posted 4 years ago
Last updated 3 years ago
#6
Did you check your logs for errors? Both the game's logs and oxide/logs.
Posted 4 years ago
Last updated 3 years ago
#7
Iv checked the games log file, i did not see anything that stood out.
There are no oxide log files that get generated when using only the rok.exe

When I use the server.exe to start it, the oxide logs are generated. There are no errors and oxide works correctly.

Here is a copy of the log file when launching with only the rok.exe

https://pastebin.com/YXTMsxQM

And for comparison, here is the log file when using the server.exe

https://pastebin.com/Cew8Lry7
Posted 4 years ago
Last updated 3 years ago
#8
In response to zack ():
Iv checked the games log file, i did not see anything that stood out.
There are no oxide log fi...
Both of those logs have nothing Oxide-related in them. I suspect you don't have Oxide installed. Where did you download it from?
Posted 4 years ago
Last updated 3 years ago
#10
In response to zack ():
From the latest release off the github and from the downloads page of umod


https://...
That screenshot looks normal. What do you see when running ROK.exe (with a script, not directly as that isn't how you start a dedicated server)?
Posted 4 years ago
Last updated 3 years ago
#11
Hmmm, There usually inst a window as it is launched using the command line settings

-batchmode -nographics -silent-crashes -nolog

removing everything but -batchmode does allow a window to open and it does appear that oxide is working then.
I can confirm that as a log file is generated in the oxide folder

I am going to mess around a bit more with those command line settings to see which is causing oxide not to load up.
I am not sure why it wasnt a problem before but it is now.
Thanks for the help and getting me pointed in the right direction.
Posted 4 years ago
Last updated 3 years ago
#12
In response to zack ():
Hmmm, There usually inst a window as it is launched using the command line settings

-batc...
None of those arguments would directly cause Oxide to not load, they are not dependent on those at all. If you aren't using -batchmode though, then your RoK server isn't being setup as a dedicated server, so therefore Oxide would not load.
Posted 4 years ago
Last updated 3 years ago
#13
We've used the same command line setup like for a long time without issues.

It appears that the -nolog is what is making oxide no longer load up. With that removed, it loads up fine.
Posted 4 years ago
Last updated 3 years ago
#14
In response to zack ():
We've used the same command line setup like for a long time without issues.

It appears th...
The -nolog argument is a Unity Engine setting to disable log output (such as that from Oxide), but that will should not affect the actual loading of Oxide.
Posted 4 years ago
Last updated 3 years ago
#15
I don't know what to tell you, When I remove that setting oxide does load up and if I add it back, it no longer loads. Either way, my issue is fixed.
Thanks for the help with this.
Locked automatically