Zugg Software :: View topic - Problem with in-game mud prompt

Apprentice Joined: 01 May 2002 Posts: 188 Location: USA

I'm not sure if this is a zmud problem or not but I have spoken with other zmud users and they don't see this problem. However, I have a problem that take the first text and places it next to my prompt. For instance, if I type look the name of the room is on the same line as my prompt and description will be beneath my prompt. Whereas, it should be:

<123/123hp yadda yada>A Small room
This is a small room yadda yadda yadda.

Where it should be:

<123/123hp yadda yada>
A Small room
This is a small room yadda yadda yadda.

You get my drift?

Sup

Adept Joined: 29 Oct 2001 Posts: 250

Only thing you can do about it is make a bunch of #SUB triggers to move it around, but I would personally look into seeing if your mud has in-game prompt settings. Next time you play, try looking in the muds help files for prompt,promptset, or configuration.

Apprentice Joined: 01 May 2002 Posts: 188 Location: USA

I have checked the in-game settings and basically I have tried everything in game. I think something with zmud is screwing it up. I tried other people's prompt that they use with no problem and it still does the same thing. Any thing that zmud could be triggering? Possibilities?

Sup

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

The problem isn't zMUD, it's the MUD you're playing on. The MUD sends the prompt without an end-of-line character and zMUD does what it's supposed to, continues on the same line.

To fix it, you need to change your prompt to include an end-of-line.

LightBulb
Vague questions get vague answers

GURU Joined: 10 Oct 2000 Posts: 4379 Location: USA

So, where is the look command you typed in the sample MUD output you provided?

Kjata

Apprentice Joined: 01 May 2002 Posts: 188 Location: USA

quote:

The problem isn't zMUD, it's the MUD you're playing on. The MUD sends the prompt without an end-of-line character and zMUD does what it's supposed to, continues on the same line.

To fix it, you need to change your prompt to include an end-of-line.

LightBulb
Vague questions get vague answers

If that is the case, then how come the same prompt from another person who uses zmud as well doesn't have the problem? I mean, I cut n' pasted his customized prompt for my prompt and it still does the same thing. However, his same prompt is not doing what mine is doing....

Sup

Apprentice Joined: 01 May 2002 Posts: 188 Location: USA

quote:

So, where is the look command you typed in the sample MUD output you provided?

Kjata

The look command is not there. I shut off the echo.

Sup

GURU Joined: 10 Oct 2000 Posts: 4379 Location: USA

Well then, there's your problem. Does the other person has local echo turned off too? I'm guessing that he/she doesn't. If this is, indeed, what is causing the problem, a possible solution is that some MUDs have the option (with some special code) to include a newline in the prompt. Try including the newline at the end of your prompt.

Kjata

Apprentice Joined: 01 May 2002 Posts: 188 Location: USA

quote:

Well then, there's your problem. Does the other person has local echo turned off too? I'm guessing that he/she doesn't. If this is, indeed, what is causing the problem, a possible solution is that some MUDs have the option (with some special code) to include a newline in the prompt. Try including the newline at the end of your prompt.

Kjata

Yes this person has echo turned off.

Sup

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

If you get different results (you and your friend), then something is different. Find out what's different and change it.

From what you've said so far, it's not the prompt, it's not echo, and it's not zMUD. That rules out everything I can think of, so while I wish you the best of luck in finding it I don't think there's anything else I can suggest.

LightBulb
Vague questions get vague answers

GURU Joined: 10 Oct 2000 Posts: 4379 Location: USA

There goes my theory, then.

But, there must still be something different, somewhere, because I just tried turning off echo in a random MUD I picked from the list, and it did move every line after the prompt to appear besides the prompt. Could you post the MUD address and port, and perhaps the prompt config if possible, to do some testing?

Kjata

Apprentice Joined: 01 May 2002 Posts: 188 Location: USA

Ok I just found out from an IMM on the mud that there should be an ESCAPE [3m which zmud is ignoring. I'm looking all over in the setting currently to find out where it is that I"m ignoring this "ESCAPE [3m" portion.

Anyone know where to look??

Sup

Wanderer Joined: 19 Jul 2001 Posts: 59 Location: Germany

Hmmm, perhaps you can ask your IMM where that
'ESC [ 3 m' sequence is sent
(after the prompt? or at the beginning of the telnet session?)
Also I'd be interested what your mud's coders think that escape sequence should do.
Because the documents about VT100/VT102 I've found so far eg. http://www.retards.org/terminals/iowa_vt100_news.txt or http://krtkg1.rug.ac.be/~colle/C/vt102.codes
don't cover it at valid sequence sent from a server.

So it seems like it's something non-standard (which means zMUD HAS to ignore it).

Apprentice Joined: 01 May 2002 Posts: 188 Location: USA

Ok I put echo on and it worked. It fixed the problem. But, I prefer to not have echo...it seems to cause more spam for me. I mean why do I need to see what I just typed?

Any suggestions?

Sup

Wanderer Joined: 19 Jul 2001 Posts: 59 Location: Germany

I'd just keep echo on, and change the color for command output in Prefs/Colors/Color Schemes to black (or whatever your background color is).
That way you don't see the additional spam

Is a kludge, but probably much less hassle then trying to use triggers to insert a line break.
(I faintly remember a similar case where I tried to #GAG or #SUB half of a line and #SHOW it in the next line, and it only confused the mapper.)

Apprentice Joined: 01 May 2002 Posts: 188 Location: USA

quote:

I'd just keep echo on, and change the color for command output in Prefs/Colors/Color Schemes to black (or whatever your background color is).
That way you don't see the additional spam

Is a kludge, but probably much less hassle then trying to use triggers to insert a line break.
(I faintly remember a similar case where I tried to #GAG or #SUB half of a line and #SHOW it in the next line, and it only confused the mapper.)

Yeah changing the background color did the trick. A work around that worked. However, I noticed, although with all the spam, there were some things that I saw that proved to be helpful.

Sup

Beginner Joined: 10 Oct 2000 Posts: 13

I see that you have found a workaround for your problem, but I had a similar problem that needed another solution. So I made a simple trigger to fix it. On Realms of Despair, if I type 2 or more commands real fast, then the mud output loses a carriage return. Here is a simple example of typing east 2 times fast:

--------------------
<1113h 0b 661m >east
east
Horizon Road
While traversing Horizon Road, you notice a curious wall of mists to
the south. You also notice the turrets of Castle Darkhawk peeking
out of the forested section of town to the north. The lengthy
cobblestone road stretches to the east and west.
Exits: east south west

<1113h 0b 653m >Horizon Road
Young and giddy adventurers pass you as you travel this portion of Horizon
Road. Gazing southward, you see the illustrious Darkhaven Academy, which
has the responsibility of training new adventurers in the Realms. The
cobbled streets of Horizon Road continue to the east and west.
Exits: east south west

<1113h 0b 645m >
--------------------

It was not a big problem, but it was annoying. I am not that good at making triggers, but I eventually figured out how to make one to fix it. Here is that trigger in case anyone is at least a little interested in it.

#TRIGGER {>[A-Z]} {} "" {notrig}
#COND {>} {#SUB >%cr} {reparse|notrig}

I had to turn off "Trigger on Commands" in Preferences/General/Script Parser to prevent it from triggering on commands I type at the prompt.

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

This is a beta solution. If you're still using the public version, 6.16, this won't work so don't even try it. The command #COND and the option "reparse" don't exist.

LightBulb
Vague questions get vague answers

Beginner Joined: 10 Oct 2000 Posts: 13

Sorry, I didn't realize those commands were only in the beta. I have tried another trigger that should work on the public version, but there is a problem with it. It strips out the ANSI color characters from the first word after the prompt. Can anyone help? Here it is:

#TRIGGER {>(%w)} {#SUB {>%cr~%1}}

Apprentice Joined: 03 Jan 2002 Posts: 152 Location: USA

Bumparooney

I found your trigger quite useful, Xander. I'm seeing the color stripped from the first word too of course, and would be very interested in a fix myself

Wanderer Joined: 19 Jul 2001 Posts: 59 Location: Germany

#TRIGGER {>%w} {#TEMP {>} {#SUB {>%cr}}}
is worth a try.
Might have side effects with other triggers on that line.

Apprentice Joined: 03 Jan 2002 Posts: 152 Location: USA

Thank you God..er Sildaren. Works like a charm, for me anyhow. No ill effects have reared their ugly head as of yet.