Zugg Software :: View topic

Newbie Joined: 05 Jun 2007 Posts: 8

I had to reinstall cMud and recreate my session due to a disk failure. On the second login the autolog wizard came on and presented me with the correct values for the login. I saved those.

Now when I try to connect to the MUD the username is correctly entered, but the MUD gives an error on the password sent to it by cMud.

I tried creating the same session with zMud. Autologon worked without problems, the password was correctly sent to the MUD. Then I imported the zMud session into cMud and the problem is there again. I tried to change the password in session parameters, but to no avail.

How do I get the autologon feature working again?

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

Before connecting or going into Offline mode, highlight the character icon and click Edit Session. This will bring up similar windows as in ZMud. Within them is a tab called Character, click on it and you should see something related to account name and password. In the password field, replace what's there with the correct value and save.

This should get you working again, but I believe there's an outstanding bug that causes the autolog feature to not update the account/password stuff if you change it.

Newbie Joined: 05 Jun 2007 Posts: 8

That is what I meant with changing the password in the session parameters. Changing the value in the password field doesn't change anything.

What surprises me is that when I imported the zMud session this time, it got the password wrong. When cMud came out, I did the same and it worked.

Posted: Wed Jun 06, 2007 4:51 pm

Check to see if you have triggers defined for the Autolog.

If the do, determine what it is sending for the password. Also try the follow alias to see what CMUD thinks the password. Note: This must called from an alias.

#ALIAS test {#MESS %char %pass}

Posted: Wed Jun 06, 2007 10:03 pm

What you're going to end up doing if it really is sending the wrong password, though, is either creating your own autolog triggers or deleting the session and recreating it. In the latter case, make sure you back up your packages.