L Aerospace KSP/R&D Division

Welcome to the Research & Development Division from L Aerospace.

Please vest your blast helmet and suit: Area subject to Uncontrolled Landings and Rapid Unplanned Disassemblies, usually followed by Incredibly Fast Air and Heat Expansion With Debris events.


The following states the current status for the Supported KSP versions:

Internmediary KSP versions (1.3.0, 1.4.0, 1.4.1, 1.4.2, 1.4.4, 1.4.5, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0, 1.10.0) usually works, but are seldom tested against and so contraindicated. They are usually unstable anyway. :)

There are no plans to support any other KSP versions at the moment.

Understanding the Different Teams on the Repository

In order to prevent confusion and misunderstandings, and to make my life easier by grouping projects by support level, every project of mine is tied to a Team, and not to myself directly:

Development Process

For the sake of curiosity, here is how I handle things here:

  1. Development is done on a branch called dev (or dev/x.xx or even KSP/x.xx for KSP version specific development).
    1. Unofficial Forks usually has a merge branch. But don't take this as written on stone.
  2. New Releases are committed to the dev branch, and the binary package is also committed to the Archive branch for historical reference
  3. A tag in the formante RELEASE/x.y.z.b or PRERELEASE/x.y.z.b are issued on the dev branch.
  4. The whole shebang is uploaded to the remote repository.
  5. The Release is created and committed to the DEV branch.
    1. Binary is committed into the Archive branch
    2. A GitHub Release is created.
  6. When the thing is ready for the masses, the master is reset to the Release commit for broadcasting announces
    1. When applicable, the binary is uploaded to CurseForge and Spacedock.

This modus operandi prevents triggering any tools that monitors the .version file on the master before the thing is ready to be downloaded - this allow me to test things on different machines (from different users) without the need of a secondary download mechanism.


Send your questions to <support at lisias dot net> . You can also create issues on the Project's Repository page.

Add [KSP:<plugin_name>] to the subject, to prevent the automated filter system from filtering out your message to the trash bin. Thank you.