When a mystic session times out whilst waiting on a "[■] More: (Y)es, (N)o, (C)ontinuous?" prompt, it appears to dump the pending list's contents to the client before terminating.
i've noticed this sort of thing as well. if you idle timeout on a yes/no prompt for example, let's say one for "read this email?" it will dump
the contents before closing the connection. your next login you will
find (or perhaps forget!) your actually-unread message.
not really sure in what way it could be fixed. i'd almost prefer a "ya still there?" message like sync does it as well. i actually ended up writing a do-nothing door with no idle timeout so i could load that when i'm sort of back/forth in modding.
oddly enough you can get booted when in the sysop menus too. kinda
creeps me out thinking you might make a ton of prompt edits only to come back to the unknown next login ;)
Do you know how I may contact Mystic's developer?
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,023 |
Nodes: | 17 (0 / 17) |
Uptime: | 25:44:36 |
Calls: | 503,193 |
Calls today: | 17 |
Files: | 219,695 |
D/L today: |
16,365 files (1,826M bytes) |
Messages: | 441,214 |
Posted today: | 3 |