NPC Variables: Difference between revisions
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
For both [[Behavior Operations]] and [[Tribe Scripting]] some of the fields are parsed for keywords and values replaced before use. | |||
== Substituted Keyword == | == Substituted Keyword == | ||
Line 45: | Line 48: | ||
|- | |- | ||
|} | |} | ||
[[Category:NPCClient Design]] |
Revision as of 10:57, 24 December 2011
For both Behavior Operations and Tribe Scripting some of the fields are parsed for keywords and values replaced before use.
Substituted Keyword
The following keywords are replaced in strings used in the NPC Client Scripting.
This allows for generic scripting like:
<talk text="My name is $name" /> <wait duration="$NBUFFER[Wait_Duration]" anim="stand" />
Before keywords is replaced the NPC and Tribe buffers will be replaced. This allows keywords in the buffers.
Keyword | Description |
---|---|
$NBUFFER[x] | Replace with the value from the NPC buffers |
$TBUFFER[x] | Replace with the value from the Tribe buffers |
Keywords that will be replaced.
Keyword | Description |
---|---|
$name | Replaced with the name of the NPC. |
$owner | If npc is a pet, replaced with the name of the owner |
$member_type | Replace with the npc tribe member type. |
$race | Replaced with the race of the NPC. |
$target | Replaced with the name of the current target. |
$tribe | If npc is part of a tribe, replaced with the tribes name. |