Triggers - Revision history

Jeremy: /* Step 3: Triggers Options. */

2016-09-15T18:11:56Z

Step 3: Triggers Options.

← Older revision		Revision as of 18:11, 15 September 2016
Line 35:		Line 35:
	There are two main option sections for triggers; '''Matching''' and '''Actions'''.		There are two main option sections for triggers; '''Matching''' and '''Actions'''.

	'''Enabled'' This checkbox marks if the trigger is currently being used by the system. If unchecked, this trigger will not be used.		'''Enabled''' This checkbox marks if the trigger is currently being used by the system. If unchecked, this trigger will not be used.

	'''Matching''' is used to find the text you would like to use for this trigger. When the game sends text to your character that matches, it will automatically send the action defined below it.		'''Matching''' is used to find the text you would like to use for this trigger. When the game sends text to your character that matches, it will automatically send the action defined below it.

Jeremy: /* Step 3: Triggers Options. */

2016-09-15T18:09:08Z

Step 3: Triggers Options.

← Older revision		Revision as of 18:09, 15 September 2016
Line 34:		Line 34:

	There are two main option sections for triggers; '''Matching''' and '''Actions'''.		There are two main option sections for triggers; '''Matching''' and '''Actions'''.

			'''Enabled'' This checkbox marks if the trigger is currently being used by the system. If unchecked, this trigger will not be used.

	'''Matching''' is used to find the text you would like to use for this trigger. When the game sends text to your character that matches, it will automatically send the action defined below it.		'''Matching''' is used to find the text you would like to use for this trigger. When the game sends text to your character that matches, it will automatically send the action defined below it.

Jeremy: /* Trigger Text */

2016-02-19T17:21:40Z

Trigger Text

← Older revision		Revision as of 17:21, 19 February 2016
Line 61:		Line 61:
	This works hand in hand with the '''Matching Type''' option. See below.		This works hand in hand with the '''Matching Type''' option. See below.

	There are times when you'll want to use wildcard matches in your triggers. ~~Say~~ you want to ~~make an alert when~~ someone ~~enters~~ the room, you can ~~surround a word~~ in <>'s to assign it to a variable. If an example line is ''Jeremy enters from the north'', you could configure your trigger to match on ''<person> enters from the <direction>''. As an added bonus, you can then use @person and @direction as variables in the trigger actions.		==== Wildcards in Trigger Text ====

			This is a very powerful feature in the Nexus client that you will want to understand.

			There are times when you'll want to use wildcard matches in your triggers. Most messages you will want to trigger will vary slightly. Character names, item number, and more.

			For example, let's say someone is entering the room you are in.

			You can the name in <>'s to allow the trigger to fire. You can also assign the name to a variable. If an example line is ''Jeremy enters from the north'', you could configure your trigger to match on ''<person> enters from the <direction>''. As an added bonus, you can then use @person and @direction as variables in the trigger actions.

	These simplified triggers do not work with regular expressions, and if using this advanced feature, you'll want to ensure that you're using the correct syntax.		These simplified triggers do not work with regular expressions, and if using this advanced feature, you'll want to ensure that you're using the correct syntax.

			[[WildcardMatching\|Here is a full example of a basic wildcard match.]]

	=== Matching Type ===		=== Matching Type ===

Justin at 05:23, 19 February 2016

2016-02-19T05:23:19Z

← Older revision		Revision as of 05:23, 19 February 2016
Line 62:		Line 62:

	There are times when you'll want to use wildcard matches in your triggers. Say you want to make an alert when someone enters the room, you can surround a word in <>'s to assign it to a variable. If an example line is ''Jeremy enters from the north'', you could configure your trigger to match on ''<person> enters from the <direction>''. As an added bonus, you can then use @person and @direction as variables in the trigger actions.		There are times when you'll want to use wildcard matches in your triggers. Say you want to make an alert when someone enters the room, you can surround a word in <>'s to assign it to a variable. If an example line is ''Jeremy enters from the north'', you could configure your trigger to match on ''<person> enters from the <direction>''. As an added bonus, you can then use @person and @direction as variables in the trigger actions.

			These simplified triggers do not work with regular expressions, and if using this advanced feature, you'll want to ensure that you're using the correct syntax.

	=== Matching Type ===		=== Matching Type ===

Justin at 05:22, 19 February 2016

2016-02-19T05:22:00Z

← Older revision		Revision as of 05:22, 19 February 2016
Line 61:		Line 61:
	This works hand in hand with the '''Matching Type''' option. See below.		This works hand in hand with the '''Matching Type''' option. See below.

	There are times when you'll want to use wildcard matches in your triggers. Say you want to make an alert when someone enters the room, you can surround a word in <>'s to assign it to a variable. If an example line is ''Jeremy enters from the north'', you ~~would enter~~ ''<person> enters from the <direction>'' ~~as your trigger text~~. As an added bonus, you can then use @person and @direction as variables in the trigger.		There are times when you'll want to use wildcard matches in your triggers. Say you want to make an alert when someone enters the room, you can surround a word in <>'s to assign it to a variable. If an example line is ''Jeremy enters from the north'', you could configure your trigger to match on ''<person> enters from the <direction>''. As an added bonus, you can then use @person and @direction as variables in the trigger actions.

	=== Matching Type ===		=== Matching Type ===

Justin at 05:20, 19 February 2016

2016-02-19T05:20:49Z

← Older revision		Revision as of 05:20, 19 February 2016
Line 61:		Line 61:
	This works hand in hand with the '''Matching Type''' option. See below.		This works hand in hand with the '''Matching Type''' option. See below.

	~~You can match text that may not always be~~ the ~~same using regular expressions. For example~~, you ~~may want~~ to ~~match~~ ''Jeremy enters from the north''~~. However~~, the ~~name or the~~ direction ~~may not always going to be the same~~. ~~This is more complicated and~~ you can ~~review the examples at the bottom of~~ the ~~page for more information~~.		There are times when you'll want to use wildcard matches in your triggers. Say you want to make an alert when someone enters the room, you can surround a word in <>'s to assign it to a variable. If an example line is ''Jeremy enters from the north'', you would enter ''<person> enters from the <direction>'' as your trigger text. As an added bonus, you can then use @person and @direction as variables in the trigger.

	=== Matching Type ===		=== Matching Type ===

Jeremy: /* Examples */

2016-02-17T18:03:02Z

Examples

← Older revision		Revision as of 18:03, 17 February 2016
Line 117:		Line 117:

	== Examples ==		== Examples ==
	* [[~~Balance Recovery Attack~~]]~~: This is an example of a trigger to automatically attack a target when you recover balance~~.		You can view some example triggers on the [[examples]] page.


	== Regular Expression Help ==		== Regular Expression Help ==
	* http://www.regular-expressions.info/		* http://www.regular-expressions.info/

Jeremy: /* Simplified Scripting */

2016-02-08T07:13:43Z

Simplified Scripting

← Older revision		Revision as of 07:13, 8 February 2016
Line 108:		Line 108:
	=== Simplified Scripting ===		=== Simplified Scripting ===

	The Nexus client allows for fifteen different [[SimplifiedScripting\|simplified scripting]] actions. In most cases instantly returning a command is the best option. However, the ~~next~~ client will allow you to loop through commands, use if statements, wait commands, highlight text, and much more.		The Nexus client allows for fifteen different [[SimplifiedScripting\|simplified scripting]] actions. In most cases instantly returning a command is the best option. However, the Nexus client will allow you to loop through commands, use if statements, wait commands, highlight text, and much more.

	All of these options, with full explanations and examples can be found here: [[SimplifiedScripting\|simplified scripting]].		All of these options, with full explanations and examples can be found here: [[SimplifiedScripting\|simplified scripting]].

Jeremy: /* Case Sensitive */

2016-02-08T07:04:45Z

Case Sensitive

← Older revision		Revision as of 07:04, 8 February 2016
Line 86:		Line 86:
	In almost all cases you will just want to keep 'Whole words only' turned on and be sure to include the full trigger text. Remember that whole words are separated by spaces and punctuation is considered part of a word.		In almost all cases you will just want to keep 'Whole words only' turned on and be sure to include the full trigger text. Remember that whole words are separated by spaces and punctuation is considered part of a word.

	=== Case ~~Sensitive~~ ===		=== Match Case ===

	If checked, capitalization must match.		If checked, capitalization must match.

Jeremy at 07:03, 8 February 2016

2016-02-08T07:03:18Z

← Older revision		Revision as of 07:03, 8 February 2016
Line 31:		Line 31:
	[[File:Trigger-create.png\|frame\|center\|Example of creating a new trigger.]]		[[File:Trigger-create.png\|frame\|center\|Example of creating a new trigger.]]

	=== Step 3: Triggers Options ===		=== Step 3: Triggers Options. ===

	There are two main option sections for triggers; '''Matching''' and '''Actions'''.		There are two main option sections for triggers; '''Matching''' and '''Actions'''.