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.