The linter we use already has some changes from the original (I gave it Python 3 support sometime around 2015, I think we did something about if constexpr, etc.), but it was never put under source control; we should put it on github (maybe as a fork of https://github.com/google/styleguide, or of https://github.com/cpplint/cpplint which seems to actually be maintained, maybe just on its own).

Get the following warning when building the documentation:

execroot/krpc/sphinx-build.py_script-env-3/lib/python3.6/site-packages/sphinx/application.py:402: RemovedInSphinx20Warning: app.info() is now deprecated. Use sphinx.util.logging instead.
  RemovedInSphinx20Warning)

Probably a sphinx build dependency that needs updated

I'm surprised this isn't a standard. But all these wikis floating about... Bollocks I say. If you're in KSP, you don't want to have to leave the game or minimize it or tab out to go hunt for it on a wiki.

I suggest adding verbose and well-written in-game documentation for the mod. Much like what FAR does. Some of the constant repeat explanations in the forum thread are the same tired questio

"Having a rocket warn you that it's almost out of lox isn't that useful when it's meant to be out of lox because you're burning it."

RO has a lot of different process configs for a lot of different life support setups that they have. One of them probably uses LOX as an input resource for life support, so there is a Resource config for LOX.

Kerbalism runs ALL resources on ALL vessels, regar

A page or pages containing the ASET props that have been converted. Ideally, a picture of one of them to help visualize it, plus a listing of the prop name + functionality + any other notes. Most likely, this will be organized by groups of props, and further organized by the style of the prop (eg, all mechanical toggle switches are together in the index, and the covered switches are grouped toge

Expected: Only Modules with minKSP < actual KSP Version < maxKSP are shown

Encountered (actual KSP Version is 1.3.1) :

Now we use a hardcoded default value - one for stack-mounted SFBs and one for radially mounted SFBs. These options should be user-definable.

Provide a warning to the user when a control flow with a body is likely accidentally closed

Examples:

  // will print here
  if true. {
      print("here").
  }

  // will print not possible
  until 10 > 20. {
      print("not possible").
  }

examples such as these are likely always unintentional. We can provide the lowest level diagnostic lev

With the addition of new config options in 1.3, the existing documentation for Custom Asteroids' config format has become too hard to navigate and read. It should be rewritten to be more user-friendly, including the following changes:

• content split across multiple pages instead of one very long page
• common data like distributions or expression syntax should be explicitly linked from descr

When going to launch a vehicle with kerbals that have low health and/or bad health conditions, display a warning (as a popup, on-screen message or with the message system).