menu_commands
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
menu_commands [2021/12/25 00:54] – 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' | Mystic BBS supports DOOR.SYS, CHAIN.TXT, and DORINFO1.DEF DOS-based door formats, as well as Mystic' | ||
- | 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). |
Each door action has a command line which will be executed by the operating system when the action is executed. | Each door action has a command line which will be executed by the operating system when the action is executed. | ||
Line 106: | Line 106: | ||
will remove it and change to the directory specified between the <> characters | will remove it and change to the directory specified between the <> characters | ||
prior to executing the command line. | prior to executing the command line. | ||
+ | |||
+ | Mystic tracks the number of doors opened by a user when using a DOOR menu command. | ||
| | ||
**The following commands are available for executing external programs and doors:** | **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 | use these alternative templates, simply execute FI with the data field of | ||
" | " | ||
+ | | ||
+ | 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** | **FL - List files in current File Base** | ||
Line 585: | Line 590: | ||
The user's password cannot be sent using an @code@ and must be manually | The user's password cannot be sent using an @code@ and must be manually | ||
- | supplied due to the password encryption. | + | supplied due to the password encryption. |
- | | + | a users password, meaning at no time does it ever know your actual |
- | | + | |
**IT - Outbound TELNET Connection** | **IT - Outbound TELNET Connection** | ||
Line 623: | Line 628: | ||
will change to the message area that is linked to the supplied unique ID. | will change to the message area that is linked to the supplied unique ID. | ||
- | **MC - Check Private | + | **MC - Check Private |
Data: /NOLIST /UNREAD /SCAN | Data: /NOLIST /UNREAD /SCAN | ||
Line 719: | Line 724: | ||
use these alternative templates, simply execute MI with the data field of | use these alternative templates, simply execute MI with the data field of | ||
" | " | ||
+ | | ||
+ | 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/ | **ML - Browser/ | ||
Line 844: | Line 853: | ||
If " | If " | ||
| | ||
- | **MV - View Sent E-mail** | + | **MV - View Sent Local E-mail** |
- | **MW - Send Private | + | **MW - Send Private |
+ | |||
+ | 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 / | ||
+ | the supplied username in < | ||
+ | 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. | ||
+ | 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** | **MX - Post text file to message base** | ||
Line 944: | Line 973: | ||
**NW - Show Who's Online** | **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 1218: | Line 1251: | ||
**!C - Create Semaphore File** | **!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** | **!D - Delete Semaphore File** |
menu_commands.1640415262.txt.gz · Last modified: 2021/12/25 00:54 by g00r00