A while back I was trying to get the connect.mps to work, I was considering moving my Door Server over to Mystic instead of a very old copy of Synchronet that I am currently using in Windows. Now I am looking to do something different or possibly the same. I figured out the error I was getting, it was because there was no startup.mps on the system. I created a blank startup.mps and it does work to an extent. It will create a user, the username is all in caps, and the password is some encrypted password that is just garbage being transferred. I am no MPL programmer that is for sure.. So my question is, is there a way to get the username saved as a Case Sensitive username and the password as whatever you send as in @USER@ for username and @USER@ for Password or whatever you choose for password?

Thanks for any info anyone can give me..


|11 Bucko |14- |06Wrong Number Family Of BBS' |07- |03www.wrgnbr.com

... THE fIRST sTEP iS tO tAKE oFF tHE cAPS lOCK

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

On 28 Aug 2026, Bucko said the following...

A while back I was trying to get the connect.mps to work, I was considering moving my Door Server over to Mystic instead of a very old copy of Synchronet that I am currently using in Windows. Now I am
looking to do something different or possibly the same. I figured out
the error I was getting, it was because there was no startup.mps on the system. I created a blank startup.mps and it does work to an extent. It will create a user, the username is all in caps, and the password is
some encrypted password that is just garbage being transferred. I am no MPL programmer that is for sure.. So my question is, is there a way to
get the username saved as a Case Sensitive username and the password as whatever you send as in @USER@ for username and @USER@ for Password or whatever you choose for password?

I don't think you really need much in the startup.mps file. That one does checks and stuff before the user reaches Mystic proper if you wanted them, iirc.

The real user account creation happens in connect.mps. A lot of the
heavy work is already in the default connect.mps iirc as well. I dunno, both of mine are heavily modified for DoorParty. I do know that connect.mps isn't 100% complete for a door server. Again, mine are both heavily modified over months of trial and error of what it needed to work seamlessly. But you should be able to get some semblance of a door server going with just the default two of those files.

I just did a fresh install of the latest prealpha. autocreate.mps is supposed to be connect.mps. Rename both of those files (mps/mpx) and compile whenever you make a change. startup.mps I don't think is really needed unless you want to do account and connection checks before the user hits the system, which for a door server you might want to do, but it's not entirely necessary. autocreate/connect.mps is where the user accounts get created; you don't want to create the accounts in startup.mps.

--- Mystic BBS v1.12 A49 2024/05/12 (Linux/64)
* Origin: throwbackbbs.com -\- meriden, ct -\- (21:1/114)

On 29 Aug 2026, maskreet said the following...

I don't think you really need much in the startup.mps file. That one does checks and stuff before the user reaches Mystic proper if you wanted
them, iirc.

The real user account creation happens in connect.mps. A lot of the
heavy work is already in the default connect.mps iirc as well. I dunno, both of mine are heavily modified for DoorParty. I do know that connect.mps isn't 100% complete for a door server. Again, mine are both heavily modified over months of trial and error of what it needed to
work seamlessly. But you should be able to get some semblance of a door server going with just the default two of those files.

I just did a fresh install of the latest prealpha. autocreate.mps is supposed to be connect.mps. Rename both of those files (mps/mpx) and compile whenever you make a change. startup.mps I don't think is really needed unless you want to do account and connection checks before the
user hits the system, which for a door server you might want to do, but it's not entirely necessary. autocreate/connect.mps is where the user accounts get created; you don't want to create the accounts in startup.mps.

Appreciate the info. I am going to play with it some more to see what happens.. :) The main issue is the password creation for each user. According to logs it is throwing some jibberish in there, if I manually change the password to a real password, the user gets right into the menu needed.. Like they say Google is your best friend so maybe it is time to start reading the help files on MPL and doing something right.. LOL


|11 Bucko |14- |06Wrong Number Family Of BBS' |07- |03www.wrgnbr.com

... Confucius say: "Its stuffy inside fortune cookie"

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)