Feature Request - Regarding Stop Watch Timer

[Settun]

Okay currently I have a Stop Watch timer (Count Up),
It's set up to search for:
{S1}, 'Hail, {S2}'s corpse'

This starts a Stop Watch Timer, If one is currently running Do nothing
{S2} Needs Rez

Now for the tricky part:
Is it possible to get a report of when the Stop Watch timer is ended normally? Through the phrase: {Currently this is entered in the End Early section}
raid, '::: Rez Attempt - {S2} :::'

This timer also has 2 other end early conditions:
tel{S4}command:{N}, '*!* STOP TIMER *!*'
tel{S4}command:{N}{S3}(Wipe|AETL|AE TL|Get out)

These last 2 allow someone able to communicate in our guild's moderated command chat channel to end all the timers, and in the event of a Wipe call all timers are terminated.
Sadly the above 2 End early expressions aren't evaluated/processed as I'd hoped they would be. Maybe someone can see where I went wrong with them?

This works when that person's corpse is attempted a resurrection, it's related timer is cleared off the screen, but there seems to be no report of how long it took for the attempted resurrection. It'd be nice if we can see the length of time from Hail to Attempt res.

Thanks much,
Settun

[HSishi]

AFAIK it's because RegEx is not useable in "End Early" field.

//Hsishi

[Gimagukk]

In 1.0.17.32 (currently in beta), End Early text now supports regular expressions and preserved variables (i.e., you can use {S2} in the end early text if you used {S2} in the original trigger text).

[HSishi]

Beta? o_O ... do you need some testers?

//HSishi

[Gimagukk]

Sure -- you can find the Beta download link here under the Downloads menu on the left. I usually like to use the release candidate for a couple weeks before I release it. Make sure you back up your config file before installing in case something goes wrong.

[HSishi]

I wasn't able to DL the Beta. The setup client itself goes well, but the installation couldn't find the GINABeta.application file.

[Gimagukk]

Try now. I've signed the executable in addition to the deployment manifest so that technologies like Windows' SmartFilter do not complain. I'm curious to see if that (or a similar technology) was causing your issue.

[HSishi]

At first, it was the problem, but I already put it into "Ask me at least" state. So the Setup.exe was able to run, but then gave a "... can't be downloaded" error.

As the problem still exists, I'll open a new thread for it.