How ksp2redux/redux works
1. What this repository is
- This repo is not the game/mod code itself. It is the public-facing repository for KSP2 Redux, a community mod for Kerbal Space Program 2.
- The contents here are mostly documentation, release metadata, and contributor/support scaffolding.
2. Primary purpose
- The project goal, stated in the README, is to continue KSP2 development and implement the original roadmap.
- For an architecture diagram, this repo sits at the top-level project coordination layer, not the runtime mod layer.
3. Documentation boundary
- README.md is the main entry point for users and contributors.
- roadmap.md defines the planned feature scope.
- contributing.md defines how external contributors participate.
- These files together form the project’s public specification and collaboration boundary.
4. Release-channel metadata
- swinfo-beta.json and swinfo-stable.json are the only machine-oriented artifacts visible here.
- They likely act as release/update descriptors for beta and stable channels, supporting tooling that selects or identifies builds.
- Architecturally, this implies a split between beta testing and stable distribution.
5. Distribution and installation flow
- The README describes a manual install/update workflow driven by a separate tool: Ksp2Redux.Tools.Installer.exe.
- The installer consumes a patch file and applies it to a stock KSP2 installation, producing a separate Redux install directory.
- This implies the repo’s release process is centered around patch-based distribution, not in-place mutation of the original game folder.
6. External dependency boundary
- The mod depends on a specific base game version: stock KSP2 v0.2.2.0.
- The install process also varies by game distribution source: Steam, Epic Games Store, or Private Division.
- So the architecture has an external boundary around the upstream game install and platform-specific file layout.
7. User support and feedback loop
- The README directs bug reports to the in-game bug reporter and to a Discord server.
- This indicates a support loop that captures logs, screenshots, saves, and vessel files for troubleshooting.
- For a diagram, this is an important feedback channel from users back to the maintainers.
8. Beta release model
- The repo explicitly warns that beta builds are not meant to be updated in place; they require a fresh install.
- That means the release model is install-per-build, not incremental self-updating for beta.
- This is relevant to lifecycle architecture because it affects how releases, installers, and user environments interact.
9. Mod ecosystem boundary
- The README notes a transition from BepInEx to an integrated mod loader and changes to the modding API.
- That suggests the project is not just content delivery; it also includes a platform/runtime integration layer for other mods.
- However, no implementation code for that layer is present in this repo snapshot.
10. Repository scaffolding
- .github/ISSUE_TEMPLATE/* supports structured issue intake, mainly bug reports.
- images/logo.png is branding/supporting documentation only.
- Overall, the repo is organized around project communication, release coordination, and install metadata, rather than source modules or services.
Main entry points: README.md README · bug_report.md Bug report · swinfo-beta.json Beta info · swinfo-stable.json Stable info
Components 15
Public spec
Documentation and contributor-facing project boundary
- README · Main public entry point and install/support overview
README.md - Roadmap · Planned feature scope and project direction
roadmap.md - Contributing · Contributor workflow and participation rules
contributing.md
Release data
Machine-readable release and distribution descriptors
- Beta info · Beta channel build descriptor
swinfo-beta.json - Stable info · Stable channel build descriptor
swinfo-stable.json
Support intake
Issue templates and reporting scaffolding
- Bug report · Structured intake for bug reports and repro data
.github/ISSUE_TEMPLATE/bug_report.md - Issue config · Repository issue template configuration
.github/ISSUE_TEMPLATE/config.yml - Logo · Repository branding and documentation asset
External boundary
Upstream game, install tooling, and mod ecosystem
- Installer · Patch-based install/update utility referenced by the docs
- Patch file · Installer input used to build a Redux install
- Stock KSP2 · Required base game version and file layout
- Game stores · Steam, Epic Games Store, and Private Division install variants
- Support loop · Bug reports, logs, screenshots, saves, and vessel files back to maintainers
- Mod loader · Integrated mod loader and modding API boundary
Other components
- Redux repo · Public coordination layer for KSP2 Redux
Connections 17
- Redux repo → README: publishes · Repository centers on the public README
- Redux repo → Beta info: releases · Maintains beta channel metadata
- Redux repo → Stable info: releases · Maintains stable channel metadata
- Redux repo → Bug report: supports · Provides structured bug intake
- README → Roadmap: describes · Public docs define planned scope
- README → Contributing: guides · Public docs define collaboration rules
- README → Installer: documents · Explains patch-based install workflow
- README → Patch file: mentions · Installation is driven by patch artifacts
- Installer → Patch file: consumes · Applies patch to create a Redux install
- Installer → Stock KSP2: targets · Updates a stock KSP2 installation
- Stock KSP2 → Game stores: varies by · Install layout depends on game store source
- README → Support loop: routes users · Directs users to bug reporter and Discord support
- Support loop → Bug report: formats · Bug reports are structured through the template
- Bug report → Issue config: governed by · Issue template availability is controlled by config
- README → Mod loader: notes boundary · Documents transition to integrated mod loading
- Beta info → Installer: feeds · Beta channel metadata can drive update/install tooling
- Stable info → Installer: feeds · Stable channel metadata can drive update/install tooling