Subj : Re: Synology Docker Mystic Test
To   : opicron
From : fusion
Date : Mon Feb 10 2025 05:54 pm

On 10 Feb 2025, opicron said the following...
 
 op> I had a look, thank you for the lead! Not sure how I would get this to
 op> work. However, you did give me an idea. If I check TERMTYPE in Mystic
 op> connect.mps I can kick the connection if termtype is ASCII. Which is the
 op> usual one for the bots it seems.

yeah that's what i currently do. just dump a message "this bbs requires an ansi capable terminal," list off a few of them and hangup. on a47 though..

ascii.mps:

Begin
  DispFile('answer') // replacing prompt 0 .. duno how your login flow goes
                     // this either shows a greeting logo or an ascii logo
                     // answer.ans or answer.asc
  If Graphics = 0 then Begin
    Write ('|CR                 USE mTelnet');
    Write ('|CR                BYE ASCII USER');
    HangUp;
    Exit;
  End;

  Write('|PA');

  DispFile('preuser');    // ansi with user/pass boxes or whatever
  Write('|[X09|[Y14 ..'); // position input, change input colors, etc
End;

compile mpl and replace prompt 0 with !ascii :)

there's probably a lot you could cram in prompt 0

 op> Thx for some giving some energy, I changed my reset scripts to send me
 op> more  detailed information through Slack and I am debugging the issue
 op> which occurs.

right on :) yeah just kinda sucks to see mystic in limbo needing workarounds..

--- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
 * Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)

.