Zugg Software :: View topic - Having problems capturing first line that comes right after prompt

Apprentice Joined: 19 Nov 2010 Posts: 119

Hi guys, I had this problem for an eternity now and have usually resorted to workarounds, but today i need to force the issue and I hope someone can help me out as the problem seems to be pretty basic at it's core.

The problem: Capturing the first line that comes right after prompt, will capture part of prompt
------------------------------------------
Trigger code:
<trigger priority="99" case="true" trigontrig="false" prompt="true" id="1349">
<pattern>(%w*) hates your guts!</pattern>
<value>#var monster %1
#print @monster set
</value>
</trigger>

And here is the result:

<901hp 924ma 361mv>A goblin hates your guts!
hp 924ma 361mv>A goblin set
You hit a goblin extremely hard.
------------------------------------------
Checking and unchecking Trigger on Trigger does nothing
And with Trigger on Prompt disabled, the trigger will not capture anything at all.
If I force the start of the line and use <pattern>^(%w*) hates your guts!</pattern> then my script will not capture anything at all with Trigger on Prompt and without it.

------------------------------------------
<trigger priority="99" case="true" trigontrig="false" prompt="true" id="1349">
<pattern>^(%w*) hates your guts!</pattern>
<value>#var monster %1
#print @monster set
</value>
</trigger>

Result:
<901hp 924ma 360mv>A kobold youth hates your guts!
You hit a kobold youth extremely hard.
------------------------------------------

I could make a <@prompt>@pattern trigger, but my mud also sends these same lines without prompt sometimes, so this would mean that I would have duplicate my triggers, one with <@prompt> and then add the same trigger without prompt, which is not acceptable.

I have tried setting my prompt in Prefs and i have tried checking and unchecking Use GA/EOR for Prompt in Perfs with no changes.

THanks

Apprentice Joined: 19 Nov 2010 Posts: 119

Here is raw data from debugger without script code.

12:56:12.982p | 901hp 927ma 361mv>
12:56:18.177p | say bla<CR><LF>
12:56:18.177p | kill kobold<CR><LF>
12:56:18.692p | You say 'bla'<ESC>[0m<CR><LF><CR><LF>
12:56:12.982p | <901hp 927ma 361mv>
12:56:18.177p | kill kobold<CR><LF>
12:56:18.692p | <901hp 927ma 361mv>
12:56:19.082p | A female kobold hates your guts!<CR><LF>
12:56:19.082p | You hit a female kobold extremely hard.<ESC>[0m<CR><LF><CR><LF>
12:56:19.082p | <901hp 927ma 361mv><IAC><SB><69><1>OPPONENT_HEALTH<2>60<IAC><SE><IAC><SB><69><1>OPPONENT_LEVEL<2>5<IAC><SE><IAC><SB><69><1>OPPONENT_NAME<2>female kobold<IAC><SE>
12:56:21.188p | You hit a female kobold extremely hard.<CR><LF>
12:56:21.188p | A female kobold misses you with her hit.<CR><LF>
12:56:21.188p | You hit a female kobold very hard.<CR><LF>
12:56:21.188p | A female kobold is stunned, but will probably regain consciousness again.<ESC>[0m<CR><LF><CR><LF>
12:56:21.188p | <901hp 927ma 361mv>
12:56:21.578p | <IAC><SB><69><1>OPPONENT_HEALTH<2>-3<IAC><SE>
12:56:25.681p | You massacre a female kobold to small fragments with your hit.<CR><LF>
12:56:25.681p | A female kobold is dead! R.I.P.<CR><LF>
12:56:25.681p | You gain 275 bonus experience!<CR><LF>
12:56:25.681p | Total exp for kill is 1179.<CR><LF>
12:56:25.681p | Your blood freezes as you hear a female kobold's death cry.<ESC>[0m<CR><LF><CR><LF>

Now here is that same log i see when it is shown mud window

<901hp 927ma 361mv>say bla
kill kobold
You say 'bla'
<901hp 927ma 361mv>A female kobold hates your guts!
hp 927ma 361mv>A female kobold set
You hit a female kobold extremely hard.

<901hp 927ma 361mv>You hit a female kobold extremely hard.
A female kobold misses you with her hit.
You hit a female kobold very hard.
A female kobold is stunned, but will probably regain consciousness again.

<901hp 927ma 361mv>You massacre a female kobold to small fragments with your hit.
BONUS XP: 275
Total XP: 1,179
Your blood freezes as you hear a female kobold's death cry.

Apprentice Joined: 03 Jul 2006 Posts: 110

get rid of the asterisk in your trigger. just (%w) will capture the single word (e.g. "goblin") which should be enough for the system. The asterisk is making the trigger capture EVERYTHING prior to the targeted phrase.

Mike

ETA: If you need to capture the description as well, such as "female kobold" in your example, you could include the A in your trigger pattern before an asterisk, such as "A (*) hates your guts!"

Posted: Wed Nov 18, 2015 2:18 pm

The issue is with the prompt itself, i would just suppress it:

Apprentice Joined: 19 Nov 2010 Posts: 119

Apprentice Joined: 19 Nov 2010 Posts: 119

Alright, so as long as there are no obvious solutions and it's the mud itself that's at fault (supposedly), i've decided to incorporate yet another 2 step workaround:

<trigger priority="99" case="true" prompt="true" id="1349">
<pattern>(*) hates your guts!</pattern>
<value>#T+ promptcheck
#var monster %1
#print @monster set
</value>
</trigger>

<trigger name="promptcheck" priority="3736400" enabled="false" id="373640">
<pattern><(%d)hp (%d)ma (%d)mv></pattern>
<value>#var promptcheck {"<"%1hp %2ma %3mv">"}
#var monster %replace(@monster,@promptcheck,"")
#T- promptcheck</value>
</trigger>

If anyone has a more elegant solution or has other thoughts on why this problem is occuring and how to fix it without any workarounds, please let me know and thanks everyone for their help.

Posted: Wed Nov 18, 2015 6:23 pm

Thats an issue of priority, give the new trigger that you made with my code a lower number, so it fires before the old one you made.
That setting is located at the bottom of the trigger in the settings editor, in the 'more' panel.

Sorcerer Joined: 15 Apr 2011 Posts: 809

You could try this regex pattern (make sure the regular expression box is ticked): ([^>]+) hates your guts!

This will match any character except ">", so it won't catch the prompt. Of course, this is assuming there are no mobs that have a literal > sign in their name.

Apprentice Joined: 19 Nov 2010 Posts: 119

Posted: Thu Nov 19, 2015 9:48 pm

I have not been noticing any posting issues like that, no...

As for the script section of the trigger, %1 is fine to use, it should never appear in the pattern, regex or not

Apprentice Joined: 19 Nov 2010 Posts: 119

Posted: Fri Nov 20, 2015 12:43 am

the output of the #PRINT command is not processed by triggers
so long as you include a %crlf at the end of the #SUB string, it should work
I typically use button gauges to display the data that is delivered in the prompt.

As for Daern's code... it looks to be anchored at the line start with only an '>' for the prompt, expand the prompt appropriately?
I'm not good with raw regex.

Sorcerer Joined: 15 Apr 2011 Posts: 809

It's not anchored to the start of the line, in this case the ^ is being used as a negation operator since it's within []. It looks like the problem is actually that there's a space at the end.

Posted: Fri Nov 20, 2015 7:24 am

Ahhh yes, i forgot about the negative ranges.