A commonly asked question.

To activate chat logging, go to your NWN directory, open nwnplayer.ini and, under [Game Options], add the line ClientChatLogging=1. This will save your logs to the \logs folder inside the NWN directory.

Note, this will only log chat text. If you want combat feedback and system messages logged too, change ClientEntireChatWindowLogging to 1 as well.

So far, so good. But not really. Everytime you launch NWN, the log file will be overwritten, which means you'll have to manually move or rename the file to avoid data loss. Lucky for us, this process can be automated.

As you may have guessed, the above file is a VBScript; not a program, thus no installation required. You will, however, still have to edit it.

After downloading the file, place it in your NWN directory. Right click it and pick Edit. Change CONST NWN_PATH = "F:\Games\NWN" to the location of your NWN directory. Save, close, and doubleclick the script. This'll check to see if the nwclientlog1.txt file contains data and, if it does, rename it according to the script, and then proceed to launch NWN; all pretty much without any delays.

Now, the default naming scheme is yyyy_mm_dd_hourminute. If you prefer another scheme, edit the file again. Locate the line that reads

sTargetFile = Year(datLastModified) & "_" & Right("00" & Month(datLastModified),2) & "_" & Right("00" & Day(datLastModified),2) & "_" & Right("00" & Hour(datLastModified),2) & Right("00" & Minute(datLastModified),2)

sTargetFile = Day(datLastModified)  & "-" & Right("00" & Month(datLastModified),2) & "-" & Right("00" & Year(datLastModified),4) & "_" & Right("00" & Hour(datLastModified),2) & Right("00" & Minute(datLastModified),2)

In order to use this thing with the standard NWN shortcut, right click the shortcut and choose Properties, then change the destination from "\nwn.exe" to "\nwn.vbs".

And that's pretty much all there is to say. If anyone with a little more skillpoints in Craft (VBScript) has something to add, please do chime in.

Credits go to Tephritidae for scripting this little perl, and Dopson for pointing it out to me.

Anyway to do this so that the .vbs file doesn't automatically fire up the player client? I'd like to get logs as both a DM and a player!

Changed to launch the selection screen rather than the client directly. This should work, but you might want to check just to make sure.

The above link directs to the new file.

Question, is there a way to make this enabled whenever NWN launches? Currently, I enter EfU from the nwlauncher.exe, which lets me double-click on the server directly without launching NWN and going to Multiplayer and browsing through Gamespy.

If I understand your question, probably, but not directly. nwlauncher.exe does not seem to be part of the BioWare package, so I don't know how it works, but you should be able to create a shortcut for nwlauncher.exe, have the shortcut point to the script file, and then make the script launch nwlauncher.exe instead of nwn.exe.

Basically, I was wandering through the vault, and I stumbled upon this Gem, which basically reads your logs and returns combat stats, such as acuracy, number of hits, total damaage, crit%, etc. But The system in the above posts is ill equipped to work well this NeverSeeit, because this makes a new file for each time you run NWN.

NeverSeeIt examines only one log at a time, which means you need to spend time adding the stats together and manually calculating. Which is very tedious, and too time consuming to bother. So I had to design my own system to work efficiently with NeverSeeIt.

This system, is not bound only to work with neverSeeit, but has all the functionality of Snoteye's VBscript, except it is not automated Yet.

The main Advantages of this system, are;

1) It works while NWN is running, so you can Minimise out, or window out, and Quickly save a log after a specific conversation or battle, which allows you to find it later. (Alot easier than with the above method, since you know exactly what it is called)

2)It 'stacks' with other log files, so you can essentially create one File for each character, and find every log in one .txt ( To clarify, if you type in "Mylog" in the box, and save your log, and then type "Mylog" and save it again at a later date, you will still have the original contents, with the new addition at the end.

3) It can Launch both NWN and the DMclient, (command line args and direct connect coming soon)

How to use this :

(NWLogger) Extract the Zip to your NWN Folder. (because NWN does not like when you try to run it from a different folder)

Open the file called config, which is the text file included in the package. You will see a single line which says "C:NeverwinterNights\NWN" This is the path for your game. If your NWN folder is not in C:Neverwinternights\nwn, you will need to change and save this file so it is correct.

Run the Program. (Note you do not need to launch NWN from this program, the function is there for efficiency's sake.)

You Should see the program, which looks like this;

The White box there is the Input, which you Type the name you want to save the log as. This can be anything, with a limit of 32 letters. Note you cant use symbols or things which are not usable in normal file names.

Note that you do not need to include a file extension, as it does it automatically. All you need to type is a name.

Once you have your Name, click the rename button. And there you have it. You should find in the Logs folder, the file with the name you specified, containing the NWlog up until the last time you Pressed Rename. You will also see a Templog and a Sessionlog, Which are there for functionality's sake. The session log saves everything in the NWLog since you first hit rename, Basically a record of what you have done. Templog contains the last portion of log you copied. Both are deleted when you Restart the program.

Thats pretty much it for that one.

(neverseeit)

Extract the Zip. I'm pretty sure this doesnt matter where you extract it to. Click File on the top left, and click Open. Find the log you want to get stats from, and They will be displayed almost right away.

Thats pretty much it for that one as well.

Enjoy, and if you have any questions or find any bugs, PM me on the forums or IRC>

I will be updating this program pretty often, and will post a link to a separate project page to avoid Forum Clutter. (Autosaving, Direct connect compatibility on the way)

Minor update to Snoteye's script:

This will do a few things.

First you can create duplicates of the script and enter in different character names to store separate logs for each character.

Second, it keeps one single log for each character, entries are separated by a time stamp and new entries are added to the bottom of the file.

Third, it direct connects to EFU. If you wish to change this behavior simply change what is in quotes in the following line:

WshShell.Run NWN_PATH & "\nwmain.exe +connect efu.us.to",,TRUE

to

WshShell.Run NWN_PATH & "\nwmain.exe",,TRUE

or

WshShell.Run NWN_PATH & "\nwn.exe",,TRUE

Code is as follows. Simply copy and paste it into notepad and save the file as "NAME.VBS" Where name is, obviously, whatever you want it to be. Then simply edit it and change the name of the log file. (Third line down, where it says "oona.txt" currently.)

See Below

IMPORTANT: Found a small logic error. It is fixed now, but if you were using the original code from this post, it will not save any logs except for the one log created the very first time. Please update to this code ^_^

Should be bug free now, however, and good to go.

And, already version two.

Changes: Log Name is now supplied when the script is run. For instance, running the command (ie, in a shortcut)

C:\NeverwinterNights\NWN\ChatLog.vbs "OO NA"

Will result in a log file named OO NA.log

Quotes are only needed if you want a space to appear in the name.

C:\NeverwinterNights\NWN\ChatLog.vbs Oona

Would, for example, create a log named Oona.log

Obviously, the script will fail if you try to enter a name with illegal characters, as it simply won't be able to create the file.

Think that's about it for changes. On to the code.

'Dynamic Log Naming variables
dim LOG_NAME
Dim args_index 
Dim command_line_args 
Set command_line_args = wscript.Arguments
LOG_NAME = command_line_args(args_index) & ".log"
'Folder where NWN is installed
CONST NWN_PATH = "C:\NeverwinterNights\NWN"
'Start NWN and halts script execution until NWN is closed
Dim WshShell
set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.Run NWN_PATH & "\nwmain.exe +connect efu.us.to",,TRUE
'Blah :-)
Dim fso: set fso = CreateObject("Scripting.FileSystemObject")
Dim sTargetFile, datLastModified, nwnSessionLog, nwnLogFile
Set nwnSessionLog = fso.OpenTextFile(NWN_PATH & "\logs\nwclientLog1.txt",1)
'If a character log file exists
If fso.FileExists(NWN_PATH & "\logs\" & LOG_NAME) Then
	Set nwnLogFile = fso.OpenTextFile(NWN_PATH & "\logs\" & LOG_NAME,8)
	'If a session log file exists
	Else
	Set nwnLogFile = fso.CreateTextFile(NWN_PATH & "\logs\" & LOG_NAME)
End If
If fso.FileExists(NWN_PATH & "\logs\nwclientlog1.txt") Then
   'And if it's bigger then 0
   If fso.GetFile(NWN_PATH & "\logs\nwclientlog1.txt").Size > 0 Then
      
      'Initialize variable to contain Line Break with Date and Time of last modification.
      datLastModified = fso.GetFile(NWN_PATH & "\logs\nwclientlog1.txt").DateLastModified   
      lineBreak =  Year(datLastModified) & "_" & Right("00" & Month(datLastModified),2) & "_" & Right("00" & Day(datLastModified),2) & "_" & Right("00" & Hour(datLastModified),2) & Right("00" & Minute(datLastModified),2)
      
      'Write Log Break Line
      nwnLogFile.WriteLine("-------------------- " & lineBreak & " --------------------")
      
      'Concatonate session log into complete log
      TextReadAll=nwnSessionLog.ReadAll
      nwnLogFile.Write TextReadAll
      nwnSessionLog.Close
      nwnLogFile.Close
      
   End If
End If

And finally, an alternative script.

This one accesses the registry to find the location of NWN. If this makes you uncomfortable don't use i!

It is perfectly safe, however, and only reads the registry. It will not delete or add any entries.

Dim WshShell
set WshShell = WScript.CreateObject("WScript.Shell")
dim logName
Dim args_index 
Dim command_line_args 
Set command_line_args = wscript.Arguments
'retrieves Log File Name based on command line input
logName = command_line_args(args_index) & ".log"
'Poll Registry for NWN location.
nwnPath = WshShell.RegRead( "HKEY_LOCAL_MACHINE\SOFTWARE\BioWare\NWN\Neverwinter\Location" )
'Start NWN and halts script execution until NWN is closed
WshShell.Run nwnPath & "\nwmain.exe +connect efu.us.to",,TRUE
'Blah :-)
Dim fso: set fso = CreateObject("Scripting.FileSystemObject")
Dim sTargetFile, datLastModified, nwnSessionLog, nwnLogFile
Set nwnSessionLog = fso.OpenTextFile(nwnPath & "\logs\nwclientLog1.txt",1)
'If a character log file exists
If fso.FileExists(nwnPath & "\logs\" & logName) Then
	Set nwnLogFile = fso.OpenTextFile(nwnPath & "\logs\" & logName,8)
	'If a session log file exists
	Else
	Set nwnLogFile = fso.CreateTextFile(nwnPath & "\logs\" & logName)
End If
If fso.FileExists(nwnPath & "\logs\nwclientlog1.txt") Then
   'And if it's bigger then 0
   If fso.GetFile(nwnPath & "\logs\nwclientlog1.txt").Size > 0 Then
      
      'Initialize variable to contain Line Break with Date and Time of last modification.
      datLastModified = fso.GetFile(nwnPath & "\logs\nwclientlog1.txt").DateLastModified   
      lineBreak =  Year(datLastModified) & "_" & Right("00" & Month(datLastModified),2) & "_" & Right("00" & Day(datLastModified),2) & "_" & Right("00" & Hour(datLastModified),2) & Right("00" & Minute(datLastModified),2)
      
      'Write Log Break Line
      nwnLogFile.WriteLine("-------------------- " & lineBreak & " --------------------")
      
      'Concatonate session log into complete log
      TextReadAll = nwnSessionLog.ReadAll
      nwnLogFile.Write TextReadAll
      nwnSessionLog.Close
      nwnLogFile.Close
      
   End If
End If