Thank you for the feedback!!!!! Completely agree on all the above needed documentation.
reading it now and yes the connection docs are totally inadequate.
i'm at like 5% capacity working from home between multiple projects, but here's a brief description for now:
The main "Station" networking object that runs on a Terminal and Pilot receives connections on the port set in prefs.json as `MSGPORT` . The Pilots attempt to connect to the Terminal at the IP address set as `TERMINALIP` and the port set as `PUSHPORT` in prefs.json.
So if you set up your terminal to have static ip 192.168.1.100, say, and set its `MSGPORT` to 5000, then you would connect a pilot to it by setting its `TERMINALIP` and `PUSHPORT` to 192.168.1.100 and 5000.
They have to be able to "see" and connect to one another via IP, (don't have network tunneling implemented), so they should work if they have unique IP addresses assigned to them (eg. not behind a router that acts as a DHCP server like in home networks), for example I connect some Pis to my Terminal through my University's network without issue. More specifically the pilots have to be able to "see" the Terminal, but once they make the initial connection the Terminal can respond even if the pi doesn't have a fixed IP. I can try to help debug network issues if you tell me a bit more about your setup, but network discovery is a sorta general problem and Autopilot's is far from as robust as it could be -- once you get them connected the networking modules work alright though ;).
(dang i'll make sure the welcome_message gets packaged correctly but will make sure the program doesn't fail on account of my sentimental attachment to ye olde internet :p )