The client extension is an add-on to the standard NWN2 game client that fixes various crash bugs, restores the Internet Server Browser for multiplayer server listings, and adds new multiplayer functionality to the game (for example, a better reply function, command history, and a host of other improvements).
Direct download link for latest version: Link (version 1.0.0.24)
There are also significant improvements to the capabilities of the DM client included (compatible with DMFI, although not dependent on DMFI). For example, you can teleport objects to specific points in other areas without jumping to the area first, and (with some server script support) you can view creatures on the map in a different area than you're currently in.
A brand new, "headless" standalone DM client for NWN2 is also included that allows PW admins to log on to their server without launching the full game DM client.
You can now create a shortcut to directly connect to a PW from the desktop with the +connect argument supported by the included NWLauncher.exe (see the included readme file for details).
Posted by egbert at 2013-04-06 14:59:42 Voted 4.50 on 04/06/13
If you are a DM or a player on custom servers (particulary PWs) this client is a must-be.
(v1.0.0.24) For all others:
- The GameSpy-search-replacement is running, but it's almost impossible to publish the campaign/module you are playing. Therefore your search will show most predominant PWs.
- The long waiting time for autorization (comes never because the Bioware server is gone) becomes near 0. 8-)
- GREAT also for single players are the hotbar key macros (e.g. all the buffs with one one key pressed). 8-) Unfortunately at now they are buggy and need to be improved. 8-(
Posted by egbert at 2013-04-01 07:35:07 Voted 4.50 on 04/06/13
I'm a new user of this Client running Win7 64-Bit.
1. Problem: My AREA Window stays empty. The CONSOLE shows a warning: "Failed to calculate Area dimensions for area X. Failed to locate RESREF X."
Any help? TIA
2. Question: Does opening an MP game publish my server to the list (as it was done with Gamespy)?
3. Feature request: A (customized) macro on the toolbar has no own texture and shows only the "a missing texture"-Picture. A customized picture would be nice.
I tracked down the problem. If you decide to change where your temp files get written and read from to something other than the default folders (%USERPROFILE%\AppData\Local\Temp) in environmental variables, then the CE may throw a fit. Especially, if your directory has limits placed upon it. I changed it back to default for the CE and everything runs fine.
I can no longer log into any PWs while the CE is used. I have been using the CE for a while with no problem, but now it messes things up. Furthermore, when I transition in a module with the CE it takes forever, that is, if I can even load a module. Please help. I do not want to play without the CE. This has happened once already and I did a full reinstall and fixed it. I do not want to reinstall again and again.
Technical Details:
Win7 32
Intel Pentium 3.4Ghz
2GB RAM
ATI Radeon HD 4300/4500 Series
You can put /mpredict into your autocmds.txt in order to turn it off persistently. Check the readme for more details about how autocmds.txt works.
Posted by Thorsson64 at 2013-02-07 11:29:33 Voted 10.00 on 02/07/13
One thing that I know irritates a number of us - can you at least put a switch in to turn off predicted movement? Even better turn it off by default. For PWs it's just a pain and everyone who knows the switch types in /mpredict.
CE release 1.0.0.24 is now available. This release includes the following features:
- Added native compatibility with the GOG.com edition of Neverwinter Nights 2.
- Added a count of online players known to the multiplayer server tracker (printed to the console window at startup).
- Other minor bug fixes and improvements.
Hey Jarrakul, I just got this to work with the GOG.com version. Rather than manually edit the registry to add the key, the simplest way to get it to work is to run nwupdate.exe inside your NWN2 install. That should setup the registry keys and from there NWLauncher should run just fine. Found this note on the old bioware forums from Skywing. HTH
Having trouble getting this to work. I'm using the GOG.com version of the game, which may be why. NWLauncher.exe can't find the installation directory, and when I try to apply ClientExtension.hdl directly, the console loads but gives the following message "Failed to prepopulate CD-Keys from game INI files: Unable to open NWN2 registry key". Am I missing something obvious?
CE release 1.0.0.23 is now available. This release includes the following features:
- Added a +connect [server-address] (and optional +password [server-pw])
argument to NWLauncher.exe. These allow you to create a shortcut to directly
connect to a PW from the desktop. You can connect as a DM, too, by using the
-dmc argument as well. For example:
Posted by Firestar001 at 2013-01-04 23:19:24 Voted 10.00 on 01/04/13
A Saint! You are an effing SAINT! I cannot express how... relieved, thankful, overjoyed... blown away I am that this works. If I could I'd give you money as thanks for what you've done.
Posted by Arvirago at 2013-01-04 08:01:54 Voted 10.00 on 01/04/13
Great job _________________________ Reino de Aldor
Posted by Curmudgeon at 2013-01-03 13:52:52 Voted 10.00 on 01/03/13
Skywing, I salute you!
Posted by ThePhalanx at 2012-12-26 04:29:38 Voted 9.75 on 12/26/12
This is a fantastic thing you're doing for the NWN community, Skywing, and your client extension is a great tool on its own.
Release 1.0.0.22 is now available (includes restored Internet Server Browser support for multiplayer).
This release includes the following features:
- Internet Server Browser functionality restored using a new master server list hosted by Skywing. Servers can participate by installing the xp_bugfix 1.0.20 or later plugin from the NWNX4.org forums (see the NWNX4 Development forum, xp_bugfix thread). Clients running the Client Extension will automatically nominate servers unknown to the Internet Server Browser on connection for broadest community coverage. Web-based versions of the Internet Server Browser are also available; for example, visit Link . See the readme file included in the .zip for more details.
- Self-update functionality included in the Client Extension. The Client Extension will present a message box at the main menu when a new Client Extension update is available; the user can choose to install the update directly from the game (or continue on to play without installing the update if desired).
- Included a fix from FoamBats4All for a DM client crash that can occur when opening the right-click context menu on a creature. This crash will not occur when running the Client Extension with the DM client (NWLauncher.exe -dmc).
- Fixed a problem where the game would infrequently not be started by NWLauncher.exe properly.
Receiving an error apparently from NWLauncher (Win7-64, standard user account with Admin escalation, Steam NWN2:PE), after NWN2 starts, popup box titled 'Failed to load client extension' with main text 'Couldn't open real process'.
Have tried with versions 1.0.0.19 through 1.0.0.21, no change. Have not tried the manual loading method (as I'd REALLY rather not add another context menu option to my shell, if it can be avoided).
Posted by Galeocerdo at 2012-08-06 16:39:13 Voted 9.75 on 08/06/12
Outstanding. Thanks for truly remarkable contribution.
Two minor issues (Windows XP, using NWLauncher.exe):
Crash on closing NWN2 (with send error report message box).
Strange character movement when running extension within PW Realms of Trinity. The only time I see this odd jerky character movement.
Posted by Curmudgeon at 2012-06-09 15:21:12 Voted 10.00 on 01/03/13
- Master server timeout at connection time reduced to one second (down from 30
seconds). This prevents the client from getting stuck for 30 seconds while
waiting to communicate with the now-down master server.
- Creatures that are marked as dead should now stop pathing immediately on the
DM's view of the Area Map window. Previously, they were displayed as
continuing to complete their old pathing orders.
- New GUI functionality for scripts: Open chat input pane with prepended text.
This is an asynchronous request to change the GUI state on the client. To
use this functionality, use the following script snippet:
This will open the chat input pane (if it was not already open), and replace
its contents with TextStringToPrepend, positioning the input caret after the
prepended string.
- New GUI functionality for scripts: Set targetted object. This is an
asynchronous request to change the client's target pane target. To use this
functionality, use the following script snippet:
This will cause the client to act as though the player had selected
ObjectToTarget. Once the client processes the request, ObjectToTarget will
show as the targetted object on the server, as well.
Posted by Dedic8ed at 2011-09-03 20:26:39 Voted 10.00 on 09/03/11
Can't believe I hadn't posted a vote on this yet. Very nice feature to have as a player; as a DM, I wouldn't want to even log on without this fantastic tool. Been using it for almost a year now, and depend upon many of its features when DMing.
Does this add-on address the WASD spin bug? In other words, in patch 1.23 if you hold down W to move for a while, then release the key, your character spins and faces a random direction. If this will fix the bug, I'll gladly reinstall NWN2. If it doesn't, I'd rather not waste a couple of hours digging through my old games and reinstalling the game.
Error occurred at 6/13/2011 18:11:24.
C:\Program Files (x86)\Atari\Neverwinter Nights 2\nwn2main.exe, run by Upstairs.
C:\Program Files (x86)\Atari\Neverwinter Nights 2\nwn2main.exe caused an Access Violation exception in module MSVCR80.dll at 0023:7076569e.
Read from location 00000001 caused an access violation.
System Info:
4 processor(s), type 586.
1 % Memory Load.
0 MBytes physical memory.
2039 MBytes available memory.
0 MBytes total virtual memory.
3164 MBytes available virtual memory
0 MBytes total page file.
0 MBytes available page file
Light, can you post a link to your nwn2_errorlog.txt file *right after the crash occurs*? The file is overwritten on each crash so be sure to do this immediately after a repro.
You can find the error log file in the game install directory, i.e. under Program Files. On Vista/Win7, you may need to click "Show compatibility files" in the Explorer to see the nwn2_errorlog.txt file.
The error log should help us identify what was going on so that it can be fixed.
I seem to have stumbled across a crash issue that occurs with 1.20 for me. On certain servers such as Forgotten Realms Dalelands or Sigil City of Doors there are bashable doors. With 1.20 I almost always crash when I bash a door. I have no overrides set and in fact I discovered by not using the extension the problem just went away. I also discovered that 1.19 does not cause the crash. Over on Dalelands if I were to bash a mineable ore vein with 1.20 running from the shortcut in the folder, it would simply crash before I even saw it get the first hit in. I switched to 1.19 and finally got in to discover I can bash away to my heart's content.
Unfortunately due to these being servers it is impossible to run debug mode without being a dm so I don't know how to derive more info from the crash issue. I can however confirm at least on my end that it is the client extension 1.20 consistently causing it since it ceases once I switch to 1.19 or simply cease using the extension and starts right back up when I go back to using 1.20. I really like 1.20 which is why I was banging my head against the table when all the evidence kept pointing back to it being the culprit. It could be something on the combat logging side of it. Maybe... unless something else was fixed. The other odd thing is another player that plays on one of the two servers I mentioned claims to not be experiencing this crash issue with 1.20. I don't know if its an issue with ati versus nvidia cards or what now. Hopefully someone else can at least confirm this issue with their own experiences. Its just weird.
I had an issue in the OC after leaving the bonegnasher lair. The game is supposed to take you to the area where you meet casavir, but when I clicked OK on the "You've encountered something on the way to your destination" window, nothing happened. I then tried using the console to jump there but I got the error "Area 1312_swdmtncasav is not a valid area". I restarted the game a few times but the same thing happened until I launched it without the client extension, then it worked fine.
Posted by Curmudgeon at 2011-04-15 15:01:13 Voted 10.00 on 01/03/13
10 - A Masterpiece, Genuinely Groundbreaking 9 - Outstanding, a Must Have 8 - Excellent, Recommended to Anyone 7 - Very Good, Deserves a Look 6 - Good, Qualified Recommendation 5 - Fair, Solid yet Unremarkable 4 - Some Merit, Requires Improvements 3 - Poor Execution, Potential Unrealized 2 - Very Little Appeal 1 - Not Recommended to Anyone
Site
at 2013-04-06 14:59:42
