perhaps i have a mismatch somewhere, because the default message target
is 'UNUSED' instead of 'All' ..
in ansimlst's case, i can get max ~17 lines between !1 and !2 before it starts scrolling the title ansi off the screen (seemingly enforcing a strange gap between !2 and the footer of the ansi)
in ansimlst's case, i can get max ~17 lines between !1 and !2 before starts scrolling the title ansi off the screen (seemingly enforcing a strange gap between !2 and the footer of the ansi)
problems with the template system ignoring the distance between the !1
and !2 settings on display. x/y coords for subject/to/etc for templates other than 25lines also no longer work correctly
-+- 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: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 104 |
Nodes: | 16 (0 / 16) |
Uptime: | 10:51:29 |
Calls: | 5,853 |
Files: | 8,496 |
D/L today: |
3 files (1,151K bytes) |
Messages: | 343,728 |