Hi,
I want to import some message areas into a group I have created.
I may be mistaken, but in older versions I could import them from the subs format. I do not see this as an import / export option any longer.
How would I convert a file I have in this format to another format that can be imported?
I would also like to mention that these groups will be part of a qwk network if this matters in any way.
How would I convert a file I have in this format to another format
that can be imported?
You have a subs.txt file? Exported from where? I guess it could be
converted or imported with some JavaScript (exec/importcfg.js
might serve as an example), but if the source of the subs.txt
was a Synchronet BBS v3.20 or later, then you could just copy the
areas from the source BBS's msgs.ini file instead.
Re: Importing Message Areas
By: Digital Man to Tom Moore on Tue Apr 14 2026 08:14 pm
How would I convert a file I have in this format to another format that can be imported?
You have a subs.txt file? Exported from where? I guess it could be converted or imported with some JavaScript (exec/importcfg.js
might serve as an example), but if the source of the subs.txt
was a Synchronet BBS v3.20 or later, then you could just copy the
areas from the source BBS's msgs.ini file instead.
That's too bad you took that out because it was a useful feature for running your own msgnetwork or joining one.
for running your own msgnetwork or joining one.
I plan to add a .ini and/or .json import option, but there's already
7 other import formats, certainly one of them would work almost
as well (?).
Re: Importing Message Areas
By: Digital Man to MRO on Wed Apr 15 2026 10:39 am
for running your own msgnetwork or joining one.
I plan to add a .ini and/or .json import option, but there's already
7 other import formats, certainly one of them would work almost
as well (?).
well with subs.txt format you could import the sub name, short name, internal code prefix, access requirements and other options.
you can't do that with the current formats that are left over, right?
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,113 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 492334:15:13 |
| Calls: | 14,238 |
| Files: | 186,312 |
| D/L today: |
3,196 files (1,044M bytes) |
| Messages: | 2,514,806 |