This section of the Mystic BBS Configuration System allows the SysOp to configure a number of system paths for the BBS software. These paths are usually set up when the software is installed but can be changed at any stage.

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

    █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ System Paths ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄
    █                                                                     █
    █  System Path       │ c:\bbs\mystic\                                 █
    █  Data File Path    │ c:\bbs\mystic\data\                            █
    █  Log File Path     │ c:\bbs\mystic\logs\                            █
    █  Message Base Path │ c:\bbs\mystic\msgs\                            █
    █  File Attach Path  │ c:\bbs\mystic\attach\                          █
    █  Semaphore Path    │ c:\bbs\mystic\semaphor\                        █
    █  Menu File Path    │ c:\bbs\mystic\menus\                           █
    █  Text File Path    │ c:\bbs\mystic\text\                            █
    █  Script Path       │ c:\bbs\mystic\scripts\                         █
    █  Inbound EchoMail  │ c:\bbs\mystic\echomail\in\                     █
    █         Unsecured  │ c:\bbs\mystic\echomail\in\unsec\               █
    █  Outbound EchoMail │ c:\bbs\mystic\echomail\out\fidonet\            █
    █  Local QWK         │ c:\bbs\mystic\localqwk\                        █
    █                                                                     █
    ▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█

The system path is the main BBS directory where MYSTIC.EXE and its supporting files are located. In almost all cases, this directory never needs to be changed.

The data path is the directory where Mystic BBS will store all of it's data files. In almost all cases, this directory never needs to be changed.

The system logs path is the directory where Mystic BBS will keep an updated log file of BBS activity. The log files can be used to see what each caller was doing while they were online. These files are not used by Mystic BBS and exist for information purposes only.

The message base path is the default directory where Mystic BBS will store it's message base data files.

The file attach path is the directory where Mystic BBS will store files that are attached to messages. Mystic BBS allows users to optionally include a file to any message posted on the BBS system.

The semaphore path is the directory where Mystic BBS creates semaphores as messages are sent or received by the BBS. These semaphores are 0kb files that the Events system can take advantage of to trigger actions to process incoming or outgoing messages as it finds them in this directory. Once messages are imported or exported the semaphore is removed.

The menu file path is the default directory where Mystic BBS will store it's menu data files.

The textfile path is the default directory where Mystic BBS will store it's ANSI (.ANS) and ASCII (.ASC) files along with a number of configuration files (.INI) for the likes of the file index reader, message editor etc.

The script path is the directory where all compiled Mystic BBS programming files are found. Mystic BBS supports an internal programming language (MPL and more recently Python) that can be used by SysOps to create games, utilities, or BBS enhancements with ease.

The directory where inbound netmail / echomail packets received by BinkP, FTP, Directory or Fidopoll sessions from known Echomail Nodes are stored.

The directory where inbound netmail / echomail packets received by BinkP, FTP, Directory or Fidopoll sessions from unknown Echomail Nodes are stored.

The directory where outbound netmail / echomail packets destined for Echomail Nodes are stored.

The local QWK is the directory where Mystic BBS will create QWK offline mail packets if the user is logged into the BBS locally. This directory usually points to the same directory of your offline mail reader, if you use one.