I've updated the latest prealpha builds. For whoever was asking about the Golded export that feature is in these latest builds.
--- Mystic BBS v1.12 A47 2020/10/13 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (1:129/215)
Are you using GoldEd now for your editor?
Are you using GoldEd now for your editor?
Mystic has a "Golded-like" interface built into it so I don't use
Golded. Someone else had requested the ability to export a Golded configuration so I added it for them!
I've updated the latest prealpha builds. For whoever was asking about
the Golded export that feature is in these latest builds.
I tried the w32 Mys112a47 and all seemed to go well, however, when I logged in my mainhdr.ans did not display. Checked in settings for
Main Menu and it was correct |DFmainhdr was there and the file mainhdr.ans was located in text folder of default theme. I have no
other themes. In fact all my *hdr files do not display the header
except the Filehdr is displayed.
I tried the w32 Mys112a47 and all seemed to go well, however, when I logged in my mainhdr.ans did not display. Checked in settings for
Main Menu and it was correct |DFmainhdr was there and the file mainhdr.ans was located in text folder of default theme. I have no other themes. In fact all my *hdr files do not display the header except the Filehdr is displayed.
I don't remember how old A46 is now, or when the change was made, but you might
want to try adding another pipe after, ie: |DFmainhdr| and see if that works.
Regards,
Nick
I tried the w32 Mys112a47 and all seemed to go well, however, when I loggedin my mainhdr.ans did not display. Checked in settings for Main
I don't remember how old A46 is now, or when the change was made, but
you might want to try adding another pipe after, ie: |DFmainhdr| and see if that works.
I tried the w32 Mys112a47 and all seemed to go well, however, when I logged in my mainhdr.ans did not display. Checked in settings for Main Menu and it was correct |DFmainhdr was there and the file mainhdr.ans was located in text folder of default theme. I have no other themes. In fact all my *hdr files do not display the header except the Filehdr is displayed.
I don't remember how old A46 is now, or when the change was made, but
you might
want to try adding another pipe after, ie: |DFmainhdr| and see if that works.
I tried the w32 Mys112a47 and all seemed to go well, however, when I loggedin my mainhdr.ans did not display. Checked in settings for Mai
When did you download the A47 version? It gets updated as much as
several times a day (the latest is today). If you had an older version that happened to be downloaded the day I was testing the new display system you might see bugs.
The headers in the default install are definately working for me on all platforms.
I tried the w32 Mys112a47 and all seemed to go well, however, when I logged in my mainhdr.ans did not display. Checked in settings for Main Menu and it was correct |DFmainhdr was there and the file mainhdr.ans
was located in text folder of default theme. I have no other themes.
In fact all my *hdr files do not display the header except the Filehdr
is displayed.
-+- Mystic BBS v1.12 A48 2022/06/03 (Windows/32)^^^^^^^^^^^^^^
-+- Mystic BBS v1.12 A48 2022/06/03 (Windows/32)^^^^^^^^^^^^^^
Do you not publish the prealphas anymore?
-+- Mystic BBS v1.12 A48 2022/06/03 (Windows/32)^^^^^^^^^^^^^^
Do you not publish the prealphas anymore?
I will I have just been too busy to test the latest changes.
In general it works this way:
1) Create new features
2) Test new features
3) Release a pre-alpha
This year has been incredibly busy for me outside of the BBS scene so features have been slower. The latest changes I made are related to e-mail password resets and e-mail validation and I need to connect to an SMTP server to test them before I release a new build.
I can build a prealpha and release it anyway if the community would
prefer but these features are untested.
g00r00... About a month or so ago I was requesting that you have mystic auto generate message areas and use a random Hex number when making message base names.
Please can you add this in the next pre-alpha
g00r00... About a month or so ago I was requesting that you have myst auto generate message areas and use a random Hex number when making message base names.
Please can you add this in the next pre-alpha
I didn't forget about you, sir!
In the next build I changed it to fix the problem where it could create a double period that you mentioned. But I also changed how it works to allow for a random hex too:
+ MUTIL ImportEchoMail now has a "dos_filename" option that can be used
to create JAM filenames in the DOS 8.3 file format. Valid options are:
0 = Do not use 8.3 filename (uses echotag for filename)
1 = Use shortened 8.3 filename (trimmed based on the echotag name)
2 = Use random hex 8.3 filename
1) Create new features
2) Test new features
3) Release a pre-alpha
This year has been incredibly busy for me outside of the BBS scene so features have been slower. The latest changes I made are related to
Thanks for what you're doing when your able. I feel the same way about busy outside of BBS scene life, so can totally relate.
I will I have just been too busy to test the latest changes.
1 = Use shortened 8.3 filename (trimmed based on the echotag
name)
Whats happend if MUTIL import two echos with similars names? For example:
ECHOMAIL_ECHOTAG trim in ECHOMAIL
ECHOMAIL_ECHOTAG2 trim in? ECHOMAI2?
I still have a feature request or two of yours in the pipeline too I
hope to get to soon!
--- Mystic BBS v1.12 A48 2022/06/03 (Windows/32)
| Sysop: | Gate Keeper |
|---|---|
| Location: | Shelby, NC |
| Users: | 792 |
| Nodes: | 20 (0 / 20) |
| Uptime: | 109:16:21 |
| Calls: | 12,362 |
| Calls today: | 1 |
| Files: | 5,294 |
| D/L today: |
113 files (483M bytes) |
| Messages: | 576,917 |