NWNX .ini file? and '-restartdelay' parameter?

[Senalaya]

Papillon,

would it bother you too much, if I'd ask you for using an .ini file for the
-port, -module, -processwatchdog, -processinterval, -gamespywatchdog, -gamespyinterval, -gamespyretries and -oldgamespyprotocol parameters?

And what would be great, is a '-restartdelay' parameter. I noticed on my server, that the nwserver.exe process is restarted too fast. The memory isn't cleaned up then and it results most times in a 2nd crash shortly after. Before I switched to NWNX2, I used a utility called 'ServerDoc' for the restarts and it had such an option. A delay of 5sec worked sufficient.

[Senalaya]

On a 2nd thought, what about having one shared .ini file for NWNX and the modules?

[Blayde Windwalker]

I agree whole heartedly with Senlaya on this. Having to keep a command line string is too cumbersome and there is not enuf space to pass all the parameters.

This certainly would be an improvement.

[Papillon]

INI files are definitely on my list.

I'm not sure whether to use one or multiple files, though.

One file:
Pros: cleaner, everything in one place
Cons: harder to maintain for the end user

Multiple files:
Pros: example files can be easily distributed and copied by the end user
Cons: Clutters up the nwn folder

What are your thoughts ?
_________________
Papillon

[Makzimia De Graf]

For ease of use, I would suggest maybe one INI per server, if that was even really necessary. Considering the low number of options, relatively speaking, I can't see the sense in multiple files.
_________________
Makzimia De Graf

DM/Creator Island of Fredian
fredian.game-host.org:5123
Forums at http://castille.us/fredian/Forums

[Papillon]

I can not pass commandline parameters from NWNX.EXE to the plugins, so those would not know which ini file to use. So it is either one or multiple ini files per NWN directory.
_________________
Papillon

[Senalaya]

As I suggested here and in the reply in the general section, I'd go for 1 .ini file per NWNX instance.

It's the cleanest solution. You could pass the name of the .ini file as commandline parameter ('-config nwnxtest.ini') if you intend to run multiple NWNX instances off the same directory. Since you can't do that with the modules, a single file would be better.

The only real downside I could see, is that the code in the modules for inserting the proper categories and fields into the common .ini file on the 1st start, would be a bit more complicated.

[JeroenB]

[Liberty Valance]

i vote for the single-ini-file method!
_________________
A Persistent World West2 | APWW2 Forums
Wirehead Studios

[Senalaya]

[Papillon]

Be my guest
_________________
Papillon