Neverwinter Nights 2 Known Issues
Please select an issue:
1.01: Exported Characters in Original Campaign
1.02: No Unarmed Weapon Masters
1.03: No Sneaky Touch Attacks
1.04: In-Game Keybinding for Quickbar, Mouse, and Right Arrow Key
1.05: Debug Console
1.06: Go to Definition… in Context Menu of Script Editor in Toolset
1.07: Placed Effects, differences between Toolset and Game Client:
1.08: Toolset and Dual Monitors
1.01: Exported Characters in Original Campaign (Back to top)
The Export Characters option in the Escape Menu can be used to create a copy of your current character. However, using an exported character in the single player campaign is not supported or recommended as it may cause problems with quest logic.
1.02: No Unarmed Weapon Masters (Back to top)
Characters cannot use the "Weapon Focus (unarmed)" feat to qualify for the Weapon Master class.
1.03: No Sneaky Touch Attacks (Back to top)
Characters cannot make sneak attacks with Touch or Ranged Touch Attacks.
1.04: In-Game Keybinding for Quickbar, Mouse, and Right Arrow Key (Back to top)
Keybindings for the Quickbar and Mouse buttons are not available.
1.05: Debug Console (Back to top)
The tilde (~) key will bring down the debug console, which is primarily intended to be used by builders in developing their content. Using the debug console commands in the Neverwinter Nights 2 Original campaign is unsupported and can cause serious gameplay issues.
1.06: Go to Definition… in Context Menu of Script Editor in Toolset (Back to top)
For performance reasons, the “Go To Definition...” option in the context menu in the Toolset Script Editor will only look within files #included in the current script, and not deeper.
1.07: Placed Effects, differences between Toolset and Game Client: (Back to top)
Certain placed effects may not draw in the toolset - however, these will still be displayed properly in-game.
Some placed objects look differently in the toolset than they do in the game.
1.08: Toolset and Dual Monitors (Back to top)
When using a dual monitor configuration, the toolset will run more slowly when part or all of a rendering window is displayed on the secondary monitor. This is caused by how certain video cards work with DirectX and is not directly because of the toolset.