TID: Mystic BBS 1.12 A49
MSGID: 1:129/215 16c67357
REPLY: 4593.fido_mystic@1:124/5016 283ea863
TZUTC: -0500
 RS> I am downloading via the BBS, not with FTP.  20 For doesn't have a date
 RS> set in the QWK menu.  I am trying to leave it 'broken' so paulie can see
 RS> what is doing the next time I can catch him when we are both on the BBS.

Gotcha.  There should be a set message date on the message menu and it works
for both QWK and your own BBS last read pointers.

Here is my theory:

When you download a QWK packet, Mystic starts at your last read message + 1.
When the last read was updated, it was setting it as last read + 1.  When
Mystic's message base packer was packing everything, it found that the last
read message was an invalid message number and was resetting it to 0.

I do think its fixed in the "Paulie" build but we'll see.  I didn't start with
a reproducable issue on my end so I can't be certain.

I've also switched to using a mixture of MultiMail QWK and online Mystic to
see if I can catch the "fixed" version doing the same stuff.  I'll be packing
the message bases daily as well.

We'll get it sorted out and a new stable release out once its done and Paulie
confirms any issues he has regarding file bases is okay!

... Kilometers are shorter than miles. Save gas, take your trip in kilometers

--- Mystic BBS v1.12 A49 2023/01/31 (Windows/64)
 * Origin: Sector 7 * Mystic WHQ (1:129/215)
SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 120/340 616 123/10
SEEN-BY: 123/131 124/5016 129/215 305 153/757 7715 154/10 30 40 50
SEEN-BY: 154/700 203/0 218/700 840 220/90 221/0 1 6 242 360 226/18
SEEN-BY: 226/30 70 227/114 201 229/110 111 112 113 114 206 275 307
SEEN-BY: 229/310 317 400 424 426 428 452 470 550 664 700 230/0 240/1120
SEEN-BY: 240/5832 266/512 280/464 5003 282/1038 292/854 8125 301/1
SEEN-BY: 317/3 320/219 322/757 335/364 341/66 234 342/200 396/45 423/81
SEEN-BY: 460/58 633/280 712/848 770/1 2320/105 3634/12 4500/1
PATH: 129/215 154/10 280/464 221/1 6 229/664 426