Having bad bad prompt behaviour...

Hi.
I'm having really weird prompt issues..

I'm a visually impaired mudder and I use the prompt to grab all kinds of information from the mud. Some people say my promtps look weird, but since I make them omit... it doesn't matter to me and people who use my scripts. anyways.. I'm having really strange issues. When I go to a certain area at first, the prompt triggers fine. Then I fight and kill a mob, and prompt trigger does not match anymore until I go to another area.

The thing is though that it matches the first time, when I enter the area before I fight. I'd be grateful if anyone here can give me any clue... I've been trying to figure this out for a while now.

The prompt that worked looked like this:
area: The fiery, unforgiving Demonic Realmgold: 30585mana: 199max 522cond: excellenthit: 294max 567terrain: wastelandmv: 294max: 294dt: xp: 5221461

the prompt that did not work
area: The fiery, unforgiving Demonic Realmgold: 30585mana: 477max 522cond: excellenthit: 567max 567terrain: wastelandmv: 294max: 294dt: xp: 5241721

matching trig
<trigger
enabled="y"
keep_evaluating="y"
match="^area: (.*?)gold: (\w+)mana: (\w+)max (\w+)cond: (.*?)hit: (\w+)max (\w+)terrain: (.*?)mv\: (\w+)max\: (\w+)dt: (.*?)xp: (.*)$"
omit_from_log="y"
omit_from_output="y"
regexp="y"
script="dprompt"
sequence="100"
>
</trigger>

The prompts look the same to me, except for the numbers.

Can you copy and paste some actual MUD output? Is it possible that there is something extra at the end during a battle? Or at the start?

Or maybe some other trigger is matching first? Or something disables your trigger?

Try turning on Game menu -> Trace. That might give a clue about other triggers firing, perhaps.

The thing is that it only happends in this area. I'm going to do some thorough testing later.

Try playing with the 'Convert IAC EOR/GA to newline' option. Without that you will have trouble matching prompts in some games.

I seem to recall a similar post a while back. In your case, for example, if the word "Demonic" happened to appear in this area name, and another trigger matched "Demonic", and that other trigger was not set to "keep evaluating", and it fired first, then it would stop your prompt trigger from firing. Like I say, using the Trace feature will probably narrow it down.