Multiplayer in Astra Protocol 2?
Astra Protocol 2 Patch Notes — May 14, 2026
Aggregated from Steam, cross-tracked with Battle.net coverage on GamePatchNote.
Attention Captains,
This is not an erroneous transmission.
The current beta, Astra Protocol 2 (v2.1.1), contains an early prototype of multiplayer functionality - though not the kind you may be expecting.
We are experimenting with remote terminal support, allowing a second user to connect to the pilot's machine and issue commands through a terminal interface. The remote player has access to a slightly reduced command set, whilst the primary player retains full control. This opens the door to cooperative roles - perhaps one captain handles weapons whilst the other focuses on evasive manoeuvres?
How It Works?
A remote user connects to the host machine using a terminal. At present, the system uses telnet on port 23, which opens automatically when the game launches. Port configuration is not yet available but planned before a full release.
For example, on Windows you can connect by entering:
telnet localhost
Once connected, the user will receive log output and can enter commands as normal. Some commands, such as SELF DESTRUCT or those that manipulate the UI - are deliberately made unavailable.
This should support any terminal. ANSI-compatible terminals provide the best experience, but even older or 'dumb' terminals should work. Mobile terminal apps are also supported.
This has only been tested on a local network so far.
We're still in the early stages of development and would greatly value feedback. Tell us how it feels, what roles you take on, and whether this feature should make it into a full release.
Known Issues, Changes and Areas For Improvement
Input behaviour has changed. The default terminal input system has been updated, and features like tab completion and cursor-key history are not yet implemented.
Separate logs per terminal. Each terminal maintains its own log, alongside a global log. This prevents one user's actions interfering with another's. Some commands (e.g. DISPLAY DIAGNOSTICS) have been redirected to a local log. As a result, external printing and voice readouts are currently apply only to the global log.
Only one remote terminal is supported. If the remote terminal disconnects for any reason, the application must be restarted before another connection can be made. Additionally, you cannot have more than one remote user connected.
Currently it only operates over port 23 and as soon as the application begins. Control of this will be moved to the settings menu.
Please jump onto the beta and try out this new functionality. We're eager to hear how you use it and what kind of crew roles emerge among your fellow captains.