Dasaria II - A NWN2 Roleplay and Story-driven Persistent World

We are testing a script to restart the das game server if it crashes. It has passed its 1st test with flying colors, but we will continue to watch it.

This is a good news, as it means that the server should be up all of the time.

Jehannum wrote:We are testing a script to restart the das game server if it crashes. It has passed its 1st test with flying colors, but we will continue to watch it.

This is a good news, as it means that the server should be up all of the time.

WHOOO! Way to go guys!

-K

Thank you! Really well done indeed!

Greaaaaaaaat. Now I wont have an excuse to sleep. Geeeeee thanks! ; )

plenty of insight there.

What actually starts the process?
Is it just an exe?

Could you use something like FireDaemon to start the exe as a service?
Configure any command line parameters to start the module and set it for Restart upon Program Exit??

Just curious and wanting to add some application expertise.

I experimented at length with FireDaemon. The issue I ran into was when I tried to load a module that was stored as a directory structure (as opposed to the usual .mod file). For some reason, FireDeamon wont accept the "-module modulename" parameter for modules stored in this fashion.

If anyone knows how to get this working though, we would love to hear it because otherwise, FireDeamon would be perfect for the job.

What is the inherent difference between a module that uses a directory as opposed to one that uses a .mod file?

Do all persistent worlds use a directory structure?
Is there a way to "pack" the directory or convert it to a .mod file?

Is this something we should be asking Obsidian?

You can save it as a .mod file OR as a directory structure. We use the directory structure because it greatly simplifies our update process. We just need to know the switch to use to load a module stored as a directory and we would be good to go (because -module definitely doesn't work).

OK...but let's say that there isn't one, wouldn't it be beneficial to then do the .mod conversion?

I understand (and thought that was the reason) about the ease of updating but couldn't you keep a "backup" directory that you can do updates to before converting it to a 'Live .mod"?

Have you tried -moduledir modulename?
(I have no idea, I'm just taking a wild semi-educated guess)

Any luck?