FLIGHT MANUAL / 13 · SUPPORT
FAQ
The short version: KMS is a private-first integrated suite with explicit installation and local mission operations.
Is this a mod pack?
Operationally, it is an integrated suite: curated components, KMS-authored code and assets, compatibility patches, a shared installer, unified documentation, and one test/release process. Redistribution packaging remains constrained by each third-party license.
Does it require CKAN?
No. KMS has its own installer and release manifest. A future metadata bridge may help users acquire redistributable dependencies, but CKAN is not the runtime, authoring environment, or source of KMS integration logic.
Does the website control KSP?
No. Live telemetry and control stay in the KSP process on loopback by default. The website provides public information, documentation, authentication, administration, and release downloads.
Do performance modes reduce quality?
Not by default. KMS first removes duplicate work, allocation churn, log storms, unnecessary graph recomputation, and unsafe polling. Visual reductions are explicit profiles, not hidden optimizations.
Can the suite be released publicly?
KMS-owned code and assets can be distributed under their chosen license. Third-party components must be classified as bundleable, official-download-only, or local-archive-only. The installer and catalog enforce that acquisition policy rather than assuming private-use permission applies to redistribution.
Is the passkey single-use?
No. The invitation link is consumed once to prove enrollment authorization. The passkey created during enrollment is reusable for sign-in until access or that credential is revoked.
What does the download install?
The single KMS Installer executable already contains the KMS release payload. It validates a supported KSP 1.12.5 destination, automatically acquires pinned official dependencies, verifies every declared hash, preserves player data, creates backups, installs the suite, and writes a receipt. It never installs KSP itself.
Who can access /admin?
Only accounts with owner, admin, release-manager, or support authorization can enter the control plane. Server-side role checks protect both the page data and every administrative API action.