I have a very old setup I am working on and would like to know if there is anyway to have Mystic not hangup/close the socket after running a MPL using
-X -U -P and -TID# from the command line.

I suppose it would be close to running a standalone MPL as a sort of door, although that's not what I am doing, but it would be the same.

At the moment the MPL runs, data is set across the socket and it all works. When I exit the MPL, it does not exit and leave the socket alone, it kills
the socket for me. Something I would like to avoid in this situation.

I understand I am probably abusing this -X function as it was not written to
do this, but if there is a way I would love to know as it would save me tons
of time. If anyone has any ideas I'll try them.

Thanks.

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Archaic Binary (46:1/118)

I understand I am probably abusing this -X function as it was not
written to do this, but if there is a way I would love to know as it
would save me tons of time. If anyone has any ideas I'll try them.

Yes, you are using it in probably an unintended way. :)

I am not opposed to adding something that could keep the socket safe, but I would have to look at the code to be sure that its feasible to do without major code change.

I can't say for sure if its easy to do or not, if its a simple implementation then I would do it for sure.

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: d i s t o r t i o n // d1st.org (46:1/145)