Differences

This shows you the differences between two versions of the page.

--- menu_commands [2021/12/22 12:38] – g00r00
+++ menu_commands [2023/01/20 02:39] (current) – [INTERNET RELATED] g00r00
@@ Line 79: / Line 79: @@
 Mystic BBS supports DOOR.SYS, CHAIN.TXT, and DORINFO1.DEF DOS-based door formats, as well as Mystic's own native DOOR32.SYS format for modern BBS doors and games.  These drop files are always created in the node's specific temporary directory.  For example, if a door is executed on node 1, then the drop files will be created in the node's temporary directory "temp1" that is created off of the root Mystic BBS directory (ie c:\mystic\temp1\)
-In the Linux and macOS versions, Mystic automatically redirects the standard input and output of external programs, allowing many programs that are not even designed for BBSes to be used.
+In the Linux and macOS versions, Mystic automatically redirects the standard input and output of external programs, allowing many programs that are not even designed for BBSes to be used.  From a technical perspective it forks and executes your command line with /bin/sh then creates a watchdog on the child process so that it can help trap lost connections even for programs that cannot detect those types of things natively (like a BBS door would).  It is important to understand that commands are not executed from bash when Mystic runs them, they are executing the system shell.  In other words, if you want to test a command line you should test it accordingly outside of Mystic by executing: /bin/sh -c <Your command line here> to see if it works.
 Each door action has a command line which will be executed by the operating system when the action is executed.  There are a number of codes that Mystic will replace with specific values if they are found in the command line:
@@ Line 106: / Line 106: @@
 will remove it and change to the directory specified between the <> characters
 prior to executing the command line.
+Mystic tracks the number of doors opened by a user when using a DOOR menu command.  Door command lines can have a /NOSTAT at the end of the command line in optional data to tell Mystic not to increment the users door count.
 **The following commands are available for executing external programs and doors:**
@@ Line 217: / Line 219: @@
   use these alternative templates, simply execute FI with the data field of
   "file_change" or whatever the custom template filename you've created is.
+  NOTE: Even if you do not use file groups for anything, there needs to be
+  at least one file group created for the Index Lister to function.
 **FL - List files in current File Base**
@@ Line 312: / Line 317: @@
 **GA - View ANSI Gallery**
-  Data: <path to files> [/TEMPLATE=mygallery]
+  Data: <path to files> [/TEMPLATE=mygallery] [/NOSAUCE]
   Opens the ANSI gallery allowing the user to browse and view ANSI
@@ Line 318: / Line 323: @@
   variations with font switching, and more).  The path to files
   should contain the root directory where users will start
-  browsing from.  The default template of "gallery" will be used
+  browsing from.
+  The default template of "gallery" will be used
   but this can be overridden using the /TEMPLATE option as shown
+  Depending on the disk and system speed, reading the contents of a
+  large directory and checking each file for SAUCE information can
+  take some time.  Adding /NOSAUCE on the optional data field will
+  disable sauce reading for the file listing.  SAUCE will always
+  still be used when viewing a file in the ANSI viewer.  This can
+  also be set in the gallery template but this will override that
+  setting.
 **GD - Show a display file**
@@ Line 539: / Line 554: @@
 Both RLOGIN and SSH protocols will require a user and password be supplied in the
-optional data.
+optional data.  All outbound connection commands can include a /PROMPT in the optional
+data field which will hide display of the "connection" prompts.
 **IR - Outbound RLOGIN Connection**
@@ Line 574: / Line 590: @@
   The user's password cannot be sent using an @code@ and must be manually
-  supplied due to the password encryption.  Mystic in the near future will
+  supplied due to the password encryption.  By default Mystic never stores
-  encrypt a users password, meaning at no time does it ever know or store
+  a users password, meaning at no time does it ever know your actual
-  your actual password.  It cannot send it because it doesn't know it.
+  password.  It cannot send a password because it doesn't know it.
 **IT - Outbound TELNET Connection**
@@ Line 612: / Line 628: @@
   will change to the message area that is linked to the supplied unique ID.
-**MC - Check Private BBS E-mail**
+**MC - Check Private Local E-mail**
   Data: /NOLIST /UNREAD /SCAN
@@ Line 708: / Line 724: @@
   use these alternative templates, simply execute MI with the data field of
   "msg_change" or whatever the custom template filename you've created is.
+  NOTE: Even if you do not use groups for anything, there needs to be
+  at least one message group created for the Index Reader to function.
 **ML - Browser/Search Network Nodelists**
@@ Line 833: / Line 853: @@
   If "G" is supplied, Mystic will search bases in the current group
-**MV - View Sent E-mail**
+**MV - View Sent Local E-mail**
-**MW - Send Private BBS E-mail**
+**MW - Send Private Local E-mail**
+  Data: /TO: /SUBJ: /F
+  Each user has a personal e-mail box that exists only on the BBS and
+  this command is used to send a message to a user's personal mailbox.
+  Messages posted here are shown to the user when the MC menu command
+  is executed to check their local mailbox.
+  If /TO:<text> is provided, the post can be automatically addressed to
+  the supplied username in <text>.  Note that spaces should be replaced
+  by underscores (_) when supplying this.  If this is not supplied then
+  Mystic will ask the user to who to send the message to.
+  If /SUBJ: is provided, the post will have its subject automatically
+  set.  Spaces should be replaced with underscores.  If this is not
+  supplied then Mystic will ask the user for the message subject.
+  If /F is provided, the post will be forced meaning the user will not
+  be able to abort posting the message when they are in the message
+  editor.
 **MX - Post text file to message base**
@@ Line 933: / Line 973: @@
 **NW - Show Who's Online**
+  If the /SCAN optional data is supplied, Mystic will not display the who's
+  online list but instead force recalculation of active users (returned by
+  the NA MCI code).
 -----
@@ Line 1207: / Line 1251: @@
 **!C - Create Semaphore File**
+This command adds three lines of text to the semaphore file:
+  * Line 1: User ID
+  * Line 2: User Handle
+  * Line 3: Node number
+If no user was logged in when this was created the ID will be -1 and the handle blank.
 **!D - Delete Semaphore File**
@@ Line 1273: / Line 1325: @@
 **F3 - Download File (Send to User)**
-  Data: <Full Path and Filename>
+  Data: <Full Path and Filename> [/PROT=X] [/NOPROMPT]
   Send the file supplied in the data field to the user.  The user's
   file statistics will not be updated.
+  If the optional PROT command is used then the Mystic will select
+  the protocol automatically that is associated to the hotkey in
+  the Protocol configuration.  For example: /PROT=Z would auto
+  select Zmodem by default.
+  If the optional /NOPROMPT command is supplied then Mystic will skip
+  the "Press a key to start transfer or Q to Quit" prompt