How to gracefully shutdown nwnx2 and server for updates?

[lordofworms]

Title pretty much says it all..
whats the best practice when doing this?
currently I shut the server down then nwnx2

or should it be the otherway around?

also one more question I couldnt find an answer to.
I have my nwnserver set for Reload on Empty. does this somehow inhibit nwnx2 since its restarting kinda internally? in other words, its not really closing or shutting down then having nwnx2 restart it. Like if I hit shut down.
maybe obvious answers but I wanted to be sure (:
thanks again for this system, it is soooo great!

[Baaleos]

Well, there are pro's and con's to both.

Persistently - there wont be any difference either way.

Killing nwnx - can cause scripts to fail in game until you turn the server off. Eg - SQL Statements wont get executed, they will fail, and possibly result in TMI errors.

Killing nwserver.exe before nwnx - wont cause any problems, nwnx may however try to restart it right away, depending on where it was in the countdown.

I personally, kill nwserver.exe, then quickly kill nwnx.exe


However, if you wanted to be fancy, you could create a bat file that does

[Lokey]

On linux, reset plugin. On windows, will that be an exit or a kill?
_________________
Neversummer PW NWNx powered mayhem

[Fireboar]

You could always just replace the module in the modules folder first, then just shutdown nwserver. NWNX will bring it back up with the updated module.

[Lokey]

On linux, yah. On win you need to be careful about that.
_________________
Neversummer PW NWNx powered mayhem

[lordofworms]

yeah, well he last few times I did that (added new updated module to module folder then had nwnx2 restart it after shutting it down) I had some quirky things happen (server running nwnx2 windows xp sp3)

by quirky I mean, some players journals were wiped, some players housing was missing, and prob other things that went unnoticed.
so I only replace the module now when the server is NOT running in any way. It may be too much caution but it makes me feel better.

so I took advice of writing a BAT file for it, works like a charm.

[maddogfargo]

I've had no trouble overwriting the module then performing a manual reset to load the update. Currently hosting on XP SP3.

I think a good practice is to make sure the server has been empty for a minute or so before doing that. I usually do that to ensure players are not using any database related features like storage or doing a HGLL/LETO character update/boot when the server is killed.

As a general rule, I kill the NWN server first then NWNx.
_________________
* illegible scribble *

[virusman]

NWNX.exe is just a loader and watchdog. The actual NWNX code is injected into nwserver.exe process, so killing NWNX.exe should not affect NWNX itself.
_________________
In Soviet Russia, NWN plays you!