Page History

This default "unknown PC" portrait appears for PC nodes.

The NPC nodes never seem to have this filled in which is a shame, presumably it was a planned feature which got cut from the toolset. At least it does make it more clear which person is speaking however.

This is only available on NPC nodes, and will let a different NPC (which could technically be a placeable, door, or creature) speak a node of dialogue, useful for multiple NPCs conversing with themselves and the PC. Left blank it defaults to [OWNER] which is the object initiating dialogue.

Note: There is a distance limit to conversations, around 20M or 2 tiles (from the PC), and so checking the NPC is nearby or moving them to be so would help this work correctly.

The dropdown will auto populate with tags of objects in the objects current area, and any speaker tags on other nodes in the given conversation, but if you click Add you can select any blueprint in your module to act as a tag in case you're editing it without the creature being pre-placed in the world.

This basic area can input plain text. The format NWN uses is UTF-8. There are no text formatting options (eg bold, underlined, italics) but you can change the text colour; you can right click anywhere to Insert Token which is detailed below.

You can use a basic undo (Ctrl + Z) here, although it only seems to save one thing - and if you undo something that becomes the thing to undo.

If you want to use TLK strings instead, put a number in this box.

Note while the spellchecker is no longer included in the toolset the colours it uses still get applied; with some interesting cases:

• Normal Text: Usually dark red (can be set in the toolset under Spellcehcking)
• Node with Journal: Purple

So spellchecker being enabled adds a little functionality. When you click a box it goes normal black in any case.

TBH there are probably some bugs there.

This selects a script that starts with int startingConditional() which returns a True or False value. The script is run when evaluating whether or not to show this particular node.

The two main use cases are:

• NPC nodes - only one will be shown, so having a Text Appears When... on each node except the last one allows you to check, for instance, on the top node if the quest has been completed, the second node if the quest has been assigend but not completed and the last node leave blank and be the node for giving out the quest
• PC nodes -  you can have several dozen options boiled own to one or two. Each node will run the script to check it is appearing or not, so don't make them too heavy, but once sorted it will display the nodes where the script returned TRUE

NWN:EE added Script Parameters as well which allows arbitrary text script parameters to be added. A tutorial on this will be put elsewhere since it can get a bit in depth and but save you a lot of time reusing scripts.

This selects a script that is a usual void main() script that does an action when the node is said.

When it is on an NPC node it will instantly fire when that node is loaded and text displayed to the player.

When it is on a PC node it will fire it only if that particular choice is chosen.

These 3 options are time savers and bypass the need to use scripts for doing basic things in the conversation.

Play Animation

This will, for the current node owner (if it's the PC, the PC will do it), play the given animation. One off animations will go back to talking when the NPC starts talking again, and persistent ones can be changed back to talking using Talk Normal (the default one). Default just "keeps the current animation".

Journal

This allows you to select a journal entry and the state it should be set to. The Edit button opens the Journal Editor.

Play Sound

This will play a mono sound effect from the current node owner. This means NPCs can play dialogue files and PCs can play sound effects. If the node is quickly skipped the sound stops playing.

These are options that affect the entire conversation as a whole.

The tickbox for Stop camera zoom in allows you to stop the camera zooming in. Players can disable this themselves game-wide but it helps to disable this in many situations.

The Normal and Aborted script options - which default to the nw_walk_wp file - are the scripts that fire when the conversation ends normally, and when it is aborted.

Aborted states occur when the player unnaturally exits the conversation;

• The PC presses escape to exit the conversation
• The PC enters combat, dies, etc.
• The NPC enters combat, dies, etc.
• The PC moves away or gets moved from the person being talked to (10M - 1 tile - range). In fact the NPC moving can cause this as well.
• The PC disconnects

You can force a PC to stay in a conversation with cutscene mode, which disables escape (which goes instead to the "Cancel Cutscene" script which can also ignore it) and stops movement.

The usage of each script event can differ on the situation:

• If it's a typical friendly NPC conversation, you'd probably leave the default nw_walk_wp in place so they go back to doing ambient animations once the conversation concludes.
• If it's a soon to be boss fight/enemy and any outcome is combat, you'd want both the normal and abort options to start combat
• If it's a creature that might become angry, perhaps when they have their conversation cancelled, just put the attack script in the aborted option