Zugg Software :: View topic

Wanderer Joined: 01 Oct 2005 Posts: 54

Is there a way that everything I type, when I hit enter it puts %CR at the end of it?

like....

say I type who it sends
#SENDP {who%cr}

and I also want it to work for sopmething like gt hello, how are you

it will send #SENDP {gt hello, how are you%cr}

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

If you use #SEND instead of #SENDP, it will put the carriage return in for you. If you want to do a carriage return for other reasons, use #CR to send one to the game. The %crlf function is mostly useful for formatting output with #SAY, #SHOW, and #ECHO.

Wanderer Joined: 01 Oct 2005 Posts: 54

Well I wanna use it cause without it it does like a blank line right after I type anything, but #SEND doesn't work either...It still needs to be #SENDP {text%CR}....anyone know how to do it?

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

I think maybe you don't understand the purpose of the #SEND and #SENDPROMPT commands. Why are you not just sending "gt Hello. How are you?" to the MUD? Do you want the carriage return to be embedded in your game text as though you were editing a letter and needed a linebreak code without actually seeing a linebreak in your own output? Perhaps if you explain more about what you're trying to do and why...

Wanderer Joined: 01 Oct 2005 Posts: 54

Okay, here is what is happening...

I type "kill mob"

It sends to the mud kill mob, AND a return...as if I hit enter twice.

so the output is like

kill mob
You hit *
prompt
prompt

What it SHOULD do is
kill mob
you hit *
prompt

Get it? When I hit enter on anything it sends an extra enter, but if I use #SENDP {text%cr} it won't send that extra enter...Is there a way to make EVERYTHING I type from the command line force it to have a #SENDP {text%CR} behavior?

Apprentice Joined: 11 Sep 2005 Posts: 124

a catch all #ONINPUT Trigger perhaps?, just an idea to point you in a direction, i've never done anything like this.

Posted: Thu Apr 06, 2006 10:08 pm

Posted: Thu Apr 06, 2006 11:18 pm

Also perhaps the MUD you are playing doesn't support the Telnet protocol properly. According to the Telnet spec, all lines should end in a CR and LF (char 13 and char 10). Some MUD coders have gotten lazy and think that a line should only end in a LF (\n in C) and when they see both the CR and LF they end up putting in two lines.

If this is the case, you should contact the MUD you are playing and have them fix it. There is no excuse anymore for a MUD that doesn't properly implement telnet.

Wanderer Joined: 01 Oct 2005 Posts: 54

okay, ill ask them about it, but in the meantime I did:

#ONINPUT {(%*)} {#SENDP {%1%cr}}

This fixes it, but now it's sending two commands...any idaes?

I type who, it sends
who
who

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

that's the fun of #ONINPUT. It can watch and do other things based on what you type, but it doesn't prevent what you type from going to the mud.

Apprentice Joined: 29 Jun 2001 Posts: 198 Location: USA