1. Community
  2. Game Support
  3. Rust
Setting -logfile argument to invalid location causes server not to startNot An Issue
Posted 7 years ago
Last updated 6 years ago
#1

On my start-script if i set logs directory to folder that doesn't exist it will throw error that Oxide Can't be started
Example:

RustDedicated.exe -batchmode -nographics -logFile "FolderThatDoesntExists/log.txt"

0Cbeqdo.png
but if i change folder to exists or to nan -> it wil work correctly

Posted 7 years ago
Last updated 6 years ago
#2
The -logfile setting has nothing to do with Oxide, that's a Unity argument. There isn't really anything we can do about that, sorry.
Posted 7 years ago
Last updated 6 years ago
#3
In response to Wulf ():
The -logfile setting has nothing to do with Oxide, that's a Unity argument. There isn't really anyth...
Oh, i didn't knew what :(

Anyways can it be fixed? Its not so important, but i spended 1h to solve it (catch and inspect). Some users can have that problem too
Posted 7 years ago
Last updated 6 years ago
#4
In response to Orange ():
Oh, i didn't knew what :(

Anyways can it be fixed? Its not so important, but i spended 1h...
That's something you'd likely have to talk to Unity about or Facepunch, as I believe it is used before we even initailize Oxide.
Posted 7 years ago
Last updated 6 years ago
#5
Wulf, for people that are not accustom to command line interfaces, is there a way to easily identify what is explicitly a Unity arguments vs RUST server variables? 
Posted 7 years ago
Last updated 6 years ago
#6
In response to CorrosionHour ():
Wulf, for people that are not accustom to command line interfaces, is there a way to easily identify...
Rust commands can be found via the 'find .' command, Unity arguments are listed in their documentation.
Locked automatically