Reading XML-like data from MUD

Posted by Drakonik on Fri 18 Jul 2008 07:17 PM — 7 posts, 29,550 views.

#0
Alright. This thread is where I'm going to put all my questions for this project, so the title is probably not going to be very descriptive for long. That being said...

The MUD I play allows users to have various information about their character sent to their client in a format like this:
<rt>3</rt>
<position>STANDING</position>
<vitality>218:226</vitality>

And so on. It's an XML like format. Open tag, close tag. I've got a trigger set up that correctly captures this string. However, when I set the trigger to Omit From Output (these data strings are sent a LOT. Any time a point of anything is lost, regained, any time I sit or stand, any time something enters or leaves my hands...something is sent), the data lines are indeed omitted. However, something odd happens. To test the trigger, I sent the captured text (the entire <foo>value</foo> string) to a world.note() in my script file. When the trigger is omitted from output, the world.note text is omitted as well. Is this a function of triggers? If so, is there a way to capture this text, and not let me see it, while still letting me put note() text to the game world?
Australia Forum Administrator #1
See http://mushclient.com/faq - point 51.
#2
Alright. Next question. MUSH seems to insert a '>' after every command I send. Like so:

sit
You sit down on the ground.
>


The odd thing about this particular MUD is that instead of new text arriving below this cursor, it arrives on the same line, and THEN wraps. Like so.


sit
You sit down on the ground.
>A sharl conscript reaches at you with its left pincer.


This causes odd behavior when the trigger mentioned in the previous post is activated. The line with the > on it is 'sucked away' and all text gets pulled one line down the screen. It's very disconcerting, and the > cursor has never really appealed to me anyway. Is there a way to disable this? I've checked global and world options and couldn't find anything.
Netherlands #3
That's not MUSHclient. It's probably output from your mud that is somehow getting butchered due to your trigger. Maybe it is not omitting the full thing you think it is omitting.
#4
Hm. Are you certain? I've played a few MUDs and the > cursor has always been there. Is it one of those unconsciously ubiquitous things people do?
Netherlands #5
I'm pretty 100% certain. It is the mud. (Unless you have a script outputting it, but that would be a rather conscious choice.)
Australia Forum Administrator #6
A lot of MUDs tend to do that. See http://mushclient.com/faq point 11 for suggestions on how to work around that.

It is often called a "prompt" and they do it to give you a visual cue that it is time to type something.

You may be able to configure it to go away, eg. "prompt off".