Problems with trigger in a German Mud

Hello,

I have built the following trigger for a german Mud:

<triggers>
<trigger
enabled="y"
ignore_case="y"
match="* redet zu dir:"
sequence="100"
sound="C:\WINDOWS\Media\chimes.wav"
>
</trigger>
</triggers>

I have triggers and triggersounds enabled, but the trigger does not work. Have I done something wrong or has Mushclient problems with german texts?

Thanks for your help

Sarah

Can you please paste the exact text that comes from the MUD, that you are trying to match against with this trigger? Copy and paste, not retype. Thanks.

Hi,

ok, I now have copied an example of the text from the mud directly.

The text I wish to match upon ist:

Info: Luma betritt FinalFrontier.

Well, Info: should be matched, the rest would be a wildcard.
I already have the trigger for this match:

<triggers>
<trigger
enabled="y"
ignore_case="y"
match="Info: *"
sequence="100"
sound="C:\WINDOWS\Media\chimes.wav"
>
</trigger>
</triggers>

But this trigger does not work, like the others I built for this mud.

I already built triggers for english muds and there I had no problems at all.

Thanks again for your help

Sarah

I tried that, and it worked.

MUSHclient doesn't know it is getting German text, so there is no real reason it shouldn't work, unless you had some obscure characters in the trigger, however "Info:" seems straightforward enough.

You say no triggers are working, have you accidentally disabled all triggers? On the trigger list there is a checkbox : Enable Triggers. Make sure that is ticked.

Also make sure "Enable Trigger Sounds" is checked.

Also, edit the trigger and see if the match count is greater than zero (about half-way down the screen). Maybe it is matching but not finding the sound to play.

Well, enable triggers and triggersounds are checked and the matchcount is zero.
I also used this sound in other muds and there it works without any problems.

Well that is a puzzle. It should work. The line you are matching appears just like that? There is no prompt in front, like this? :


<100/100hp 143/143m 210/210mv 0/343xp> Info: Luma betritt FinalFrontier.


If things are exactly as you describe, then we must dig deeper. Can you please do this:

1. Log onto the MUD, and play until roughly when (before) the "Info:" line is about to appear.
   
2. Turn on "packet debug": Edit menu -> Debug Packets.
   
3. Keep playing until the "Info:" line appears.
   
4. Turn off "packet debug": Edit menu -> Debug Packets (uncheck it).
   
5. Another window should have appeared behind the main one - a notepad window, with the packet debug in it.
   
   Scan backwards through that until you see a packet with the "Info:" line in it. It will look something like this:
   
   

   
   3/143m .[1;32m21   33 2f 31 34 33 6d 20 1b 5b 31 3b 33 32 6d 32 31
   0/210mv .[1;35m0   30 2f 32 31 30 6d 76 20 1b 5b 31 3b 33 35 6d 30
   /343xp.[0m>.[0m    2f 33 34 33 78 70 1b 5b 30 6d 3e 1b 5b 30 6d
   
   Incoming packet: 9 (39 bytes)
   
   ..Info: Luma bet   0d 0a 49 6e 66 6f 3a 20 4c 75 6d 61 20 62 65 74
   ritt FinalFronti   72 69 74 74 20 46 69 6e 61 6c 46 72 6f 6e 74 69
   er.....            65 72 2e 0d 0a 0d 0a
   
   Sent  packet: 9 (7 bytes)
   
   score..            73 63 6f 72 65 0d 0a
   
   Incoming packet: 10 (161 bytes)
   
   .[1;37m.[1;31m.[   1b 5b 31 3b 33 37 6d 1b 5b 31 3b 33 31 6d 1b 5b
   

   
   
   I have underlined the relevant bit so you can see what I mean.
   
6. Copy that entire packet and paste into the forum here. I need to see the hex codes, so copy the entire thing, not just the underlined part.

Thank you.