02 Mar, 2011, thalor wrote in the 1st comment:
Votes: 0
Ok I've gone over this as much as I can on my code….

In ZMUD when I send the CLI command #MXP <SEND>Look</SEND>

Which displays look

I click on it and it sends look to the mud and the mud looks…..Thats great.

I can also have the mud send MXP to the client as well.


write_to_buffer( d, MXPTAG ("!ELEMENT look \"<send href='look'>\""),0);


stc( "* " MXPTAG("look") "@Rlook@x" MXPTAG("/look")"",ch);

Which displays look

My problem stems from wanting mobprogs to send the codes to the client.

Im probably being REAL stupid about it….

I am using

mob echoat $n #MXP<SEND>look</SEND>

to try to get it to send. It prints on the screen.

All I get is whatever I type into the mobprog displayed on the screen, zmud either wont interpret it OR
its not being translated properly in the code before being sent to the character.

Any help with this would be great! Thanks!
02 Mar, 2011, plamzi wrote in the 2nd comment:
Votes: 0
One thing you can do while waiting for the MXP experts to respond is to log what is being outputted to the user in each of those cases. Log the outgoing string as late as possible, in the func that does the sending. There's string processing going on in mob echo that could be breaking or escaping some necessary characters.
02 Mar, 2011, David Haley wrote in the 3rd comment:
Votes: 0
It looks like you might be using Nick Gammon's MXP implementation. In that case, MXPTAG is introducing special characters that the output routines transform into angle brackets, while escaping angle brackets. In other words, your mob prog echoing <SEND> is actually sending &lt;SEND&gt; to the client.

You might have to change your mob prob echo routines to detect that #MXP tag you put in front, or to manually convert angle brackets to the special characters used by MXPTAG.