Message Variables

Introduction

In your custom ANSI files, there are several message variables that can be used to provide information about the system/current session/etc. Below is a list of these variables, and what they translate to.

All message variables can be left or right padded to a specific length, to help fit the text into a custom ANSI screen. For example, {DATE} might return "1/1/2007" or "12/31/2007". If spacing is important to your layout, the potential 2 character difference could throw things off. So you could use {DATE10} to force the date string to be 10 characters, so either "1/1/2007 " (note the 2 extra spaces on the right) or "12/31/2007" (no extra padding was required) would be returned. Similarly, you could use {10DATE} to have either " 1/1/2007" (2 extra spaces on the left) or "12/31/2007" (no padding required) returned.

If you specify a length that is less than the actual length of the string, instead of padding the string, it will be truncated to the requested length. For example, if a user named "LOCAL:ThisIsAReallyLongUserName" was on node 3, {NODE03USERNAME20} and {20NODE03USERNAME} would both return "LOCAL:ThisIsAReallyL".

Descriptions

  1. {BBSNAME}
  2. {DATE}
  3. {GSDIR}
  4. {NODE}
  5. {OPERATINGSYSTEM}
  6. {SYSOPEMAIL}
  7. {TIME}
  8. {TIMELEFT}
  9. {NODE##REMOTEINFO}
  10. {NODE##STATUS}
  11. {NODE##USERNAME}