KSCTowerNetwork v1.0.1 - In-game server selection

Pilots can now enter the operator's server address directly in Tower login. The client remembers it; no settings-file edit or server-specific Client ZIP is required.

What's changed

• Enter a hostname, IP address or full HTTP(S) URL in the in-game login window. Bare hostnames/IPs use HTTPS; root URLs automatically use /v1.
• Log out and reopen Tower login to change servers. Changing the API clears the old login and room, then reconnects the bundled voice bridge after signing in.
• An optional advanced web desk address supports operators whose website and API use separate addresses.
• Updated installation instructions and focused address/persistence tests.

Install or upgrade

Download KSCTowerNetwork-Client-1.0.1-win-x64.zip. Close KSP, back up personal PluginData/settings.cfg and auth.cfg, then extract the ZIP's GameData folder into the KSP directory and preserve those personal files. Install ModuleManager separately. The portable Node runtime is included.

Launch KSP and click the Tower toolbar button. Enter your operator's address and account credentials. If already signed in, use Log out and reopen the toolbar window to change the server. For an HTTP server, use the full http://host:port URL. Controllers continue to use the operator's website.

Existing server operators do not need to redeploy solely for this client UI. The matching Server ZIP is included for fresh installations or separate server updates; follow its hosting instructions. KSCTowerNetwork.ckan and SHA256SUMS.txt describe the new downloads. CKAN catalog inclusion is separate and is not claimed.

Verification and acceptance

Built from a clean source commit with Node 24.22.1. Backend: 238 passed, 4 skipped. Web: 120 passed, 1 skipped. Bridge: 16 passed. Server/release checks: 11 passed. Voice/ACARS invariants, production builds and plugin checks passed, including 37 server-address checks and 31 tests using the real KSP ConfigNode parser.

This remains a prerelease. Live in-game KSP pairing/telemetry and two-participant LiveKit microphone/PTT/audio acceptance have not been verified for this release. Automated and archive checks do not establish those live paths.

Both extracted ZIPs matched all file manifests and SHA256 sums (1,158 client files and 326 server files). The extracted DLL reports 1.0.1.0 and contains the new Server address UI. The packaged Node 24.22.1 runtime successfully imports the LiveKit Windows native binding.

Source commit: b745a15aa6e7c0acd9dea95f6926356129a7fbef.

Client SHA256: 0a7f113a14ed1af79a6ed7123b0e767b64972cbd489cedbf1b6f0ec6186d368c.

KSCTowerNetwork v1.0.0 - Client and Server Preview

Initial client and server prerelease for KSCTowerNetwork. Controllers use an operator's website; pilots install the Windows client. Each player retains their own KSP physics and save.

Downloads

• KSCTowerNetwork-Client-1.0.0-win-x64.zip — KSP plugin, portable Node 24.22.1, patched LiveKit voice bridge and Windows native dependencies. Includes installation instructions and license notices. Install ModuleManager separately; optional integrations are described in INTEGRATIONS.md.
• KSCTowerNetwork-Server-1.0.0.zip — built backend and website, locked dependency manifests, Linux/Windows launchers, deployment templates, hosting documentation and optional chart installer. Requires Node 24.22.1 or newer Node 24 with npm, MariaDB, Redis, an HTTPS reverse proxy and LiveKit. Database/cache/LiveKit services are not bundled.
• KSCTowerNetwork.ckan — separate client metadata with the final download URL, size and hashes. CKAN catalog submission/dependency review is separate; this release does not claim catalog inclusion.
• SHA256SUMS.txt — hashes of both ZIPs and CKAN metadata.

The automatic GitHub source archives are source downloads, not built player installations.

Install

Pilot: close KSP, extract the client ZIP's GameData folder into the KSP directory, and configure PluginData/settings.cfg with your operator's host, port, TLS setting and API path. Defaults are local loopback, not a hosted public tower. Preserve your personal settings.cfg and auth.cfg when updating. No separate Node installation is needed on a pilot's PC.

Server operator: extract the Server ZIP into a fresh directory. From KSCTowerNetwork-dev run bash deploy/server.sh install on Linux or powershell -File deploy/server.ps1 install on Windows. Configure backend/.env.production, including an owner password hash and your own database/Redis/LiveKit secrets. Start using the corresponding start command. Serve web/dist through an HTTPS proxy with SPA fallback and /v1 API/WebSocket proxying; see the included SERVER_HOSTING.md. Both backend and website are prebuilt for a single public origin. Install production dependencies on the host OS; Windows node_modules are not shipped to Linux.

Back up the database, backend/data and private production env/JWT secret before server updates. Charts, fonts and player-installed planet textures are optional and excluded from these downloads. KSP assemblies and other mods are not redistributed.

Validation and remaining acceptance

Both archives were built from clean tracked-source staging with locked dependencies, fresh backend/web/plugin/bridge builds, automated tests, voice/ACARS invariant checks and plugin pure logic checks. Extracted archives were checked against their per-file SHA256 manifests. The bundled Windows Node and LiveKit native library were checked directly.

The extracted server was installed and started on Linux with real isolated MariaDB and Redis. Checks covered schema initialization, health, owner login, a secure session cookie, owner access controls, invite persistence, an HTTPS nginx proxy, SPA deep-link fallback, built JS/CSS entry assets and the empty optional-chart manifest.

This remains a prerelease: live in-game KSP pairing/telemetry and two-participant LiveKit microphone/PTT/audio acceptance have not been verified for this release. Container and native-import checks do not establish those live paths. Public DNS/TLS provisioning and Windows service supervision remain the operator's deployment work.

Source commit: fc4b7fa. Automated results: 238 backend, 120 web, 16 bridge and 11 launcher/archive tests passed; five optional tests skipped. Plugin pure checks passed.