Named Trigger

This trigger can be used only via the #CALL executor. You can call a Named Trigger inside of a Named Trigger too, but don't ever call a named trigger inside of itself if you don't know what you are doing. It could cause an infinite loop.

Or, alternatively, you may use /trg call <NamedTrigger name> to execute it as if it was called in a random CommandTrigger through #CALL

There are no commands to create a named trigger. Instead, just create an empty file and start coding from there. Make sure your file has the .trg extension. If you want a named trigger called foo, the file should be named foo.trg

Using Named Trigger

Unlike other triggers, named triggers can only be called from other triggers.

To do so, use #CALL executor in the other triggers.

For example, in your Command Trigger:

#CALL "Trigger1"

This will activate Trigger1. But if you have more than one line of code, it might be confusing.

For example:

#MESSAGE "HEY"
#CALL "Trigger1"
#MESSAGE "Done!"

In this scenario, here is how the execution will go:

First, the #MESSAGE executor will print HEY to the user.

Second, the current trigger will hand execution control over to the named Trigger (Trigger1 in our example), and the named Trigger will begin working. While the named Trigger is working, the current Trigger will wait for the named Trigger to end.

Third, when the execution of named Trigger is done, it will hand the execution control back to the current Trigger, and now the current Trigger can continue. In our example, Done! will be printed.

Variable sharing

By default, Named Triggers share local variables with the current Triggers. So any local variable in the current Trigger can be used in the Named Trigger, and any local variable created from a Named Trigger can be used in the current Trigger too.

Concurrency

If you want the Named Trigger to run concurrently, you may add an additional parameter to the #CALL executor. For example:

#CALL "MyTrigger1" false

This code will spawn a new task that will be running concurrently beside the Trigger that just started the MyTrigger1.

But in this case, the variables will be 'copied' to the Named Trigger, and will not be shared with the current Trigger.

Grouping Named Trigger

If your project gets larger, it's always a good idea to put groups of named triggers in folders to avoid naming collision. All you have to do is create a sub folder inside of the main named triggers folder and move your named triggers inside. Named Triggers inside of folders will not collide with named triggers in the main folder or inside of other folders even if they have identical names.

Don't forget to run /trg reload after creating new folders or files!

Calling trigger that is in a folder

Very simple. You just have to specify the path of Trigger using ':'

For example, if you have your Trigger5 in folder named MyTriggers, then call it with the following code:

#CALL "MyTriggers:Trigger5"