[snip]

If a connection is made when all of the nodes configured for telnet are
being used, MIS will attempt to send them the contents of busy.txt from
the Mystic DATA directory. If this file does not exist, it will simply
print "BUSY" to the terminal and disconnect them.

[snip]

This is an historical note but I did test it with the version in my tearline and it does not seem to be working. MIS is only printing BUSY and not the contents of the busy.txt I placed in the data directory. Can you confirm the code is still in place to do this and if not add it back in? :)

Best, Paul

--- Mystic BBS v1.12 A37 2017/12/23 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

This is an historical note but I did test it with the version in my tearline and it does not seem to be working. MIS is only printing BUSY
and not the contents of the busy.txt I placed in the data directory. Can

The new MIS doesn't send busy.txt, but I will add this in for the next pre-alpha.

--- Mystic BBS v1.12 A37 2017/12/27 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 12/27/17, g00r00 pondered and said...

The new MIS doesn't send busy.txt, but I will add this in for the next pre-alpha.

Tested and confirmed for v1.12 A37 Windows/32 compiled 2017/12/27 20:33:09

Thanks for restoring this.

Could you also take a look at dupeip.txt that would also print if in the same directory. I suspect that may be depreciated also?

Best, Paul

--- Mystic BBS v1.12 A37 2017/12/27 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Could you also take a look at dupeip.txt that would also print if in the same directory. I suspect that may be depreciated also?

No, dupeip.txt still shows and so does blocked. Only BUSY was removed.

--- Mystic BBS v1.12 A37 2017/12/27 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)