menu_commands
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
menu_commands [2019/01/30 09:41] – [MENU ACTION REFERENCE] g00r00 | menu_commands [2019/03/24 21:17] – g00r00 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== MENU ACTION | + | ====== MENU COMMAND |
+ | ^ Related Categories | ||
+ | | [[themes|Themes]] | | ||
+ | | [[menus|Menus]] | ||
+ | |||
+ | ----- | ||
Mystic BBS has a completely configurable and incredibly flexible menu system that allows for full control over the visual appearance and functionality of the BBS. Each menu consists of the basic settings, and a list of menu commands that define what options are available on each menu. These menu commands can then be assigned one or many " | Mystic BBS has a completely configurable and incredibly flexible menu system that allows for full control over the visual appearance and functionality of the BBS. Each menu consists of the basic settings, and a list of menu commands that define what options are available on each menu. These menu commands can then be assigned one or many " | ||
This section contains a reference to all of the menu actions available in your Mystic BBS as well as any information needed that relates to those actions. | This section contains a reference to all of the menu actions available in your Mystic BBS as well as any information needed that relates to those actions. | ||
- | **Note: Mystic has somewhere | + | **Note: Mystic has around |
---- | ---- | ||
Line 49: | Line 54: | ||
**BS - List entries in a BBS list (abbreviated view)** | **BS - List entries in a BBS list (abbreviated view)** | ||
- | Data: <LIST ID>; | + | |
- | | + | |
- | | + | |
- | | + | mode. This provides more information than the typical abbreviated list |
- | | + | The <LIST ID> must be specified in the optional data. If "; |
- | | + | appended onto the List ID, then Mystic will prompt and allow the user |
+ | to search for entries in the BBS list. | ||
----- | ----- | ||
Line 65: | Line 71: | ||
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. | ||
+ | %# = User's unique ID | ||
+ | %A = User's real name (spaces are replaced by an underscore) | ||
+ | %B = User's real name (with spaces) | ||
%C = The current user's codepage (CP437 or UTF8) (added 1.12 A39) | %C = The current user's codepage (CP437 or UTF8) (added 1.12 A39) | ||
- | %N = The current node number (added 1.12 A34) | ||
%H = The current socket handle (added 1.12 A34) | %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 = The node's temp directory | ||
- | %# = User' | + | %R = User' |
%T = User's time left in minutes | %T = User's time left in minutes | ||
%U = User's handle (spaces are replaced with an underscore _) | %U = User's handle (spaces are replaced with an underscore _) | ||
Line 209: | Line 218: | ||
**FU - Upload a file** | **FU - Upload a file** | ||
- | | + | |
Description: | Description: | ||
| | ||
Line 232: | Line 241: | ||
In the event a protocol is chosen from the stoneage, like Xmodem, then | In the event a protocol is chosen from the stoneage, like Xmodem, then | ||
| | ||
+ | |||
+ | If the /current option is specified, Mystic will attempt to upload to | ||
+ | the current file base even if a specific file base has been configured | ||
+ | for uploads | ||
**FV - View contents of a file** | **FV - View contents of a file** | ||
Line 420: | Line 433: | ||
using the TELNET protocol. | using the TELNET protocol. | ||
/port option is not provided then the default port of 23 will be used. | /port option is not provided then the default port of 23 will be used. | ||
+ | |||
+ | ----- | ||
+ | ===== MESSAGE BASES ===== | ||
+ | |||
+ | The following menu commands related to the Message Bases and reading/ | ||
+ | |||
+ | **MN - Scan for New Messages** | ||
+ | |||
+ | Data: /G /P /M /NOLR /NOFROM /NOREAD | ||
+ | Description: | ||
+ | for modifiers to the default behavior. | ||
+ | is provided, Mystic will scan for all new messages in the user's current | ||
+ | | ||
+ | |||
+ | If /P is provided in optional data, Mystic will only scan for personal | ||
+ | | ||
+ | |||
+ | If /G is provided in optional data, Mystic will scan all message bases | ||
+ | in all groups. | ||
+ | |||
+ | If /M is provided in optional data, Mystic will forced the user to read | ||
+ | the new messages (mandatory read). | ||
+ | |||
+ | If /NOLR is provided, Mystic will not update the user's "last read" | ||
+ | | ||
+ | |||
+ | The following commands augment the behavior of the /P personal scan | ||
+ | | ||
+ | |||
+ | If /NOFROM is provided, Mystic will only look at the To field when | ||
+ | | ||
+ | |||
+ | If /NOREAD is provided, Mystic will not show messages that have been | ||
+ | | ||
+ | |||
+ | **MX - Post text file to message base** | ||
+ | |||
+ | Data: < | ||
+ | Description: | ||
+ | a file up to 10,000 lines to be posted and will automatically split | ||
+ | them into multiple posts of 1000 lines each if the post is more than | ||
+ | 1000 lines (including automatically appending a message count to the | ||
+ | end of the subject ie: (1 of 3)" | ||
+ | |||
+ | If you want to post an ANSI file, it should be saved with a 79 column | ||
+ | width using a capable ANSI editor. | ||
+ | can save an ANSI file properly formatted for message posting by | ||
+ | | ||
+ | |||
+ | The optional data field is required for this to work, except for the | ||
+ | | ||
+ | | ||
+ | |||
+ | The < | ||
+ | | ||
+ | | ||
+ | |||
+ | The <Base ID> is the Message Base ID as found in the Message Base Editor | ||
+ | |||
+ | < | ||
+ | |||
+ | < | ||
+ | |||
+ | < | ||
+ | |||
+ | | ||
+ | | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | | ||
menu_commands.txt · Last modified: 2023/01/20 02:39 by g00r00