Skywing's NWNX4 improvements

[virusman]

Nice, thanks for uploading.
Please make a separate plugin for packet logging. I don't think it's necessary to have it in the core
(See tickets #1 and #2)

[Skywing]

Can’t register or login to your trac, seems that it’s not entirely functional yet?

Register dies with:

Not Found
No handler matched request to /register
TracGuide — The Trac User and Administration Guide

Due to trac breakage, will send responses inline:

Re ticket 1:

Packet logging is planned to be moved to a separate plugin. This was just a straight port of my changes to pre-1.09, plus fixes for various things that got broken anew with the pre-1.09 release and some other enhancenments I had done locally already. Everything there is functional and tested.

(Splitting packet logging out falls under "merge in NWN2Lib", which is where I was starting to put all the NWN2 version-specific stuff.)

Re ticket 2:

The crash dump writing logic is already controlled by a config file directive (if a crashDumpDir is not specified, then the controller will not write out minidumps). The primary reason to disable crash dumps (and they are disabled by default right now as theres’s no crashDumpDir directive in the ini file) is avoid writing out a potentially large disk file on every nwn2server crash.

However, the crash dump client and server code is always active in the controller process and in the hook. If crash dumps are not enabled then the controller will log a message with some (very basic) information about the fault and then restart nwn2server. I see no reason to disable this given that it provides useful diagnostics capability (already used it “in the field” a number of times to identify whether a user was running into a problem that xp_bugfix repaired) and otherwise has minimal impact over letting the nwn2server process die and get picked up by the JIT debugger (which if it is, say, WinDbg or Visual Studio or another interactive debugger, could be the exactly wrong thing to allow to happen – as would be the case on my systems, for instance).

Additionally, leaving the crash client / server logic always on allows for nice differentiation between "clean" shutdowns (e.g. scheduled morning restarts of nwn2server via nwn2srvutil or the like) and hard crashes by examining the controller log.

[Dragonsbane777]

I am curious, will this plugin work with the new 1.13 update for NWN2? Or, is it in the works, or not planned, etc?

Thanks for your time

DB

[juliam]

[Skywing]

There is an undocumented ini option in NWN2 to set the receive timeout.

[Server Options]
Player Timeout=timeout in seconds

Note that clients may tend to need this set as well or the client will still "give up" early.

[juliam]

thank you Skywing

now, i am double-checking if i have everything to update, i.e.:
1- xp_bugfix for patch 1.13 with hotfix;
2- nwnx4 improved

i assume that your nwnx4 improved version works with last xp_bugfix
so, i'll download those and prepare the update then i'll check back if all is ok...
thanks again Skywing

[Skywing]

You can use xp_bugfix with either the stock NWNX4 or my build of it.

[serafim]

Hi,

i'm going to build a new pw and i'm in trouble with the various versions of nwnx4 now waytingh to be merged in 1.09, so.....

Your nwnx_improved is compatible with which plug-ins?

I wish to implement:

- nwnx4_bugfix (that is compatible, is'nt it?)
- nwnx4_profiler
- xp_craft (known problems?)
- virusman's last mysql with sco/rco (?)
- nwnx4_system

I would really appreciate any advice.
Thanks in advice.

[Skywing]

The changes to the core/hook module do not affect plugins. All NWNX plugins should work unmodified with the improved core.

[serafim]

Thanks a lot Skywing for the fast reply, i really appreciate .