Hey all,

Checking on things and realized I fell behind again. Way behind. Upgraded from A38 to A43 and shooting a test message out to make sure things are still working.

Since none of the versions in between were available to my knowledge, I used the 'upgrade' executable from A43 and copied binaries, scripts, and newly
added stuff straight from A43 to A38, but followed all instructions for every version upgrade in between (adding strings, copying new files over, etc). Here's hoping that was ok. ;)

Looks like I have a few minor things to tweak since some new strings were
added and/or modified. Along with an odd continue prompt in my last caller screen now, but that likely doesn't have anything to do with Mystic. May just be ye olde plague of the 79 vs 80 columns thing that wasn't an issue in previous versions.

Otherwise as far as FSX goes, were there any new echos added I should know about? I'm sure I can take a peek at the infopack in my inbound either way.

Anyway, hello! *waves*

Regards,
Nick

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

On 13 Apr 2019, Accession said the following...

Checking on things and realized I fell behind again. Way behind.
Upgraded from A38 to A43 and shooting a test message out to make sure things are still working.

It's looking good from here.. :)

Ttyl :-),
Al

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: The Rusty Point - Penticton, BC Canada (21:4/106.1)

On 13 Apr 2019 at 08:41a, Accession pondered and said...

@TID: Mystic BBS 1.12 A43
@MSGID: 21:1/200 0f5f7e58
@PATH: 1/200 100
Hey all,

Hey there :)

Checking on things and realized I fell behind again. Way behind.
Upgraded from A38 to A43 and shooting a test message out to make sure things are still working.

Yep got you 5 x 5 good sir.

Since none of the versions in between were available to my knowledge, I used the 'upgrade' executable from A43 and copied binaries, scripts, and newly added stuff straight from A43 to A38, but followed all
instructions for every version upgrade in between (adding strings,
copying new files over, etc). Here's hoping that was ok. ;)

Looks like so far so good :)

Looks like I have a few minor things to tweak since some new strings were added and/or modified. Along with an odd continue prompt in my last
caller screen now, but that likely doesn't have anything to do with Mystic. May just be ye olde plague of the 79 vs 80 columns thing that wasn't an issue in previous versions.

Yep check whatsnew.txt for a summary. There's been a ton of stuff that g00r00 has added since your last update.

Otherwise as far as FSX goes, were there any new echos added I should
know about? I'm sure I can take a peek at the infopack in my inbound either way.

MMmmm yeah there's been a 2-3 so have a look at the infopack and areafix away if you want them :)

Best, Paul

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 14 Apr 2019, Avon said the following...

Looks like so far so good :)

Well that's good to hear. Nothing like breaking something and it taking long hours to figure it out and fix it. ;)

Yep check whatsnew.txt for a summary. There's been a ton of stuff that g00r00 has added since your last update.

So it wasn't in my last callers, but my who's online instead. I misspoke last go-round. I'm guessing it has something to do with the fact that I
encapsulated the "username" MCI code in a $R padded doohicky, and left the "action" MCI code without any padding.

Since I still haven't read the whatsnew (I plan to at some point), I'm
assuming something here was changed so that if you justify one thing on the line, you should probably justify everything else on the same line so that it stays within the 80 character limit... or something.

Just looks like once the first node line is displayed, it sends the
continue (Y/N) prompt because the line may wrap due to too many characters. Then the rest of the node lines display fine. I'll fix it when I get a chance.

MMmmm yeah there's been a 2-3 so have a look at the infopack and areafix away if you want them :)

Ok thanks for the heads up. I'll take a look.

Regards,
Nick

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

On 15 Apr 2019, Accession said the following...

Since I still haven't read the whatsnew (I plan to at some point), I'm assuming something here was changed so that if you justify one thing on the line, you should probably justify everything else on the same line
so that it stays within the 80 character limit... or something.

Just looks like once the first node line is displayed, it sends the continue (Y/N) prompt because the line may wrap due to too many characters. Then the rest of the node lines display fine. I'll fix it
when I get a chance.

Following up on this: I didn't see anything in whatsnew.txt regarding this,
and wrapping the "action" MCI in a $R padded MCI doesn't change anything.

Basically, I have a single ansi screen that displays who's online. At the beginning of the ansi is CL and PO to clear screen and turn pause off. At the end of the ansi I have a "goto" MCI to go to a certain X/Y coordinate on the screen to start displaying who's online. After the first node line is
displayed (the one with me as a user and my action, prompt 139) I get a
"More: Y/N/C" prompt on the very next line when no CR is defined anywhere including said "More" prompt. When I hit enter, all the rest of the nodes
with "Waiting for connection.." (prompt 268) are displayed fine, and then goes to x01y24 for a pause prompt which is defined in my footer prompt (prompt 140) to do so.

So something odd is happening that wasn't happening before, and can't see any reason as to why a "More: Y/N/C" prompt is occurring. The ansi always was 79 columns wide.

Regards,
Nick

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)