Differences

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

--- menu_commands [2020/11/06 19:45] – [EXTERNAL DOORS] g00r00
+++ menu_commands [2020/11/06 19:48] – [EXTERNAL DOORS] g00r00
@@ Line 77: / Line 77: @@
 ===== EXTERNAL DOORS =====
-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 temp1 temporary directory.
+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 OS X 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.
 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 89: / Line 89: @@
    %H = The current socket handle (added 1.12 A34)
    %N = The current node number (added 1.12 A34)
-   %P = The node's temp directory
+   %P = Node's temp directory where drop files are stored (with trailing slash)
    %R = User's handle (with spaces)
    %T = User's time left in minutes