NB> "User is sent to this menu after logging in."
 NB> 
 NB> I would think as long as that user creates the account, let that be
 NB> their only login.. then you can change their start menu to whatever you
 NB> want, or create a new one..

That works if you are not using the matrix login.  If you are using Matrix,
Mystic forces the matrix menu at every menu load, so even if you use a GO
menu command to change the menu, Mystic will reset it to the Matrix before it
ever loads the new menu...

This is done of course for security reasons, and because most of the BBS
functions require there to be an actual user logged in.

The easiest way (IMO) to accomplish the task is to just have the Matrix menu
display a different menu/options by using ACS.  You can test for U0 to see if
there is no known user yet, and !U0 if there is a known user, and then build
out your menu from that.  It would appear to be multiple menus, but really
it'd all just be within the single Matrix menu.

You could also combine that with stacking of menu commands and access flags to
determine how the user became known (applied new, did a check for access, etc).

--- Mystic BBS v1.10 A59 (Windows)