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,044 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 47:02:25 |
| Calls: | 500,943 |
| Calls today: | 6 |
| Files: | 109,374 |
| D/L today: |
7,098 files (1,223M bytes) |
| Messages: | 304,061 |