Differences

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

--- menu_commands [2022/02/03 10:29] – 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 588: / 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 971: / 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 1245: / 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**