Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    MYSTIC    |    Mystic support echo    |    16,010 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 14,246 of 16,010    |
|    g00r00 to LEE WESTLAKE    |
|    Re: MPL Timer Clarification    |
|    18 Jan 22 12:33:27    |
      TID: Mystic BBS 1.12 A48       MSGID: 1:129/215 c5c7b4d9       REPLY: 2:250/6 a2603802       TZUTC: -0500        LW> Function TIMER : LongInt               LW> As such, may I assume the timer value rolls over from 86399 to 0 at        LW> midnight? If so, doesn't the delta between two readings require        LW> modulation in order to accommodate successive readings across this        LW> boundary?              Yes both Timer and TimerMin would roll over at midnight and probably aren't       all that useful for timing despite their function names lol.              If you want to count seconds independant of a midnight rollover, you can use       the "DateUnix" function which returns the number of seconds since Jan 1, 1970       and has no rollover.              ... Honk if you love peace and quiet!              --- Mystic BBS v1.12 A48 2022/01/14 (Windows/64)        * Origin: Sector 7 * Mystic WHQ (1:129/215)       SEEN-BY: 1/120 123 15/0 18/0 90/1 105/81 106/201 116/116 120/340 616       SEEN-BY: 123/0 10 25 40 115 131 180 190 200 755 129/215 305 135/300       SEEN-BY: 138/146 153/250 7715 154/10 30 40 50 700 220/80 90 222/2       SEEN-BY: 226/18 30 227/114 201 229/110 307 310 317 400 424 426 428       SEEN-BY: 229/452 550 664 700 6502 240/1120 5832 249/206 250/1 266/512       SEEN-BY: 275/100 282/1038 292/854 299/6 300/4 301/1 317/3 320/219       SEEN-BY: 322/757 342/11 200 396/45 633/280 640/1321 712/848 2320/105       SEEN-BY: 3634/0 12 15 27 50 119       PATH: 129/215 154/10 3634/12 153/7715 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca