Dialog Tutorial - Revision history

Fullwall at 15:27, 14 February 2013

2013-02-14T15:27:47Z

← Older revision		Revision as of 15:27, 14 February 2013
Line 21:		Line 21:
	Here's an example rule; it doesn't too much at all.		Here's an example rule; it doesn't too much at all.
	rule example {		rule example {
	criteria events="any";		criteria events=any;
	}		}

Line 30:		Line 30:
	Notice the semicolon (';') after the criteria statement - every line within a rule should end with one of these.		Notice the semicolon (';') after the criteria statement - every line within a rule should end with one of these.
	You can also have multiple events, separated by commas:		You can also have multiple events, separated by commas:
	criteria events="onchat", "ondamage";		criteria events=onchat, ondamage;

	Before we move onto more advanced examples of criteria, let's review the different types of values in dialogs. Notice that "any" was in quotes - this means that the value should be treated as a block of text.		Before we move onto more advanced examples of criteria, let's review the different types of values in dialogs. Notice that "any" was in quotes - this means that the value should be treated as a block of text.
Line 65:		Line 65:
	Copy and paste the text below into a new file, 'Hello.txt' inside the plugins/Adventures/dialog folder.		Copy and paste the text below into a new file, 'Hello.txt' inside the plugins/Adventures/dialog folder.
	rule saidHi {		rule saidHi {
	criteria events="onchat" $message="Hi!";		criteria events=onchat $message="Hi!";
	response sayHi;		response sayHi;
	}		}

Fullwall: /* Writing a full Dialog */

2013-02-14T15:24:06Z

Writing a full Dialog

← Older revision		Revision as of 15:24, 14 February 2013
Line 65:		Line 65:
	Copy and paste the text below into a new file, 'Hello.txt' inside the plugins/Adventures/dialog folder.		Copy and paste the text below into a new file, 'Hello.txt' inside the plugins/Adventures/dialog folder.
	rule saidHi {		rule saidHi {
	criteria events=onchat $message="Hi!";		criteria events="onchat" $message="Hi!";
	response sayHi;		response sayHi;
	}		}

Fullwall: /* Writing a full Dialog */

2013-02-06T06:44:50Z

Writing a full Dialog

← Older revision		Revision as of 06:44, 6 February 2013
Line 69:		Line 69:
	}		}
	response sayHi {		response sayHi {
	say message="Hello, ${sender.name}!" target=$sender;		say message:"Hello, ${sender.name}!", target:$sender;
	}		}

Fullwall: /* Writing a full Dialog */

2013-02-06T06:28:10Z

Writing a full Dialog

← Older revision		Revision as of 06:28, 6 February 2013
Line 69:		Line 69:
	}		}
	response sayHi {		response sayHi {
	say message="Hello, ${sender.name}!" target=sender;		say message="Hello, ${sender.name}!" target=$sender;
	}		}

Fullwall: /* Writing a full Dialog */

2013-02-04T02:19:22Z

Writing a full Dialog

← Older revision		Revision as of 02:19, 4 February 2013
Line 65:		Line 65:
	Copy and paste the text below into a new file, 'Hello.txt' inside the plugins/Adventures/dialog folder.		Copy and paste the text below into a new file, 'Hello.txt' inside the plugins/Adventures/dialog folder.
	rule saidHi {		rule saidHi {
	criteria events=onchat message="Hi!";		criteria events=onchat $message="Hi!";
	response sayHi;		response sayHi;
	}		}

Fullwall: /* Writing a Rule */

2013-02-04T02:19:01Z

Writing a Rule

← Older revision		Revision as of 02:19, 4 February 2013
Line 32:		Line 32:
	criteria events="onchat", "ondamage";		criteria events="onchat", "ondamage";

	Before we move onto more advanced examples of criteria, let's review the different types of values in dialogs. Notice that "any" was in quotes - this means that the value should be treated as a block of text~~. Text without quotes gets the value from the query facts~~.		Before we move onto more advanced examples of criteria, let's review the different types of values in dialogs. Notice that "any" was in quotes - this means that the value should be treated as a block of text.
	100 - a number		100 - a number
	"100" - text containing the characters 100		"100" - text containing the characters 100
	"text" - text		"text" - text
	true/false - yes or no value		true/false - yes or no value
	sender.location.x - value is taken from the query fact "sender.location.x"		$sender.location.x - value is taken from the query fact "sender.location.x"
	"${sender.name}" - value is text containing the fact under sender.name		"${sender.name}" - value is text containing the fact under sender.name

	Now, criteria that just match the events are pretty pointless. You can also check facts from the query. Let's say that we only want to match the rule when the NPC is standing at x=100.		Now, criteria that just match the events are pretty pointless. You can also check facts from the query. Let's say that we only want to match the rule when the NPC is standing at x=100.
	criteria events="any" npc.location.x=100;		criteria events="any" $npc.location.x=100;
	What about when y is below 50?		What about when y is below 50?
	criteria events="any" npc.location.x=100, npc.location.y<50;		criteria events="any" $npc.location.x=100, $npc.location.y<50;
	What about matching a chat rule that starts with h? (note: this uses regex)		What about matching a chat rule that starts with h? (note: this uses regex)
	criteria events="onchat" message~=/h[a-zA-Z]+/		criteria events="onchat" $message~=/h[a-zA-Z]+/

	==Writing a Response==		==Writing a Response==

Fullwall at 11:00, 30 January 2013

2013-01-30T11:00:26Z

← Older revision		Revision as of 11:00, 30 January 2013
Line 17:		Line 17:

	==Writing a Rule==		==Writing a Rule==
	Let's get onto the syntax. Before continuing, make sure you have Adventures downloaded and installed. Any NPC using the dialog system will need to have the dialog trait, so use /~~npc~~ trait dialog before trying out any of these examples.		Let's get onto the syntax. Before continuing, make sure you have Adventures downloaded and installed. Any NPC using the dialog system will need to have the dialog trait, so use /trait dialog before trying out any of these examples.

	Here's an example rule; it doesn't too much at all.		Here's an example rule; it doesn't too much at all.

Fullwall: /* Writing a full Dialog */

2013-01-30T10:34:47Z

Writing a full Dialog

← Older revision		Revision as of 10:34, 30 January 2013
Line 69:		Line 69:
	}		}
	response sayHi {		response sayHi {
	say message="Hello, ${~~player~~.name}!" target=~~player~~;		say message="Hello, ${sender.name}!" target=sender;
	}		}

Fullwall at 10:34, 30 January 2013

2013-01-30T10:34:17Z

@@ Line 38: / Line 38: @@
   true/false - yes or no value
   sender.location.x - value is taken from the query fact "sender.location.x"
 Now, criteria that just match the events are pretty pointless. You can also check facts from the query. Let's say that we only want to match the rule when the NPC is standing at x=100.
@@ Line 45: / Line 46: @@
 What about matching a chat rule that starts with h? (note: this uses regex)
   criteria events="onchat" message~=/h[a-zA-Z]+/
 ==Writing a full Dialog==

Fullwall: /* Writing a Rule */

2013-01-30T10:15:52Z

Writing a Rule

@@ Line 29: / Line 29: @@
                   ^ matches any kind of event, as a demonstration
 Notice the semicolon (';') after the criteria statement - every line within a rule should end with one of these.
 ==Writing a full Dialog==