TID: Mystic BBS 1.12 A48
MSGID: 1:129/215 f6cfc1ee
REPLY: 1:317/3 624c70b2
TZUTC: -0400
 BP> This is returning '0' to the log file when logging in from the command
 BP> line. I wonder if possibly adding a servertype for local login might be
 BP> simpler than doing the 'local' boolean. Perhaps adding servertype of 3
 BP> for local.

I don't know what OS or version you're using but it seems to be working from
here I just tested it in Windows A48 and Linux.  The simple test I did was
logged in and tried to download the BBS list and on both OSes it says "Local
mode:" and asked me to save.

Are you sure you're logging in with -L?  Make sure you're not setting the
value of Local anywhere in any MPL anywhere, otherwise that will change it for
the entire connection.

The ServerType that is used internally by Mystic for terminal services does
have a Local mode value.  They should be (as of A48 current releases):

0=telnet,1=rlogin,2=ssh,3=modem,4=local,5=other

5 is left open broadly so (for example) someone could use that as a packet
radio type if they wanted to and configure server type 5 to show up as "RADIO"
in the callers list (or whatever else they want).

... No honey, I can't eat with the family. My computer gets lonely!

--- Mystic BBS v1.12 A48 2022/04/03 (Windows/64)
 * Origin: Sector 7 * Mystic WHQ (1:129/215)
SEEN-BY: 1/120 123 14/5 15/0 18/0 90/1 105/81 106/201 116/116 120/340
SEEN-BY: 120/616 123/0 10 25 115 131 180 200 755 129/215 305 330 331
SEEN-BY: 135/300 138/146 6502 153/7715 154/10 30 40 50 700 218/700
SEEN-BY: 220/90 222/2 226/18 30 227/114 201 229/110 206 307 310 317
SEEN-BY: 229/400 424 426 428 452 550 664 700 240/1120 5832 250/1 261/38
SEEN-BY: 266/512 275/100 1000 282/1038 292/854 299/6 300/4 301/1 317/3
SEEN-BY: 320/219 322/757 342/11 200 396/45 460/58 633/280 640/1321
SEEN-BY: 712/848 2320/105 3634/0 12 15 27 50 119 5020/1042
PATH: 129/215 154/10 3634/12 153/7715 229/426