For you people using the Pi, I just ran in to a problem likely caused by the hacking: multiple 'mystic' tasks holding on to the telnet ports.
I switched my Pi from mis binkp to mis2, but my telnet was dead!
Now I did killall mis mis2, set things up (which took a minute or two.
Then started it back up and nothing. Checked the logs and found:
---------- Mystic v1.12 A35 Tue, Sep 12 2017 (loglevel 3)
+ 10:02:26 MANAGER Starting 2 server(s)
+ 10:02:26 MANAGER Starting servers in DAEMON mode
+ 10:02:26 BINKP Listening on IPV4 port 24556 using interface "0.0.0.0"
+ 10:02:26 BINKP Listening on IPV6 port 24556 using interface "::"
+ 10:02:26 TELNET Unable to open IPV4 port: Error -1 (98 Address in use)
+ 10:02:26 TELNET Unable to open IPV6 port: Error -1 (98 Address in use)

Checked top and found two 'mystic' tasks. Tried to kill them, killall, then had to do kill -9 on the two PIDs to get it to work. Put things back and restarted OK this time. Now normally I don't see a 'mystic' task, but in
that case there were two 'mystic' tasks that I had to kill. Could be the hackers, they were tying up three ports and could have done who knows what. Anyway, not trying that from work again ;) I can never be sure of a reboot when I'm not there to watch it.
Just something to look for if mystic doesn't pick up on the Pi. Try 'top' to see what's running and check the mystic logs as well.

--- Mystic BBS v1.12 A35 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)