Zugg Software :: View topic - Logging into Mud problem

Newbie Joined: 24 Jun 2004 Posts: 2 Location: USA

I have a similar problem as Narsliss.

there is a mud i am trying to log into and yesterday I get to the log in screen and get the message:

You failed to blah blah --- reasons might be
1. you quit
2. you dropped link
3. something about slp ppp

it just autodropped me when i tried to log in

today -- i tried again but this time zmud fails to recognize the ipa to the mud --- I CAN telnet in and no problems -- but if i try and log in via the zmud client all I get is the reconnect in 5 4 3 2 1 message

any thoughts?

I have disabled all the autoconnect and pueblo stuff

Ant

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

I think if you really wanted help you'd tell us the name of the MUD so we could go see if there is a zMUD problem or just something wrong on your character.

Newbie Joined: 22 Jun 2004 Posts: 4

sure it has has happened on 2 muds now.. homelands... homeland.homelinux.org 9999 and a mud I am working on.. 64.105.110.6 9200 any help would be most appreciated.. wasn't trying to be cryptic.. just wanted to know if anyone had run across it

Newbie Joined: 24 Jun 2004 Posts: 2

ok...im having the same problem...let me see if i can make it a bit more clearer for you to understand.

i hit the connect button and the welcome screen for my mud appears

as soon as it does i get the disconnect screen

now when i set up an auto login script and put the name and password in, it only types in the name for me and i still have to put in the password but i am able to log onto the mud

the only problem with this is that i have multiple characters on that mud so i need the freedom to be able to log in any character because over 100 of my aliases/triggers overlap and i dont wanna type them im 1000+ times each (yeah i have 11 chars)

the mud should not matter in this case so any help with the client would be appreciated

Newbie Joined: 24 Jun 2004 Posts: 2

when u are looking at triggers and aliases make sure u have "all classes" clicked....i found some hidden stuff and deleted it then zmud worked as it should

Newbie Joined: 24 Jun 2004 Posts: 2 Location: USA

I have disabled all -- even looking and unhiding the hidden things in alias and in triggers - I still cannot connect to the mud in 7.05

and it is the second addy that Narsliss posted - with port 9200

Ant

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

Your disconnects probably result from the MUD dropping you. This is usually the result of giving the wrong answers or answering too slow during the login process.

I logged on to Homelands at the address you gave and created a character. I had no difficulty logging in with the alias and triggers created by the Autolog wizard.

I did notice that if you don't choose a terminal and supply your name or password within a few seconds, you 'timeout' and the MUD disconnects you. You probably also get disconnected if you supply an incorrect password. The correct order of commands appears to be:
#CR or 1 (terminal type)
#CH (name)
#PW (password)
#T- Autolog (this is done to make it more difficult for someone to hijack your character)

Guesses:
1. Your atconnect alias and/or Autolog triggers have extra information in them, send information before it is asked for, or don't send the required information when it is asked for
2. Your name or password is entered incorrectly in the zMUD character database
3. You have a slow connection so that it takes you too long to answer the questions

These are just guesses.

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

Further clarification:
If you get disconnected as soon as you see the welcome screen, you are either sending wrong information or sending it too fast.
1. Wrong information would be if you had the wrong name/password combination. This is fixed by selecting Edit from the character selection screen then entering the correct information on the Character tab

2. Too fast would be sending the name or password before it is asked for, usually the name. This is usually caused by sending the name in the atconnect alias instead of a trigger. To fix, open your character Offline and enter this script at the command line. #CR is for ANSI terminal (color on), change it to 1 if you want the VT100 terminal (color off).

#AL atconnect {#CR} System
#TR {By what name do you wish to be known? } {#CH} {Autolog} {case|verbatim|nocr|prompt}
#TR {Password: } {#PW;#T- Autolog} {Autolog} {case|verbatim|nocr|prompt}

Delete or disable any other triggers or aliases you have made for logging in, then try to connect.