graywolf.theheathen
Member
I saw this thread, http://www.gamersonlinux.com/forum/threads/star-wars-the-old-republic-manual-test.216/ , and it seems to be frozen in time. Anyone still working on it?
An extra step must be performed when installing the stand-alone server under Linux. After extracting the downloaded .zip file into an appropriate directory, one of the extracted files will be a .tar.gz archive containing the Linux-specific files (including the Linux executable). This archive also needs to be extracted to that same directory, overwriting any existing files. An important file to overwrite (or delete, as the Linux-specific version is empty) is nwn.ini, as the Windows version contains backslashes and the Linux executable expects front-slashes. A symptom of failing to overwrite/delete this file is that no modules will load.
Depending on where the server has been installed, it may be necessary to set permissions so that the intended user(s) can execute nwserver and read all files in both the the installation directory and subdirectories thereof.
The Linux dedicated server is usually an interactive terminal application without a graphical interface. Thus the application must be started from a terminal window (command prompt), where it will write output and accept directives. A full list of these directives can be obtained with the directive help, and most are listed in the filereadme.linuxserver.txt which is included in the Linux-specific archive. Many directives have command-line equivalents, allowing them to be specified when the server is started, rather than having to be typed into the server each time the server is started. The command-line arguments can be viewed by executing
Code:./nwserver -help
or by reading readme.linuxserver.txt. The most common argument is likely the one that specifies the module to load, as in
Code:./nwserver -module "modulename"
Another argument of note is "-quiet", which enables the server to run (non-interactively) in the background. Correct use of this argument requires that all necessary directives have been replaced by command-line arguments, as it will not be possible to enter any directives. One consequence is that with this argument, the server does not need to be run in a terminal window.
Problems get logged in the file nwserverLog1.txt in the logs.0 directory.