Show Posts
1
Freelance Ramblings / Why can't i test my triggers?
« on: April 12, 2025, 03:53:03 AM »
As you may have noticed, some triggers have special characters in the search text. These make Gina run more efficiently, but they also make triggers un-testable outside of events.
for example, the run emote to avoid Penance in High Priest mission is
^You need to do penance for your disobedience\.$
The leading ^ means the Search Text has to start at the beginning of line.
With leading ^, this will NOT fire the trigger
[Fri Apr 11 22:05:44 2025] You told Soandso, 'You need to do penance for your disobedience'
Whereas this WILL
[Fri Apr 11 21:16:51 2025] You need to do penance for your disobedience.
Now what about the \.$ and the end of the Search Text?
\ before the ".", means that the "." is NOT to be treated as a special character. It is just a regular period.
$ means there can be nothing further after the search text. If there are additional characters after, then the trigger will fail.
So with the $, this WILL fire the trigger
[Fri Apr 11 21:16:51 2025] You need to do penance for your disobedience.
but this will NOT
[Fri Apr 11 21:16:51 2025] You need to do penance for your disobedience. you knucklehead
If you want to test a trigger in game, via /g or /tell for example, then open the trigger editor window and remove the leading ^ and the trailing \.$
So converting the search text from this
^You need to do penance for your disobedience\.$
to this
You need to do penance for your disobedience
will allow you to test your trigger in /g or /tell or /say. For example you can /tell Bumkus You need to do penance for your disobedience
Once you confirm that triggers work, feel free to add the leading ^ and trailing \.$ back in.
Now, what if a Trigger STILL doesn't work, or worse it displays something that is not in the Trigger you are testing?
You might have 2 different triggers trying to fire off the same search text. This is especially likely for Raids like High Priest and Control Room, since there are missions for these events and the emotes are the same for both. You need to turn one of these off. To see which Trigger fires, look at the Trigger list. If it points to a different trigger, then find that trigger group and make sure the Box is Un-checked.
for example, the run emote to avoid Penance in High Priest mission is
^You need to do penance for your disobedience\.$
The leading ^ means the Search Text has to start at the beginning of line.
With leading ^, this will NOT fire the trigger
[Fri Apr 11 22:05:44 2025] You told Soandso, 'You need to do penance for your disobedience'
Whereas this WILL
[Fri Apr 11 21:16:51 2025] You need to do penance for your disobedience.
Now what about the \.$ and the end of the Search Text?
\ before the ".", means that the "." is NOT to be treated as a special character. It is just a regular period.
$ means there can be nothing further after the search text. If there are additional characters after, then the trigger will fail.
So with the $, this WILL fire the trigger
[Fri Apr 11 21:16:51 2025] You need to do penance for your disobedience.
but this will NOT
[Fri Apr 11 21:16:51 2025] You need to do penance for your disobedience. you knucklehead
If you want to test a trigger in game, via /g or /tell for example, then open the trigger editor window and remove the leading ^ and the trailing \.$
So converting the search text from this
^You need to do penance for your disobedience\.$
to this
You need to do penance for your disobedience
will allow you to test your trigger in /g or /tell or /say. For example you can /tell Bumkus You need to do penance for your disobedience
Once you confirm that triggers work, feel free to add the leading ^ and trailing \.$ back in.
Now, what if a Trigger STILL doesn't work, or worse it displays something that is not in the Trigger you are testing?
You might have 2 different triggers trying to fire off the same search text. This is especially likely for Raids like High Priest and Control Room, since there are missions for these events and the emotes are the same for both. You need to turn one of these off. To see which Trigger fires, look at the Trigger list. If it points to a different trigger, then find that trigger group and make sure the Box is Un-checked.