Zugg Software :: View topic

Newbie Joined: 25 Jan 2008 Posts: 2

I've been having several issues with cMUD since I got it, most of which I've been able to resolve myself. For example, all of my aliases and triggers would vanish with each successive login, so I created a new package file that I save into each time I make a setting. However, the autolog file is ALWAYS disabled upon login. I can deal with this- I just enable it and move on, ignoring the fact that my auto login NEVER works... My newest problem, I can't solve. I opened cMUD; everything ok. But as soon as I connected to a session, my command line disappeared. I checked under Options, under General, and everything there is fine. Even tried reseting to defaults with no results. The only way I can input information to the mud is to bring up my command history and type in on that entry line. I have to do this EACH TIME I want to input something; just typing without seeing anything on the screen does nothing. Needless to say, it's extremely tedious to do this, and I cannot mud this way. I didn't do anything to cause this- I logged in last night and everything was fine, then today, this randomly happened without any action from me... I've tried every logical thing I can think of to fix this- gone through all options and settings, and nothing appears to be out of order. HELP!!!

Posted: Fri Jan 25, 2008 6:25 am

Couple of questions? What version of CMUD are you using? Are you using packages from earlier versions? If you connect to the same mud from a completely new session do you still have the problem?

It sounds reminiscent of a problem that was solved several versions ago.

Posted: Fri Jan 25, 2008 6:38 am

Sounds like you have a corrupted layout file. Always be sure to look in the Troubleshooting section since common questions are answered there. You should try holding down the SHIFT key when you click the Open Offline action to create a new layout file, then rearrange your windows the way you want and it will save when you exit (or you can force a save via the #SAVE command). That should fix the command line issue.

For the autologin, go into the AutoLog folder in your settings and make sure the triggers are set up correctly. The AutoLog option simply enables this class folder when you connect so that the triggers in it are active.

Newbie Joined: 25 Jan 2008 Posts: 2

I'm using version 2.18, and the problem still happened when I connected to the same mud from a new session... When I opened cMUD today, however, the problem seemed to have resolved itself... Don't understand why, but not complaining... Thanks for the help.