Zugg Software :: View topic

Newbie Joined: 30 Jan 2010 Posts: 6

Greetings. Im trying to set up a trigger to read a muds prompt but am having strange issues. Someone please let me know what i might be overlooking, as I have done pretty well making every other trigger I've wanted.

The mud has an unusually parsed prompt. EG:

hp/mana experience >

I made a prompt to read this, but it only appears to work sometimes. If I press enter to get mud prompts, it wont work at first, but if i gradually hit enter faster, it will always work once the prompts are received at faster than a certain rate, while it will never work if they are received slower. If a prompt is recieved after other lines of text, it will always work because it doesnt seem to be the other prompts being before it that helps, but really any text being sent before necessary to make it work.

In the above example, my trigger would be pattern matching the inside brackets portion: {^(%d)/(%d) (%d) >}
Im completely baffled by this problem if anyone can provide guidance.

Beginner Joined: 25 Apr 2009 Posts: 28

Sounds like you need to check the 'Trigger on Prompt' box instead of new line.

Newbie Joined: 30 Jan 2010 Posts: 6

Enchanter Joined: 11 Feb 2003 Posts: 511 Location: USA

> is a special character, try quoting it in your trigger

{^(%d)/(%d) (%d) ~>}

Posted: Sun Jan 31, 2010 1:55 pm

you dont need to match the whole line... is that space more then one charlength? is there a leading space?

Newbie Joined: 30 Jan 2010 Posts: 6

So in attempt to figure out what im doing wrong, i changed the text on this trigger to {*(%d)/(%d)*} and made it simply #echo a command if it was successful or not, and the problem is still exactly the same. It will never fire if i press enter and get the next line. However, if cmud receives other lines of text first then this prompt, it always works. No matter how basic I make the trigger, it appears unwilling to make the first line work. Ive tried every button combination possible. I know im missing something.

Copy pasted from client- the first one was where i pressed enter, the other lines are where enter was held and auto repeat sent additional ones.

485/485 984 >
485/485 984 > worked
485/485 984 > worked
485/485 984 > worked

If i dont have prompt button clicked and use newline, text output looks like this:

485/485 984 >

485/485 984 >
worked
485/485 984 >
worked
485/485 984 >
worked

Newbie Joined: 30 Jan 2010 Posts: 6

Further information:

<trigger priority="240" trigontrig="false" newline="false" prompt="true" id="24">
<pattern>*(%d)/(%d)*</pattern>
<value>#echo worked
</value>
</trigger>

Is my exact XML trigger copy. There are currently 0 other triggers on my cmud

Posted: Sun Jan 31, 2010 9:56 pm

the below code should work i just tested it, i set my prompt to match your original one

Newbie Joined: 30 Jan 2010 Posts: 6

Worked great on my laptop, and i got all excited to come home and try it out.... only to have it not work at home :(.

I have a feeling there is some sort of bug- perhaps this is related to the beta.

Newbie Joined: 30 Jan 2010 Posts: 6

Reinstalled... works great Question