One thing that's a little hidden in the new A35 alpha is you have to move or delete your old nodespy.phn file (I moved mine to onodespy.phn), as g00r00
has changed the structure and included ssh and such. Ports are now part of
the phonebook instead of tacked on to the address as they were. The .ini is
the same. Nodespy if run with the old phonebook with a port on the address
will just drop out when you try to 'dial'.

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)

are we seeing these changed so we can enjoy the sdl2.dll soon for cp437 to match with netrunner? ;)

|08 .|05ú|13ù|15Dr|07e|08am Ma|07st|15er|13ù|05ú|08.
|08 øù|05ú|13ùø |13øù|05ú|08ùø
|11 DoRE|03!|11ACiDiC|03!|11Demonic |08[|15dreamland|09.|15darktech|09.|15org|08]

--- Mystic BBS v1.12 A35 (Windows/64)
* Origin: |08--[|15!|07dreamland BBS dreamland.darktech.org (21:1/163)

One thing that's a little hidden in the new A35 alpha is you have to
move or delete your old nodespy.phn file (I moved mine to onodespy.phn),

No you shouldn't have to delete anything. It will still load up, its just
that if you use a custom port on a particular entry, you just have to edit it to set the port and remove the port from the address.

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

are we seeing these changed so we can enjoy the sdl2.dll soon for cp437
to match with netrunner? ;)

I suppose I could make a SDL version.

I've actually been considering picking up the Mystic2demo again soon and
doing more work there. That has an SDL2 option.

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

On 08/25/17, g00r00 said the following...

One thing that's a little hidden in the new A35 alpha is you have to move or delete your old nodespy.phn file (I moved mine to onodespy.ph

No you shouldn't have to delete anything. It will still load up, its
just that if you use a custom port on a particular entry, you just have
to edit it to set the port and remove the port from the address.

Ah, I did have to. I just looked at the nodespy.phn (I do have it), it has a large number of entries that just show like:
[100]
name=
address=
user=
pass=
statusbar=1
last=00/00/00
calls=0

That is the last entry. nodespy dropped every time I tried an entry, I had to move it out and start again. I did use another system and that was fine - so only one case so far. Perhaps the original came from an early netrunner? It worked till A35, that was the first drop, A34 was OK.

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

Quickie,

Noticed this with the updates, but unable to connect using SSH ipv4/ipv6
using nodespy on linux. Telnet both ipv4/ipv6 work still, this might be some changes that where made to the mystic core code that where not made into nodespy? =P

Cheers!

|15:|07: |15pequito |08<|07<|14.|11PH|15EN|11OM|14.|07>|08> |07:|15: |15:|07: |02telnet://|10twinklebbs.net |07:|15:

--- Mystic BBS v1.12 A43 2019/02/08 (Linux/64)
* Origin: Twinkle BBS # (21:1/126)

Noticed this with the updates, but unable to connect using SSH ipv4/ipv6 using nodespy on linux. Telnet both ipv4/ipv6 work still, this might be

I've added this to my list of things to look at, thanks!

--- Mystic BBS v1.12 A43 2019/02/08 (Linux/64)
* Origin: Sector 7 (21:1/108)