(Megamud) logging in, type to fast and it goes haywire?

[scratacorn]

well, not exactly haywire. Anyways i was lagging a little and typed my username and password fairly quick, and notice that only part of my name and then part of my password got on the first line, then about 2 characters of my password got on the password line.......I've never had this problem with WG logons no matter how laggy i was. I've been able to duplicate it a few times. Don't know if this is something that could be changed? or maybe it's just my end?

[The Crazy Animal]

Is this happening to anyone else? I'm if no one answers yes then I'm going to assume this was on his side and close this one.

[Ian]

Yes, but not typing manually.  Mega has had a few problems logging in, and this sounds pretty similar.

[Vitoc]

On every WG board I've ever logged into they have that auto-sensing crap in the beginning that usually takes at least a few seconds.  You'll notice on the GMUD server there is no delay at all.  Maybe during that auto-sensing test the client is *supposed* to send a carriage return?   ???

I can handle it, but it's strange that the second time you connect with Mega the behavior doesn't occur.

[The Crazy Animal]

On every WG board I've ever logged into they have that auto-sensing crap in the beginning that usually takes at least a few seconds.  You'll notice on the GMUD server there is no delay at all.  Maybe during that auto-sensing test the client is *supposed* to send a carriage return?   ???

I can handle it, but it's strange that the second time you connect with Mega the behavior doesn't occur.

Well normally when you start a telnet session the client and server both negotiate for a standard.. Thats the only thing I can imagine the auto-sensing message is masking...

[Vitoc]

Well normally when you start a telnet session the client and server both negotiate for a standard.. Thats the only thing I can imagine the auto-sensing message is masking...

Before starting on GMUD my goal was to create a client superior to MegaMUD, and to do that I had to create a functional telnet client.  IIRC, the auto sensing is actually the server moving your cursor to a location via one or more ansi commands and then immediately requesting the cursor location from the client.  If the client was capable of handling ANSI, it would report the correct cursor location.  If it couldn't, it would report the wrong cursor location and the server would know the client could not handle ANSI.  When people connect to the GMUD server I'm not bothering to check if they support it, they're going to get ANSI codes whether their client can interpret them or not. ;)

One easy, if not cheesy, fix would be to just ignore a client CRLF when the server is asking for firstname unless there's something else already typed in the field.

[The Crazy Animal]

Before starting on GMUD my goal was to create a client superior to MegaMUD, and to do that I had to create a functional telnet client.  IIRC, the auto sensing is actually the server moving your cursor to a location via one or more ansi commands and then immediately requesting the cursor location from the client.  If the client was capable of handling ANSI, it would report the correct cursor location.  If it couldn't, it would report the wrong cursor location and the server would know the client could not handle ANSI.  When people connect to the GMUD server I'm not bothering to check if they support it, they're going to get ANSI codes whether their client can interpret them or not. ;)

One easy, if not cheesy, fix would be to just ignore a client CRLF when the server is asking for firstname unless there's something else already typed in the field.

Nod... Give it a try and we can see if it works...

[DeathCow]

Thats not a cheesy fix.

[Ian]

Yes, but not typing manually.  Mega has had a few problems logging in, and this sounds pretty similar.

Actually I just had another look at mega going spaz on logon.  It seems that the first connect line "Please enter your username or "new":" sometimes gets sent twice.  So Mega sends my logon name (Ian) twice.  But after the first entry I get prompted for password, and that prompt catches the second coming of Ian.  So then mega gets out of whack and keeps sending username as password and password as username until I'm denied entry.

!Welcome to the Official Greater MUD server!
Please enter your username or "new":
Please enter your username or "new": Ian
Please enter your password: ***
Invalid username/password!
Please enter your username or "new": password
Please enter your password: **
Invalid username/password!
Please enter your username or "new": password
Please enter your password: ***
Invalid username/password!
Please enter your username or "new": password
Please enter your password: ***
Too many invalid attempts! Goodbye!

[ghaleon]

so why not have it look for "new" and send {userid}^M{pswd}^M
bypassing the fact that it looks for password...

if it then duplicates "new" it will just send your userid/password once its already logged in...

???

[The Crazy Animal]

so why not have it look for "new" and send {userid}^M{pswd}^M
bypassing the fact that it looks for password...

if it then duplicates "new" it will just send your userid/password once its already logged in...

???

I have mine sending {userid}^M{userid}^M for new and then a single password for password and it gets in doing that too..