internal code prefix, access requirements and other options.
you can't do that with the current formats that are left over, right?
Nope, but you can by simply copy/pasting the msgs.ini entries (which
don't have the same ordering and extensibility issues that the
subs.txt entries did).
Re: Importing Message Areas
By: Digital Man to MRO on Thu Apr 16 2026 10:18 am
internal code prefix, access requirements and other options.
you can't do that with the current formats that are left over, right?
Nope, but you can by simply copy/pasting the msgs.ini entries (which don't have the same ordering and extensibility issues that the
subs.txt entries did).
i could do that or something else, but being able to export/export subs.txt was useful for people that ran msg networks or sysops who want to carry them.
I never had any problem with the subs.txt format and i used it a lot over the years. i like the newer .ini formats for things in most cases, but i'm surprised you ripped that out.
subs.txt and dirs.txt were missing newer sub-board/directory fields
and the format was kind of dumb (like all door drop file formats).
I'll add some better import/export formats that'll serve the same
purpose, but better.
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,126 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 52:03:48 |
| Calls: | 14,414 |
| Calls today: | 2 |
| Files: | 186,401 |
| D/L today: |
11,542 files (3,178M bytes) |
| Messages: | 2,548,959 |
| Posted today: | 1 |