This section of the Mystic BBS Configuration System allows the SysOp to configure a number of login settings that apply to the overall BBS system. Here you can also enable and configure aspects of a'Matrix' style login to the BBS. There are areas here that you will want to update from their default settings.

This example screen is from a Windows based system and displays the standard 'out of the box' settings that ship with the default installation.

█▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Login/Matrix ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄
█                                                                    █
█  Default CodePage  │ CP437           Multi Login ACS   │ s255      █
█  Local CodePage    │ CP437           Login Attempts    │ 3         █
█  Ask CodePage      │ Detect          Login Time        │ 30        █
█  Ask Theme         │ No              Password Change   │ 0         █
█  Ask Emulation     │ Detect/Ask      Password Inquiry  │ Yes       █
█  Use Matrix Login  │ No              Password Attempts │ 3         █
█  Matrix Menu       │ matrix                                        █
█  Matrix Password   │ ******                                        █
█  Matrix ACS        │ s50                                           █
█  Login After Apply │ No                                            █
█  Invisible ACS     │ s255                                          █
█  See Invisible ACS │ s255                                          █
█                                                                    █
▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█

Mystic can send client terminals either CP437 or UTF8 data output, converting relevant outbound data to UTF8 when selected. For compatibility reasons, data still is stored in CP437 encoding within Mystic itself. The first two options in this configuration section relate to these UTF8 encoding options.

Default CodePage
Ask CodePage

** READ THIS:
If you do not understand what these are, set Default to CP437 and
Ask CodePage to "Detect".  What this basically does is allows users to use
things like Putty to connect to your BBS, and everything should look and
work as expected.

When Mystic starts up, by default a user will have the configured "Default"
code page.  Then depending on the setting of "Ask CodePage", Mystic will do
one of the following:

   Detect : Mystic only changes codepage from default if it is able
            to detect a terminal that is likely NOT the default, but the
            user is never prompted.
   Ask    : Mystic will ask the user which Codepage they would like
            to use after detecting ANSI.
   CP437  : Codepage will always be set to MS-DOS (CP437)
   UTF8   : Codepage will always be set to UTF8

In Linux, the Default code page will actually be what Mystic runs in
when you run mystic from the command line, too.  In Windows, the Sysop
side will always execute in CP437, even when a user is logged in that
has UTF8 enabled (the user of course will still get sent UTF8).

One other consideration, is that many terminals that use UTF8 are using
VT102 instead of ANSI-BBS, which means a few things are different - most
noticably are ANSI clear screen codes.  In ANSI-BBS, the clear screen also
moves the cursor to 1,1, while in VT102 it does not.  This means its best
to edit your ANSIs and add a |CL at the very top so Mystic clears the
screen in a compatible way.

Set user's default code page. See above for description.

Code page to use for local login (Linux/OSX). See above for description.

Code page determination on login. See above for description.

Place holder text :)